diff --git a/specification/archSpec/archSpec-technicalContent.ditamap b/specification/archSpec/archSpec-technicalContent.ditamap index 02305a3f..6c037690 100644 --- a/specification/archSpec/archSpec-technicalContent.ditamap +++ b/specification/archSpec/archSpec-technicalContent.ditamap @@ -6,8 +6,5 @@ - - - diff --git a/specification/archSpec/technicalContent/technical-content-domains.dita b/specification/archSpec/technicalContent/technical-content-domains.dita index 2a9ea24a..cfc0b9b0 100644 --- a/specification/archSpec/technicalContent/technical-content-domains.dita +++ b/specification/archSpec/technicalContent/technical-content-domains.dita @@ -3,8 +3,8 @@ Domain specializations This section contains information about the technical content domains, including a - general overview and more specific information about the xNAL, release management, equation, and + general overview and more specific information about the release management, equation, and MathML domains.Should this be more comprehensive, and not just limited to those three or four domains? Or - are the others like "software" too obvious to require a topic? + >Should this be more comprehensive, and not just limited to those domains? Or are the others + like "software" too obvious to require a topic? diff --git a/specification/archSpec/technicalContent/xNALDomain.dita b/specification/archSpec/technicalContent/xNALDomain.dita deleted file mode 100644 index eec284ad..00000000 --- a/specification/archSpec/technicalContent/xNALDomain.dita +++ /dev/null @@ -1,36 +0,0 @@ - - - - xNAL domain - The DITA xNAL domain specialization defines a number of metadata elements that are - useful in representing personal/organizational names and addresses. The metadata can be used - to identify authors and content owners. The OASIS xNAL Standard (extensible Name and Address - Language) was selected to represent close mappings from the DITA bookmap metadata content - model to an existing standard. xNAL is included in the Bookmap document type distributed - with this version of DITA. - -

The OASIS Customer Information Quality (CIQ) standard for global-customer information - management contains the definition of the OASIS - extensible Name and Address Language (xNAL) metadata elements. Version 2 of - the standard states:

- -

The objective of xNAL is to describe a common structure for Personal/Organization Names and - Addresses that would enable any applications that want to represent customer names - and addresses in a common standard format. The applications could be CRM/e-CRM, - Customer Information Systems, Data Quality (Parsing, Matching, Validation, - Verification, etc.), Customer Data Warehouses, Postal services, etc.

-

However, any party for its own purposes and applications can use xNAL grammar or parts of - it.

- -

The DITA xNAL specialization is based on the OASIS extensible Name and Address Language - metadata elements. Due to differences between the two processing architectures, the DITA - xNAL domain does not incorporate all of the definitions from the OASIS xNAL standard - directly. Instead, there is a transformational equivalence between the DITA and OASIS - xNAL definitions for names and addresses. This equivalence enables XML-aware tools in - workflow systems to capture and manipulate names and addresses in a standard manner.

-

The xNAL domain is available for use in the bookmap document type. It - can be included in any DITA document types that require metadata for names and - addresses.

- - diff --git a/specification/archSpec/technicalContent/xnaldetails.dita b/specification/archSpec/technicalContent/xnaldetails.dita deleted file mode 100644 index 973e2759..00000000 --- a/specification/archSpec/technicalContent/xnaldetails.dita +++ /dev/null @@ -1,254 +0,0 @@ - - - - xNAL usage guidelines - Extended information and usage examples for DITA bookmap metadata - elements associated with OASIS xNAL Standard (extensible Name and Address - Language). - -

DITA bookmaps use a set of - elements associated with a subset of the - OASIS extensible - Name and Address Language (xNAL) specification (Version 2) to denote - name and address information related to persons and organizations.

-

While the elements share element names, and the - expectation is that content written using this type of metadata is be straightforward to transform, the element name - pairs do not share content models. The difference in content models reflects the - different purposes of the two standards. The purpose of the name and address elements in - DITA is to identify persons or organizations associated with the creation of a document; - the purpose of the name and address elements in xNAL is to support customer resource - management.

-

The examples shown after the - table provide sample tagging methods for name and address information, using - the DITA elements associated with xNAL.

-
- DITA elements associated with xNAL elements -

