Subject: Re: [ubl-lcsc] [code] possible amendment to codelist strawmanschemas
Chee-Kai If there were the requirement to amend the Core Component Types (e.g. by adding defaults) then creating copies in a separate namespace/schema and referencing that namespace instead from the codelist schemas would probably work. Hopefully it would be OK to use extension or restriction within the CCT-copy schema so that the *actual* CCT's are still referenced. However, there would be the need, I think, to avoid circular references by still *not* importing the codelist-schemas into the normative CoreComponent schemas but instead, as I have done, import them into the Reusable schema and document schemas. All the best Steve >>> Chin Chee-Kai <email@example.com> 05/09/03 09:09:06 >>> Just a note on the structural arrangement of codelists with respect to other schemas within UBL. On Fri, 5 Sep 2003, Stephen Green wrote: >>This of course requires that the CoreComponentTypes schema be >>imported and the namespace referenced. I suspect codelist schemas will have to be as self-atomic as possible without inclusion of what might potentially be their "including" schemas. When codelists are completed, some CoreComponentTypes may utilize some codelists in turn, leading to circular inclusion if codelist schemas themselves include CoreComponentTypes (for need of supporting type definition that don't use codelists). Even if use of codelists within CoreComponentTypes is not immediately obvious, structurally it would leave room for such possibility if there's no inclusion dependency required of codelist schemas on CoreComponentTypes, whereas the converse will close such possibility for certain. It's not difficult to separate the dependencies by duplicating some structures that are needed by codelist schemas to put them into a supporting file called, say, CodeListTypes on its own namespace, to define for use by codelist schemas exclusively. Best Regards, Chin Chee-Kai SoftML Tel: +65-6820-2979 Fax: +65-6743-7875 Email: cheekai@SoftML.Net http://SoftML.Net/ To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl-lcsc/members/leave_workgroup.php.