spacerHomespacer|spacernav_bug User's Guidespacer|spacerFAQspacer|spacerContact Usspacer|spacerSuggestion Boxspacer
arrow_left arrow_right
 
  1.   Introduction
  2. arrow_right Cengage Learning Coding Requirements
 2.1   CenDoc Namespace Prefix
 2.2   Character Encoding
 2.3   Identifier Values
 3.   Structural Overview
 4.   Coding Requirements
 4.7.7.3    <cl:quote>
 

2. Cengage Learning Coding Requirements

The purpose of these standards is to supplement the CenDoc Tag Documentation with specific guidance on the use of some key elements. If the application of these standards is unclear, or any ambiguous situations occur in the tagging or XML conversion process, seek guidance from the Cengage Learning Content Project Manager or full-service Production Project Manager assigned to the project.

Cengage Learning uses the CenDoc schema for content creation and the ability to effectively mange content. It is composed of modules, collectively known as CenDoc Schema, which can be used to create compatible subset schemas.

2.1 CenDoc Namespace Prefix
All CenDoc elements have a namespace prefix of "cl:" which should then point to the the “http://xml.cengage-learning.com/cendoc -core”namespace. Namespace prefixes are now shown in coding examples.
2.2 Character Encoding
Characters, such as copyright symbols, m-dashes and similar, should be captured using their UTF-8 values and not the ISO ones. For example, the copyright symbol should be entered as © and not as ©.
2.3 Identifier values
1.  An “identifier” attribute value is required for the following elements:
<cl:chapter><cl:key-term-entry><cl:reading-passage>
<cl:chapter><cl:key-term-entry><cl:reading-passage>
<cl:chapter><cl:key-term-entry><cl:reading-passage>
<cl:chapter><cl:key-term-entry><cl:reading-passage>
<cl:chapter><cl:key-term-entry><cl:reading-passage>
<cl:chapter><cl:key-term-entry><cl:reading-passage>
<cl:chapter><cl:key-term-entry><cl:reading-passage>
<cl:chapter><cl:key-term-entry><cl:reading-passage>
2. Values for the “identifier” attribute should conform to format of the XML attribute type “ID”. See Extensible Markup Language (XML) 1.0 (Third Edition), Section 3.3.1 "Attribute Types" (http://www.w3.org/TR/2004/REC-xml-20040204/ - sec-attribute-types)
3. The "identifier" attribute values should be unique within the <cl:doc> element structure.
4. The "identifier" attributes is available on all element but is optional in most cases.
5. There is no current identifier value format convention other than that specified in item 2 above.


© Cengage Learning, Inc., 2008
Hosted by www.Geocities.ws

1