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

DTDs and namespaces (was Re: Namespaces on Attribute Names

  • From: james anderson <James.Anderson@m...>
  • To: "xml-dev@i..." <xml-dev@i...>
  • Date: Tue, 21 Jul 1998 20:53:06 +0200

DTDs and namespaces (was Re: Namespaces on Attribute Names
David Megginson wrote:
> 
> james anderson writes:
> ...
>  > do i understand the suggestion correctly, to specify that the
>  > presence of an attribute from a given namespace denotes a dynamic
>  > subtype relation between the containing element and an element with
>  > the same name as the prefix used for the namespace (the correctness
>  > of applying 'LC.getRefNo' to the element).
> 
> No, I wouldn't go that far, mainly because namespaces don't have
> elements or attributes; they just have names.
> 

ah!! music to my ears....

> I'd suggest instead that the attribute from a given namespace implies
> a subtype relationship between the current element and an unnamed
> element type that includes the qualified attribute.
> 

but then, i'm not sure this is any better.
if it's "unnamed" then all that has been accomplished is that, by virtue of
changing the prefix between the tag name and the attribute name, you're
permitting attributes in addition to those declared in an attlist. why
encumber namespaces with this?

>  [skipping merrily over the rhetoric]
> 
> Namespaces and DTDs are two different kinds of things: a DTD specifies
> what an author is allowed to include in a specific document, and what
> defaulting for attribute values, etc., should be used.  A namespace
> simply guarantees that a name is globally unique, whatever that name
> happens to be used for.

with which i agree, and which is why i am skeptical of saying that the
presence of particular prefixes implies the pertinence of "unnamed" element types.
> 
>  ...
> 
> The problem with DTDs will come if namespaces include some kind of
> defaulting or local scoping mechanism -- at that point, writing a DTD
> for an XML document will become extremely difficult.

here we get to something substantive.

with the proper storage model for universal names and the proper encoding
semantics, i have yet to see a case where there is a problem.

if the universal names are taken to denote symbols , then the prefixes (or the
lack thereof in the case of implicit qualification through lexical or dynamic
prefix scope) do (does) not matter. (please see my earlier posts in this
thread as well as my responses to MURATA Makoto under the thread "attributes
with intent (and namespaces)" ca. 03.07.)

no, i do not claim it could be implemented to the benefit of the DPH.
yes, it could be done with SAX.

bye,

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.