OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-lcsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ndr accepted checklist check



Title: ndr_checlist_check
NDR Rule #
NDR Rule Text
25 June 2003 NDR 'ACCEPTED'
(from UBL Schema Naming and Design Rules Checklist_20030625.rtf as posted to ndr site)



[R1]
All UBL schema design rules MUST be based on the W3C XML Schema Recommendations: XML Schema Part 1: Structures and XML Schema Part 2: Datatypes.
ACCEPTED.
[R3]
Each dictionary entry name must define one and only one fully qualified path (FQP) for an element or attribute.
ACCEPTED.

CK: Seems to suggest that dictionary entry name use XPath, but then current usage of dictionary entry name doesn't do that.  So which is which?
[R4]
Names must be in the English language, using the primary English spellings provided in the Oxford English Dictionary.
ACCEPTED.
[R8]
Names must be in singular form unless the concept itself is plural (example: Goods).
ACCEPTED.

CK: Please define a measure of "clarity".
[R9]
Upper-camel-case (UCC) MUST be used for naming elements and types.
ACCEPTED.

Standards document that describes the Upper and Lower case, we need reference there.
[R10]
Lower-camel-case (LCC) MUST be used for naming attributes.
ACCEPTED.
[R27]
A common attribute should be declared as a global attribute only in cases where the attribute's meaning is identical no matter what element it is used on, and where the attribute is useful on every UBL element. This rule applies to both external (such as xml:lang) and UBL-specific global attributes.

Note that this rule allows for the creation of common attributes that are allowed on every element but are not globally declared, and that need documentation of their meaning in each XML environment in which they are used
ACCEPTED.
[R43]
The number scheme must be the major number is a non-negative integer and the minor number is a non-negative integer.
ACCEPTED AS IS.
[R46]
Each version Must have a namespace.
ACCEPTED.  Move up above namespace rules.  Leave that to the discretion of the editor.
[R47]
Each minor version must be given a separate namespace.
ACCEPTED.  Same as above.
[R48]
A published namespace MUST never be changed. 
ACCEPTED.
[R49]
When the URN changes to reflect a change in the namespace, this change will be reflected in the version number, either major or minor.
ACCEPTED.
[R50]
Minor versioning must be limited to declaring new optional constructs, extending existing constructs and refinements of an optional nature.
ACCEPTED.
[R51]
Changes in minor versions must not break semantic compatibility with prior versions.
ACCEPTED.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]