AW: SMEs : was RE: Party XML Schema Defintions

[Hermes Hartmut <Hartmut.Hermes@MCH11.siemens.de>]

Dear all,

it seems that we all are in agreement to support language neutral constructs
to identify ebXML components (including aggregates). They would allow to
cross reference ebXML human readable tags in whatever language. Another
benefit could be the mapping with interfaches of applications and/or with
other former or future eb relevant standards (ANSI X12, EDIFACT, ...).

Thanks Arofan for this support!

Kind regards / Mit freundlichen Gruessen
Hartmut Hermes     
Siemens AG GPL GLO LE	D-80286 Muenchen     
Tel: +49 89 9221 4564     	Fax: +49 89 636 718 580
Tel: +49 8233 600 222     	Cellular phone: +49170 22 97 606  
Project Omega Information may be found at:
http://www.el.siemens.de/cgi-bin/index.pl?href=/new/logistik/geschabw/omega/
uebersicht.en.htm
<http://www.el.siemens.de/cgi-bin/index.pl?href=/new/logistik/geschabw/omega
/uebersicht.en.htm> 
If you want to get information on the Basic Semantic Register please visit:
http://forum.afnor.fr/afnor/WORK/AFNOR/GPN2/TC154WG1/index.htm
<http://forum.afnor.fr/afnor/WORK/AFNOR/GPN2/TC154WG1/index.htm> 


	-----Ursprüngliche Nachricht-----
	Von:	Blantz, Mary Kay [SMTP:mblantz@netfish.com]
	Gesendet am:	Freitag, 9. Februar 2001 16:49
	An:	'Gregory, Arofan'; 'Joaquin Miller';
ebxml-core@lists.ebxml.org
	Betreff:	RE: SMEs : was RE: Party XML Schema Defintions

	Arofan,

	This is exactly how I understand Hartmut and Andreas' approach.  I
have
	presented it this way to AIAG and to X12/EWG.  Everyone is most
excited
	about it.  I understand that OAG and OMG are presenting it this way
to
	their members, since both have asked for my presentation.  

	A round of applause to Hartmut and Andreas!  (And to Sue Probert,
who
	explained it so well to me!)

	MK

	-----Original Message-----
	From: Gregory, Arofan [mailto:arofan.gregory@commerceone.com]
	Sent: Thursday, February 08, 2001 4:12 PM
	To: 'Joaquin Miller'; ebxml-core@lists.ebxml.org
	Subject: RE: SMEs : was RE: Party XML Schema Defintions


	Folks:
	 
	At the Orlando meeting, Harmut suggested that we have
non-semantic-bearing
	IDs for each construct, and then "official", language-specific
	human-readable tags for each language, with an English-language
version
	being one of the first outputs, but with others constrcuted along
the same
	lines. This approach lets you build applications to either the
unique IDs
	(for multi-language support) or to build applications that support
only a
	single, language-specific version. Presumably, the human-readable
tags would
	have their own consistent rules about providing names, but these
rules
	themselves might be prone to localization(!)
	 
	This is a good, flexible approach that would seem to offer the most
in terms
	of handling localization problems, and I suggest we follow it.
	 
	(Harmut - sorry if I have mangled your suggestion - if I am wrong,
please
	feel free to correct).
	 
	Cheers,
	 
	Arofan Gregory

	-----Original Message-----
	From: Joaquin Miller [mailto:miller@joaquin.net]
	Sent: Thursday, February 08, 2001 12:48 PM
	To: ebxml-core@lists.ebxml.org
	Subject: RE: SMEs : was RE: Party XML Schema Defintions


	At 12:09 PM 2/8/2001 -0800, Hayes, Brian wrote:


	It is general considered to be good architecture to seperate user
interface
	issues from data issues: Your user friendly user interface sould not
be
	displaying XML tag and attribute names.


	Absolutely!  I could not agree more.

	It's why i wrote: "Everyone can use software to display the data
with field
	names they can read and to provide explanations for what those field
names
	mean."

	I side with those who suggest using identifiers.  I feel it is a
much better
	way than hanging our hat on natural language tags, whether English
or
	so-called "Foreign."  I don't want to repeat here all the traffic
about the
	problems with dependence on exclusive use of natural language tags.




	-----Original Message-----
	From: Joaquin Miller [ mailto:miller@joaquin.net
<mailto:miller@joaquin.net>
	]
	STEPHENIE COOPER wrote:

	ebXML's goal should be to help make that happen.

	Yes.  Let's go for the whole planet.  Not just our company's
customers or
	partners.  And let's go for the people who speak Foreign, too.
Everyone can
	use software to display the data with field names they can read and
to
	provide explanations for what those field names mean.  There has
been a lot
	of recent eMail traffic about how to define ebXML in order to make
that easy
	for everyone.  Let's do it.



	Cordially,

	Joaquin 

	................................................
	Joaquin Miller
	Chief Architect
	Financial Systems Architects

	mailto:joaquin@acm.org <mailto:joaquin@acm.org> 

	San Francisco
	phone: +1 (510) 336-2545
	fax:   +1 (510) 336-2546
	PGP Fingerprint:
	CA23 6BCA ACAB 6006 E3C3 0E79 2122 94B4 E5FD 42C3