[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl] CodeList Conundra
All,I am trying to help normalize the code list subcommittee draft to match the evolving schemas / models. Since I can assert that the contents of these (schemas models) relative to the code list paper were source material and no invention was intentionally done by the code list committee, differences have to do with my faulty tracking of the source material.In addition, the code list representation in XMLSchema requires that for each code list there be defined a ComplexType, a SimpleType, and Attribute, a global abtract element, and a global element. I imagine that these components would be described in the abstract in one of the more abstract UBL modules and used in specific code lists.Please provide me with guidance as to the following:1) What is the normative data model for code lists desired by UBL is it the "model spreadsheet" or the models in the schema drafts?
this is the item for discussion on the co-ordination all. it appears that your proposed architecture has been merged with the old code list mechanism with the new and created some redundnacy which we need to resolve. to put this another way, becasue we did not follow CCT in the original schemas or code list implementation we devised a work around module structure. we don't think we need this anymore . this should simplify the whole issue and answer this question.2) Where is the base class of a code list schema to appear --UBL-CoreComponentTypes-1.0-draft-7.1.xsd Code and CodeType? or in a new Code List Schema module, or, in UBL-CodeListUnspecializedDatatype-1.0-draft-7.1.xsd?
again, stephen is suggesting two options. have code content in the specialised data type schema or have them in seperate schemas. there are arguments for both cases. we need to decide on this today.3) Where are instances of actual code lists to appear? Is this the subdirectory Stephen is aiming for?
you almost answer your own question. the Amount Currency. Identifier is not a code, it is an identifier. If it were a code it would be aclled Amount Currency. Code. UBL did not make these decisions it is given by the CCTS.4) Why don't core component types that use code lists as an attribute use the code list schemas e.g. Amount.currencyID?
two parts to this..5) Why don't the core schemas that have standardized attributes use UBL-CoreComponentParameters-1.0-draft-7.1.xsd
surely this also brings into play versions of the same code list. in fact, i thought that was how we proposed to establish modnamver.6) Is it intended that all code lists have the same name within their namespace? It might be helpful to have a currencyCode named currencyCode where-ever it is used and not require its namespace to decode what its for (of course you need the namespace to uniquely qualify it).
certainly, it does feel like we are not yet able to document the code list representation. i suspect this is because we haven't yet got a working implementation. in other words, we need to protoype this rather than design on paper. What Stephen has posted today is part of this protoyping. Rather than try and keep your document normalized it may be better use of our resources to work together on constructing this protoype and then document what have built.I am ready to correct the code list document accordingly and provide examples of code list schema that meet the requirements of the code list committee model as soon as I can understand what to normalize against and which schemas to edit.
Thanks for helping a newbie,Marty
-- regards tim mcgrath phone: +618 93352228 postal: po box 1289 fremantle western australia 6160
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]