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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

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

Subject: Re: ebXML glossary

The term ebXML Infrastructure has been used with different meanings within ebXML. We decided in Vancouver to stick with the interpretation of the TA specification, i.e. meaning the entire framework. If we feel we need to distinguish between the BOV and FSV views, we should either use these terms or come up with new ones.
----- Original Message -----
Sent: Thursday, February 22, 2001 1:29 PM
Subject: Re: ebXML glossary

It probably should be noted, that the definition for ebXML Infrastructure is not consistent with the way it was used during  the Thursday meeting (in Vancouver) regarding the future of ebXML.  At that meeting, Infrastructure was used to indicate those ebXML specifications that would probably go under OASIS - that is, Reg/Rep, TRP, and Trading Partners.   The current glossary definition states that the Infrastructure is ALL the specifications.


At 01:04 PM 2/22/01 +0100, agrangard@nycall.com wrote:
Content-type: text/plain
X-MIME-Autoconverted: from 8bit to quoted-printable by ridley.nist.gov id f1MCE8B02801

Attached you will find the updated ebXML glossary to be voted at the next
steering committee conference call.

Anders Grangard
Ingénieur - Consultant en Commerce électronique
Tel: +33 (0)1 42 91 62 24

[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