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: FW: Latest Specification document


Hi All,

The Architecture Document (Section 3.5.5 a)(TechArch group) currently
proposes that an ebXML document be framed within an 'ebXML' element. 
TR&P is referenced in an Editor's note to this rule. See below:

  a)      The message will use a root tag of <ebXML> to identify it as an
ebXML compliant transaction.

  [EDITORS NOTE:  THE TRP GROUP MUST EITHER ADOPT THIS OR SPECIFY AN
ALTERNATIVE IDENTIFICATION ELEMENT OR METHOD]

I do not support this means of identification, and propose instead that an
XML conformant document include a 'Processing Instruction' asserting ebXML
compliance.  I suggest:

	<?ebXML version='1.0' reference='someURI'>

where 'version' provides the ebXML version to which compliance is claimed,
and 
      'reference' provides a URI for use in accessing a repository of
metadata relating to this message. 

I believe this approach is less intrusive upon XML syntax.  It eliminates
the need, if a DTD (or other schema declaration)is used, to define an ebXML
element and its allowed content.

Cheers,
        Bob


[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