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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

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


Subject: Re: [ubl] CodeList in document-id (was: CD2 sanity check)


Hi Jon,

I think your example points out another problem.  I hadn't looked at NM6 
all that closely until now.  Does NM6 necessarily follow from NM4 and 
NM5?  Because if we follow the naming as it is in NM6, 'subtype' will 
always be 'xsd', and we would have to have all schemas under a directory 
names 'xsd', since there is no space in the NM6 pathname for the 
subdirectories we now use to organize the schemas: 'common', 'codelist', 
and 'maindoc'.

Here is an example from the AcknowledgementResponseCode' schema:

<xsd:import 
namespace="urn:oasis:names:specification:ubl:schema:xsd:CoreComponentParameters-1.0" 
schemaLocation="../common/UBL-CoreComponentParameters-1.0.xsd"/>

If we followed NM6 then we will also need to redo the package structure 
to remove the subdirectories 'common', 'codelist', and 'maindoc', and 
leave all schemas in the 'xsd' directory only.

So my question is whether there is a benefit in the specific pathname 
being specified by NM6 over the schemaLocation we currently use?  Is 
there some reason for us to change the package current structure to 
match NM6?  Does NM6 add more value than the cost of adhering to it in 
it's current form?  Is it the package that should change, or the rule? 
 NM6 says 'the UBL modules must be hosted ...'  Is there any reason for 
NM6 to specify the pathname beyond the word 'schema' (ie. past 
http://www.oasis-open.org/committees/ubl/schema/)?

-A

jon.bosak@sun.com wrote:

>[stephen_green@seventhproject.co.uk:]
>
>| This would require changes to the Schemas (the imports of the
>| codelist Schemas) so I'm not sure it would be worth such changes
>| since it may affect others downstream.
>
>Yeah, well, I'm sorry, but it's clear to me now that our final
>naming and design rules require it.  Here are our rules:
>
>   [NMS4] The namespace names for UBL Schemas holding committee
>   draft status MUST be of the form:
>
>      urn:oasis:names:tc:ubl:schema:<subtype>:<document-id>
>
>   [NMS5] The namespace names for UBL Schemas holding OASIS
>   Standard status MUST be of the form:
>
>      urn:oasis:names:specification:ubl:schema:<subtype>:<document-id> 
>
>   [NMS6] UBL Schema modules MUST be hosted under the UBL
>   committee directory:
>
>      http://www.oasis-open.org/committees/ubl/schema/<subtype>/UBL-<document-id>.<filetype>
>
>Now look at Anne's example:
>
>   <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CurrencyCode-1.0" schemaLocation="../codelist/UBL-CodeList-CurrencyCode-1.0.xsd"/>
>
>Clearly by NMS5 the document-id in the namespace attribute is
>"CurrencyCode-1.0", but just as clearly by NMS6 the document-id in
>the schemaLocation attribute is "CodeList-CurrencyCode-1.0".  One
>of these is wrong.
>
>Jon
>
>
>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/members/leave_workgroup.php.
>
>  
>




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