OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: Namespace prefixes optional?

[ Lists Home | Date Index | Thread Index ]
  • From: David Megginson <david@megginson.com>
  • To: Bob Kline <bkline@rksystems.com>
  • Date: 06 Jan 2000 19:21:58 -0500

Bob Kline <bkline@rksystems.com> writes:

> I'm still trying to absorb all of the intricacies of namespaces, and I
> can see I have a long way to go.  I'm looking at the XLink
> recommendation (http://www.w3.org/TR/xlink/) and I see the following:

Here are the tricky points about Namespaces:

1. Namespace URIs are just unique identifiers, like Java or Perl
   package names; they don't (necessarily) point to anything.

2. There can be a default Namespace for element names but not for
   attribute names.

3. Not withstanding #2, some apps may treat unprefixed attribute names
   as if they belong to the same Namespace as the corresponding
   element name.

Anything I'm missing?  If you want to run through a quick Q-and-A to
make sure you've got it, take a look at the following:

  http://www.megginson.com/docs/namespaces/namespace-questions.html

Sure, the stuff about per-element Namespace partitions and global
attributes is confusing, but it's non-normative and you can safely
ignore it.

>   A sample set of declaration for a series of elements that use the
>   type attribute might look as follows:
> 
>     <!ELEMENT student EMPTY>
>     <!ATTLIST student
>       xlink:type     (locator)     #FIXED "locator"
>       xlink:href     CDATA         #REQUIRED
>       xlink:role     NMTOKEN       #FIXED "student"
>       xlink:title    CDATA         #IMPLIED
>     >
>     . . . .
> 
>   The following example shows how an XML document using these
>   declarations might look:
> 
>     <student
>       href="/students/patjones.xml"
>       title="Pat Jones" />
>     . . . .
> 
> Does this mean that once the namespace prefix has been declared in the
> DTD the parsers understand that (for example) "href" really means
> "xlink:href" (and therefore this sample document will be valid)?

To me, that looks very much like a typo.  I would have expected

  <student 
    xlink:href = "/students/patjones.xml" 
    xlink:title="Pat Jones" />


All the best,


David

-- 
David Megginson                 david@megginson.com
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@ic.ac.uk the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)






 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS