- From: Henry Story <henry.story@bblfish.net>
- Date: Wed, 12 Jun 2013 00:02:43 +0200
- To: Arnaud Le Hors <lehors@us.ibm.com>
- Cc: public-ldp-wg@w3.org
Received on Tuesday, 11 June 2013 22:03:19 UTC
I really don't think one can just not answer the following question: On 11 Jun 2013, at 22:06, Henry Story <henry.story@bblfish.net> wrote: > So what you really want is a way to describe that an LDP Resource is an LDPR, or an LDPC an LDPC. > > Now you want to do this with a header > > Link: <http://www.w3.org/ns/ldp#Resource>; rel=profile > > which would be the equivalent semantically to > > <> ldp:profile <http://www.w3.org/ns/ldp#Resource> > > >> Isn't that something you can live with? > > Is that what you want? The proposal has not been made clear yet. > > How is that such a great improvement over > > <> a ldp:Resource . > > ie: > > Link: <http://www.w3.org/ns/ldp#Resource>; rel=type > > What is the difference? Social Web Architect http://bblfish.net/
Received on Tuesday, 11 June 2013 22:03:19 UTC