Since the namespaces are, like you said beyond XML 1.0, I could not get a
successful run of my parser. The software cannot get past the namespaces to
parse the file. My meaning was that the document could not be validated or
parsed; there was a fatal error at the beginning of the file. Even if the
document could be parsed by some non-MS XML software, it is really of no use
if you cannot extract the relevant business data, due to the proprietary
syntax/namespaces. Really, what is at issue is the question of which
entities are best suited to drive XML standards efforts and why. These
discussions, in my opinion, have served to highlight some of the specifics
as to why a standards body, and not a software company, should drive this
ship ;)
-----Original Message-----
From: G. Hussain Chinoy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 1:54 PM
To: '[EMAIL PROTECTED]'
Subject: RE: xmledi-group Digest for 24 Apr 2001 in hour 22:00
I don't follow this? Do you mean 'validate' not 'parse', meaning that a
non-MS XML parser could read the document, but since there's no DTD and
that the Schema specified in the namespaces are beyond 'XML 1.0
Validation' that the "proper" business logic would not be extracted?
Using my highest level language (other than pseudo-code :), it seems to
parse out ok:
http://ix.granularity.net/test/test.biztalkexample.cfm
h
On Thu, 26 Apr 2001, Williams, Brad wrote:
> Timothy,
>
> As I stated in my email, "this is a well-formed XML file". That is to say,
> that it is syntactically correct. For every start tag, there is an end
tag,
> etc. However, this has nothing to do with actually parsing the file. That
is
> a different matter entirely. IE, is, after all a MS product, and the
default
> parser in XML Spy 3.5 is MSXML. If you have an XML parser, other than MS's
> XML parser, try to run it and you will see that the file will not
parse(you
> can change the default parser in XML Spy 3.5 under settings, after you
> install the parser, if you don't want to run command line). This
discussion
> began with the pitfalls/dangers of application specific vs. industry
> "standards". A BizTalk XML file is MS application specific.
>
> Brad
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
