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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-coord message

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

Subject: Re: XML Schema or DTDs?

you are correct that both DTD and XML Schemas appear in various ebXML specs.

as stated in the ebXML Requirements document, there is a general business
requirement for ebXML is to provide:
"Design rules for developing ebXML compliant XML documents that are based on
approved W3C schema specifications"

however, it was subsequently pointed out that XML Schema is not an 'approved'
W3C specification.  hence, the original reluctance to use XML Schema and teams
using DTDs instead.

at the Vancouver plenary,  the TRP specification (Message Services) was being
realigned to incorporate SOAP and as part of this it was propsoed they be
allowed to use XML Schemas in this document.  there was agreement that the
adoption of XML Schema by W3C was now so close (and inevitable) that they could
now be considered for use in ebXML.  This has been borne out by the recent
announcement from W3C...
"16 March 2001: W3C is pleased to announce the advancement of XML Schema to
Proposed                          Recommendation." (http://www.w3c.org)

therefore, i would expect to see more schema definitions used in ebXML
specifications as they develop.

you are also correct that ebXML needs to be consistent.  the policy should be to
use XML Schema (as per the original ebXML Requirement).  this is just one of
those situations were we are trying to stay in alignment with best practice (a
moving target!).

"Munter, Joel D" wrote:

> Please clarify a simple thing for me.  Is ebXML Specifying XML Schemas or
> DTDs?  I have asked this question before and have never received a clear
> answer.  Should this be consistent throughout ebXML?  Of the two teams that
> I have monitored and contributed to, I note that Reg/Rep has defined DTDs
> and TR&P has defined Schemas.  What about the other teams?
> Ref: 0.98 TR&P Spec
> Appendix A ebXML SOAP Extension Elements Schema
> The following is the definition of the ebXML SOAP Header extension elements
> as a schema that
> conforms to [XMLSchema]. This schema is a normative definition of the ebXML
> SOAP extension
> elements. Section 8 details the normative specification for these elements.
> Ref: 0.88 Registry Services Specification
> Appendix A Schemas and DTD Definitions The following are definitions for the
> various ebXML Message payloads described
> in this document.
> A.1 ebXMLError Message DTD
> See [ERR] for ebXMLError Message DTD.
> A.2 ebXML Registry DTD
> Thanks,
> Joel Munter
> Intel / eArchitecture Solutions Lab
> joel.d.munter@intel.com
> (480) 552-3076
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-coord-request@lists.ebxml.org

tim mcgrath
TEDIS   fremantle  western australia 6160
phone: +618 93352228  fax: +618 93352142

[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