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

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [ebxml-dev] ebXML core components derivation by restriction

Ron,

<Ron>If they concur, then perhaps they will support a change to the CCTS
that representatives of the aerospace industry suggested a few years ago
while the CCTS was in its earlier draft form. The recommended change
would not mandate but simply allow for a "permanent" structured ID to be
assigned rather than the current "temporary" 6 digit ID.
The current wording in Section 5.3.1 states 
"Step 6. Assign a Temporary Identifier to the new item in the form of a
6 digit alphanumeric string, chosen at the discretion of the user."
The suggested new wording in Section 5.3.1 would state
"Step 6. Assign an identifier to the new item in the form of a
alphanumeric string, chosen at the discretion of the user."</Ron>

Please submit this change request. It is not TBG17 who decides upon it,
but the CCTS team.
The UID identifier is meant to be a pure identifier. Some even want to
change it into a UUID (the lengthy numbers you find in e.g. MS-Windows
registries). It is temporary upon submission because it may change after
harmonising (when the submitted CC may have been combined with other
submissions). I think it would already serve your goal if a UDEF GUID
would be added in the registries that store Core Components.

Fred

 

<<attachment: winmail.dat>>



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