- From: Stephen D Green <stephengreenubl@gmail.com>
- Date: Wed, 3 Jul 2013 15:08:09 +0100
- To: "Rushforth, Peter" <Peter.Rushforth@nrcan-rncan.gc.ca>
- Cc: "public-xmlhypermedia@w3.org" <public-xmlhypermedia@w3.org>
- Message-ID: <CAA0AChXUcdVeODksSFq71BSh92=AUCAOm=harqPpSfHOt=ZCxg@mail.gmail.com>
So there could be a media type - 'application/*fooxml'* that required that for every URL containing a document of its media type, http://abc.xyz/foo/bar/123 there MUST be a corresponding document containing its links at http://abc.xyz/foo/bar/123/ <http://abc.xyz/foo/bar/123/links>*fooxml* and, say, state that the links MUST be published using a particular XML syntax with particular semantics to state which attributes, say, are for the actual links. Is that still not enough? ---- Stephen D Green On 3 July 2013 14:59, Rushforth, Peter <Peter.Rushforth@nrcan-rncan.gc.ca>wrote: > ** > Hi Stephen, > > I think a media type could declare link semantics over anything it wanted. > > If application/nxml (say) declared that @href, @src etc meant such and > such, > then that's what they'd be. > > Similarly, if application/nxml said that the xml: namespace attributes > were declared by virtual document node properties, > I think that would be feasible too. The media type could also declare > that everything > else in xml was incorporated. > > I think that's the way media types work: they RFC describing them is the > last word. > > But one can't just say (now) that in application/xml @href, @src mean > anything, because > there is a large installed base of xml out there in which @href etc are > used and may not > mean exactly what we want them to at this point. > > Peter > > > ------------------------------ > *From:* Stephen D Green [mailto:stephengreenubl@gmail.com] > *Sent:* July 3, 2013 09:49 > *To:* Rushforth, Peter > *Cc:* public-xmlhypermedia@w3.org > > *Subject:* Re: document node attributes > > [Forgive me if this sounds rather ignorant.] > > Would an alternative be to standardize a convention? E.g. > that for every (RESTful) XML document on the Web at URL > http://abc.xyz/foo/bar/123 > there may be a corresponding document containing its links > at > http://abc.xyz/foo/bar/123/links > > Then the standard convention might specify a format for the links > e.g. the Atom Link Model, say. > > Or is that too far short of what is needed by way of hypermedia > for XML? > > > > > ---- > Stephen D Green > > > On 11 June 2013 02:02, Rushforth, Peter <Peter.Rushforth@nrcan-rncan.gc.ca > > wrote: > >> Hi, >> >> According to the XML data model, is it conceivable that the document node >> (not the root element) >> be deemed to carry virtual, hard coded attributes? >> >> In other words, could a media type definition say that the document node >> of this media type has >> these fixed attribute values? >> >> http://www.w3.org/community/xmlhypermedia/wiki/NeoXML >> >> Thanks for any feedback, >> Peter >> > >
Received on Wednesday, 3 July 2013 14:09:00 UTC