OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: To get things started.... Data formats..



Aren't people confusing $ within the name of an element and $ within the
value of an element?

*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



David Lyon <djlyon@one.net.au> on 05/31/2001 01:14:32 PM

To:   mike@rawlinsecconsulting.com
cc:   ebxml-core@lists.ebxml.org
Subject:  Re: To get things started.... Data formats..



Mike, all,

All I can say then is that it sounds to me like there is a long, long way
to
go before we will be seeing too many production ready and operationally
secure ebXML systems.

I don't know of too many financial institutions that would use ebXML if the
parsers used got confused by the '$' symbol. That's just a huge security
flaw when you think about it.

But by all means, if this is how it must be done....

David Lyon

----- Original Message -----
From: Mike Rawlins <mike@rawlinsecconsulting.com>
To: David Lyon <djlyon@one.net.au>
Cc: <ebxml-core@lists.ebxml.org>; <ebxml-dev@lists.ebxml.org>
Sent: Friday, June 01, 2001 2:02 AM
Subject: Re: To get things started.... Data formats..


> Sorry, but this seems to me to be verging on the silly.
>
> David Lyon wrote to Betty Harvey's reply <snipped>:
>
> >
> > > There is a serious problem with using the '$'.  This signifys an
> > > entity within a dataflow.  Any parser who sees the $ will be
> > > looking for the closing delimiter ';', i.e., $myentity;.  If
> > > you have <date$> it is going to confuse the parser beyond
> > > belief.
> >
> > So why not fix the problem ?
> >
> > Why perpetuate it forever more ?
> >
> > Why can't ebXML be better than previous attempts at XML ?
>
> ebXML decided to adopt a sound software engineering practice of re-using
> existing work whenever possible.  In this case it was XML (based on ISO
standard
> SGML).  "Fixing" SGML or XML are clearly not now nor were they ever
within
the
> scope of our efforts.  Making such suggestions only damages your
credibility
> within this group.
>
> --
> Michael C. Rawlins, Rawlins EC Consulting
> www.rawlinsecconsulting.com
>
>
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-dev-request@lists.ebxml.org
>


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-core-request@lists.ebxml.org





[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