RE: [regrep] BIEs re-visited.

["Damodaran, Suresh" <Suresh_Damodaran@stercomm.com>]

David,

Perhaps you can shed some light on BIE catalogs also.
Who creates them and who will populate them, and how.
The CC catalog, is "owned" by CC standard, and possibly
stored in Registry. Can we say the same about BIE catalog?

Wouldn't these catalogs be the natural "containers" for storing
Core Components and BIEs in Registry?

Thanks,

-Suresh



-----Original Message-----
From: David RR Webber - XMLGlobal [mailto:Gnosis_@compuserve.com]
Sent: Friday, May 17, 2002 8:52 AM
To: OASIS Registry List
Subject: [regrep] BIEs re-visited.


Team,

Just wanted to share some points on BIEs here, as it appears
there has been some significant clarifications on what BIEs 
are and their role in the ebXML stack.

Most particularly the request to store BIEs in the registry now
makes sense, as it is clear they are static instances.

First however - I want to offer up an explanation of what a BIE is!

"BIE - Business Information Entity - a re-usable collection of
  core components with optionally associated passive context".

So an example is:

BIE within a Purchase Order I may have a BIE of Item.Details
which comprises of:

Part.Number, Part.Description,  Part.Weight,
Shipping.Temperature, Unit.Cost, Handling.Care, Choice.Colour,
Discount.Code.

in amongst the all the rest fo the PO details, and the context 
may be Walmart and Household Paint.

This contrasts to a Core Component
such as Address - where the child details are specific to Address 
and the context is undefined.

There's probably some grey area between Aggregate Core Components
and BIEs with no context - but I'm not sweating that detail here!

Contrast this to an AssemblyDoc - which can reference and include 
Core Components, and BIEs and also provides syntax specific 
structural information, and also provides active context and 
application content referencing.   An AssmeblyDoc gets stored as-is,
with an Association link to one or more BPSS items as needed.

However - from the Registry standpoint - the question is - do we need
anything extra here in the RIM to store these and allow people to 
search and discover them?

My first inclination is to say "No" - that Package, and Association methods
that we have already can handle the needs here, along with the 
query tools.

Once the CCR work on defining XML for storing Core Components 
themselves in the Registy has been completed and agreed - then 
we will be able to more accurately assess all this of course.

Just wanted to update people here since there had been a shift
in the detail on BIE that has helped clarify their use in the latest
architecture work that I'm expecting to be published after
the Barcelona meetings next week.

Thanks, DW.

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>