- From: Martynas Jusevičius <martynas@graphity.org>
- Date: Sat, 21 Feb 2015 15:16:30 +0100
- To: Michael Brunnbauer <brunni@netestate.de>, public-lod <public-lod@w3.org>
Hey Michael, the resource description being edited is loaded with a SPARQL query. The updated description is inserted using SPARQL update. Although often it is useful to edit and update full content from a named graph using Graph Store Protocol instead. So view and update mechanisms are not necessarily symmetrical. Triple objects also can ordered alphabetically? We use ordering resources by properties (e.g. container items) a lot, but it is more relevant in the view case than in the edit case. Does that answer your question? If not, I'm not exactly sure what kind of ordering you are referring to, or why it is relevant. On Fri, Feb 20, 2015 at 8:49 PM, Michael Brunnbauer <brunni@netestate.de> wrote: > > Hello Martynas, > > On Fri, Feb 20, 2015 at 06:04:49PM +0100, Martynas Jusevi??ius wrote: >> The layout is generated with XSLT from RDF/XML. The triples are >> grouped by resources. Within a resource block, properties are sorted >> alphabetically by their rdfs:labels retrieved from respective >> vocabularies. > > So the ordering of triple objects cannot be controlled by the user and this > ordering is not relevant for your use case? > > 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 Saturday, 21 February 2015 14:16:58 UTC