[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-jc] draft text for TAB requests
Colleen:
I'd add the following in (1) (in bold)
but have no problem if we don't:
(1)We feel there is a need for an OASIS-wide way to implement shema
versioning and documentation across OASIS approved schemas.
More generally, specifications should include a formal representation
of their version number, e.g. using a common XML document format.
All this would make it easier to obtain, query, and process the version number
of an implementation.
(2) We also feel there is a need for a common way to represent
compatibility links to other specs. While the ebXML Joint Technical
Liaison Team is developing an ebXML standards compatibility matrix, a more
formal way to code a compatibility matrix (for integration as well as interoperability)
is required across OASIS, ideally a model that could be processed by a tool
and well understood across specifications.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC