RDF Working Group Wiki - User contributions [en]

Chatlog 2011-08-31

Mtiffiel — Wed, 07 Sep 2011 10:38:54 GMT

Mtiffiel: Made minor changes to the text based on my rookie scribing abilities

{{chatlog|rrsagent=http://www.w3.org/2011/08/31-rdf-wg-irc.txt|chatlog={{fullurl:{{PAGENAME}}}}}}
<pre><nowiki>
14:52:51 <RRSAgent> RRSAgent has joined #rdf-wg
14:52:51 <RRSAgent> logging to http://www.w3.org/2011/08/31-rdf-wg-irc
14:52:58 <Zakim> Zakim has joined #rdf-wg
14:53:34 <davidwood> Chair: David Wood
14:53:38 <davidwood> Agenda: http://www.w3.org/2011/rdf-wg/wiki/Meetings:Telecon2011.08.31
14:53:51 <davidwood> Scribe: Mischa Tuffield
14:54:17 <davidwood> ScribeNick: mischat
14:55:01 <mbrunati> mbrunati has joined #rdf-wg
14:55:37 <mischat_> mischat_ has joined #rdf-wg
14:56:34 <mischat_> i might need help with the tidy up tasks at the end of the call
14:57:31 <davidwood> mischat: No problem.
14:58:05 <sandro> zakim, this is rdf
14:58:05 <Zakim> ok, sandro; that matches SW_RDFWG()11:00AM
14:58:05 <AndyS> zakim, this is RDF-WG
14:58:07 <Zakim> sorry, AndyS, I do not see a conference named 'RDF-WG' in progress or scheduled at this time
14:58:09 <Zakim> +??P8
14:58:20 <Zakim> -??P7
14:58:23 <AlexHall> AlexHall has joined #rdf-wg
14:58:32 <mischat> zakim, ??P8 is me
14:58:32 <Zakim> +mischat; got it
14:58:38 <mischat> zakim, mute me
14:58:38 <Zakim> mischat should now be muted
14:58:54 <Zakim> +??P12
14:58:56 <mischat> zakim, unmute me
14:58:56 <Zakim> mischat should no longer be muted
14:58:59 <AndyS> zakim, ??P12 is me
14:58:59 <Zakim> +AndyS; got it
14:59:16 <mischat> one last thing to check before this starts
14:59:32 <ivan> zakim, dial ivan-voip
14:59:32 <Zakim> ok, ivan; the call is being made
14:59:33 <Zakim> +Ivan
14:59:39 <mischat> when i do "foo: say hello" that means "person food. said hello"
14:59:47 <sandro> yes.
14:59:50 <davidwood> Zakim, who is here?
14:59:54 <Zakim> On the phone I see +1.540.898.aaaa, Sandro, mischat, AndyS, Ivan
15:00:05 <Zakim> On IRC I see AlexHall, mischat, mbrunati, Zakim, RRSAgent, danbri, MacTed, cygri, ivan, tomayac, AndyS, sandro, trackbot, davidwood, manu1, yvesr, ericP, manu, NickH
15:00:15 <manu1> zakim, code?
15:00:18 <davidwood> Zakim, aaaa is me
15:00:19 <Zakim> + +1.443.212.aabb
15:00:31 <AlexHall> zakim, aabb is me
15:00:31 <Zakim> +OpenLink_Software
15:00:35 <mischat> manu1 the code 73394
15:00:38 <MacTed> Zakim, OpenLink_Software is temporarily me
15:00:40 <Zakim> the conference code is 73394 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), manu1
15:00:40 <MacTed> Zakim, mute me
15:00:45 <Zakim> +davidwood; got it
15:00:49 <mbrunati> zakim, +1.443.212.aabb is me
15:00:51 <Zakim> +??P18
15:00:58 <Zakim> +AlexHall; got it
15:01:05 <Zakim> +MacTed; got it
15:01:09 <Scott_Bauer> Scott_Bauer has joined #rdf-wg
15:01:11 <Zakim> MacTed should now be muted
15:01:20 <Zakim> sorry, mbrunati, I do not recognize a party named '+1.443.212.aabb'
15:01:24 <MacTed> MacTed has changed the topic to: RDF-WG -- http://www.w3.org/2011/rdf-wg/ -- 2011-08-31 Agenda: http://www.w3.org/2011/rdf-wg/wiki/Meetings:Telecon2011.08.31 (MacTed)
15:01:37 <mbrunati> Zakim, +1.443.212.aabb is me
15:01:52 <zwu2> zwu2 has joined #rdf-wg
15:01:56 <Zakim> sorry, mbrunati, I do not recognize a party named '+1.443.212.aabb'
15:01:56 <zwu2> zakim, code?
15:01:57 <MacTed> Zakim, aabb is mbrunati
15:01:59 <mischat> mbrunati, try "zakim, aabb is me"
15:02:08 <mbrunati> thanks misha
15:02:10 <Zakim> the conference code is 73394 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), zwu2
15:02:14 <Zakim> sorry, MacTed, I do not recognize a party named 'aabb'
15:02:26 <Zakim> + +1.404.978.aacc
15:02:35 <MacTed> oh! because aabb is already AlexHall
15:02:37 <tomayac> zakim, aacc is me
15:02:42 <Zakim> +tomayac; got it
15:02:49 <MacTed> Zakim, who's here?
15:02:49 <Zakim> On the phone I see davidwood, Sandro, mischat, AndyS, Ivan, AlexHall, MacTed (muted), ??P18, tomayac
15:02:54 <Zakim> On IRC I see zwu2, Scott_Bauer, AlexHall, mischat, mbrunati, Zakim, RRSAgent, danbri, MacTed, cygri, ivan, tomayac, AndyS, sandro, trackbot, davidwood, manu1, yvesr, ericP, manu,
15:02:57 <Zakim> ... NickH
15:03:01 <Zakim> +Souri
15:03:05 <Zakim> + +1.650.265.aadd
15:03:19 <zwu2> zakim, +1.650.265.aadd is me
15:03:19 <Zakim> +zwu2; got it
15:03:28 <davidwood> PROPOSED to accept the minutes of the 24 Aug telecon:
15:03:28 <davidwood> http://www.w3.org/2011/rdf-wg/meeting/2011-08-24
15:03:28 <zwu2> zakim, mute me
15:03:28 <Zakim> zwu2 should now be muted
15:03:39 <Zakim> +??P35
15:03:44 <mischat> davidwood: accepted the minutes from last week, any issues? any objections?
15:03:45 <manu1> zakim, I am ??P35
15:03:45 <Zakim> +manu1; got it
15:04:01 <davidwood> Action item review:
15:04:01 <trackbot> Sorry, couldn't find user - item
15:04:01 <davidwood> http://www.w3.org/2011/rdf-wg/track/actions/pendingreview
15:04:01 <davidwood> http://www.w3.org/2011/rdf-wg/track/actions/open
15:04:03 <Zakim> +Tony
15:04:06 <mischat> davidwood: resolve to accept the minutes now on to the action items
15:04:10 <Souri> Souri has joined #RDF-WG
15:04:18 <Scott_Bauer> Zakim, Tony is me
15:04:18 <Zakim> +Scott_Bauer; got it
15:04:27 <ericP> Zakim, please dial ericP-office
15:04:27 <Zakim> ok, ericP; the call is being made
15:04:29 <Zakim> +EricP
15:04:36 <sandro> action-65?
15:04:36 <trackbot> ACTION-65 -- Sandro Hawke to and Pat to consider what words to add to minimal proposal. -- due 2011-06-29 -- PENDINGREVIEW
15:04:36 <trackbot> http://www.w3.org/2011/rdf-wg/track/actions/65
15:04:43 <gavinc> gavinc has joined #rdf-wg
15:04:44 <mischat> davidwood: we are looking at pending action items, Pat and Sandro to look at "looking for a minimal proposal"
15:05:01 <mischat> http://www.w3.org/2011/rdf-wg/track/actions/71
15:05:16 <mischat> who is speaking ?
15:05:21 <Zakim> + +1.707.861.aaee
15:05:29 <gavinc> Zakim, aaee is me
15:05:29 <Zakim> +gavinc; got it
15:05:43 <mischat> davidwood: the action change from 65 -> 71, was about contacting the provenance WG
15:06:08 <mischat> davidwood: to see what proposal in the g* world would suit their needs.
15:06:28 <mischat> it seems that Guus has made contact to the provenance WG, we are now waiting for them to respond
15:06:49 <mischat> davidwood: Guus seemed to mark the action item as pending review, dave proposing that we close it
15:07:25 <mischat> davidwood: think that this approach of contacting via an action item, as apposed to opening an issue which would have required action from the provenance WG, was the best way forward.
15:07:43 <PatH> PatH has joined #rdf-wg
15:07:49 <mischat> davidwood: Guus seemed to have also closed issue 66, relating to 65
15:07:52 <PatH> Sorry Im late
15:08:06 <AndyS> It's done in email.
15:08:08 <mischat> davidwood, perhaps "update" protocol
15:08:10 <mischat> http://www.w3.org/2011/rdf-wg/track/actions/68
15:08:45 <AndyS> http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0231.html
15:08:52 <mischat> ivan: pierre-A sent regrets, and has provided a review of the sparql 1.1 graphstore protocol
15:09:01 <AlexHall> http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0228.html
15:09:03 <mischat> davidwood: happy to call the action as done
15:09:19 <mischat> pierre-A, provided a review as per action item 68
15:09:28 <LeeF> LeeF has joined #rdf-wg
15:09:28 <mischat> davidwood: 70 and 71 seem to be duplicates
15:09:53 <mischat> ivan: left the work to be done by davidwood
15:09:57 <mischat> http://www.w3.org/2011/rdf-wg/track/actions/75
15:09:58 <Zakim> + +1.617.553.aaff
15:10:06 <LeeF> zakim, aaff is me
15:10:06 <Zakim> +LeeF; got it
15:10:10 <mischat> davidwood: Guss seems to have done action 75
15:10:13 <Zakim> +PatH
15:10:29 <mischat> http://www.w3.org/2011/rdf-wg/track/actions/76
15:10:46 <mischat> PatH: has done action 76
15:11:16 <mischat> danbri: ?
15:11:34 <mischat> s/danbri:/danbri,/
15:11:57 <mischat> davidwood: is performing the .well-known registration action as we speak
15:13:18 <davidwood> http://www.w3.org/2011/rdf-wg/track/actions/68
15:13:37 <mischat> davidwood: as per action 68, it looks like PatH is going to follow the action item
15:13:52 <mischat> davidwood: action item 68 http://www.w3.org/2011/rdf-wg/track/actions/68 points to an email which Pat will look at
15:14:15 <mischat> gavinc: has finished his action item relating to the turtle spec
15:14:21 <mischat> http://www.w3.org/2011/rdf-wg/track/actions/78
15:14:37 <mischat> gavinc: has completed action 78
15:15:12 <mischat> the above action item is about appending the N-triples content as an appendix to the turtle draft
15:15:38 <mischat> davidwood: RDF concepts was published as a FPWD
15:15:39 <mischat> http://www.w3.org/blog/SW/2011/08/30/rdf1-1-concepts-published/
15:15:49 <mischat> davidwood: the above url should be added to our documents page ^^
15:15:57 <davidwood> JSON work progress & planning
15:16:13 <davidwood> Revisit ISSUE 2: http://www.w3.org/2011/rdf-wg/track/issues/2
15:16:14 <mischat> http://www.w3.org/2011/rdf-wg/track/issues/2
15:16:29 <PatH> zakim, mute me
15:16:29 <Zakim> PatH should now be muted
15:16:42 <mischat> davidwood: following on from last week, issue 2 is pending, in terms of what what this WG should do re: JSON and RDF
15:16:46 <Zakim> +??P45
15:16:54 <NickH> Zakim, ??P45 is me
15:16:54 <Zakim> +NickH; got it
15:17:07 <mischat> so, the current position as of the f2f is a note for JSON-LD, and rec for Talis JSON
15:17:24 <mischat> davidwood: is proposing that we don't make a rec of the Talis JSON work
15:17:28 <LeeF> Happy with that!
15:17:35 <mischat> and to wait on the incubation of JSON-LD
15:18:08 <mischat> ivan: tried to summarise last weeks discussion. Feeling that that this group might not be best placed to produce a JSON document
15:18:10 <davidwood> Proposal: Change ISSUE-2 resolution to (a) Not move RDF/JSON to REC.
15:18:21 <mischat> ivan: due to not having active JSON folks
15:18:39 <NickH> ivan, not sure that we all agreed about lack of JSON experience
15:18:57 <mischat> ivan: post meeting, there was discussion on the mailing, the conclusion being that JSON-LD might suffice all of the use-case we had for JSON RDF stuff
15:19:37 <mischat> ivan: 1. this group won't produce to a JSON RDF spec, and we would try to spin off the JSON-LD work into a community group
15:20:01 <mischat> ivan: the community group might attract the right people
15:20:46 <ivan> q+
15:20:52 <manu1> q+
15:20:54 <davidwood> ack Ivan
15:20:57 <mischat> davidwood: saw lots of people reaction re: JSON from within the WG. Why don't we ask people from the JSON community group to join our WG
15:20:57 <gavinc> +q to avoid this question for now
15:21:09 <mischat> davidwood: so that we can push this JSON work forward
15:21:51 <mischat> ivan: looking at the core JS/JSON community, they might have difficult to communicate with the diehard RDF group
15:22:08 <PatH> fwiw, i feel that this group should have a final sign-off, since there may be issues of formal compliance which the json folk simply dont care about, but we do.
15:22:16 <mischat> ivan: wonders if they will find it hard to communicate with the RDF folks
15:22:37 <davidwood> ack manu1
15:22:44 <mischat> ivan: doesn't think from a social point of view any liaison would be ideal
15:23:15 <mischat> manu1: there seems to be a strange barrier between the two groups. This is due to camps when people think about RDF and JSON
15:23:38 <mischat> manu1: 1. people which have triplestore and the SW stack, and their needs re: transporting RDF via JSON
15:24:33 <mischat> manu1: 2. the other group. People just getting into the linked data world. They can't afford the engineering effort to get stuck into the full SW tech stack. These folks don't want to use RDF, they want to use JSON
15:25:06 <mischat> manu1: they may find it neat that RDF folks might be able to use their JSON
15:25:25 <mischat> manu1: manu's company falls into the 2nd community
15:26:16 <mischat> manu1: believes that group 2, and not interested in helping people which have requirements such as "we have to make it work with our triplestore", or "we need to make our JSON talk to our RDF data"
15:26:21 <LeeF> manu1++
15:26:50 <mischat> manu1: believes that we need to incubate the work, and that we should move people from the RDF WG to the community group
15:27:02 <manu1> q+
15:27:03 <PatH> listening to this social discussion makes me wonder if it might just not be the right time to standardize this stuff.
15:27:16 <davidwood> ack gavinc
15:27:16 <Zakim> gavinc, you wanted to avoid this question for now
15:27:30 <davidwood> ack manu1
15:27:37 <mischat> ivan: thinks that the community should push the work forward, and that when the JSON CG are ready they should present their work to the WG
15:27:59 <mischat> manu1: doesn't think that this WG is the right place to push the work forward
15:28:23 <PatH> I have exactly the dual concertn.
15:28:29 <PatH> concern.
15:28:39 <mischat> manu1: is worried about that when the JSON CG thinks they are finished, they are going to have changes imposed by the RDF WG
15:29:01 <mischat> manu1: thinks that moving specs between groups won't be a fruitful activity
15:30:12 <gavinc> http://www.w3.org/community/groups/proposed/ ;)
15:30:20 <mischat> davidwood: thinks we should clean up issue two before we press on
15:30:31 <PatH> we are falling into a black hole of premature optimization. This standard will be obsolete within a year.
15:30:33 <mischat> ivan: doesn't think we need to recharter
15:30:52 <AndyS> q+ to ask what's the status of "make a Note on current practice stuff like Linked Data API" in issue/2 ?
15:31:00 <davidwood> ack AndyS
15:31:00 <Zakim> AndyS, you wanted to ask what's the status of "make a Note on current practice stuff like Linked Data API" in issue/2 ?
15:31:10 <mischat> davidwood: proposes that we vote, to remove "moving JSON from the rec"
15:31:39 <mischat> AndyS: is asking about the "note current practice stuff like Linked Data API" ?
15:31:49 <mischat> davidwood: thinks that the issue there is that we don't have an editor
15:32:14 <AndyS> q+
15:32:35 <Zakim> +??P0
15:32:56 <mischat> davidwood: proposed that we make no resolution to "to move RDF JSON to rec"
15:33:00 <AndyS> q+ to ask if we are going to advance it as a NOTE in the meantime or just pause work on it?
15:33:06 <yvesr> Zakim, ??P0 is me
15:33:06 <Zakim> +yvesr; got it
15:33:09 <davidwood> ack AndyS
15:33:09 <Zakim> AndyS, you wanted to ask if we are going to advance it as a NOTE in the meantime or just pause work on it?
15:33:13 <mischat> davidwood: i.e. we remove that statement from the resolution, so that we can push on
15:33:40 <mischat> AndyS: what do you mean by "not move to rec" ?
15:33:54 <Zakim> +aharon
15:34:06 <mischat> davidwood: is proposing that we do no work on the RDF JSON, i.e. we hold off on all work, until we know what we are going to do in terms of RDF and JSON
15:34:06 <PatH> yvesr, we are just fixing peace in the middle east.
15:34:48 <mischat> davidwood: just clarified that by "not moving to rec", does not mean "writing a note" it means "holding off work on the JSON RDF stuff for now"
15:35:07 <davidwood> Proposed to remove the words "make a REC on something like Talis RDF/JSON" from the resolution to ISSUE-2
15:35:14 <tomayac> +1
15:35:16 <manu1> +1
15:35:17 <ivan> +1
15:35:18 <MacTed> +1
15:35:19 <mischat> mischat: +1
15:35:20 <sandro> +1
15:35:20 <zwu2> +1
15:35:20 <PatH> +1
15:35:22 <mbrunati> +1
15:35:24 <AlexHall> +1
15:35:24 <gavinc> +1 (TQ)
15:35:28 <LeeF> +1
15:35:33 <NickH> +1
15:36:04 <yvesr> +1
15:36:15 <mischat> the proposal is resolved. We are going to remove the words "make a REC on something like Talis RDF/JSON"
15:36:23 <manu1> q+ to ask about JSON-LD Community Group
15:36:24 <mischat> davidwood: will fix the issue on the wiki
15:36:30 <gavinc> Zakim, mute me
15:36:31 <Zakim> gavinc should now be muted
15:36:54 <mischat> davidwood: has updated issue2
15:37:01 <davidwood> ISSUE-76 Empty Lexical Space Disagreement
15:37:01 <davidwood> http://www.w3.org/2011/rdf-wg/track/issues/76
15:37:39 <PatH> zakim, unmute me
15:37:39 <Zakim> PatH should no longer be muted
15:37:42 <mischat> davidwood: can PatH summarise issue 76
15:37:51 <manu1> q-
15:38:30 <mischat> PatH: the intent for an empty lexical, so that any class name can be delivered as a datatype
15:39:12 <mischat> PatH: this causes problems, because an empty lexical returned will never be a suitable answer to a useful question
15:39:51 <mischat> davidwood: Richard seemed to suggest that if we modified Concepts we would have to touch XSD
15:41:03 <mischat> davidwood: given that xsd is normative, we can't be changing that
15:41:28 <mischat> PatH: believes that this discussion has yet to come up before in the RDF world nor in the XSD world
15:41:41 <davidwood> Pat wrote: 3. No literal can denote any value in the value space of ex:empty.
15:42:17 <davidwood> Antoine wrote: Point 3 is not correct. For instance, owl:real has an empty lexical space (as pointed out by Andy) and yet, there are plenty of literals that can denote a real number. "2"^^xsd:integer, "1.2"^^xsd:decimal, "1/3"^^owl:rational all denote elements of the value space of owl:real.
15:42:59 <mischat> PatH: should have been more clear, you can't have a literal with that datatype
15:44:47 <mischat> PatH: if we really want to allow empty lexical spaces, pat can update the semantic docs, but there would be a running thread of "assuming not an empty lexical space"
15:45:04 <ivan> q+
15:45:11 <mischat> AndyS: asks where in the Semantics document would be need to be updates
15:45:31 <mischat> PatH: said that he would go through the Semantics documents to see what needs changing
15:47:01 <mischat> PatH: if we believes this is bug, he can make the changes to semantics, and will update the text
15:47:10 <davidwood> q?
15:47:26 <mischat> PatH: notes that there is a conflict with the semantics and concepts.
15:47:40 <mischat> davidwood: this that the core documents should agree is the salient point here
15:48:12 <mischat> davidwood: doesn't believe that the resolution of this issue relies on the resolution of issue-12
15:48:27 <mischat> davidwood: asked PatH whether he would need to wait for a resolution on issue12
15:48:33 <mischat> PatH: said no
15:48:36 <davidwood> ack ivan
15:49:31 <mischat> PatH: taking a step backwards on the language-tag issues, 2 or 3 solutions which have been put forward. And ivan feels that the various solutions are a matter of taste
15:50:10 <mischat> ivan: i thinks that we should put up a poll, where by the solutions are described in full, and then post poll, we should go with the solution the WG voted for
15:50:53 <mischat> PatH: thinks we are talking about different things, we are still talking about the disagreement between RDF semantics and concept.
15:51:02 <mischat> ivan: acknowledges this.
15:51:15 <mischat> davidwood: asked PatH to work out the details with peter
15:51:40 <mischat> resolution PatH has agreed to make the changes to the RDF Semantics and is happy to confirm the details with peter
15:51:40 <davidwood> RESOLVED ISSUE-76: Pat Hayes (RDF Semantics editor) has agreed to make this change to RDF Semantics and will confirm the details with Peter.
15:52:00 <PatH> e
15:52:12 <PatH> zakim, mute me
15:52:12 <Zakim> PatH should now be muted
15:52:13 <davidwood> ISSUE-12 language-tagged literals
15:52:15 <mischat> davidwood: onto language tag literals now …
15:52:38 <mischat> ivan: proposed to setup a poll, with the 2-3 alternatives made explicit, and then the working group can move forward
15:52:57 <mischat> ivan: doesn't think that the proposals are all the same from an end-user point of view
15:53:17 <mischat> davidwood: thinks we have a summary of options, done by PatH on the 18th
15:53:31 <davidwood> http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0066.html
15:53:31 <PatH> I will draft an email summarizing, for each alternative, what the pain points of that one are. There are some more alternatives now.
15:53:41 <mischat> sandro: asked how he can find both PatH's and Pierre-A's summary
15:54:05 <PatH> yes, and more uptodate
15:54:20 <mischat> PatH: said he would draft an email summarising for each alternative, a more up-to-date summary
15:54:25 <davidwood> Antoine's summary: http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0181.html
15:54:36 <mischat> ivan: thinks that a poll is the way forward
15:54:38 <PatH> i agree about the poll.
15:54:58 <PatH> its my old action re-opened :-)
15:55:04 <SteveH> SteveH has joined #rdf-wg
15:55:22 <PatH> I will try to be objective, but good idea.
15:55:35 <PatH> glad i am muted, guys.
15:55:47 <PatH> fofl here
15:56:04 <mischat> sandro: voices concerns about PatH's biased coming through too strongly in his summary, and would like that someone which doesn't agree with Pat would also chip in
15:56:15 <PatH> yes.
15:56:26 <PatH> will do
15:56:45 <mischat> sandro: would like pierreA and PatH to work together to to produce the summary, as per sandro's suggestion
15:57:13 <PatH> I have to leave in few minutes.
15:57:27 <mischat> action PatH to work with pierreA to produce a summary of options re: language tags
15:57:28 <trackbot> Created ACTION-80 - Work with pierreA to produce a summary of options re: language tags [on Patrick Hayes - due 2011-09-07].
15:57:44 <mischat> action ivan to set up a poll when PatH and Pierre are done with action 80
15:57:44 <trackbot> Sorry, amibiguous username (more than one match) - ivan
15:57:44 <trackbot> Try using a different identifier, such as family name or username (eg. ivan, imikhail)
15:58:32 <davidwood> action ivanh to set up a poll when PatH and Pierre are done with action 80
15:58:32 <trackbot> Sorry, couldn't find user - ivanh
15:58:55 <mischat> action ivanherman to set up a poll when PatH and Pierre are done with action 80
15:58:55 <trackbot> Sorry, couldn't find user - ivanherman
15:59:00 <PatH> does case matter?
15:59:26 <mischat> action ivanh to set up a poll when PatH and Pierre are done with action 80
15:59:26 <trackbot> Sorry, couldn't find user - ivanh
15:59:41 <PatH> :-)
16:00:05 <davidwood> http://www.w3.org/2011/rdf-wg/track/actions/81
16:00:23 <PatH> hey, I have to leave. If i get any more actions, send me an email.
16:00:34 <mischat> davidwood: now we are ending on triples
16:00:35 <gavinc> zakim, unmute me
16:00:35 <Zakim> gavinc should no longer be muted
16:00:44 <davidwood> N-Triples
16:00:46 <mischat> davidwood: been thinking about Lee's position on triples
16:00:53 <Zakim> -PatH
16:00:58 <gavinc> Topic: N-Triples
16:01:34 <mischat> davidwood: from a big vendor perspective, oracles perspective is valid, they don't want to break running code, and they don't want to confuse users
16:01:40 <AlexHall> s/Lee/zhe
16:01:42 <mischat> thanks
16:01:43 <zwu2> it is me (Zhe) ivan
16:01:55 <zwu2> hey :)
16:02:11 <mischat> davidwood: wants to move forward re: aligning RDF and internationalisation
16:02:55 <ivan> q+
16:02:56 <MacTed> a fairly clear proposal on this from Richard -- http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0170.html
16:02:56 <mischat> davidwood: it seems to davidwood the best way to move forward to create a UTF-8 version of ntriples ?
16:03:01 <zwu2> zakim, unmute me
16:03:01 <Zakim> zwu2 should no longer be muted
16:03:05 <zwu2> q+
16:03:07 <mischat> davidwood: does this sound like a good idea to people ?
16:03:14 <davidwood> ack zwu
16:04:16 <mischat> zwu2: oracle are chatting internally about internationalisation and ntriples. and how this can go forward
16:04:46 <mischat> zwu2: believes that an ascii ntriples, uft8 triples, and turtle should suffice
16:04:52 <davidwood> ack ivan
16:05:07 <mischat> davidwood: the down side to what zwu2 said is that we would have more docs
16:05:08 <NickH> Having more formats isn't a great situation to be in
16:05:13 <NickH> there are quite a lot already
16:05:49 <mischat> ivan: so we wouldn't have multiple documents, it just would be a note in the turtle doc
16:05:55 <mischat> q+
16:05:57 <gavinc> +q to mention that N-Triples is NOT well specified at the moment, and has no specific media type.
16:06:48 <Souri> something like: N-Triple, Turtle, Turtle/N-Triple (N-Triple subset of Turtle that also allows UTF-8)
16:06:57 <mischat> zwu2: this note, would be fine with oracle, but leaving ntriples as ascii would be great, they don't object to having another utf8 ntriples format
16:07:03 <yvesr> NickH, +1
16:07:24 <davidwood> Zwu: Oracle does not object to creating a new version of ntriples with UTF-8 encoding, as long as ASCII-encoded ntriples remains an option.
16:07:26 <mischat> zwu2: as long as the ascii encode triples remains an option
16:07:41 <davidwood> ack mischat
16:07:41 <AndyS> That is possible via "application/n-triples;charset=ascii"
16:07:44 <mischat> zwu2: oracle wants to ensure that existing software doesn't break
16:07:46 <ericP> not sure that "remains an option" captures "has a distinct name", which i think they require
16:07:46 <NickH> do we have to standardise ascii N-Triple at all then?
16:08:25 <yvesr> zwu2, maybe stupid question - but does oracle actually support ntriples escaping, currently?
16:08:38 <zwu2> yes yvesr
16:08:39 <ivan> q+
16:08:45 <davidwood> ack gavinc
16:08:45 <Zakim> gavinc, you wanted to mention that N-Triples is NOT well specified at the moment, and has no specific media type.
16:08:49 <NickH> mischat, it is easier to make an N-Triples parser than a Turtle parser - very useful to specifiy a subset
16:08:52 <ericP> manu1, i suspect it more about whether you can write UTF-8 N-Triples and act surprised when Oracle's tools don't swallow it
16:09:46 <mischat> gavinc: according the grammar, almost all of the test cases, they don't adhere to the grammar
16:10:11 <ericP> yeah, almost a branding issue
16:10:19 <mischat> gavinc: doesn't think that people are using ntriples as specified
16:10:51 <ericP> i'd say it's useful to have a label which unambiguously advertises to your capabilities to your users
16:11:20 <yvesr> and what about just versioning the spec?
16:11:33 <mischat> gavinc: states that the "ntriples" mutli-encoding spec could state how each of the encoding could be used
16:11:55 <ericP> yvesr, prob is that v1 doesn't have a version identifier
16:11:57 <manu1> q+ to suggest two levels of conformance - ASCII and UTF-8.
16:12:06 <AndyS> EricP : isn't that label ";charset=ascii"? What about "text/turtle;charset=ascii"
16:12:09 <mischat> davidwood: notes that there is a difference between a standard and a vendor specific serialisation
16:12:16 <yvesr> ericP, we could refer to it using its date (like rdf 2004)?
16:12:22 <ericP> AndyS, that's pretty compelling
16:12:43 <NickH> davidwood++
16:13:05 <mischat> davidwood: we are chartered to standardising turtle, and we have the chance to align ntriples with current internationalisation efforts
16:13:11 <ericP> write "ASCII Turtle" on the box and "Accept: text/turle;charset=ascii"
16:14:32 <AlexHall> zhe, over what interface does Oracle accept N-Triples documents? is it even HTTP?
16:14:44 <mischat> gavinc: doesn't think that we need two specs, we can state that ntriples can be used either with ascii or utf8
16:14:49 <NickH> even if it doesn't get standardised people will produce and parse N-Triples as utf8, rightly or wrongly
16:15:20 <davidwood> ack ivan
16:15:41 <mischat> zwu2: oracles wants to be able to say that they support a standard. 2 levels of affordances to the ntriples serialisations.
16:15:59 <manu1> q-
16:16:00 <Souri> I am happy with the choices: N-Triple (classic - unchanged), Turtle, Turtle/N-Triple (N-Triple subset of Turtle that also allows UTF-8)
16:16:00 <mischat> ivan: would we have a mime type for utf8 ntriples
16:16:02 <gavinc> N-Triples Prime at the moment
16:16:14 <Souri> I am happy with the choices: N-Triple (classic - unchanged), Turtle, Turtle/N-Triple (N-Triple subset of Turtle that also allows UTF-8)
16:16:17 <manu1> q+ to make one final note about JSON-LD CG and RDF WG.
16:16:26 <mischat> ivan: 2 media types: one for turtle and one for ntriples
16:17:06 <mischat> ivan: the question would be, would we define a third mime type for triples ascii?
16:17:31 <Souri> +1 agree to Ivan
16:17:45 <mischat> gavinc: ntriples is not recommended as a transfer medium
16:18:04 <AndyS> (cough) N-Triples does have a media type - it's text/plain (sec 3).
16:18:14 <MacTed> Zakim, unmute me
16:18:14 <Zakim> MacTed should no longer be muted
16:18:17 <gavinc> exactly
16:18:25 <MacTed> http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0170.html
16:18:30 <gavinc> it intentionally did not have one
16:18:36 <mischat> MacTed: richard's very clear proposal ^^
16:20:16 <mischat> gavinc: is pretty sure that richard's proposal has been added to turtle's current editor's draft (n-triples prime)
16:20:26 <gavinc> http://dvcs.w3.org/hg/rdf/raw-file/n-triples/rdf-turtle/index.html
16:21:07 <mischat> davidwood: would we leave the ntriples in test-cases? and would be only have ntriples prime in the turtle doc?
16:21:10 <davidwood> PROPOSED: Create a UTF version of ntriples in the Turtle REC, while making clear that the ASCII version of ntriples is still acceptable for use. ASCII ntriples would continue to live in the test cases document. File extensions and media types should be in conformance to the proposal at http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0170.html
16:21:26 <yvesr> i wonder why oracle breaking 'standards compliance' would be an issue, as there's no w3c rec for ntriples atm?
16:21:26 <ivan> +1
16:21:38 <gavinc> -1 To N-Triples still being in Test Cases
16:21:39 <yvesr> +0
16:21:53 <LeeF> abstain
16:22:06 <mischat> zwu2: asking him whether the ascii-ntriples goes into the rec ?
16:22:12 <zwu2> +1
16:22:40 <LeeF> I don't care from a Cambridge Semantics point of view, but I don't think it's that helpful to the world to have 2 versions of n-triples
16:23:10 <yvesr> LeeF, +1
16:23:11 <LeeF> :-)
16:23:36 <MacTed> +1 to overall proposal ... thinking that UTF-8 ntriples should then also be added to Test Cases
16:23:43 <NickH> Could we have a new thing with a new name that is Ntriples Utf8?
16:23:45 <mischat> gavinc: as an editor thinks we can specify a version of ntriples which can support ascii
16:23:54 <AndyS> +0.75 (one form, use charset to disambiguiate)
16:24:08 <NickH> and never standardise N-triples ASCII
16:24:26 <LeeF> To me, having one version of a technology feels more important than unanimous consensus on an issue like this
16:24:44 <LeeF> (And I don't care which version it is. :-)
16:24:46 <manu1> +0
16:24:46 <mischat> mischat: i agree with AndyS here, one media type and charset to disambiguate seems like the right thing
16:24:52 <mischat> mischat: +0.2
16:24:59 <Souri> A new name for the extended version: possible choices: N-Triples Prime, N-Triples/UTF-8
16:25:06 <manu1> +0 (not a clear idea of the rammifications of the proposal)
16:26:05 <Souri> Another choice for name: Turtle/N
16:26:13 <mischat> davidwood: ntriples is not prohibited as something going across the wire
16:26:47 <manu1> what about this - PROPOSAL: Allow two levels of conformance in N-Triples - people MAY use ASCII-only, but UTF-8 is RECOMMENDED.
16:26:52 <gavinc> -0.5
16:26:56 <AndyS> ASCII N-triples , UTF-8 N-triples :: common name "N-triples" -- market decides exactly the def of common name.
16:27:09 <mischat> yup
16:27:19 <AndyS> +1 to manu1
16:27:29 <manu1> q-
16:27:55 <mischat> davidwood: resolve we would have two version of ntriples, a utf8 and a us-ascii one
16:28:12 <mischat> so that oracle's software won't break
16:28:13 <manu1> I just wanted to say: I hope I didn't have too much of an anti-RDF vibe in what I said - I have a great deal of respect for the people in this group. I just don't think that this group is the right one to standardize the JSON-LD work.
16:28:18 <yvesr> bye!
16:28:20 <Zakim> -Scott_Bauer
16:28:22 <Zakim> -Ivan
16:28:22 <davidwood> RESOLVED: Create a UTF version of ntriples in the Turtle REC, while making clear that the ASCII version of ntriples is still acceptable for use. ASCII ntriples would continue to live in the test cases document. File extensions and media types should be in conformance to the proposal at http://lists.w3.org/Archives/Public/public-rdf-wg/2011Aug/0170.html
16:28:23 <mischat> zwu2: just thanked gavinc for his hardwork
16:28:23 <Zakim> -MacTed
16:28:24 <Zakim> -yvesr
16:28:25 <Zakim> -Sandro
16:28:27 <Zakim> -AlexHall
16:28:30 <Zakim> -gavinc
16:28:31 <mbrunati> bye
16:28:34 <Zakim> -Souri
16:28:36 <Zakim> -EricP
16:28:36 <Zakim> -LeeF
16:28:37 <AlexHall> AlexHall has left #rdf-wg
16:28:38 <Zakim> -davidwood
16:28:40 <Zakim> -zwu2
16:28:42 <Zakim> -mischat
16:28:44 <Zakim> -??P18
16:28:45 <Zakim> -NickH
16:28:50 <davidwood> RRSAgent, make minutes
16:28:50 <RRSAgent> I have made the request to generate http://www.w3.org/2011/08/31-rdf-wg-minutes.html davidwood
16:29:07 <Zakim> -AndyS
16:30:29 <mischat> do i need to do more stuff
16:30:30 <mischat> ?
16:30:46 <mischat> i have only been an on incubator group with harry before
16:31:02 <mischat> we did no post-scribe tidy-ups :)
16:31:10 <davidwood> I think that's it. Thanks for scribing!
16:31:16 <mischat> np
16:31:43 <mischat> mischat has joined #rdf-wg
17:17:43 <mbrunati> mbrunati has joined #rdf-wg
17:32:17 <Zakim> -tomayac
17:33:10 <Zakim> -manu1
17:33:38 <manu1> zakim, who is on the call?
17:33:38 <Zakim> On the phone I see aharon
17:33:45 <manu1> zakim, drop aharon
17:33:45 <Zakim> aharon is being disconnected
17:33:47 <Zakim> SW_RDFWG()11:00AM has ended
17:33:48 <Zakim> Attendees were +1.540.898.aaaa, Sandro, mischat, AndyS, Ivan, +1.443.212.aabb, davidwood, AlexHall, MacTed, +1.404.978.aacc, tomayac, Souri, zwu2, manu1, Scott_Bauer, EricP,
17:33:51 <Zakim> ... +1.707.861.aaee, gavinc, +1.617.553.aaff, LeeF, PatH, NickH, yvesr, aharon
19:45:34 <Zakim> Zakim has left #rdf-wg
20:17:37 <tomayac> tomayac has joined #rdf-wg
20:36:11 <tomayac> tomayac has joined #rdf-wg
21:31:40 <tomayac> tomayac has joined #rdf-wg
21:35:05 <mischat> mischat has joined #rdf-wg
22:38:22 <tomayac> tomayac has joined #rdf-wg
# SPECIAL MARKER FOR CHATSYNC. DO NOT EDIT THIS LINE OR BELOW. SRCLINESUSED=00000483
</nowiki></pre>

