Just exactly what does NVDL disrupt?

It's a really natural development as schema parsers and validators
become more developed, and its timing is near perfect as we find
more than 1 standardized schema language around.  It's exciting,
but I don't see what market place it disrupts.

For the points you made, (1) is not necessarily a plus point for
users, schema owners, and application developers.  (2) is not
going to be a necessary outcome from presence of NVDL.
(3) is more a "best practice" guideline for schema developers
rather than due to NVDL.  One could always practice writing
simple schemas in a chosen schema language.  A mixed
schema language environment is not an easy one to manage.
(4) is also not a significantly NVDL-only attribute, since
developers still need to worry about proper schema description
and syntax, although they now could pick their own favorite
schema language if their organization permits mix-and-matching
schema languages.  Their focus must still be both vocabulary and
schema.

All in all, I think the excitement about NVDL is understandable.
But I certainly hope its presence is not going to disrupt all
the schema validations and development.

cheers,
mc


At 08:49 PM 11/5/2008, Costello, Roger L. wrote:
>Hi Folks,
>
>Here are the evolutionary (disruptive) changes I envision NVDL bringing
>about in the marketplace:
>
>
>1. Opens the marketplace to utilizing a variety of schema languages.
>
>Previously, you and all your trading partners were locked into using
>one schema language (typically W3C XML Schema) if you wanted
>interoperability.  With NVDL that limitation is lifted and you can
>achieve interoperability while using a variety of schema languages.
>
>
>2. Promotes using the right schema language for the right job.
>
>XML Schema and Relax NG are two schema languages for expressing
>grammar-based rules. They are both standards, the former a W3C
>standard, the later an ISO standard.  Although their capabilities are
>largely overlapping, there are important differences.  "Use the right
>tool for the right job" is an adage that applies to choosing a schema
>language. Knowing the differences in capabilities is important to
>making a good decision in choosing a schema language.
>
>
>3. Encourages the creation of small, simple, independent schemas,
>written in any schema language.
>
>Rick Jelliffe captures this nicely in his article "Standardize The
>Jellybeans Not The Jars"
>http://www.oreillynet.com/xml/blog/2007/11/standardize_the_jellybeans_n
>ot.html
>
>
>4. Moves the application developer's focus from:
>
>        "using a schema"
>
>    to:
>
>        "using XML vocabularies"
>
>
>Can you think of other changes that NVDL may bring about in the
>marketplace?
>
>
>/Roger
>
>_______________________________________________________________________
>
>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