[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep] [TN Proposal] Mapping Business Information Models toebXMLRegistryInformationModel (Was: [regrep] UN/CEFACT-ICG adoptsfreebXMLRegistry)
Duane, The bottom line for me is that context is not stored with the CCs themselves - but externally referencing too the CCs. In math you store the equation - not all the uses of the equation itself. Same in chess - you store the combination fragments - not every possible game that could be played using those fragments. That is the way the BPSS is setup - to provide the context instance - that then acts on what CCs are in the business transactions that get used during the process execution. With jCAM engine - you pass those context values into it - and ask it to evaluate the information exchange based on those. So I do not see it as CEFACTS job to put implace all possible context instances - those will be carried externally in the business application BPSSs, the CPAs, CAM templates and such. DW. Duane Nickull wrote: > Joseph: > > It is stated in this highlighted implementation note. Read the > document::page 27: > > "Implementation Note: A problem does exist however with respect to > registry classification scheme bloating. If all the CCTS context > classifications are used for the purpose of aiding modelers in > locating contextually specific business information entities, the > registry classification scheme would be unmanageably large. " > > It is documented ;-) > > The problem is that I have no answer how to solve this. Since > UN/CEFACT CCWG has not yet decided what enumerated list sets to use > for declarations of context, the exact magnitude of the problem is an > unknown. If we can somehow incorporate ranges, it may help. Ranges > are NOT accounted for in my solution. I do not have any ideas how to > do this and will not try to solve it before CCWG decides on what > context qualifiers it will use. > > Duane > Chiusano Joseph wrote: > >> Duane, >> >> I *always* want to help, and I *have* read the document. The problem is >> that you mentioned the following: >> >> <Quote> >> The set of contexts is also another huge problem. There may be 8-10 >> million. >> </Quote> >> >> What threw me off is that there is no mention in the document of >> anything in the *millions* (try a string search and you will see). Now >> that you've made your point clearer below, I understand. >> >> Joe >> >> >> >>> Chiusano Joseph wrote: >>> >>> >>> >>>> If you mean that each French-speaking country and region would have to >>>> be involved in an association, this can perhaps be alleviated by >>>> using a >>>> hierarchy for Geopolitical Context that groups accordingly. >>>> >>>> >>> >>> No. It means what the document states. Each context declaration is >>> made up of up to eight context values or ranges. There is a BIG >>> problem >>> to sort out how to declare this and link the two together. Please read >>> the document. >>> >>> >>> >>>> In CCTS >>>> 2.01, the example on p.60 states "If the Geopolitical Context has a >>>> value of Anywhere in the European Union,..." in which case there >>>> can be >>>> a single association rather than an association to each EU country. >>>> Duane, were you still taking this into account in your example above? >>>> >>>> >>>> >>> >>> Yes - again, please read the document. This is all clearly explained >>> within. >>> >>> >>> >>>> That is, were you assuming that groupings would exist? >>>> >>>> >>> >>> Yes- that is CCTS methodology. Read the CCTS document. Business >>> Context = 8 * (unique( [context category and value]). That may have to >>> e reviewed given that ranges may apply. >>> >>> >>> >>>> Or were you >>>> assuming that they would not exist, and that an association would need >>>> to be made to each country (in this case)? >>>> >>>> >>>> >>> >>> No - please read the document. This is way off base. >>> >>> Duane >>> >>> >>> >>>> Cheers, >>>> Joe >>>> >>>> >>>> >>>> >>>> >>>>> These are just a few of the potential problems. >>>>> >>>>> Duane >>>>> >>>>> To unsubscribe from this mailing list (and be removed from the >>>>> roster of the OASIS TC), go to >>>>> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php. >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> -- >>> *********** >>> Senior Standards Strategist - Adobe Systems, Inc. - >>> http://www.adobe.com >>> Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/ >>> Chair - OASIS eb SOA TC - >>> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebsoa >>> *********** >>> >>> To unsubscribe from this mailing list (and be removed from the >>> roster of the OASIS TC), go to >>> http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php. >>> >>> >> >> >> >> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]