The set of bookmap elements - associated with elements from the - OASIS extensible - Name and Address Language (xNAL) standard are listed in the table below.

- - DITA elements associated with xNAL elements - - - - addressdetails - - honorific - - otherinfo - - - - administrativearea - - lastname - - person - - - - authorinformation - - locality - - personinfo - - - - contactnumber - - localityname - - personname - - - - contactnumbers - - middlename - - postalcode - - - - country - - namedetails - - thoroughfare - - - - emailaddress - - organization - - url - - - - emailaddresses - - organizationinfo - - urls - - - - firstname - - organizationname - - - - - generationidentifier - - organizationnamedetails - - - - - -
-
- - Example 1: Tagging personal information in DITA -

This example shows a way to - tag the following personal name and description.

- Mr. Ram V. Kumar Jr. -Chief Technologist -MSI Business Solutions - <authorinformation> - <personinfo> - <namedetails> - <personname> - <honorific>Mr.</honorific> - <firstname>Ram</firstname> - <middlename>V.</middlename> - <lastname>Kumar</lastname> - <generationidentifier>Jr.</generationidentifier> - <otherinfo>Chief Technologist</otherinfo> - </personname> - </namedetails> - </personinfo> - <organizationinfo> - <namedetails> - <organizationnamedetails> - <organizationname>MSI Business Solutions</organizationname> - </organizationnamedetails> - </namedetails> - </organizationinfo> -</authorinformation> - - - Example 2: Tagging address information in DITA -

This example shows a way to - tag the following address.

- 23 Archer St. -Chatsworth -NSW 2067 -Australia - <addressdetails> - <thoroughfare>123 Archer St.</thoroughfare> - <locality> - <localityname>Chatsworth</localityname> - <postalcode>2067</postalcode> - </locality> - <administrativearea>NSW</administrativearea> - <country>Australia</country> -</addressdetails> - - - - Example 3: Tagging complex name and address information in - DITA -

This example shows two ways to - tag a fairly complex collection of personal, organizational, and address - information.

- Mr. Samuel L. Johnson Jr. -Chief Technologist -c/o XYZ Corporation -52 New Main St. -Carrboro, NC 27510 USA -email: johnson@example.com -phone: 919-555-7987 -

This method tags all the - organizational information as associated with the identified person.

- <personinfo> - <namedetails> - <personname> - <firstname>Samuel</firstname> - <middlename>L.</middlename> - <lastname>Johnson</lastname> - <generationidentifier>Jr.</generationidentifier> - <otherinfo>Chief Technologist</otherinfo> - <otherinfo>c/o XYZ Corporation </otherinfo> - </personname> - </namedetails> - <addressdetails> - <thoroughfare>52 New Main St.</thoroughfare> - <locality> - <localityname>Carrboro</localityname> - <postalcode>27510</postalcode> - </locality> - <administrativearea>NC</administrativearea> - <country>USA</country> - </addressdetails> - <contactnumbers> - <contactnumber>919-555-7987</contactnumber> - </contactnumbers> - <emailaddresses> - <emailaddress>johnson@example.com</emailaddress> - </emailaddresses> -</personinfo> -

The following method separates - the person and organization information. It might be used if it were necessary - to associate address information with organizations rather than persons.

- <authorinformation> - <personinfo> - <namedetails> - <personname> - <firstname>Samuel</firstname> - <middlename>L.</middlename> - <lastname>Johnson</lastname> - <generationidentifier>Jr.</generationidentifier> - <otherinfo>Chief Technologist</otherinfo> - </personname> - </namedetails> - <contactnumbers> - <contactnumber>919-555-7987</contactnumber> - </contactnumbers> - <emailaddresses> - <emailaddress>johnson@example.com</emailaddress> - </emailaddresses> - </personinfo> - <organizationinfo> - <namedetails> - <organizationnamedetails> - <organizationname>XYZ Corporation</organizationname> - <otherinfo>c/o </otherinfo> - </organizationnamedetails> - </namedetails> - <addressdetails> - <thoroughfare>52 New Main St.</thoroughfare> - <locality> - <localityname>Carrboro</localityname> - <postalcode>27510</postalcode> - </locality> - <administrativearea>NC</administrativearea> - <country>USA</country> - </addressdetails> - </organizationinfo> -</authorinformation> - - -