OASIS Open Mailing List Archives  ·  All Lists  ·  ubl-ndrsc  ·  2002-05

ubl-ndrsc — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

RE: [ubl-ndrsc] [Fwd: FW: [oagis-users] UserArea Extensions for Version 8.0]


 MHonArc v2.5.2 -->
















ubl-ndrsc message

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


Subject: RE: [ubl-ndrsc] [Fwd: FW: [oagis-users] UserArea Extensions for Version 8.0]


<polemic>
I've always thought that open content models are a crutch to avoid difficult
design decisions. With correct information modeling, it shouldn't be such a
big problem to include information from other namespaces into a document.
However, there should be some commonly understood base semantics referenced
in the core document and not just a wooly "any" tag (purposesly using gobs
of loaded terms).

In other words, say we have a "unit" tag somewhere in UBL, and we want to be
able to stick in other vocabularies that represent units of measure. Either
we should find out if there is an appropriate base type for this (unlikely),
or define our own and mandate that other vocabularies should be adapted
accordingly. After all, this is supposed to be a *universal* business
language. Admittedly, this will be a challenge and it will take time for
people to adapt, but this is why we have a Liaison SC working hard on
coordinating with other groups. Just sticking in a bunch of "any" tags to
make the vocabularies entirely flexible totally contradicts the idea of
defining schemas for valid documents in the first place.
</polemic>

Matt

> 

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]