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: RE: languages and tags


The Bizcodes mechanism refines this to the next couple of levels.

See http://www.bizcodes.org/   

I'm seeing everyone is basically on-board with using this mechanism,
whether you call it Bizcodes, BizTags, ebTags, ebCodes, etc, is just
pure politics.  Bottom line - this XLink/XPointer mechanism is how
the job gets done.   The bigger issue is registration and the 
repository group is the appropriate place to discuss those
mechanisms and business functionals.


Message text written by "Eckenfels. Bernd"
Hello Achim and List,

given one possible solution to take the whole EDIFACT Data Dictionary I
think it would be a very painfull job to translate all the Segment,
Element and Code Entries into Memonic english. Some automated jobs
(first three words of the official EDIFACT description for example) wont
produce very good tag Names in all parts of the system. Therefore I
think coded elements are the much better solution here.. after all we
are talking about data processing not printing. It is quite easy to
store the Full Text Name of every Element in an attribute and use it in
a XSL Stylesheet for Visualisation.

This means:
                                            generic XSL+language
coded-XML-EDI-Message + DTD-with-fixed-attributes)  --->  HTML with
localized output


[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