Title: AW: [ubl] Re: Next Version & Customization
What
does 'We have identified ...' mean?
Which
officially, approved TC document mentions these three ways, binds them
together and describes the ways or links to other documents describing the
ways? Is this document informative or normative?
Which
document describes the concept, i.e. not only the rules. Especially how these
ways constitute advantages for users, which current legacy XML languages do not
offer.
Michael Dill
-----Ursprüngliche Nachricht-----
Von:
[mailto:]
Gesendet: Samstag, 9. April 2005
01:44
An: ;
Betreff: RE: [ubl] Re: Next Version &
Customization
- As far as I understand, there is not yet a concept telling
people, how to
extend, restrict, specify UBL data.
We have identified three ways:
1) come to UBL and change the model which will then be reflected
in the schema
2) extend/restrict following our customization guidelines to be
considered UBL conformant
3) extend/restrict any way you choose but you are not UBL
conformant
- Also I'm not aware of any decision whether this concept
starts on a model
level or on a schema level or both.
See above. My understanding all along has been that the
customization (and the use of derivation by extension and restriction) is for
customizers - not UBL
Mark
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates
this mail. You may a link to this group and all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
