[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Bolt-in Type Systems (RE: Relax NG and Web Servi

  • To: "Bullard, Claude L \(Len\)" <clbullar@i...>,<xml-dev@l...>
  • Subject: RE: Bolt-in Type Systems (RE: Relax NG and Web Services (formerly Joining the church))
  • From: "Dare Obasanjo" <dareo@m...>
  • Date: Fri, 11 Jul 2003 11:40:15 -0700
  • Thread-index: AcNHtGjy1bobs6qBSw+QkZXyzkKCDQAJ3V+v
  • Thread-topic: Bolt-in Type Systems (RE: Relax NG and Web Services (formerly Joining the church))

re bolt
The ability to specify which datatype libraries are used by the validation language means that if you want to interop with other parties you have to use a standardized set of datatypes. The only [recognized] standardized set of datatypes we have in the XML world has been W3C XML Schema: Part 2. This is what most RELAX NG implementations support. 

PS: If you need an example, read http://www.oasis-open.org/committees/relax-ng/tutorial-20011203.html#IDA5UYR 


From: Bullard, Claude L (Len) [mailto:clbullar@i...]
Sent: Fri 7/11/2003 6:56 AM
To: xml-dev@l...
Subject:  Bolt-in Type Systems (RE:  Relax NG and Web Services (formerly Joining the church))

Somewhere in these interrelated threads, someone mentioned
that the RELAX NG approach to type systems was to enable a
designer to add their own.  How does that work?  Are there

Some can pretend type issues don't exist or are purely private
local affairs.  That really doesn't work for languages that
initially are defined as object models and treat the XML
or other encodings as just that, the bits on the wire
representation of what an implementation of that object
model needs to operate.  True extensibility for these is
in the object model, and true interoperability as well.

The X in XML is pretty worthless for that.  It must be
able to express that an extension to the object model
is needed and there are ways to do that (eg, modify
the schema or DTD, add a namespace, add application
language constructs such as X3D PROTOs), but using
XML to design extensibility is backwards.  Using it
to detect it in the document is not.  We shouldn't
confuse the diet of the animal with the animal.

We can't get away from types.  Because it seems that
for the object model languages, extensibility has to
be worked out in the object model first then and only
then worked out as an expression in the encodings such
as XML application languages or in terms of the metalanguage
(eg, namespaces), bolt-in types seem highly desirable and
this could be a crucial feature for choosing which schema
application languages (eg, XSD, NG, DTD) to normatively


The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.