Hello Stian, On Fri, Feb 20, 2015 at 09:54:33AM +0000, Stian Soiland-Reyes wrote: > So if you tell the user his information is just RDF, but neglect to mention > "and then some", he could wrongfully think that his list of say "preferred > president" has its order preserved in any exposed RDF. Then tell the user his information is just a RDF dataset. > My apologies, I got the impression there was a suggestion to control > ordering of triples without making any collection statements. I would suggest to do that with named graphs. We are talking about a generic triple editor and IMO most properties are not compatible with collections. Of course, there would also be a "default graph mode" in the editor that does not use named graphs and does not support ordering. > >> Don't let the user encode information he considers important in a way > that is not preserved semantically. Named graphs can be queried via SPARQL. You can query the default (union) graph where this information would be lost or the named graphs where it is preserved semantically and publicly accessible. Regards, Michael Brunnbauer -- ++ Michael Brunnbauer ++ netEstate GmbH ++ Geisenhausener Straße 11a ++ 81379 München ++ Tel +49 89 32 19 77 80 ++ Fax +49 89 32 19 77 89 ++ E-Mail brunni@netestate.de ++ http://www.netestate.de/ ++ ++ Sitz: München, HRB Nr.142452 (Handelsregister B München) ++ USt-IdNr. DE221033342 ++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer ++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
Received on Friday, 20 February 2015 11:34:46 UTC