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

RE: Comments on Section 2.6 of XML-Namespaces

  • From: Andrew n marshall <amarshal@u...>
  • To: "'Andrew Layman'" <andrewl@m...>, "'tbray@t...'" <tbray@t...>, "'dmh@c...'" <dmh@c...>
  • Date: Wed, 1 Apr 1998 00:21:53 -0800

RE: Comments on Section 2.6 of XML-Namespaces
On Tuesday, March 31, 1998 7:26 PM, Andrew Layman 
[SMTP:andrewl@m...] wrote:
> Thanks for your question, and for reading the document closely.
>
> I think you are expecting namespaces to do more than it in fact does.
> Namespaces simply allows you to distinguish the T.Heat:Temp attribute 
from
> the T.Color.Temp attribute.  It does not take on the job of expressing
> grammatical rules such as that the T.Heat.Temp attribute must only be 
used
> in conjunction with another attribute, e.g. T.Heat.Units.  Namespaces are
> just a named set of names.  Keeping the names distinct is the goal of
> namespaces.  Defining the grammar, semantics, etc. of the named things is
> beyond the pale.

But aren't attribute names already unique?  From the XML spec [3.3], a DTD 
may contain "at most one attribute definition for a given attribute name 
[in an attribute-list declaration]".  As long as the element names unique, 
which it seems you have done successfully, then there is no need for your 
syntax.  I believe the syntax you propose introduces more problems than it 
is worth for the previously given reasons, even if it does not intend to 
describe semantics.

I will make one exception, which it seems you are already aware of: 
processor specific information that may apply to every element and 
therefore does not specify a particular element as the source of the 
attribute.  A good example of this usage can be found in the new XLink 
notation 'xml:link'.  Another possible use may be in XML architectures, as 
in 'Arc:URL' ( realize this isn't the currently recommended form, but I 
think it makes sense).

I guess my complaint boils down to allowing QNames of the form 
'namespace:ELEMENT.attribute' as the name of an Attribute.  While I don't 
see any reason for this notation at all, it should at least include a 
validation constraint to check that the STag uses the QName 
'namespace.ELEMENT'.

Andrew n marshall
  student - artist - programmer
    http://www.media-electronica.com/anm-bin/anm
      "Everyone a mentor,  Everyone a pupil"

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)


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.