MHonArc v2.5.0b2 -->
ubl message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: AW: [ubl] Procurement Models for UBL 2.0
Tim,
when I read the May paper, I did not see, that there is any rule, which
says, that cross references are allowed. Thus for me a concept, where models
are referencing to each other (ABIE A in Model 1 bases on ABIE B in model 2
and ABIE C in Model 2 bases on ABIE D in model 1) is not the desirable
design concept. And your comment (Financial Institution etc) further below
seems to support that.
Is this correct?
But at the very end of your email you said, that "it would be safest to
assume that any ABIE
can reference any other ABIE whever it appears in the UBL spreadsheet
models". Personally I assume, that tools in general will put all
spreadsheets together and import them into data modelling software. For
these approaches the safest way is not a problem and this is, what I could
do easily with GEFEG FX.
But this is a way I must disagree with. The only reason to accept the
separation of the UBL Library data is a partially separated maintenance and
further development of the different models. They have different owners and
sub committees and can be updated separately. Considering the lessons
learned from established industry standardization organizations this is of
real value. But then a cross reference concept will make it very difficult
to maintain and further develop the sub models.
In order to minimize the described negative impacts of he separation of the
UBL library into different sub's, I hereby request, that the rule should be
stated, that the common library should never refer to higher specialized
libraries and that there aren't any mutual references between sub models.
Furthermore you wrote "I suspect this
needs correction and that the "Branch" actually belongs in procurement as
well." Shall I read this that there would be two identical 'Branch' entries:
one in 'common' and a second in 'procurement'?
thanks
Michael
-----Urspr�ngliche Nachricht-----
Von: Tim McGrath [mailto:tmcgrath@portcomm.com.au]
Gesendet: Dienstag, 13. September 2005 15:45
An: swebb@gefeg.com
Cc: ubl@lists.oasis-open.org; ubl-psc@lists.oasis-open.org; Mark Leitch;
Jostein Fr�myr
Betreff: Re: [ubl] Procurement Models for UBL 2.0
I think in the interests of time it best if I answer now. if i am in
error then soemone can correct me.
In July the UBL TC agreed to the Model Architecture for UBL 2.0. there
is no plan (and we are too far down the path) to change this.
The minutes of Pacific UBL TC call 11|12 July 2005 state:
> The group continued the discussion of Reusable noted in the
> Atlantic TC minutes. It appears that earlier concerns
> regarding the proposal would not apply if the changes were
> restricted to the structure of the spreadsheets.
>
> AGREED that we will divide the spreadsheets as proposed by
> Saito-san using the terminology proposed by JonB with the
> understanding that we will adhere to CCTS, populate the
> "context" columns in the spreadsheets, and not change the
> structure of the schemas.
>
> AGREED that we will use the term "context-specific
> libraries" in generic references to the Transportation
> Library and the Procurement Library.
>
> We understand from Saito-san's proposal that any element
> used in more than one context will always be put in the
> (non-context-specific) Common Library (though not all
> elements in the Common Library will necessarily be used in
> more than one context-specific library).
>
i should also point out that we still have to refine the actual contents
of these libraries - but these are ongoing (and continuous) refinements.
for example, i would not expect many common library ABIEs to associate
with context-specific ABIEs (such as in the procurement library). a
case in point is the problem you noted with "Branch" in common
associating to "Financial Institution" in procurement. I suspect this
needs correction and that the "Branch" actully belongs in procurement as
well.
from an EDIFIX point of view, it would be safest to assume that any ABIE
can reference any other ABIE whever it appears in the UBL spreadsheet
models.
Sylvia Webb wrote:
>Peter,
>
>Please confirm that the methodology and techniques described in the UBL v2
>Model Architecture document are what should be used for UBL 2.0.
>Specifically, I am referring to recommendations in this document that
ABIE's
>exist in the Common Library, Procurement Library, as well as other
libraries
>like Transport that will be created. Additionally, please confirm that
>ABIE's in the Common library can refer to more restricted ABIE's in the
>Procurement Library.
>
>Lastly, please confirm that this methodology will remain stable for the
>remainder of UBL 2.0 development.
>
>Thanks,
>Sylvia
>
>
>
>---------------------------------------------------------------------
>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
>
>
>
>
--
regards
tim mcgrath
phone: +618 93352228
postal: po box 1289 fremantle western australia 6160
DOCUMENT ENGINEERING: Analyzing and Designing Documents for Business
Informatics and Web Services
http://mitpress.mit.edu/catalog/item/default.asp?sid=632C40AB-4E94-4930-A94E
-22FF8CA5641F&ttype=2&tid=10476
---------------------------------------------------------------------
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
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]