Draft of code list paper, revised after face to face

[Burnsmarty@aol.com]

All,

 

I have revised the code list design document based on the results of the face to face. The specific goal of this exercise was to facilitate implementation of schemas based on the results of the face to face. Specifically, the model was modified to explicitly show how to use an extendable code list as one or more attributes of a component element. Tests were done to verify that the "choice 4" solution discussed at the meeting (see Ken Holman emails) would work and be parsable by at least one XML schema parser/validator -- XMLSpy 2004).

 

Specifically I have done the following:

 

1) Added additional new requirements

2) Appologies -- did not yet integrate Eve's valuable comments on requirements from last week.

3) Added explicit support for code values as attribute of component type. Verified that qualification of attribute can be independent of containing element, opening way for the "solution 4" approach in UBL <future>.

4) Qualified requirements as to (FUTURE) when section 4 does not yet support them by agreement at the face to face.

 

The attached zip file contains two versions. One normal version and one with revisions showing from the previous draft. Don't have pdf generator with me (I'm on the road). Will try to call in to conference on Wednesday to discuss.

 

All the best,

Marty

 

 

wd-ublclsc-codelist-20040229.zip