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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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

Subject: RE: Glossary?

I seem to recall that this was a continued topic of discussion at the
Orlando ebXML Steering Committee meetings in February. Also, I believe the
decision was that the ebXML Technical Coordination Project Team would take
on this responsibility to develop and publish such a glossary.

Perhaps this could be a deliverable for the TC PT at Brussels?

Rachel Foerster
Marketing, Awareness & Education PT lead

-----Original Message-----
From: owner-ebxml-transport@lists.oasis-open.org
[mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of David
Sent: Wednesday, April 26, 2000 5:50 PM
To: 'Christopher Ferris'; ebXML-Transport@lists.oasis-open.org
Subject: RE: Glossary?

A good idea !


-----Original Message-----
From: Christopher Ferris [mailto:chris.ferris@east.sun.com]
Sent: Wednesday, April 26, 2000 11:31 AM
To: ebXML-Transport@lists.oasis-open.org
Subject: Glossary?


Seeing the definitions section in David's
doc, and the Glossary in Dick's packaging
spec leads me to suggest that we might want
to consider a separate glossary/definitions
document so that there is one and only
one definition for any given term and we don't
end up with inconsistencies (either at the
start, or as the documents are evolved).

In fact, it might be wise to have the Technical
Coordination WG edit/produce the document,
taking input from the other WGs. That way,
there isn't conflict between WGs (which might
not be caught).

Just a thought,


[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