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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-dev message

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


Subject: RE: [ubl-dev] Customising and versioning


Correction to first sentence
 "(though with a bearing on
any subsequent minor versioning of a minor version so derived)"
should read
" (though with a bearing on
any subsequent customization of a minor version so derived)"


>>> "Stephen Green" <stephen_green@bristol-city.gov.uk> 08/09/06 10:02:39 >>>
Hi Mark

I'd stress again that I'm talking minor versioning here rather
than customization in general (though with a bearing on
any subsequent minor versioning of a minor version so derived).
The problem is that the namespace is supposed to stay the same.
This is what seems to me to hinder use of substitution groups
for it, otherwise you get a nameclash. You can't base a
substitution group on itself :-)

You could use substitution groups fine for minor versioning
in UBL 2 prd1 as the namespace for the minor version was
different from the previous version so an Order say could
use substitutionGroup="po:Order" where po is the prefix
of an imported Order schema with the previous version
namespace. Changing the namespace so it only has the
major version identifier removes the possibility of import.
You could say to me, yes but you can use substitution
groups with a redefine (thanks again to Joe for pointing
this out to me months back). 

The problem then is you can't say;
<xsd:element name="Order" substitutionGroup="Order"/>
because then there are two elements both called Order
in the same namespace. Plus you can't base a substitution
group on itself. Change the name of the element??
Mmm... Hardly minor versioning.

All the best

Steve

>>> "Crawford, Mark" <mark.crawford@sap.com> 07/09/06 18:09:23 >>>
> For instance,
> not knowing what mechanisms will be used but knowing that
> there is a barrier to using substitution groups for it in
> UBL 2, leads to the conclusion that one might have to think
> how to customize a redefined schema and if this is indeed
> a major problem, one might wish to feed this back to UBL
> as the NDR 2.0 goes to public review (perhaps shortly
> from the look of the recent minutes). 

Could you be more specific - what barriers are there to substitution
groups in UBL2?

---------------------------------------------------------------------
To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org 
For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org 



---------------------------------------------------------------------
To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org 
For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org 




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