Re: SMEs : was RE: Party XML Schema Defintions

[Sandy Klausner <klausner@coretalk.net>]

Joaquim:
I respectfully disagree with you on this point. Element and attribute entity
names should be in plain English "real word phases" (with linked foreign and
dialect UNICODE names as well) and these string pattern representations
should be identical in any projected user interface. Without identical
symbolic representations, it leaves a question in the mind of the viewer if
the two string appearances refer to the same entity.
Sandy

> From: "Hayes, Brian" <Brian.Hayes@Commerceone.com>
> Date: Thu, 08 Feb 2001 12:09:03 -0800
> To: 'Joaquin Miller' <joaquin@acm.org>, ebxml-core@lists.ebxml.org
> Subject: RE: SMEs : was RE: Party XML Schema Defintions
> 
> 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.
> 
> -----Original Message-----
> From: Joaquin Miller [mailto:miller@joaquin.net]
> Sent: Wednesday, February 07, 2001 9:04 AM
> To: ebxml-core@lists.ebxml.org
> Subject: RE: SMEs : was RE: Party XML Schema Defintions
> 
> 
> 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
> 
>