Hi Betty,
I agree 100% with you. That is exactly what I am seeing also.
DTDs are the current workhorse. XSD's have more sizzle, but are not in widespread use...yet.
The basic need is not the DTD or XSD or RelaxNG, but the business process.
Use the technology that best solves the business problem. Try not to use the technology just for technology sake. Most companies don't have the extra time or money to 'do' and then 'undo', and then 'redo'.
Thanks for the straight talk.
Jeff Eck
XML Chancellor
GE Global eXchange Services
-----Original Message-----
From: Betty Harvey [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 24, 2002 9:55 PM
To: [EMAIL PROTECTED]
Cc: XML/edi Group
Subject: Re: [relax-ng] New article on RELAX NG vs W3C XML Schema
Actually, the lion's share are using DTD's and are waiting to see what
happens with Schemas. The clients that I have who had developed Schemas
have contacted me 'after the fact' and are now trying to figure out
how to use them |-).
I know DTD's are not 'politically correct' but they work and have a long
history (as long as EDI) and are suitable for most applications.
Before organizations decide to blindly follow Schema (W3C, RelaxNG or
whatever) or DTD's they need to define their requirements. I am finding
that organizations are blindly following Schema because of the hype
without real information.
We have seen so much hype revolving around XML in the last few years.
The real success stories are the ones that looked at their requirements
and used XML where it fit their business model. We have seen some
major failures where organizations were not well informed!
XML is really cool and can be used in many useful and productive ways that
no one has even thought of yet but when organizations are sold a 'bill of
goods' it can lead to failure.
Before XML can be deployed successfully a real understanding of the
business models and information is required. The schema (W3C, RelaxNG,
XML Data Reduced, ...) or DTD or whatever is just the vehicle for
identifying and processing information in a standardized way.
Betty
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Betty Harvey, XML Consultant, | Phone: 410-787-9200 FAX: 9830
Electronic Commerce Connection, Inc. |
[EMAIL PROTECTED] | Washington,DC SGML/XML Users Grp
URL: http://www.eccnet.com | http://www.eccnet.com/xmlug/
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\\/\/
On Thu, 24 Jan 2002, Mike Rawlins wrote:
> So, getting to my question, I take it from your answer that your clients are using
> W3C Schemas?
>
> Do they know what Relax NG is, and if so, have they considered it?
>
> Betty Harvey wrote <snipped>:
>
> > This is really a hard issue. There are problems with the W3C
> > schema specification. Every W3C situation I have encountered with my
> > clients who have contracted to have a W3C Schema created has issues. The
> > schema parses with the tool that was used to create the schema but does
> > not parse on any other schema parser. IMHO this is a very serious
> > situation. This means that the user is locked into a vendor specific
> > product. I don't believe this is because of vendor's diligence but
> > because of ambiguities in the specification.
>
> Yeah, W3C schema is not perfect, but I think you could find the same problems with
> V1 of lots of specifications and V1 of nearly every product that implements a new
> specification.
>
> > I believe RelaxNG is getting some 'wings' behind it because of
> > the OASIS-Open endorsement and the fact that it is going through ISO.
> > Timing is critical though, as we all know. The best solution doesn't
> > always win.
>
> My point exactly. Such decisions are often made for non-technical reasons.
>
> --
> Michael C. Rawlins, Rawlins EC Consulting
> www.rawlinsecconsulting.com
>
>
>
>
> ------ 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
------ 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
