W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2001

RE: issue 168 proposal: xsi:type of external references in Encoding

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Tue, 11 Dec 2001 16:01:13 -0800
Message-ID: <79107D208BA38C45A4E45F62673A434D05A53BE7@red-msg-07.redmond.corp.microsoft.com>
To: "Jacek Kopecky" <jacek@systinet.com>
Cc: <xml-dist-app@w3.org>

Not to sound dismissive but I don't think layering has anything to do
with this. It is a question of us providing a data model that can be
used for a variety of purposes.

To my knowledge, we don't have any requirements on limiting the model to
RPC - our requirements document [1] contains word to the effect of
"These data models include object graphs and directed labeled graphs".

There currently is no limitation to where href values can point to and
IMO doing so would be in severe contradiction with the general Web


[1] http://www.w3.org/TR/xmlp-reqs/#N400

> I'm a strong believer in layering. I don't like mixing semantically 
>different layers. As for the representation of RDF using the SOAP 
>Encoding, as seen in [5], I'm not sure how RDF views the href, so let 
>me discuss it a bit. There are two possibilities, with the difference 
>being rather subtle:
> 1) href is a first-class data whose meaning is to point somewhere.
> 2) href is a metadata whose meaning is "the data is not here,
>it's at this URI".  I view SOAP Encoding's usage of href as 
>the latter, while it seems to me that RDF's usage is the 
>former. Let me explain why.
Received on Tuesday, 11 December 2001 19:01:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:17 UTC