- From: Svensson, Lars <L.Svensson@dnb.de>
- Date: Mon, 18 May 2015 16:57:33 +0000
- To: "henry.story@bblfish.net" <henry.story@bblfish.net>, Linking Open Data <public-lod@w3.org>
- Cc: Social Web Working Group <public-socialweb@w3.org>, "Linked Data Platform WG" <public-ldp-wg@w3.org>
Henry, On Wednesday, May 13, 2015 2:15 PM, henry.story@bblfish.net wrote > There is a potential use of profiles that I can think of which has to do with cases > where there is a need to create JSON-LD crystalisations of RDF [1]. I defined a > crystalisation of RDF in 2006 as giving an RDF a specific shape. A good example > of this in the RDF/XML work was RSS1.1 [2]. I just note that this is related but not similar to what I envision for serving information about an entity in several "profiles". > RDF/XML has gone I think RDF/XML is still very much alive... [...] > Accept: application/ld+json;profile=http://www.w3.org/TR/activitystreams- > core/profile I see that we use the term "profile" differently. I think my use is more related to "data shape" as used in the data shapes WG (not quite sure, though...). The use of the Accept-header to transport profile information is elegant. I had looked at that, too, but noticed that it's only allowed with two content-types (XHTML [1] and JSON-LD [2]). E. g. you cannot ask for Accept: text/turtle;profile=http://www.w3.org/TR/activitystreams-core/profile which probably is not an issue since your problem is restricted to JSON-LD. Your question how to describe those profiles is very much similar, though. Best, Lars
Received on Monday, 18 May 2015 16:58:03 UTC