- From: Henry Story <henry.story@bblfish.net>
- Date: Tue, 26 Mar 2013 14:26:09 +0100
- Cc: public-ldp@w3.org
- Message-Id: <1AC02CC3-E46F-4621-B223-C654F13A8499@bblfish.net>
On 26 Mar 2013, at 12:44, Kingsley Idehen <kidehen@openlinksw.com> wrote: > On 3/26/13 5:15 AM, Henry Story wrote: >> On 26 Mar 2013, at 10:06, Richard Cyganiak <richard@cyganiak.de> wrote: >> >>> On 26 Mar 2013, at 02:35, James Leigh <james@3roundstones.com> wrote: >>>> Something like "text/turtle;profile=http://ldp.net/ldpr" would be really >>>> cool as it could be applied to any (past or future) RDF format and >>>> mostly ignored by clients/servers that don't understand it. >>> That would be ok with me. >> I have argued before this is the wrong place to put that information, and >> that it has nothing to do with the mime type. >> >> Henry > > Yes you have [1]. Thus, it's profiles or media type. Which is the least costly to folks on the RDF side of things? > > Links: > > 1. http://lists.w3.org/Archives/Public/public-ldp-wg/2013Feb/0069.html -- earlier thread. Thanks for finding the link to my post. My argument there is that this is not a media type issue. If you want to specify in the Header that the resource is an LDPC you can use the Link relation type. Doing it at the media-type level is a misunderstanding of the role of media types. My post went into detail on why this is so. > > > Kinglsey >> >>> Richard >>> >> Social Web Architect >> http://bblfish.net/ >> > > > -- > > Regards, > > Kingsley Idehen > Founder & CEO > OpenLink Software > Company Web: http://www.openlinksw.com > Personal Weblog: http://www.openlinksw.com/blog/~kidehen > Twitter/Identi.ca handle: @kidehen > Google+ Profile: https://plus.google.com/112399767740508618350/about > LinkedIn Profile: http://www.linkedin.com/in/kidehen > > > > > Social Web Architect http://bblfish.net/
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Tuesday, 26 March 2013 13:26:44 UTC