Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] XML spec and XSD

From: "Len Bullard" <cbullard@------.--->
To: "'Mukul Gandhi'" <gandhi.mukul@-----.--->, "'Michael Sokolov'"
Date: 11/7/2009 3:53:00 PM
No.  I think it was a way of saying something simple and familiar will work
until something more precise and powerful can replace it.  It was a
stabilizer in a time of incredible shifts and unpredictable fortunes.  It's
clear that validity is not intrinsic to markup functionally.  It is just as
clear that validation is useful to applications.

We let the next thing go too far in terms of application.  We needed
multiple validators for different users and uses.   We have that now but
also we have entrenched factions of users.

len

-----Original Message-----
From: Mukul Gandhi [mailto:gandhi.mukul@g...] 
Sent: Saturday, November 07, 2009 9:25 AM
To: Michael Sokolov
Cc: Michael Kay; xml-dev@l...
Subject: Re: [xml-dev] XML spec and XSD

On Sat, Nov 7, 2009 at 7:04 PM, Michael Sokolov <sokolov@i...>
wrote:
> There seems to have
> been an insistence on making validity a property of the document, rather
> than a separate concern.

I think, presence of DTD in the XML spec exactly says this (i.e,
validity is a concept inseparably tied to XML markup). But of course,
XML document validity is optional for applications to perform.

Since DTD is already mentioned in the XML spec, why not specify XSD as
well as a normative reference to a future XML spec? I think, even an
errata to a current XML spec can fix this. I am not sure, if another
edition of XML is underway [1]. If that's [1] happening at W3C at the
moment, it may even contain this normative reference I am suggesting.

Even W3C says, that XSD replaces DTD as a better XML validation
technology. And XSD 1.0 version has been in existence since many years
now, and implemented by quite a few XML products, and also deployed
widely in end user applications.
Therefore, why XML standard cannot say that XSD is a validation
technology like what DTD is?

I think, mentioning XSD in the XML spec will encourage users to use
XSD as a better validation technology, than DTD. Mentioning this as a
reference link in XML spec, looks like a very minor and non disruptive
addition to me, for the XML spec.



-- 
Regards,
Mukul Gandhi

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent