On 31 Jan 2013, at 15:47, "Wilde, Erik" <Erik.Wilde@emc.com> wrote:
> hello henry.
>
> On 2013-01-31 13:28 , "Henry Story" <henry.story@bblfish.net> wrote:
>> Why not have your service document do something like this
>> <> xyz:service <http://ldp.example/> .
>> <http://ldp.example/> a ldp:Container .
>> And then if you want to specify the media types available on that you
>> could add
>> <http://ldp.example/> xxx:mime "application/atom+xml", "text/turtle" .
>> If it wants to link to another service it could write:
>> <> xyz:service <http://ldpng.example/> .
>> <http://ldpng.example/> a ldpng:Container .
>> See nothing special here.
>
> that works on the semantic web (where you expose things via RDF), but not
> on the web (where you have to live with HTTP's uniform interface).
The semantic web is not part of the web?
And LDP is perhaps not part of the web either? As far as I know
LDP uses HTTP, and all the big Linked Data projects use HTTP. Some
even use HTTPs.
Social Web Architect
http://bblfish.net/