W3C home > Mailing lists > Public > public-xmlhypermedia@w3.org > June 2013

RE: document node attributes

From: David Lee <David.Lee@marklogic.com>
Date: Fri, 14 Jun 2013 17:57:21 +0000
To: "Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>, "liam@w3.org" <liam@w3.org>
CC: "public-xmlhypermedia@w3.org" <public-xmlhypermedia@w3.org>
Message-ID: <6AD72D76C2D6F04D8BE471B70D4B991E127A35@EXCHG10-BE02.marklogic.com>
Trying to whip this horse one more time.  I *do* wish it would run :)


<root hm:href="someplace" xmlns:hm="http://www.hypermedia.org/XML/2013/hypermedia">
stuff
</root>

is that so bad ?


-----------------------------------------------------------------------------
David Lee
Lead Engineer
MarkLogic Corporation
dlee@marklogic.com
Phone: +1 812-482-5224
Cell:  +1 812-630-7622
www.marklogic.com



-----Original Message-----
From: Rushforth, Peter [mailto:Peter.Rushforth@NRCan-RNCan.gc.ca] 
Sent: Tuesday, June 11, 2013 8:52 AM
To: liam@w3.org
Cc: public-xmlhypermedia@w3.org
Subject: RE: document node attributes

> There are multiple data models used with XML - W3C hs 
> specific more than one, and there are others.
> 
> The XPath and XQuery Data Model is the most recent; the XML 
> DOM is another, and some people have argued that the XML 
> Information Set is another.
> 
> XML people tend to be nervous about "hard-coded" but it's 
> true that XML Base would suggest a base URI property.
> 
> But, the DOM spec does do the sort of thing you want, 
> although as properties since the document node can't really 
> have XML attributes, being outside the document.

Oh yes.

> 
> Of course, you'd be abandoning XPath, XQuery, XSLT, XSD, 
> XProc, since such metadata isn't transmitted in XML documents.

Not an acceptable trade off.

> 
> > In other words, could a media type definition say that the document 
> > node of this media type has these fixed attribute values?
> 
> I don't really see advantages over attributes on the root 
> element. 

I think you're right, since once a 'message' gets separated from its
context/metadata there is no guarantee that it be labelled with application/nxml
anymore.  There needs to be, or perhaps just 'should be', an explicit 
bit of metadata such as @xml:href, etc on the root element.  I don't
think that unprefixed @href, @rel etc would work, since in appliaction/xml, they
would be in no namespace and hence not reliably associated with 
a particular meaning.  I was hoping to avoid that though, because of
course you can't have duplicate attributes so having xml:href="http://www.w3.org/XML/1998/namespace"
on the root element would preclude having it point to anything else.


> You could define neoxml:head and neoxml:body 
> instead, as another approach.

As in elements?  While willing to specify concrete attributes, I think
going to the extent of specifying elements is very xhtml or possibly
atom-like, and that has already been done.  

Anyway, it's just a thought experiment.

Cheers,
Peter
Received on Friday, 14 June 2013 17:57:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:06 UTC