F2F2

Mtiffiel — Tue, 06 Sep 2011 14:15:53 GMT

Mtiffiel: /* Participants */ added mischa to the BBC location thing

Scheduled for 12-13 October 2011 at W3C offices at MIT, Stata Center.

See the (closed) poll results at: http://www.w3.org/2002/09/wbs/46168/RDFWGFTF2/results

== Accommodation ==

The meeting will be held in the [http://en.wikipedia.org/wiki/Stata_Center Stata Center] at MIT, at [http://maps.google.com/maps?client=ubuntu&channel=fs&q=32+vassar+st+cambridge+ma&oe=utf-8&um=1&ie=UTF-8&hq=&hnear=0x89e370abe1db5703:0xd3b042dc26a8b515,32+Vassar+St,+Cambridge,+MA+02139&gl=us&ei=JbVgTquCDYXegQfE9-GuAQ&sa=X&oi=geocode_result&ct=title&resnum=3&ved=0CCQQ8gEwAg 32 Vassar St, Cambridge, MA], across the river from Boston, Massachusetts, USA. The meeting is close to the "Kendall" stop on the [http://mbta.com/schedules_and_maps/subway/lines/?route=RED MBTA Red Line] subway.

When booking at a local hotel, be sure to ask for the MIT rate, which is often 10% cheaper.

* Visiting MIT page: http://web.mit.edu/visit/stay.html
* 463 Beacon Street Guest House, Back Bay, http://www.463beacon.com/

== Participants ==

; Intend to attend (you must sign up to get Internet access, food, ...)
: David Wood
: Guus Schreiber
: Scott Bauer
: Dan Brickley (tentative - really not sure yet, depends on timing, location, funding, ...)
: Ted Thibodeau (tentative. more likely if in Boston than in Murray Hill; much less likely if in CA)
: Zhe Wu(tentative)
: Gavin Carothers
: Alex Hall

; Intend to attend from BBC location
: Yves Raimond
: Nicholas Humfrey
: Thomas Steiner
: Ivan Herman
: Steve Harris
: Richard Cyganiak
: Pierre-Antoine Champin
: Andy Seaborne
: Mischa Tuffield

; Intend to attend remotely
: Matteo Brunati

; Regrets
: Fabien Gandon
: Antoine Zimmermann

; At risk
: Peter F. Patel-Schneider (probable regrets)
: Eric Prud'hommeaux

== Possible remote participation from UK ==

We're looking into organizing a second location from where Europeans could jointly remote-participate. If you're interested in joining such a meeting (tentatively: London, UK), then please add your name here:

* Thomas Steiner

Editors

Mtiffiel — Wed, 20 Apr 2011 17:33:02 GMT

Mtiffiel: /* Turtle Syntax */ de-nominated myself as one of the editors of Turtle... time constraints wont allow me to do a thorough job

== RDF Concepts ==
* Richard Cyganiak
* David Wood

== RDF Semantics ==
* Peter Patel-Schneider
* TDB: ACTION-36 to ask Pat Hayes (http://www.w3.org/2011/rdf-wg/track/actions/36)

== RDF Vocabulary ==
* Dan Brickley
NB: See ISSUE-36 re name change to RDF Schema (http://www.w3.org/2011/rdf-wg/track/issues/36)

== Turtle Syntax ==
* Eric Prud'hommeaux
* Gavin Carothers

== N-Triples Syntax ==
* Zhe Wu
* Souripriya Das
NB: See Andy S's page: http://www.w3.org/2011/rdf-wg/wiki/N-Triples-Format

== RDF JSON Syntax ==
* Thomas Steiner
* TBD: possibly someone from Talis

== JSON Recipes Note ==
* Mischa Tuffield
* Nick Humfrey
* Matteo Brunati
* TBD: One of Guus' postdocs
* Yves Raimond

== RDF Primer ==
* Guus Schreiber
* Fabien Gandon
* Many other contributors, including Pierre-Antoine Champin, Christopher Matheus

== TriG/N-Quads Syntax (may be part of Turtle doc) ==
* Richard Cyganiak

== RDF/XML Syntax Errata ==
* Fabien Gandon

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 22:37:08 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ changed ordering added allegrograph json in previous commit

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestores can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

It should be noted that this table illustrates the RDF parsing/serialising capabilities of the various systems, most of which use 3rd party libraries to perform these operations.

{| border="1" align="center"
! Triplestore
| rdfxml
| ntriples
| nquads
| turtle
| trig
| trix
| n3
| rdfa
| grddl
| json 0
| json 1
| json 2
| Notes
|-
| [http://4store.org/ 4store/5store]
| I O
| I O
| I
| I O
| I
|
|
| I
| I
| O ([http://mmt.me.uk/misc/example.json.ttl example json])
| O ([http://mmt.me.uk/misc/example.json-triples.ttl example jsontriples ])
|
| uses [http://librdf.org/raptor/ libraptor]
|-
| [http://www.franz.com/agraph/allegrograph/ Allegrograph]
| I O
| I O
| I
|
|
| I O
| I O
|
|
| O [http://mmt.me.uk/misc/allegro.example.json json serialised N-Triples]
|
|
|
|-
| [http://www.openanzo.org/ Anzo]
| I O
| I
|
| I O
| I O
|
|
|
|
| O custom triple-based format
|
|
| also bundles [http://www.openrdf.org/ Sesame] serialisers
|-
| [http://incubator.apache.org/jena Apache Jena]
| I O
| I O
| I O
| I O
| I
|
| I
| I *
| I *
|
|
|
|
|-
| [https://github.com/semsol/arc2/wiki ARC2]
| I O
| I O
|
| I O
|
|
|
| I
|
| O ([http://mmt.me.uk/misc/arc2.example.json example json])
|
|
|
|-
| [http://www.systap.com/bigdata.htm BigData]
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
|-
| [http://www.mulgara.org/ Mulgara]
| I O
| I O
|
| I
|
|
| I
| I
|
| O json(application/sparql-results+json with "subject" "predicate" "object" variables)
|
|
|
|-
| [http://www.oracle.com/pls/db112/homepage Oracle 11g Release 2]
| I O
| I O
| I O
| I O
| I O
|
| I
| I
|
|
|
|
| uses [http://jena.sourceforge.net/ Jena/Joseki], [http://www.openrdf.org/ Sesame]
|-
| [http://www.ontotext.com/owlim/change_log.html OWLIM]
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| uses [http://www.openrdf.org/ Sesame's Rio parser]
|-
| [http://rdf.rubyforge.org/ RDF.rb]
| I O
| I O
|
| I O
|
| I O
| I O
| I O
|
| I O ([http://mmt.me.uk/misc/rdfrb.example.json example json])
|
|
| Supports [http://librdf.org/raptor/ libraptor] based plugins
|-
| [http://search.cpan.org/dist/RDF-Query/ RDF::Query]
| I O
| I O
| I O
| I O
| I
|
|
| I
|
| I O ([http://mmt.me.uk/misc/rdfquery.example.json example json])
|
|
| uses [http://search.cpan.org/dist/RDF-Trine/ RDF::Trine]
|-
| [http://www.openrdf.org/ Sesame]
| I O
| I O
| I *
| I O
| I O
| I O
|
| I *
|
|
|
|
|
|-
| [http://virtuoso.openlinksw.com/ Virtuoso]
| I O
| I O
| I
| I O
| I
|
| I O
| I
| I
| I O ([http://mmt.me.uk/misc/virtuoso.example.json example json])
|
|
|
|}

'''"*"''' implies plugin

'''"I"''' RDF import supported

'''"O"''' RDF serialisations available via SPARQL CONSTRUCT

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 22:31:33 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestores can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

It should be noted that this table illustrates the RDF parsing/serialising capabilities of the various systems, most of which use 3rd party libraries to perform these operations.

{| border="1" align="center"
! Triplestore
| rdfxml
| ntriples
| nquads
| turtle
| trig
| trix
| n3
| rdfa
| grddl
| json 0
| json 1
| json 2
| Notes
|-
| [http://4store.org/ 4store/5store]
| I O
| I O
| I
| I O
| I
|
|
| I
| I
| O ([http://mmt.me.uk/misc/example.json.ttl example json])
| O ([http://mmt.me.uk/misc/example.json-triples.ttl example jsontriples ])
|
| uses [http://librdf.org/raptor/ libraptor]
|-
| [http://www.openanzo.org/ Anzo]
| I O
| I
|
| I O
| I O
|
|
|
|
| O custom triple-based format
|
|
| also bundles [http://www.openrdf.org/ Sesame] serialisers
|-
| [http://www.franz.com/agraph/allegrograph/ Allegrograph]
| I O
| I O
| I
|
|
| I O
| I O
|
|
| O [http://mmt.me.uk/misc/allegro.example.json json serialised N-Triples]
|
|
|
|-
| [https://github.com/semsol/arc2/wiki ARC2]
| I O
| I O
|
| I O
|
|
|
| I
|
| O ([http://mmt.me.uk/misc/arc2.example.json example json])
|
|
|
|-
| [http://www.systap.com/bigdata.htm BigData]
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
|-
| [http://incubator.apache.org/jena Apache Jena]
| I O
| I O
| I O
| I O
| I
|
| I
| I *
| I *
|
|
|
|
|-
| [http://www.mulgara.org/ Mulgara]
| I O
| I O
|
| I
|
|
| I
| I
|
| O json(application/sparql-results+json with "subject" "predicate" "object" variables)
|
|
|
|-
| [http://www.oracle.com/pls/db112/homepage Oracle 11g Release 2]
| I O
| I O
| I O
| I O
| I O
|
| I
| I
|
|
|
|
| uses [http://jena.sourceforge.net/ Jena/Joseki], [http://www.openrdf.org/ Sesame]
|-
| [http://www.ontotext.com/owlim/change_log.html OWLIM]
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| uses [http://www.openrdf.org/ Sesame's Rio parser]
|-
| [http://rdf.rubyforge.org/ RDF.rb]
| I O
| I O
|
| I O
|
| I O
| I O
| I O
|
| I O ([http://mmt.me.uk/misc/rdfrb.example.json example json])
|
|
| Supports [http://librdf.org/raptor/ libraptor] based plugins
|-
| [http://search.cpan.org/dist/RDF-Query/ RDF::Query]
| I O
| I O
| I O
| I O
| I
|
|
| I
|
| I O ([http://mmt.me.uk/misc/rdfquery.example.json example json])
|
|
| uses [http://search.cpan.org/dist/RDF-Trine/ RDF::Trine]
|-
| [http://www.openrdf.org/ Sesame]
| I O
| I O
| I *
| I O
| I O
| I O
|
| I *
|
|
|
|
|
|-
| [http://virtuoso.openlinksw.com/ Virtuoso]
| I O
| I O
| I
| I O
| I
|
| I O
| I
| I
| I O ([http://mmt.me.uk/misc/virtuoso.example.json example json])
|
|
|
|}

'''"*"''' implies plugin

'''"I"''' RDF import supported

'''"O"''' RDF serialisations available via SPARQL CONSTRUCT

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 10:21:44 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ added in some hyperlinks to stuff

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestores can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

It should be noted that this table illustrates the RDF parsing/serialising capabilities of the various systems, most of which use 3rd party libraries to perform these operations.

{| border="1" align="center"
! Triplestore
| rdfxml
| ntriples
| nquads
| turtle
| trig
| trix
| n3
| rdfa
| grddl
| json 0
| json 1
| json 2
| Notes
|-
| [http://4store.org/ 4store/5store]
| I O
| I O
| I
| I O
| I
|
|
| I
| I
| O ([http://mmt.me.uk/misc/example.json.ttl example json])
| O ([http://mmt.me.uk/misc/example.json-triples.ttl example jsontriples ])
|
| uses [http://librdf.org/raptor/ libraptor]
|-
| [http://www.openanzo.org/ Anzo]
| I O
| I
|
| I O
| I O
|
|
|
|
| O custom triple-based format
|
|
| also bundles [http://www.openrdf.org/ Sesame] serialisers
|-
| [http://www.franz.com/agraph/allegrograph/ Allegrograph]
| I O
| I O
| I
|
|
| I O
| I O
|
|
| O json serialised N-Triples
|
|
|
|-
| [https://github.com/semsol/arc2/wiki ARC2]
| I O
| I O
|
| I O
|
|
|
| I
|
| O ([http://mmt.me.uk/misc/arc2.example.json example json])
|
|
|
|-
| [http://www.systap.com/bigdata.htm BigData]
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
|-
| [http://jena.sourceforge.net/ Jena]
| I O
| I O
| I O
| I O
| I
|
| I
| I *
| I *
|
|
|
|
|-
| [http://www.mulgara.org/ Mulgara]
| I O
| I O
|
| I
|
|
| I
| I
|
| O json(application/sparql-results+json with "subject" "predicate" "object" variables)
|
|
|
|-
| [http://www.oracle.com/pls/db112/homepage Oracle 11g Release 2]
| I O
| I O
| I O
| I O
| I O
|
| I
| I
|
|
|
|
| uses [http://jena.sourceforge.net/ Jena/Joseki], [http://www.openrdf.org/ Sesame]
|-
| [http://www.ontotext.com/owlim/change_log.html OWLIM]
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| uses [http://www.openrdf.org/ Sesame's Rio parser]
|-
| [http://rdf.rubyforge.org/ RDF.rb]
| I O
| I O
|
| I O
|
| I O
| I O
| I O
|
| I O ([http://mmt.me.uk/misc/rdfrb.example.json example json])
|
|
| Supports [http://librdf.org/raptor/ libraptor] based plugins
|-
| [http://search.cpan.org/dist/RDF-Query/ RDF::Query]
| I O
| I O
| I O
| I O
| I
|
|
| I
|
| I O ([http://mmt.me.uk/misc/rdfquery.example.json example json])
|
|
| uses [http://search.cpan.org/dist/RDF-Trine/ RDF::Trine]
|-
| [http://www.openrdf.org/ Sesame]
| I O
| I O
| I *
| I O
| I O
| I O
|
| I *
|
|
|
|
|
|-
| [http://virtuoso.openlinksw.com/ Virtuoso]
| I O
| I O
| I
| I O
| I
|
| I O
| I
| I
| I O ([http://mmt.me.uk/misc/virtuoso.example.json example json])
|
|
|
|}

'''"*"''' implies plugin

'''"I"''' RDF import supported

'''"O"''' RDF serialisations available via SPARQL CONSTRUCT

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 10:07:46 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ added in RDF.rb to the table

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestores can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

It should be noted that this table illustrates the RDF parsing/serialising capabilities of the various systems, most of which use 3rd party libraries to perform these operations.

{| border="1" align="center"
! Triplestore
| rdfxml
| ntriples
| nquads
| turtle
| trig
| trix
| n3
| rdfa
| grddl
| json 0
| json 1
| json 2
| Notes
|-
| 4store/5store
| I O
| I O
| I
| I O
| I
|
|
| I
| I
| O ([http://mmt.me.uk/misc/example.json.ttl example json])
| O ([http://mmt.me.uk/misc/example.json-triples.ttl example jsontriples ])
|
| uses libraptor
|-
| Anzo
| I O
| I
|
| I O
| I O
|
|
|
|
| O custom triple-based format
|
|
| also bundles Sesame serialisers
|-
| Allegrograph
| I O
| I O
| I
|
|
| I O
| I O
|
|
| O json serialised N-Triples
|
|
|
|-
| ARC2
| I O
| I O
|
| I O
|
|
|
| I
|
| O ([http://mmt.me.uk/misc/arc2.example.json example json])
|
|
|
|-
| BigData
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
|-
| Jena
| I O
| I O
| I O
| I O
| I
|
| I
| I *
| I *
|
|
|
|
|-
| Mulgara
| I O
| I O
|
| I
|
|
| I
| I
|
| O json(application/sparql-results+json with "subject" "predicate" "object" variables)
|
|
|
|-
| Oracle 11g Release 2
| I O
| I O
| I O
| I O
| I O
|
| I
| I
|
|
|
|
| uses Jena/Joseki, Sesame
|-
| OWLIM
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| uses Sesame's Rio parser
|-
| [http://rdf.rubyforge.org/ RDF.rb]
| I O
| I O
|
| I O
|
| I O
| I O
| I O
|
| I O ([http://mmt.me.uk/misc/rdfrb.example.json example json])
|
|
| Supports libraptor based plugins
|-
| RDF::Query
| I O
| I O
| I O
| I O
| I
|
|
| I
|
| I O ([http://mmt.me.uk/misc/rdfquery.example.json example json])
|
|
| uses RDF::Trine
|-
| Sesame
| I O
| I O
| I *
| I O
| I O
| I O
|
| I *
|
|
|
|
|
|-
| Virtuoso
| I O
| I O
| I
| I O
| I
|
| I O
| I
| I
| I O ([http://mmt.me.uk/misc/virtuoso.example.json example json])
|
|
|
|}

'''"*"''' implies plugin

'''"I"''' RDF import supported

'''"O"''' RDF serialisations available via SPARQL CONSTRUCT

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 09:59:54 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ added in example json from RDF::Query

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestores can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

It should be noted that this table illustrates the RDF parsing/serialising capabilities of the various systems, most of which use 3rd party libraries to perform these operations.

{| border="1" align="center"
! Triplestore
| rdfxml
| ntriples
| nquads
| turtle
| trig
| trix
| n3
| rdfa
| grddl
| json 0
| json 1
| json 2
| Notes
|-
| 4store/5store
| I O
| I O
| I
| I O
| I
|
|
| I
| I
| O ([http://mmt.me.uk/misc/example.json.ttl example json])
| O ([http://mmt.me.uk/misc/example.json-triples.ttl example jsontriples ])
|
| uses libraptor
|-
| Anzo
| I O
| I
|
| I O
| I O
|
|
|
|
| O custom triple-based format
|
|
| also bundles Sesame serialisers
|-
| Allegrograph
| I O
| I O
| I
|
|
| I O
| I O
|
|
| O json serialised N-Triples
|
|
|
|-
| ARC2
| I O
| I O
|
| I O
|
|
|
| I
|
| O ([http://mmt.me.uk/misc/arc2.example.json example json])
|
|
|
|-
| BigData
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
|-
| Jena
| I O
| I O
| I O
| I O
| I
|
| I
| I *
| I *
|
|
|
|
|-
| Mulgara
| I O
| I O
|
| I
|
|
| I
| I
|
| O json(application/sparql-results+json with "subject" "predicate" "object" variables)
|
|
|
|-
| Oracle 11g Release 2
| I O
| I O
| I O
| I O
| I O
|
| I
| I
|
|
|
|
| uses Jena/Joseki, Sesame
|-
| OWLIM
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| uses Sesame's Rio parser
|-
| RDF::Query
| I O
| I O
| I O
| I O
| I
|
|
| I
|
| I O ([http://mmt.me.uk/misc/rdfquery.example.json example json])
|
|
| uses RDF::Trine
|-
| Sesame
| I O
| I O
| I *
| I O
| I O
| I O
|
| I *
|
|
|
|
|
|-
| Virtuoso
| I O
| I O
| I
| I O
| I
|
| I O
| I
| I
| I O ([http://mmt.me.uk/misc/virtuoso.example.json example json])
|
|
|
|}

'''"*"''' implies plugin

'''"I"''' RDF import supported

'''"O"''' RDF serialisations available via SPARQL CONSTRUCT

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 09:57:48 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ added in virtuoso example json

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 00:44:59 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ as per http://chatlogs.planetrdf.com/swig/2011-04-07#T00-42-13

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 00:25:47 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ Based on feedback from the Allegrograph people especially Craig Norvell - Franz Inc. <cnorvell@franz.com>

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 00:16:53 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ updated the table, style changes

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 00:15:56 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */ added a legend

TriplestoreRDFSupport

Mtiffiel — Thu, 07 Apr 2011 00:12:26 GMT

Mtiffiel: updated the format as per people's suggestions on #swig

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestores can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

Where '''"I"''' stands for "RDF import serialisations " and '''"O"''' implies "RDF serialisations available via SPARQL CONSTRUCT". It should be noted that this table illustrates the RDF parsing/serialising capabilities of the various systems, most of which use 3rd party libraries to perform these operations.

{| border="1" align="center"
! Triplestore
| rdfxml
| ntriples
| nquads
| turtle
| trig
| trix
| n3
| rdfa
| grddl
| json 0
| json 1
| json 2
| Notes
|-
| 4store/5store
| I O
| I O
| I
| I O
| I
|
|
| I
| I
| O ([http://mmt.me.uk/misc/example.json.ttl example json])
| O ([http://mmt.me.uk/misc/example.json-triples.ttl example jsontriples ])
|
| uses libraptor
|-
| Anzo
| I O
| I
|
| I O
| I O
|
|
|
|
| O custom triple-based format
|
|
| also bundles Sesame serialisers
|-
| Allegrograph
| I O
| I O
| I
| I O
|
| I O
|
|
|
| O json
|
|
|
|-
| ARC2
| I O
| I O
|
| I O
|
|
|
| I
|
| O application/rdf+json
|
|
|
|-
| BigData
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
|-
| Jena
| I O
| I O
| I O
| I O
| I
|
| I
| I rdfa (plugin)
| I grddl (plugin)
|
|
|
|
|-
| Mulgara
| I O
| I O
|
| I
|
|
| I
| I
|
| O json(application/sparql-results+json with "subject" "predicate" "object" variables)
|
|
|
|-
| Oracle 11g Release 2
| I O
| I O
| I O
| I O
| I O
|
| I
| I
|
|
|
|
| uses Jena/Joseki, Sesame
|-
| OWLIM
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| ???
| uses Sesame's Rio parser
|-
| RDF::Query
| I O
| I O
| I O
| I O
| I
|
|
| I
|
| I O json(Talis json)
|
|
| uses RDF::Trine
|-
| Sesame
| I O
| I O
| I (plugin)
| I O
| I O
| I O
|
| I (plugin)
|
|
|
|
|
|-
| Virtuoso
| I O
| I O
| I
| I O
| I
|
| I O
| I
| I
| I O json application/rdf+json
|
|
|
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 21:32:53 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| rdfxml nquads ntriples trix turtle
| rdfxml ntriples trix turtle json
|-
| ARC2
| rdfa rdfxml turtle ntriples
| ntriples json(application/rdf+json) rdfxml turtle
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 nquads trig rdfa/grrdl (plugins)
| turtle rdfxml ntriples nquads
|-
| Mulgara
| rdfxml ntriples turtle n3 rdfa
| rdfxml ntriples json(application/sparql-results+json with "subject" "predicate" "object" variables)
|-
| Oracle 11g Release 2
| ntriples rdfxml rdfa n3 trig turtle nquads (uses Jena/Joseki, Sesame)
| ntriples rdfxml trig turtle nquads (uses Jena/Joseki, Sesame)
|-
| OWLIM
| ??? (uses Sesame's Rio parser)
| ??? (uses Sesame's Rio parser)
|-
| RDF::Query
| nquads ntriples json(Talis json) rdfxml nt rdfa trig turtle
| ntriples json(Talis json) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix trig nquads/rdfa (plugins)
| rdfxml ntriples turtle trix trig
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa grrdl
| rdfxml n3 json(application/rdf+json) turtle ntriples
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 20:59:52 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| rdfxml nquads ntriples trix turtle
| rdfxml ntriples trix turtle json
|-
| ARC2
| rdfa rdfxml turtle ntriples
| ntriples json(application/rdf+json) rdfxml turtle
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 nquads trig rdfa/grrdl (plugins)
| turtle rdfxml ntriples nquads
|-
| Mulgara
| rdfxml ntriples turtle n3 rdfa
| rdfxml ntriples json(application/sparql-results+json with "subject" "predicate" "object" variables)
|-
| Oracle 11g Release 2
| ntriples rdfxml rdfa n3 trig turtle nquads (uses Jena/Joseki, Sesame)
| ntriples rdfxml trig turtle nquads (uses Jena/Joseki, Sesame)
|-
| OWLIM
| ??? (uses Sesame's Rio parser)
| ??? (uses Sesame's Rio parser)
|-
| RDF::Query
| nquads ntriples json(Talis json) rdfxml nt rdfa trig turtle
| ntriples json(Talis json) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix trig
| rdfxml ntriples turtle trix trig
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa grrdl
| rdfxml n3 json(application/rdf+json) turtle ntriples
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 18:24:05 GMT

Mtiffiel: added the allegrograph details

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| rdfxml nquads ntriples trix turtle
| rdfxml ntriples trix turtle json
|-
| ARC2
| rdfa rdfxml turtle ntriples
| ntriples json(application/rdf+json) rdfxml turtle
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 nquads trig rdfa/grrdl (plugins)
| turtle rdfxml ntriples nquads
|-
| Mulgara
| rdfxml ntriples turtle n3 rdfa
| rdfxml ntriples json(application/sparql-results+json with "subject" "predicate" "object" variables)
|-
| Oracle 11g Release 2
| ntriples rdfxml rdfa n3 trig turtle nquads (uses Jena/Joseki, Sesame)
| ntriples rdfxml trig turtle nquads (uses Jena/Joseki, Sesame)
|-
| OWLIM
| ??? (uses Joseki)
| ??? (uses Joseki)
|-
| RDF::Query
| nquads ntriples json(Talis json) rdfxml nt rdfa trig turtle
| ntriples json(Talis json) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix turtle trig
| rdfxml ntriples turtle
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa grrdl
| rdfxml n3 json(application/rdf+json) turtle ntriples
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:58:19 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| ???
| ???
|-
| ARC2
| rdfa rdfxml turtle ntriples
| ntriples json(application/rdf+json) rdfxml turtle
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 rdfa/grrdl/nquads/trig (3rd party)
| turtle rdfxml ntriples
|-
| Mulgara
| rdfxml ntriples turtle n3 rdfa
| rdfxml ntriples json(?)
|-
| Oracle
| ntriples rdfxml rdfa (uses Jena/Joseki, Sesame)
| ??? (uses Joseki and Sesame)
|-
| OWLIM
| ??? (uses Joseki)
| ??? (uses Joseki)
|-
| RDF::Query
| nquads ntriples json(Talis json) rdfxml nt rdfa trig turtle
| ntriples json(Talis json) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix turtle trig
| rdfxml ntriples turtle
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa grrdl
| rdfxml n3 json(application/rdf+json) turtle ntriples
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:57:27 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| ???
| ???
|-
| ARC2
| rdfa rdfxml turtle ntriples
| ntriples json(application/rdf+json) rdfxml turtle
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 rdfa/grrdl/nquads/trig (3rd party)
| turtle rdfxml ntriples
|-
| Mulgara
| rdfxml ntriples turtle n3 rdfa
| rdfxml ntriples json(?)
|-
| Oracle
| ntriples rdfxml rdfa (uses Jena/Joseki, Sesame)
| ??? (uses Joseki and Sesame)
|-
| OWLIM
| ??? (uses Joseki)
| ??? (uses Joseki)
|-
| RDF::Query
| nquads ntriples json(application/rdf+jso) rdfxml nt rdfa trig turtle
| ntriples json(application/rdf+jso) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix turtle trig
| rdfxml ntriples turtle
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa grrdl
| rdfxml n3 json(application/rdf+json) turtle ntriples
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:42:59 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| ???
| ???
|-
| ARC2
| rdfa rdfxml turtle ntriples
| ntriples json(application/rdf+json) rdfxml turtle
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 rdfa/grrdl/nquads/trig (3rd party)
| turtle rdfxml ntriples
|-
| Mulgara
| ??? (uses Joseki same as Jena)
| ??? (uses Joseki same as Jena)
|-
| Oracle
| ntriples rdfxml rdfa (uses Jena/Joseki, Sesame)
| ??? (uses Joseki and Sesame)
|-
| OWLIM
| ??? (uses Joseki)
| ??? (uses Joseki)
|-
| RDF::Trine
| nquads ntriples rdfjson(?) rdfxml nt rdfa trig turtle
| ntriples rdfjson(?) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix turtle trig
| rdfxml ntriples turtle
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa grrdl
| rdfxml n3 json(application/rdf+json)
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:42:00 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| ???
| ???
|-
| ARC2
| rdfa rdfxml turtle ntriples
| ntriples json(application/rdf+json) rdfxml turtle
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 rdfa/grrdl/nquads/trig (3rd party)
| turtle rdfxml ntriples
|-
| Mulgara
| ??? (uses Joseki same as Jena)
| ??? (uses Joseki same as Jena)
|-
| Oracle
| ??? (uses Joseki and Sesame)
| ??? (uses Joseki and Sesame)
|-
| OWLIM
| ??? (uses Joseki)
| ??? (uses Joseki)
|-
| RDF::Trine
| nquads ntriples rdfjson(?) rdfxml nt rdfa trig turtle
| ntriples rdfjson(?) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix turtle trig
| rdfxml ntriples turtle
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa
| rdfxml n3 json(application/rdf+json)
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:40:10 GMT

Mtiffiel: first pass at adding the ARC2 formats

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json) (?)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| ???
| ???
|-
| ARC2
| rdfa rdfxml turtle ntriples
| ntriples json(application/rdf+json) rdfxml turtle
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 rdfa/grrdl/nquads/trig (3rd party)
| turtle rdfxml ntriples
|-
| Mulgara
| ??? (uses Joseki same as Jena)
| ??? (uses Joseki same as Jena)
|-
| Oracle
| ??? (uses Joseki and Sesame)
| ??? (uses Joseki and Sesame)
|-
| OWLIM
| ??? (uses Joseki)
| ??? (uses Joseki)
|-
| RDF::Trine
| nquads ntriples rdfjson(?) rdfxml nt rdfa trig turtle
| ntriples rdfjson(?) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix turtle trig
| rdfxml ntriples turtle
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa
| rdfxml n3 json(application/rdf+json)
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:36:19 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json) (?)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serialisers)
|-
| Allegrograph
| ???
| ???
|-
| ARC2
| ???
| ???
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 rdfa/grrdl/nquads/trig (3rd party)
| turtle rdfxml ntriples
|-
| Mulgara
| ??? (uses Joseki same as Jena)
| ??? (uses Joseki same as Jena)
|-
| Oracle
| ??? (uses Joseki and Sesame)
| ??? (uses Joseki and Sesame)
|-
| OWLIM
| ??? (uses Joseki)
| ??? (uses Joseki)
|-
| RDF::Trine
| nquads ntriples rdfjson(?) rdfxml nt rdfa trig turtle
| ntriples rdfjson(?) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix turtle trig
| rdfxml ntriples turtle
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa
| rdfxml n3 json(application/rdf+json)
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:35:17 GMT

Mtiffiel: clarified what is was meant by json in places

== Table of Triplestore and Supported RDF formats ==

This table lists the RDF serialisations which the various triplestore can take as an import format, and as an output format in terms of output generated via the SPARQL CONSTRUCT verb.

{| border="1" align="center"
! Triplestore
! Import Format
! Output Format
|-
| 4store/5store
| rdfxml ntriples nquads trig rdfa turtle grddl
| turtle ntriples rdfxml json-triples(?) json(application/rdf+json) (?)
|-
| Anzo
| rdfxml ntriples turtle trig
| trig rdfxml turtle json (custom triple-based format) (also bundles Sesame serializers)
|-
| ARC2
| ???
| ???
|-
| BigData
| ???
| ???
|-
| Jena
| rdfxml ntriples turtle n3 rdfa/grrdl/nquads/trig (3rd party)
| turtle rdfxml ntriples
|-
| Mulgara
| ??? (uses Joseki same as Jena)
| ??? (uses Joseki same as Jena)
|-
| Oracle
| ??? (uses Joseki and Sesame)
| ??? (uses Joseki and Sesame)
|-
| OWLIM
| ??? (uses Joseki)
| ??? (uses Joseki)
|-
| RDF::Trine
| nquads ntriples rdfjson(?) rdfxml nt rdfa trig turtle
| ntriples rdfjson(?) rdfxml turtle
|-
| Sesame
| rdfxml ntriples turtle trix turtle trig
| rdfxml ntriples turtle
|-
| Virtuoso
| rdfxml ntriples nquads trig rdfa turtle n3 json(application/rdf+json) rdfa
| rdfxml n3 json(application/rdf+json)
|}

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:10:24 GMT

Mtiffiel: s/nt/ntriples/

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:07:41 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:05:53 GMT

Mtiffiel: /* Table of Triplestore and Supported RDF formats */

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 14:01:31 GMT

Mtiffiel: adedd in more vendors to the list

TriplestoreRDFSupport

Mtiffiel — Wed, 06 Apr 2011 13:54:00 GMT

Mtiffiel: Initial population of page listing which serialisation are supported by which triplestores

F2F1

Mtiffiel — Wed, 09 Mar 2011 16:15:43 GMT

Mtiffiel:

;Date
:13-14 April 2011
;Location
: Amsterdam, The Netherlands ([http://homepages.cwi.nl/~steven/amsterdam.html a guide])
;Agenda
:tbd
;Venue
:[http://www.cwi.nl CWI]; See [http://www.cwi.nl/general/Address separate page] for directions, or the [http://homepages.cwi.nl/~steven/amsterdam.html pages on Amsterdam] done by Steven Pemberton
;Hotel Recommendations
:[[ftf-amsterdam-hotels|Hotel info]]

; Intent to attend
: David Wood
: Ivan Herman
: Richard Cyganiak
: Matteo Brunati
: Sandro Hawke
: Steve Harris
: Guus Schreiber
: Jean-Francois Baget
: Mischa Tuffield

; Intent to attend remotely
: Antoine Zimmermann
: Andy Seaborne
: Peter F. Patel-Schneider (maybe in person, but not yet determined)

TF-Graphs-UC

Mtiffiel — Wed, 09 Mar 2011 15:38:51 GMT

Mtiffiel: /* Provenance Use Cases */ Added in "Provenance Info for Data Retention" section to

This page lists use cases collected by the [[TF-Graphs|TF-Graphs task force]] related to the work item “Support for Multiple Graphs and Graph Stores” (see RDF Next Steps workshop results: [http://www.w3.org/2001/sw/wiki/index.php?title=RDF_Core_Work_Items#Graph_Identification_and_Metadata_Work_Items Graph Identification and Metadata]).

== Storage Use Cases ==
When storing RDF information in a graph store, we would like to organize related information into separate graphs. Each graph must be identified with a URI to facilitate retrieval.
=== Slicing datasets according to multiple dimensions ===
Within the [http://www.bbc.co.uk BBC], we want to slice large RDF datasets according to multiple dimensions: statements about individual programmes, access control, 'ownership' of the data (what product owns/maintains what set of triples), versioning, etc. All those graphs are potentially overlapping or contained within each other. Those issues are very common in large organisations using a single, centralised, triple store.

=== Permissions ===
Another purpose in storing RDF content in different graphs is to enforce a permissions model so that sensitive information is not accessed by unauthorized users.
=== Graph Changes Over Time ===
When storing graph information retrieved from a URL external to an application, it becomes important to store snapshots of the location over time. When these graph snapshots are taken, it is useful to annotate each snapshot with information such as retrieval time, HTTP Headers used, HTTP Response returned, and other such items that may have affected the contents of the graph snapshot.

* [[TF-Graphs-UC/Changes over time|Example on separate page]]

=== Tracing inference results ===
By identifying the graphs that where consumed and produced by an inference engine, and keeping track of their relationships, one can trace an inferred statement back to its premises. One can also more easily undo some reasoning, for instance when the store is updated.

<pre>
:G1 { :Tom ex:manage :ACompany }

:G2 { :Tom rdf:type ex:Manager }

:G2 ex:deducedFrom :G1
</pre>

=== Exchanging the contents of RDF stores ===
Frequently, the entire contents of a SPARQL store have to be “dumped”, for purposes such as backup, replication, migration and archival. One could resort to multipart files or multi-file archives such as tar, or otherwise use a file format that can serialize an RDF Dataset.

As well whole store dumps, data may be added to the store as a collection of graphs to be added or merged (where there is already a graph in the store with that IRI). This can be achieved with multiple files but it can be convenient to have a single file-format. Such additional information may be human-authored so it's not just a machine format.

There is a relationship to subsets of [http://www.w3.org/TR/sparql11-update/ SPARQL 1.1 Update] to be explored. SPARQL Update provides <tt>INSERT DATA</tt> and <tt>DELETE DATA</tt>.

== Query Use Cases ==
While query services are not explicitly addressed in the RDF spec, SPARQL does make use of graph IRIs and we should ensure that the semantics of graph identifiers are compatible with the way in which RDF datasets are defined by SPARQL.
=== Find Information In a Graph ===
When a query service processes a query containing a graph identifier, it must resolve the graph identifier to some collection of materialized RDF content that will be returned in the result set.
=== Computed Graphs ===
Often, graphs exposed by a query service are not present in any sort of physical storage, but rather their contents are computed at query time. Examples include:
* A federated query service may define a graph URI to be the union of graphs accessible through other query services.
* A service that does RDB to RDF mapping via [http://www.w3.org/TR/r2rml/ R2RML] may dynamically compute RDF results based on SQL results at query time.
=== Graph URIs as Locations ===
In the situation where a query service is presented with a graph identifier that is not present in local storage, the query service may wish to resolve the graph URI as a URL and make a request to that URL (possibly with conneg) for a document that serializes the content of that graph.

NB: It is important to consider what the linked data "Follow your nose" approach means for identified graphs.

=== Contextual constraints in queries ===
In e-Science projects we can use identified graphs to represent and query contextual metadata. For instance, evidence-based reasoning requires being able to differentiate assertions considered as universally true and assertions which are concurrent hypothesis or interpretations. One can use identified graphs when annotating experiments (e.g. in biology) or analysis (e.g. in geology). Identified graphs are used to represent different contexts within which alternative metadata can be described.

Identifying the graphs also allows us to hierarchically organize the RDF datasets, based on RDFS entailment. When considering RDF datasets as contexts, the root of the hierarchy contains the triples that are true in any context below it i.e. any other node of the hierarchy entails it. The other nodes of the hierarchy represent specific contexts; each one recursively inherits and adds to the triples of its ancestors. Each node then provides a different context for querying and reasoning. When a hypothesis is tested (as a SPARQL query), the context of the test is specified by the identifier of the graph to be used.

A special case is the introduction of temporal or geographical aspects in querying and reasoning over the triple store: a query may be solved considering only the assertions that are true in a specific range of time or geographical area.

A way to address this family of scenarios is to allow a basic algebra of sets over the identified graphs. For instance to allowing to assert inclusion.

<pre>
:G1 { http://dbpedia.org/page/Nice geo:lat 43.703392 ;
geo:long 7.266274 . }

:G2 ex:includes :G1
:G2 { http://dbpedia.org/page/Nice ex:belongsTo http://dbpedia.org/page/France }

:G3 ex:includes :G1
:G3 { http://dbpedia.org/page/Nice ex:belongsTo http://dbpedia.org/page/Italy }

</pre>

== Provenance Use Cases ==

One advantage of the RDF data model is the ease with which data from different sources can be combined. Aggregating data in a single place for exploration, querying, and visualization can be as easy as loading everything into a single model. Nevertheless, it is often important to retain provenance information. What came from where? How were the different data produced or obtained?

=== Web crawling ===
Two issues arise when crawling RDF documents from the Web:

* Statements come from untrusted sources; therefore, it is important to know which statement came from which source (site/domain)
* When re-crawling documents in order to update their contents, one needs to know which triples originally came from which document

One way of approaching this is to store the triples parsed from each document in a separate named graph. The simplest scheme uses the document URI as the graph name. The source is recorded, as the DNS domain is part of the document URI. Re-crawling can be implemented by simply replacing the graph's contents.

'''Examples:'''

* [http://www4.wiwiss.fu-berlin.de/bizer/ng4j/semwebclient/ Semantic Web Client Library]
* [http://sindice.com/ Sindice.com]

=== Sharing collections of RDF documents ===
The contents of an RDF store are often collected from a number of different sources. The creation of such a collection in itself can be a major effort, and are hard to reproduce. Examples include large-scale web crawls of RDF documents, and extractions of structured data from large numbers of text documents.

The creators of such collections sometimes want to share the collection with third parties. Keeping provenance (which triple came from which source URL?) intact is very important.

This is for instance done for the Billion Triple Challenge, which in fact does not provide a billion triples but a billion quadruple, so that sources are identified.

'''Examples:'''

* [http://wiki.dbpedia.org/Downloads36 DBpedia dumps]
* [http://km.aifb.kit.edu/projects/btc-2010/ Billion Triples Challenge datasets]
* DERI GoodRelations crawl (link?)

=== Backup / Restore of Triplestores ===

In similar vein to the above use case "Sharing collections of RDF documents", the ability to backup and restore dumps of triplestores is something that needs to be considered. There may be subtleties related the correct restoration of bNodes to their scoped graphs, and these should be addressed by any serialisation of quads.

Furthermore, from a parsing point of view it would be good to know from the outset whether or not a file contains quads or triples, so that one would not need to parse the entirety of a file before finding out that it has both quads and triples.

=== Digital Signatures on Graphs ===

There are a number of ways to create digital signatures on RDF graphs. Often, you do not want to co-mingle the signature information and the graph. Co-mingling signature information in a graph requires the software to use an algorithm to clean the graph in order to generate the signature hash for verification purposes. It also means that it becomes very difficult to sign a graph containing a digital signature at the top-most level. In order to express a digital signature on a graph of information, the idea of a Graph Literal becomes useful. Take the following as an example of a graph that we would like to digitally sign:

* [[TF-Graphs-UC/Digital Signatures|Example on separate page]]

=== Capture elements of the production context ===
A graph may be produced through a variety of means and in very different contexts. For instance it could be the result of some natural language processing or other extractions techniques.
An identified graph may be linked to the context in which it was produced (source, properties, etc.)

<pre>
:G1 {
<http://dbpedia.org/resource/Antibes>
geo:lat 43.580833;
geo:long 7.123889 .
}
:G1 ex:extractedFrom <http://en.wikipedia.org/wiki/Antibes>;
dc:date "2010-11-12"^^xsd:date .
</pre>

Note that :G1 could also be named <nowiki><http://dbpedia.org/data/Antibes></nowiki>.

=== Applying Named Graphs to a Terminology Service Prototype ===

[http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-521/paper2.pdf LexRDF] is an prototype implementation of [https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/LexBig_and_LexEVS#What_is_LexEVS.3F LexEVS] on an RDF triple store.

Among its assertions is an expression of definition source using reification to resolve a non-preferred term definition. Named Graphs could eliminate some of the overhead associated with reification. An example assertion is expressed as follows:

<pre>
FAO:0000025 a owl:Class;
skos:prefLabel "mid reproductive";
skos:altLabel “principal growth stages 6.1-6.3" .

_:A1 a rdf:Statement;
rdf:subject FAO:0000025;
rdf:predicate skos:definition;
rdf:object “middle stages of reproductive phase.";
dc:source TAIR:lr .
</pre>

Using Named Graphs:

<pre>
LexRDF:Graph1 {
FAO:0000025 a owl:Class;
skos:prefLabel “mid reproduction”;
skos:altLabel “principal growth stages 6.1-6.3" .
}
LexRDF:Graph2 {
FAO:0000025 skos:definition ”middle stages of reproduction” .
}
LexRDF:Graph3 {
LexRDF:Graph2 dc:source TAIR:lr .
}
</pre>

=== Provenance Information and Data Retention ===

In Garlik we use named graphs to track the provenance of personal information we hold inside our triplestores. These Named Graphs have timestamped information associated with them upon import and are subsequently used to identify how long the data is held within our systems. This is used to comply with Data Protection Laws in the UK, whereby information about individuals who are not our customers are only stored and indexed within our systems for 90 days. Furthermore, other information regarding the source of the data and the software used to process the data is associated to the named graph, this information is also used to track the provenance of data which may be presented to an end user.

== Providing a standard foundation for W3C specs ==
The 2004 recommendation set is focused on individual RDF graphs: It defines an RDF graph as a simple set of triples. It defines the semantics of such an individual graph. It defines syntaxes for serializing such an individual graph into a text. Later W3C groups, however, had requirements that went beyond this, raising questions about interactions between multiple graphs, about mutable graphs, and about the persistent identity of graphs beyond the mathematical set. They treated these topics in an ad hoc fashion, defining their own concepts and terminology that is not aligned.

=== SPARQL's “RDF Dataset” and “Graph store” ===
SPARQL 1.0 defines the concept of a ''RDF Dataset'', a collection of graphs containing one default graph and zero or more named graphs (pairs of URI and graph). SPARQL queries are evaluated against an RDF dataset.

RDF Dataset: [http://www.w3.org/TR/rdf-sparql-query/#rdfDataset Discussion], [http://www.w3.org/TR/rdf-sparql-query/#defn_RDFDataset formal definition] (in [http://www.w3.org/TR/rdf-sparql-query/ SPARQL 1.0])

<blockquote>A SPARQL query is executed against an RDF Dataset which represents a collection of graphs. An RDF Dataset comprises one graph, the default graph, which does not have a name, and zero or more named graphs, where each named graph is identified by an IRI. A SPARQL query can match different parts of the query pattern against different graphs as described in section 8.3 Querying the Dataset.

An RDF Dataset may contain zero named graphs; an RDF Dataset always contains one default graph. A query does not need to involve matching the default graph; the query can just involve matching named graphs.</blockquote>

SPARQL 1.1 adds the concept of a ''Graph Store'', essentially a mutable RDF Dataset. The contents of the graphs can be modified, and graphs can be added or removed. SPARQL 1.1 also adds additional discussion about the default graph: Depending on implementation, it could be a separate graph, or a union of all or some of the named graphs.

Graph Store: [http://www.w3.org/TR/sparql11-update/#sec_graphStore Discussion], [http://www.w3.org/TR/sparql11-update/#def_graphstore formal definition] (in [http://www.w3.org/TR/sparql11-update/ SPARQL 1.1 Update])

<blockquote>A Graph Store is a repository of RDF graphs managed by a single service. Like an RDF Dataset operated on by the SPARQL 1.1 Query Language, a Graph Store contains one unnamed graph and zero or more named graphs. Operations may specify graphs to work with, or they may rely on a default graph for that operation. Unless overridden (for instance, by the SPARQL protocol), then the unnamed graph for the store will be the default graph for any operations on that store. Depending on implementation, the unnamed graph may refer to a separate graph, or it could be a representation of a union of other graphs.

Unlike an RDF dataset, named graphs can be added to or deleted from a graph store. A Graph Store needs not be authoritative for the graphs it contains, i.e. the graph URIs do not need to be in the same pay level domain as the endpoint. That means a Graph Store can keep local copies of RDF graphs defined elsewhere on the Web and modify those copies independently of the original graph.

In the simple case, where there is one unnamed graph and no named graphs, SPARQL 1.1 Update is a language for the update of a single graph.</blockquote>

These concepts are applicable beyond SPARQL.

=== OWL's “Ontology Documents” ===
An OWL ontology can be serialized as RDF and stored in a graph store. The general convention is to store each ontology in a separate graph, which is in turn identified with a graph URI. The OWL spec uses the notion of an [http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Ontology_Documents Ontology Document] as the means of organizing ontologies. An Ontology Document has an IRI, but it is left open-ended what that IRI represents (graph in a graph store? file on a file system? web resource?) Can the document IRI and the graph IRI that stores the ontology be the same?

This is especially relevant in the case of an ontology that [http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Imports imports] another ontology. If an ontology is serialized as RDF and stored in a graph store, then there may be an <tt>owl:imports</tt> predicate whose object is an IRI identifying the ontology to import. How do we resolve this IRI to determine which graph contains that ontology, so that we can parse and process its contents?

=== Scope of blank nodes in RDF Semantics ===
RDF Concepts defines an RDF graph as an abstract set of triples. It also defines blank nodes as being scoped to the graph. But clearly a blank node can be part of multiple graphs at the same time, e.g., of a graph and its subgraphs. So, what stops a blank node from occurring in two completely unrelated graphs?

In RDF Semantics this is handled by introducing the operation of merging graphs, which is not the same as a simple set union. Merging graphs involves some rather complicated mechanics for “standardizing apart” blank nodes.

If new concepts beyond the graph as a set of triples were defined, then this would create an opportunity to explain the semantics of RDF in a more compact and intuitive way, removing some of the confusion and stigma that surround blank nodes (if not the implementation challenges).

=== VoID and metadata for RDF datasets ===
[http://www.w3.org/TR/void/ Describing Linked Datasets with the VoID Vocabulary] is a SWIG Note on a metadata vocabulary for RDF datasets. It fuzzily defines the concept of a “dataset” as a “meaningful collection of RDF triples that are published, maintained or aggregated by a single provider.” It states that datasets can be published in different ways, including RDF dumps, SPARQL endpoint, or as collections of multiple RDF documents, but relying on the readers' intuition instead of solid definitions for all these terms. A proper formal definition of VoID is currently lacking, and would require concepts for collections of mutable graphs.

=== Supporting formal alignment of Linked Data principles with RDF and ''AWWW'' ===

The ''Web of Data'', as the macro entity that emerges from the micro principles of ''Linked Data'', can be seen as an RDF Dataset. It contains a potentially unlimited number of named graphs. The contents of graph <nowiki></nowiki> are given by the function <code>get-and-parse</code>, which performs an HTTP get on <nowiki></nowiki> and parses the result with an RDF parser. An actual implementation would of course deviate from this idealized description in many ways (it would likely contain a subset of graphs, which are older snapshots; how are media types handled; what parsers are used; content-type sniffing and tag-soup parsing; redirects; etc etc). But the basic intuition of this model appears to be widespread in the Linked Data community, and is implemented in a number of tools (see Web Crawling use case above).

A formal definition of a concept such as “RDF Dataset”, “Set of Named Graphs”, and the g-box/g-snap/g-text distinction in a core RDF spec would make it easier to formally define such a model, tying together the Linked Data principles and practices, ''[http://www.w3.org/TR/webarch/ Architecture of the World Wide Web]'', and the REST model of information resources and representations, in a formal way.

== Advanced Annotations Use Cases ==

=== Separate Ontology Use Case ===

This use case is derived from a proposal to have OWL annotations that
can be collected together into a separate ontology (and that might even
be able to affect the main ontology). The proposal itself can be seen
at http://www.w3.org/2007/OWL/wiki/Annotation_System however this "use
case" is somewhat of a modification of the suggestions in the proposal.

The basic need is to be able to generate multiple ontologies
(http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Ontologies, i.e.,
the basic OWL construct that holds OWL axioms and other stuff)
from a
single OWL document. One ontology is the ontology that corresponds to
the main information in the document. The other ontology (or
ontologies) would sit alongside the main ontology. These secondary
ontologies might be used to store and reason about things like
provenance or certainty.

The secondary ontologies would not necessarily contain information about
the domain of the ontology (and thus need not share axioms with the main
ontology) but could refer to the syntactic bits (axioms, annotations,
etc.) of the main ontology. Note that this does *not* directly require
reflection, as the referenced syntactic bits don't have their semantic
import in the secondary ontologies. Any semantic relationship between
the main ontology and secondary ontologies is mediated by relationships
outside the formalism semantics, again so that there is no need for
reflection or reification or ....

So far this is about (OWL) ontologies, not graphs, but it can easily be
turned into a use case for named graphs. An RDF document that encodes
multiple OWL ontologies would contain named graphs that encode the
secondary ontologies and the main graph of the document would encode the
main ontology. Uses of the names of the named graphs would encode the
links between the main ontology and the secondary ontologies. How to
encode the links from the secondary ontology into the main ontology
remains an unsettled issue, however.

=== Reasoning over annotations ===

We want to support reasoning based on annotations, using a generic approach as defined in <ref name=r1>U. Straccia, N. Lopes, G. Lukacsy, A. Polleres. A General Framework for Representing and Reasoning with Annotated Semantic Web Data. In ''Proceedings of the Twenty-Fourth AAAI Conference on Artificial Intelligence (AAAI-10)'', AAAI Press, 2010. http://axel.deri.ie/publications/stra-etal-2010AAAI.pdf</ref><ref name=r2>N. Lopes, A. Zimmermann, A. Hogan, G. Lukácsy, A. Polleres, U. Straccia, S. Decker. RDF Needs Annotations. In ''RDF Next Steps'', June 2010. http://www.w3.org/2009/12/rdf-ws/papers/ws09</ref><ref name=r3>N. Lopes, A. Polleres, U. Straccia, A. Zimmermann, AnQL: SPARQLing Up Annotated RDFS. In ''Proceedings of the International Semantic Web Conference (ISWC-10)'', no. 6496 in Lecture Notes in Computer Science, Springer-Verlag, 2010, pp.518–533. http://iswc2010.semanticweb.org/pdf/51.pdf</ref>. Annotations include, but are not limited to:

* temporal annotations (when is a statement valid?)
* provenance annotations (where did a statement originate?)
* uncertainty annotations (how likely is a statement to be true?)

For instance, if temporal annotations exist in a dataset, one can ask when a triple holds (e.g., "who was a GoogleEmployee and when?"). If:

<pre>
ex:chadhurley rdf:type ex:YoutubeEmployee . [2005,2010]
ex:YoutubeEmployee rdf:type ex:GoogleEmployee . [2006,2011]
</pre>

then:

<pre>
ex:chadhurley rdf:type ex:GoogleEmployee . [2006,2010]
</pre>

With provenance annotation, if:

<pre>
foaf:Person rdfs:subClassOf foaf:Agent . foaf:
ex:chadhurley rdf:type foaf:Person . dbpedia:
</pre>

then one can infer:

<pre>
ex:chadhurley rdf:type foaf:Agen . foaf: \and dbpedia:
</pre>

Following the same generic framework, it is also possible to deal with fuzzy, probabilistic and uncertain information, e.g.,:

<pre>
ex:pictureAreaXYZ rdf:type ex:HumanFace . 0.82
ex:HumanFace rdfs:subClassOf ex:Ellipse . 0.75
</pre>

Fuzzy-annotated RDF are likely to be produced automatically by tools relying on statistical data or heuristic-based algorithm. Terminological statements with uncertainty are very common outputs of ontology matching algorithms.

In all these situations, identifying the triples or graphs to which attach the annotations is necessary.

== References ==
<references/>

TF-Graphs-UC

Mtiffiel — Wed, 09 Mar 2011 15:26:17 GMT

Mtiffiel: /* Provenance Use Cases */ Added in a use-case for backup/restore of triplestores

This page lists use cases collected by the [[TF-Graphs|TF-Graphs task force]] related to the work item “Support for Multiple Graphs and Graph Stores” (see RDF Next Steps workshop results: [http://www.w3.org/2001/sw/wiki/index.php?title=RDF_Core_Work_Items#Graph_Identification_and_Metadata_Work_Items Graph Identification and Metadata]).

== Storage Use Cases ==
When storing RDF information in a graph store, we would like to organize related information into separate graphs. Each graph must be identified with a URI to facilitate retrieval.
=== Slicing datasets according to multiple dimensions ===
Within the [http://www.bbc.co.uk BBC], we want to slice large RDF datasets according to multiple dimensions: statements about individual programmes, access control, 'ownership' of the data (what product owns/maintains what set of triples), versioning, etc. All those graphs are potentially overlapping or contained within each other. Those issues are very common in large organisations using a single, centralised, triple store.

=== Permissions ===
Another purpose in storing RDF content in different graphs is to enforce a permissions model so that sensitive information is not accessed by unauthorized users.
=== Graph Changes Over Time ===
When storing graph information retrieved from a URL external to an application, it becomes important to store snapshots of the location over time. When these graph snapshots are taken, it is useful to annotate each snapshot with information such as retrieval time, HTTP Headers used, HTTP Response returned, and other such items that may have affected the contents of the graph snapshot.

* [[TF-Graphs-UC/Changes over time|Example on separate page]]

=== Tracing inference results ===
By identifying the graphs that where consumed and produced by an inference engine, and keeping track of their relationships, one can trace an inferred statement back to its premises. One can also more easily undo some reasoning, for instance when the store is updated.

<pre>
:G1 { :Tom ex:manage :ACompany }

:G2 { :Tom rdf:type ex:Manager }

:G2 ex:deducedFrom :G1
</pre>

=== Exchanging the contents of RDF stores ===
Frequently, the entire contents of a SPARQL store have to be “dumped”, for purposes such as backup, replication, migration and archival. One could resort to multipart files or multi-file archives such as tar, or otherwise use a file format that can serialize an RDF Dataset.

As well whole store dumps, data may be added to the store as a collection of graphs to be added or merged (where there is already a graph in the store with that IRI). This can be achieved with multiple files but it can be convenient to have a single file-format. Such additional information may be human-authored so it's not just a machine format.

There is a relationship to subsets of [http://www.w3.org/TR/sparql11-update/ SPARQL 1.1 Update] to be explored. SPARQL Update provides <tt>INSERT DATA</tt> and <tt>DELETE DATA</tt>.

== Query Use Cases ==
While query services are not explicitly addressed in the RDF spec, SPARQL does make use of graph IRIs and we should ensure that the semantics of graph identifiers are compatible with the way in which RDF datasets are defined by SPARQL.
=== Find Information In a Graph ===
When a query service processes a query containing a graph identifier, it must resolve the graph identifier to some collection of materialized RDF content that will be returned in the result set.
=== Computed Graphs ===
Often, graphs exposed by a query service are not present in any sort of physical storage, but rather their contents are computed at query time. Examples include:
* A federated query service may define a graph URI to be the union of graphs accessible through other query services.
* A service that does RDB to RDF mapping via [http://www.w3.org/TR/r2rml/ R2RML] may dynamically compute RDF results based on SQL results at query time.
=== Graph URIs as Locations ===
In the situation where a query service is presented with a graph identifier that is not present in local storage, the query service may wish to resolve the graph URI as a URL and make a request to that URL (possibly with conneg) for a document that serializes the content of that graph.

NB: It is important to consider what the linked data "Follow your nose" approach means for identified graphs.

=== Contextual constraints in queries ===
In e-Science projects we can use identified graphs to represent and query contextual metadata. For instance, evidence-based reasoning requires being able to differentiate assertions considered as universally true and assertions which are concurrent hypothesis or interpretations. One can use identified graphs when annotating experiments (e.g. in biology) or analysis (e.g. in geology). Identified graphs are used to represent different contexts within which alternative metadata can be described.

Identifying the graphs also allows us to hierarchically organize the RDF datasets, based on RDFS entailment. When considering RDF datasets as contexts, the root of the hierarchy contains the triples that are true in any context below it i.e. any other node of the hierarchy entails it. The other nodes of the hierarchy represent specific contexts; each one recursively inherits and adds to the triples of its ancestors. Each node then provides a different context for querying and reasoning. When a hypothesis is tested (as a SPARQL query), the context of the test is specified by the identifier of the graph to be used.

A special case is the introduction of temporal or geographical aspects in querying and reasoning over the triple store: a query may be solved considering only the assertions that are true in a specific range of time or geographical area.

A way to address this family of scenarios is to allow a basic algebra of sets over the identified graphs. For instance to allowing to assert inclusion.

<pre>
:G1 { http://dbpedia.org/page/Nice geo:lat 43.703392 ;
geo:long 7.266274 . }

:G2 ex:includes :G1
:G2 { http://dbpedia.org/page/Nice ex:belongsTo http://dbpedia.org/page/France }

:G3 ex:includes :G1
:G3 { http://dbpedia.org/page/Nice ex:belongsTo http://dbpedia.org/page/Italy }

</pre>

== Provenance Use Cases ==

One advantage of the RDF data model is the ease with which data from different sources can be combined. Aggregating data in a single place for exploration, querying, and visualization can be as easy as loading everything into a single model. Nevertheless, it is often important to retain provenance information. What came from where? How were the different data produced or obtained?

=== Web crawling ===
Two issues arise when crawling RDF documents from the Web:

* Statements come from untrusted sources; therefore, it is important to know which statement came from which source (site/domain)
* When re-crawling documents in order to update their contents, one needs to know which triples originally came from which document

One way of approaching this is to store the triples parsed from each document in a separate named graph. The simplest scheme uses the document URI as the graph name. The source is recorded, as the DNS domain is part of the document URI. Re-crawling can be implemented by simply replacing the graph's contents.

'''Examples:'''

* [http://www4.wiwiss.fu-berlin.de/bizer/ng4j/semwebclient/ Semantic Web Client Library]
* [http://sindice.com/ Sindice.com]

=== Sharing collections of RDF documents ===
The contents of an RDF store are often collected from a number of different sources. The creation of such a collection in itself can be a major effort, and are hard to reproduce. Examples include large-scale web crawls of RDF documents, and extractions of structured data from large numbers of text documents.

The creators of such collections sometimes want to share the collection with third parties. Keeping provenance (which triple came from which source URL?) intact is very important.

This is for instance done for the Billion Triple Challenge, which in fact does not provide a billion triples but a billion quadruple, so that sources are identified.

'''Examples:'''

* [http://wiki.dbpedia.org/Downloads36 DBpedia dumps]
* [http://km.aifb.kit.edu/projects/btc-2010/ Billion Triples Challenge datasets]
* DERI GoodRelations crawl (link?)

=== Backup / Restore of Triplestores ===

In similar vein to the above use case "Sharing collections of RDF documents", the ability to backup and restore dumps of triplestores is something that needs to be considered. There may be subtleties related the correct restoration of bNodes to their scoped graphs, and these should be addressed by any serialisation of quads.

Furthermore, from a parsing point of view it would be good to know from the outset whether or not a file contains quads or triples, so that one would not need to parse the entirety of a file before finding out that it has both quads and triples.

=== Digital Signatures on Graphs ===

There are a number of ways to create digital signatures on RDF graphs. Often, you do not want to co-mingle the signature information and the graph. Co-mingling signature information in a graph requires the software to use an algorithm to clean the graph in order to generate the signature hash for verification purposes. It also means that it becomes very difficult to sign a graph containing a digital signature at the top-most level. In order to express a digital signature on a graph of information, the idea of a Graph Literal becomes useful. Take the following as an example of a graph that we would like to digitally sign:

* [[TF-Graphs-UC/Digital Signatures|Example on separate page]]

=== Capture elements of the production context ===
A graph may be produced through a variety of means and in very different contexts. For instance it could be the result of some natural language processing or other extractions techniques.
An identified graph may be linked to the context in which it was produced (source, properties, etc.)

<pre>
:G1 {
<http://dbpedia.org/resource/Antibes>
geo:lat 43.580833;
geo:long 7.123889 .
}
:G1 ex:extractedFrom <http://en.wikipedia.org/wiki/Antibes>;
dc:date "2010-11-12"^^xsd:date .
</pre>

Note that :G1 could also be named <nowiki><http://dbpedia.org/data/Antibes></nowiki>.

=== Applying Named Graphs to a Terminology Service Prototype ===

[http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-521/paper2.pdf LexRDF] is an prototype implementation of [https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/LexBig_and_LexEVS#What_is_LexEVS.3F LexEVS] on an RDF triple store.

Among its assertions is an expression of definition source using reification to resolve a non-preferred term definition. Named Graphs could eliminate some of the overhead associated with reification. An example assertion is expressed as follows:

<pre>
FAO:0000025 a owl:Class;
skos:prefLabel "mid reproductive";
skos:altLabel “principal growth stages 6.1-6.3" .

_:A1 a rdf:Statement;
rdf:subject FAO:0000025;
rdf:predicate skos:definition;
rdf:object “middle stages of reproductive phase.";
dc:source TAIR:lr .
</pre>

Using Named Graphs:

<pre>
LexRDF:Graph1 {
FAO:0000025 a owl:Class;
skos:prefLabel “mid reproduction”;
skos:altLabel “principal growth stages 6.1-6.3" .
}
LexRDF:Graph2 {
FAO:0000025 skos:definition ”middle stages of reproduction” .
}
LexRDF:Graph3 {
LexRDF:Graph2 dc:source TAIR:lr .
}
</pre>

== Providing a standard foundation for W3C specs ==
The 2004 recommendation set is focused on individual RDF graphs: It defines an RDF graph as a simple set of triples. It defines the semantics of such an individual graph. It defines syntaxes for serializing such an individual graph into a text. Later W3C groups, however, had requirements that went beyond this, raising questions about interactions between multiple graphs, about mutable graphs, and about the persistent identity of graphs beyond the mathematical set. They treated these topics in an ad hoc fashion, defining their own concepts and terminology that is not aligned.

=== SPARQL's “RDF Dataset” and “Graph store” ===
SPARQL 1.0 defines the concept of a ''RDF Dataset'', a collection of graphs containing one default graph and zero or more named graphs (pairs of URI and graph). SPARQL queries are evaluated against an RDF dataset.

RDF Dataset: [http://www.w3.org/TR/rdf-sparql-query/#rdfDataset Discussion], [http://www.w3.org/TR/rdf-sparql-query/#defn_RDFDataset formal definition] (in [http://www.w3.org/TR/rdf-sparql-query/ SPARQL 1.0])

<blockquote>A SPARQL query is executed against an RDF Dataset which represents a collection of graphs. An RDF Dataset comprises one graph, the default graph, which does not have a name, and zero or more named graphs, where each named graph is identified by an IRI. A SPARQL query can match different parts of the query pattern against different graphs as described in section 8.3 Querying the Dataset.

An RDF Dataset may contain zero named graphs; an RDF Dataset always contains one default graph. A query does not need to involve matching the default graph; the query can just involve matching named graphs.</blockquote>

SPARQL 1.1 adds the concept of a ''Graph Store'', essentially a mutable RDF Dataset. The contents of the graphs can be modified, and graphs can be added or removed. SPARQL 1.1 also adds additional discussion about the default graph: Depending on implementation, it could be a separate graph, or a union of all or some of the named graphs.

Graph Store: [http://www.w3.org/TR/sparql11-update/#sec_graphStore Discussion], [http://www.w3.org/TR/sparql11-update/#def_graphstore formal definition] (in [http://www.w3.org/TR/sparql11-update/ SPARQL 1.1 Update])

<blockquote>A Graph Store is a repository of RDF graphs managed by a single service. Like an RDF Dataset operated on by the SPARQL 1.1 Query Language, a Graph Store contains one unnamed graph and zero or more named graphs. Operations may specify graphs to work with, or they may rely on a default graph for that operation. Unless overridden (for instance, by the SPARQL protocol), then the unnamed graph for the store will be the default graph for any operations on that store. Depending on implementation, the unnamed graph may refer to a separate graph, or it could be a representation of a union of other graphs.

Unlike an RDF dataset, named graphs can be added to or deleted from a graph store. A Graph Store needs not be authoritative for the graphs it contains, i.e. the graph URIs do not need to be in the same pay level domain as the endpoint. That means a Graph Store can keep local copies of RDF graphs defined elsewhere on the Web and modify those copies independently of the original graph.

In the simple case, where there is one unnamed graph and no named graphs, SPARQL 1.1 Update is a language for the update of a single graph.</blockquote>

These concepts are applicable beyond SPARQL.

=== OWL's “Ontology Documents” ===
An OWL ontology can be serialized as RDF and stored in a graph store. The general convention is to store each ontology in a separate graph, which is in turn identified with a graph URI. The OWL spec uses the notion of an [http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Ontology_Documents Ontology Document] as the means of organizing ontologies. An Ontology Document has an IRI, but it is left open-ended what that IRI represents (graph in a graph store? file on a file system? web resource?) Can the document IRI and the graph IRI that stores the ontology be the same?

This is especially relevant in the case of an ontology that [http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Imports imports] another ontology. If an ontology is serialized as RDF and stored in a graph store, then there may be an <tt>owl:imports</tt> predicate whose object is an IRI identifying the ontology to import. How do we resolve this IRI to determine which graph contains that ontology, so that we can parse and process its contents?

=== Scope of blank nodes in RDF Semantics ===
RDF Concepts defines an RDF graph as an abstract set of triples. It also defines blank nodes as being scoped to the graph. But clearly a blank node can be part of multiple graphs at the same time, e.g., of a graph and its subgraphs. So, what stops a blank node from occurring in two completely unrelated graphs?

In RDF Semantics this is handled by introducing the operation of merging graphs, which is not the same as a simple set union. Merging graphs involves some rather complicated mechanics for “standardizing apart” blank nodes.

If new concepts beyond the graph as a set of triples were defined, then this would create an opportunity to explain the semantics of RDF in a more compact and intuitive way, removing some of the confusion and stigma that surround blank nodes (if not the implementation challenges).

=== VoID and metadata for RDF datasets ===
[http://www.w3.org/TR/void/ Describing Linked Datasets with the VoID Vocabulary] is a SWIG Note on a metadata vocabulary for RDF datasets. It fuzzily defines the concept of a “dataset” as a “meaningful collection of RDF triples that are published, maintained or aggregated by a single provider.” It states that datasets can be published in different ways, including RDF dumps, SPARQL endpoint, or as collections of multiple RDF documents, but relying on the readers' intuition instead of solid definitions for all these terms. A proper formal definition of VoID is currently lacking, and would require concepts for collections of mutable graphs.

=== Supporting formal alignment of Linked Data principles with RDF and ''AWWW'' ===

The ''Web of Data'', as the macro entity that emerges from the micro principles of ''Linked Data'', can be seen as an RDF Dataset. It contains a potentially unlimited number of named graphs. The contents of graph <nowiki></nowiki> are given by the function <code>get-and-parse</code>, which performs an HTTP get on <nowiki></nowiki> and parses the result with an RDF parser. An actual implementation would of course deviate from this idealized description in many ways (it would likely contain a subset of graphs, which are older snapshots; how are media types handled; what parsers are used; content-type sniffing and tag-soup parsing; redirects; etc etc). But the basic intuition of this model appears to be widespread in the Linked Data community, and is implemented in a number of tools (see Web Crawling use case above).

A formal definition of a concept such as “RDF Dataset”, “Set of Named Graphs”, and the g-box/g-snap/g-text distinction in a core RDF spec would make it easier to formally define such a model, tying together the Linked Data principles and practices, ''[http://www.w3.org/TR/webarch/ Architecture of the World Wide Web]'', and the REST model of information resources and representations, in a formal way.

== Advanced Annotations Use Cases ==

=== Separate Ontology Use Case ===

This use case is derived from a proposal to have OWL annotations that
can be collected together into a separate ontology (and that might even
be able to affect the main ontology). The proposal itself can be seen
at http://www.w3.org/2007/OWL/wiki/Annotation_System however this "use
case" is somewhat of a modification of the suggestions in the proposal.

The basic need is to be able to generate multiple ontologies
(http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/#Ontologies, i.e.,
the basic OWL construct that holds OWL axioms and other stuff)
from a
single OWL document. One ontology is the ontology that corresponds to
the main information in the document. The other ontology (or
ontologies) would sit alongside the main ontology. These secondary
ontologies might be used to store and reason about things like
provenance or certainty.

The secondary ontologies would not necessarily contain information about
the domain of the ontology (and thus need not share axioms with the main
ontology) but could refer to the syntactic bits (axioms, annotations,
etc.) of the main ontology. Note that this does *not* directly require
reflection, as the referenced syntactic bits don't have their semantic
import in the secondary ontologies. Any semantic relationship between
the main ontology and secondary ontologies is mediated by relationships
outside the formalism semantics, again so that there is no need for
reflection or reification or ....

So far this is about (OWL) ontologies, not graphs, but it can easily be
turned into a use case for named graphs. An RDF document that encodes
multiple OWL ontologies would contain named graphs that encode the
secondary ontologies and the main graph of the document would encode the
main ontology. Uses of the names of the named graphs would encode the
links between the main ontology and the secondary ontologies. How to
encode the links from the secondary ontology into the main ontology
remains an unsettled issue, however.

=== Reasoning over annotations ===

We want to support reasoning based on annotations, using a generic approach as defined in <ref name=r1>U. Straccia, N. Lopes, G. Lukacsy, A. Polleres. A General Framework for Representing and Reasoning with Annotated Semantic Web Data. In ''Proceedings of the Twenty-Fourth AAAI Conference on Artificial Intelligence (AAAI-10)'', AAAI Press, 2010. http://axel.deri.ie/publications/stra-etal-2010AAAI.pdf</ref><ref name=r2>N. Lopes, A. Zimmermann, A. Hogan, G. Lukácsy, A. Polleres, U. Straccia, S. Decker. RDF Needs Annotations. In ''RDF Next Steps'', June 2010. http://www.w3.org/2009/12/rdf-ws/papers/ws09</ref><ref name=r3>N. Lopes, A. Polleres, U. Straccia, A. Zimmermann, AnQL: SPARQLing Up Annotated RDFS. In ''Proceedings of the International Semantic Web Conference (ISWC-10)'', no. 6496 in Lecture Notes in Computer Science, Springer-Verlag, 2010, pp.518–533. http://iswc2010.semanticweb.org/pdf/51.pdf</ref>. Annotations include, but are not limited to:

* temporal annotations (when is a statement valid?)
* provenance annotations (where did a statement originate?)
* uncertainty annotations (how likely is a statement to be true?)

For instance, if temporal annotations exist in a dataset, one can ask when a triple holds (e.g., "who was a GoogleEmployee and when?"). If:

<pre>
ex:chadhurley rdf:type ex:YoutubeEmployee . [2005,2010]
ex:YoutubeEmployee rdf:type ex:GoogleEmployee . [2006,2011]
</pre>

then:

<pre>
ex:chadhurley rdf:type ex:GoogleEmployee . [2006,2010]
</pre>

With provenance annotation, if:

<pre>
foaf:Person rdfs:subClassOf foaf:Agent . foaf:
ex:chadhurley rdf:type foaf:Person . dbpedia:
</pre>

then one can infer:

<pre>
ex:chadhurley rdf:type foaf:Agen . foaf: \and dbpedia:
</pre>

Following the same generic framework, it is also possible to deal with fuzzy, probabilistic and uncertain information, e.g.,:

<pre>
ex:pictureAreaXYZ rdf:type ex:HumanFace . 0.82
ex:HumanFace rdfs:subClassOf ex:Ellipse . 0.75
</pre>

Fuzzy-annotated RDF are likely to be produced automatically by tools relying on statistical data or heuristic-based algorithm. Terminological statements with uncertainty are very common outputs of ontology matching algorithms.

In all these situations, identifying the triples or graphs to which attach the annotations is necessary.

== References ==
<references/>

TF-Turtle

Mtiffiel — Wed, 09 Mar 2011 14:18:55 GMT

Mtiffiel: /* Participants */ Added myself as a participant to the Turtle TF

= Task Force "Turtle" =

== Material ==

* [[Inputs_Turtle|Inputs]]
* [[TF-Turtle/Proposals|Proposals]]

== Participants ==
* [http://www.w3.org/2011/rdf-wg/wiki/User:Gcarothe3 Gavin Carothers]
* [http://www.w3.org/2011/rdf-wg/wiki/User:Lfeigenb Lee Feigenbaum]
* [http://www.w3.org/2011/rdf-wg/wiki/User:Andy_Seaborne Andy Seaborne]
* [http://www.w3.org/2011/rdf-wg/wiki/User:Nrixham Nathan Rixham]
* [http://www.w3.org/2011/rdf-wg/wiki/User:sharris2 Steve Harris]
* [http://www.w3.org/2011/rdf-wg/wiki/User:Sandro Sandro Hawke]
* [http://www.w3.org/2011/rdf-wg/wiki/User:Mtiffiel Mischa Tuffield]

TF interests

Mtiffiel — Fri, 18 Feb 2011 01:01:20 GMT

Mtiffiel: linked my name to my User: page . confirmed my interests in two of the task forces

The table content is based on the users’ own pages…

{| border=1
|
! Turtle Spec
! JSON Serialization
! Graph Identification
|-
| [[User:Jbaget|Jean-François Baget, INRIA]]
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Sbauer2|Scott Bauer, Mayo Clinic]]
| align="center" |
| align="center" |
| align="center" |
|-
| Dan Brickley, VU
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Mbrunati|Matteo Brunati, IWA-HWG Association]]
| align="center" |
| align="center" | ✓
| align="center" |
|-
| [[User:Gcarothe3|Gavin Carothers]], TopQuandrant
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Jcarroll|Jeremy Carroll, TopQuandrant]]
| align="center" |
| align="center" |
| align="center" | ✓
|-
| [[User:Pchampin|Pierre-Antoine Champin, Un Lyon]]
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Ocorby|Olivier Corby, INRIA]]
| align="center" |
| align="center" |
| align="center" | ✓
|-
| [[User:Rcygania2|Richard Cyganiak, DERI]]
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| [[User:Sdas2|Souripriya Das, Oracle]]
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Lfeigenb|Lee Feigenbaum]], Cambridge Semantics
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| Dieter Fensel, Ontotext
| align="center" |
| align="center" |
| align="center" | ?
|-
| [[User:Fgandon|Fabien Gandon, INRIA]]
| align="center" |
| align="center" |
| align="center" | ✓
|-
| Alex Hall, Revelytix
| align="center" |
| align="center" |
| align="center" |
|-
| Michael Hausenblas, DERI
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Sharris2|Steve Harris, Garlik]]
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| [[User:Sandro|Sandro Hawke, W3C]]
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Phayes3|Pat Hayes, Invited Expert]]
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| [[User:Ivan|Ivan Herman, W3C]]
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Nhumfrey|Nicholas Humfrey, BBC]]
| align="center" | ✓
| align="center" | ✓
| align="center" |
|-
| [[User:CMatheus|Christopher Matheus, Alcatel-Lucent]]
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Peter_F_Patel-Schneider|Peter F Patel-Schneider, Alcatel-Lucent]]
| align="center" |
| align="center" |
| align="center" | ✓
|-
| Axel Polleres, DERI
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Yraimond|Yves Raimond, BBC]]
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| [[User:Nrixham|Nathan Rixham, Invited Expert]]
| align="center" | ✓
| align="center" | ✓
| align="center" | ✓
|-
| Guus Schreiber, VU
| align="center" |
| align="center" |
| align="center" |
|-
| Andy Seaborne, Apache
| align="center" | ✓
| align="center" | ✓
| align="center" | ✓
|-
| [[User:Msporny|Manu Sporny, Digital Bazaar]]
| align="center" |
| align="center" | ✓
| align="center" | ✓
|-
| [[User:Tsteiner|Thomas Steiner, Google]]
| align="center" | ✓
| align="center" | ✓
| align="center" |
|-
| [[User:Mtiffiel|Mischa Tuffield, Garlik]]
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| [[User:Dwood4|David Wood, Talis]]
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:ZheWu|Zhe (Alan) Wu, Oracle]]
| align="center" |
| align="center" |
| align="center" |
|-
| Mohamed Zergaoui, Innovimax
| align="center" |
| align="center" |
| align="center" |
|-
| Antoine Zimmermann, Un Lyon
| align="center" |
| align="center" |
| align="center" | ✓
|}

TF interests

Mtiffiel — Wed, 16 Feb 2011 16:36:07 GMT

Mtiffiel: added mischa's interest

The table content is based on the users’ own pages…

{| border=1
|
! Turtle Spec
! JSON Serialization
! Graph Identification
|-
| Jean-François Baget, INRIA
| align="center" |
| align="center" |
| align="center" |
|-
| Scott Bauer, Mayo Clinic
| align="center" |
| align="center" |
| align="center" |
|-
| Dan Brickley, VU
| align="center" |
| align="center" |
| align="center" |
|-
| Matteo Brunati, IWA-HWG Association
| align="center" |
| align="center" | ✓
| align="center" |
|-
| Gavin Carothers, TopQuandrant
| align="center" |
| align="center" |
| align="center" |
|-
| Jeremy Carroll, TopQuandrant
| align="center" |
| align="center" |
| align="center" | ✓
|-
| Pierre-Antoine Champin, Un Lyon
| align="center" |
| align="center" |
| align="center" |
|-
| Olivier Corby, INRIA
| align="center" |
| align="center" |
| align="center" | ✓
|-
| Richard Cyganiak, DERI
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| Souripriya Das, Oracle
| align="center" |
| align="center" |
| align="center" |
|-
| Lee Feigenbaum, Cambridge Semantics
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| Dieter Fensel, Ontotext
| align="center" |
| align="center" |
| align="center" |
|-
| Fabien Gandon, INRIA
| align="center" |
| align="center" |
| align="center" | ✓
|-
| Alex Hall, Revelytix
| align="center" |
| align="center" |
| align="center" |
|-
| Michael Hausenblas, DERI
| align="center" |
| align="center" |
| align="center" |
|-
| Steve Harris, Garlik
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| Sandro Hawke, W3C
| align="center" |
| align="center" |
| align="center" |
|-
| Pat Hayes, Invited Expert
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| Ivan Herman, W3C
| align="center" |
| align="center" |
| align="center" |
|-
| [[User:Nhumfrey|Nicholas Humfrey, BBC]]
| align="center" | ✓
| align="center" | ✓
| align="center" |
|-
| Christofer Matheus, Alcatel-Lucent
| align="center" |
| align="center" |
| align="center" |
|-
| Peter F Patel-Schneider, Alcatel-Lucent
| align="center" |
| align="center" |
| align="center" |
|-
| Axel Polleres, DERI
| align="center" |
| align="center" |
| align="center" |
|-
| Yves Raimond, BBC
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| Nathan Rixham, Invited Expert
| align="center" | ✓
| align="center" | ✓
| align="center" | ✓
|-
| Guus Schreiber, VU
| align="center" |
| align="center" |
| align="center" |
|-
| Andy Seaborne, Apache
| align="center" | ✓
| align="center" | ✓
| align="center" | ✓
|-
| Manu Sporny, Digital Bazaar
| align="center" |
| align="center" | ✓
| align="center" | ✓
|-
| Thomas Steiner, Google
| align="center" |
| align="center" | ✓
| align="center" |
|-
| Mischa Tuffield, Garlik
| align="center" | ✓
| align="center" |
| align="center" | ✓
|-
| David Wood, Talis
| align="center" |
| align="center" |
| align="center" |
|-
| Zhe (Alan) Wu, Oracle
| align="center" |
| align="center" |
| align="center" |
|-
| Mohamed Zergaoui, Innovimax
| align="center" |
| align="center" |
| align="center" |
|-
| Antoine Zimmermann, Un Lyon
| align="center" |
| align="center" |
| align="center" | ✓
|}

User:Mtiffiel

Mtiffiel — Thu, 10 Feb 2011 11:40:05 GMT

Mtiffiel: Added in some stuff about me

== Mischa Tuffield ==

I represent [http://www.garlik.com/ Garlik] on the RDF WG (our main representative is Steve Harris). I am a developer at Garlik, and before that worked at the University of Southampton on the AKT project. Garlik run a number of services all of which make heavy use of RDF and SPARQL technology, as well as being a vendor of RDF databases, namely 4store (GPL) and 5store (proprietary). My personal interest in the working group are around the standardisation of named graphs, turtle, and the aliment of RDF's URIRefs to the more modern IRIs. This is so that RDF imported via SPARQL Update, can always be outputted as valid RDF via the CONSTRUCT verb.

We have written a book chapter about how Garlik makes use of RDF and Semantic Web tech from a software engineering perspective [1]. I built and maintain the [http://foaf.qdos.com/validator/ FOAF validator], as well a number of services on [http://qdos.com/apps foaf.qdos.com].

[1] Harris, S., Ilube, T. and Tufﬁeld M. (2010) [http://4store.org/publications/garlik-linked-enterprise-data-2010.pdf Enterprise Linked Data as Core Business Infrastructure] in book [http://www.amazon.co.uk/dp/1441976647 Linking Enterprise Data]

For more information about me, check my personal homepage at [http://mmt.me.uk/ http://mmt.me.uk/]. I tend to hang around in #swig on freenode under the alias of mischat.

=== W3C Experience ===

I helped author and was one of the editors of the [http://www.w3.org/2005/Incubator/socialweb/XGR-socialweb/index.html Social Web XG's Final Report].

I am also on the newly started [http://www.w3.org/2005/Incubator/webid/ WebID XG].