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] Minutes of Pacific UBL TC call 16|17 May 2005

I think my findings
agree pretty much with Mark's position.

The changes I prototyped which have the least impact on instances
(allowing model/cc changes for minor versions) have very little
that is essentially different from the existing schema design.
The changes I've tried out are mainly to naming and could be omitted.
There is more need to revise things (a little) due to ATG2 alignment
rather than the newly proposed model architecture (e.g. singular
forms in names rather than plurals such as '...Component' rather than

All the best


----- Original Message ----- 
From: <MCRAWFORD@lmi.org>
To: <ubl@lists.oasis-open.org>
Sent: Monday, May 23, 2005 3:52 PM
Subject: RE: [ubl] Minutes of Pacific UBL TC call 16|17 May 2005

In the Pacific Call minutes, Jon wrote:

>     - The Reusables are continuing to grow with things that are
>       actually specific to a given context. It is proposed that we
>       distinguish "common" BIEs (that is, used by more than one
>       doc type) from "core" BIEs (that is, used by many doc types)
>       from BIEs that are used in only one doc type. JP is working
>       up a proposal for this. Some of us are skeptical that this
>       distinction can be made cleanly. Some believe that such a
>       change will make it easier to align with CEFACT CC. Clearly,
>       any change in this direction will mean a change to the NDRs.

I think that changing the library model spreadsheet however LC wants to
do it can be done with no changes to the schema.  The proposed changes
to the library modeling are no different that what we already do in
CEFACT - individual spreadsheets for individual projects.  We still have
common reusable schema modules however that cut across all functional

We need to be careful however in distinguishing our BIEs.  There is no
concept in CCTS of "common" or "core" BIEs.  BIEs are actually specific
to a particular context albeit reusable by many different contexts.  A
pure procurement context Address can still be used by anyone who
subscribes to the actual content model and restrictions of the BIE.
Just because it was created for procurement, doesn't mean it can't and
shouldn't be used elsewhere.


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

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