OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-core message

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

Subject: RE: XML Implementation spec


The point of subclassing is that the core information structure (the "Party"
information) would be the same whether the Party was acting as Buyer or
Seller. This way, it becomes possible to reuse the data structure of the
superclass in each of these otherwise disparate cases. That is the whole
point of subclassing - to allow re-use of the information in cases where
there is a different semantic associated with the same bits of data. So long
as the structure (at the level of the super-class) is common, the semantic
can be adjusted without making interoperability impossible.


Arofan Gregory

-----Original Message-----
From: Bob Haugen [mailto:linkage@interaccess.com]
Sent: Friday, May 26, 2000 1:26 PM
To: 'ebxml-core@lists.oasis-open.org'
Subject: RE: XML Implementation spec

Ernie Nishiseki wrote:
>Attached is a first draft of the XML Implementation Methodology

Question:  in this document, Buyer and Seller are subclasses
of Party.  Is this the way the core component for Party will be
designed (I hadn't noticed it in other documents), or is that just 
an example of how to implement subclasses?

To put a point on the question, how could the same Party
be a Buyer in one exchange and a Seller in another,
if Buyer and Seller are subclasses?

Bob Haugen

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC