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

[Fwd: Defining "public interfaces" in specifications]

  • To: xml-dev@l...
  • Subject: [Fwd: Defining "public interfaces" in specifications]
  • From: Eric van der Vlist <vdv@d...>
  • Date: 26 Oct 2002 10:26:12 +0200

public interfaces
FYI, since this is extending an idea first posted here :-)

Eric

-- 
Curious about Relax NG? My book in progress is waiting your review!
                                   http://books.xmlschemata.org/relaxng/
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
--- Begin Message ---
  • To: www-qa@w...
  • Subject: Defining "public interfaces" in specifications
  • From: Eric van der Vlist <vdv@d...>
  • Date: 26 Oct 2002 10:23:42 +0200
Hi,

Not really sure this belongs to this list, but after the recent issues
with XML 1.1, I came to think that it would be a good thing to define
"public interfaces" in specifications.

These public interfaces would be, like in Java, definitions that a WG
(and the W3C in general) would commit to maintain or explicitely
depracate in future versions of the specs.

The definition of a XML Name could be an example of such interface.

If that had been the case, other specs such as XPath 1.0 could have
refered to "the latest definition of a XML Name" instead of nominatively
quote "the current definition of a XML Name in XML 1.0".

This has already been done with external specs and, for instance, XSLT
1.0 relies on the fragment definition for the mime type of the
dereferenced document in the definition of the document() function. In
other words, XSLT 1.0 relies on whatever will the definition of a XML
fragment be.

I think we could use this example to go still further than what I have
just proposed and define a global repository of "documentation
interfaces" without specifying in which specs these interfaces are
defined.

In the example of XML Names, a spec could then make reference to "the
latest definition of a XML Name" without specifying in which spec this
is defined and the repository would know where to find this definition.

This would allow to move definitions from a spec to another and may be
very usefull. For instance, consider XLink. Because this spec has been
the first to get the problem, XLink has defined the normalization to
apply to the representation URL found in an attribute to convert it into
a "real" URL. This definition probably doesn't belong here, but many
other specs (W3C XML Schema and even Relax NG for instance) made
references to this spec.

Making a reference to "the URL normalization rules" without mentioning
that it belongs to XLink would make specs much more modular.

And of course, a strict management of these "W3C definitions" would not
only help make specs more modular, reduce the need for "cascading
updates" but also increase their level of quality.

Hopes this might help.

Eric
-- 
Freelance consulting and training.
                                            http://dyomedea.com/english/
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
--- End Message ---

PURCHASE STYLUS STUDIO ONLINE TODAY!

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.
Email
First Name
Last Name
Company
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.