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: COMPLEXITY BIG ISSUE


Rik / Duane,

Notice that the eDTD schema proposal already contains the necessary
syntax to fully enable multilingual support via the Bizcodes abstraction
method.

Since this uses the XLink/XPointer toolset I expect this to be widely
utilized
as soon as the parsers support the mechanism.

Thanks, DW.

Message text written by "Rik Drummond"
>
The message structure should be reasonably intuitive.  This means that a
human being should be able to somewhat decifer a message.  This is very
important for manually constructed messages, error checking, archiving and
searching.  It also reduces the system architectural complexity.

In short - I am totally against using numerical values for Elements.  We do
not want to create another cryptic taxonomy.

EXAMPLE:

If you encounter:

<ebXML>
  <Header>
     <From>Foo Inc.</From>
     <To>Bar Corp.</To>
  </Header>
  <Message Type="Index">
   Blah
  </Message>
</ebXML>

OR:

<ebXML>
  <En-tÍte>
     <Du>Foo Inc.</Du>
     <A>Bar Corp></A>
  </En-tÍte>
  <Communique Tapent="facture">
   Blah
  </Communique>
</ebXML>
<



[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