W3C home > Mailing lists > Public > www-xml-linking-comments@w3.org > April to June 2001

RE: XLink specified in XML Schema

From: Vun Kannon, David <dvunkannon@kpmg.com>
Date: Tue, 19 Jun 2001 15:01:30 -0400
Message-Id: <53A3C10BA714D511BA9300805FA7FB2A01B5D872@usmnyexc05.us.kworld.kpmg.com>
To: "'Simon \"St.Laurent'" <simonstl@simonstl.com>
Cc: "'www-xml-linking-comments@w3.org'" <www-xml-linking-comments@w3.org>
I agree and understand. I don't think providing a normative schema for XLink
creates a dependency, any more than publishing a RELAX module would create a
dependency. Given that the XLink editors have to allocate their very scarce
resources, my request merely indicates my preference of documentation in XML
Schema over DTD and RELAX.
Cheers,
David vun Kannon


> -----Original Message-----
> From: Simon "St.Laurent [mailto:simonstl@simonstl.com]
> Sent: Tuesday, June 19, 2001 11:45 AM
> To: Vun "Kannon," David
> Cc: 'www-xml-linking-comments@w3.org'
> Subject: Re: XLink specified in XML Schema
> 
> 
> On 19 Jun 2001 11:24:52 -0400, Vun Kannon, David wrote:
> >       The XLink spec currently defines the attributes of the Xlink
> > namespace using DTDs. There are a few aspects of the new XML Schema
> > specification which may be helpful to XLink applications. 
> Defining XLink in
> > terms of XML Schema will allow a certain level of 
> validation of the XLink
> > information by the general process of schema validation. 
> This could include
> > namespace correctness, datatyping and enumeration values 
> and defaults, and
> > uniqueness constraints.
> >       XLink currently uses the xlink:type attribute to 
> distinguish various
> > kinds of elements. This function could be handled in XML 
> Schema by abstract
> > element definitions and the use of element substitution groups. 
> > 
> >       My request is that the XLink specification include a 
> normative XML
> > Schema as part of the spec.
> 
> While I wouldn't  necessarily object to inclusion of a normative XML
> Schema, I would strongly oppose any effort to make XLink processing
> dependent on XML Schema processing.  
> 
> While xlink:type could perhaps be abolished by abstract 
> elements and the
> use of element substitution groups, doing so would render 
> XLink far less
> useful to a large group of developers who are working with DTDs,
> alternative schema languages (notably RELAX NG), or with no schema
> support whatsoever.
> 
> Simon St.Laurent
> 
> 
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************
Received on Tuesday, 19 June 2001 15:01:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:08:12 UTC