- From: Michael Brunnbauer <brunni@netestate.de>
- Date: Sat, 21 Feb 2015 21:38:35 +0100
- To: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Cc: public-lod@w3.org
- Message-ID: <20150221203835.GA14453@netestate.de>
Hello Stian, I admit that what you sketch here is better than what I have sketched with named graphs. But it seems to require a very sophisticated editor or a very sophisticated user. I was talking about an editor where the user can add triples with arbitrary properties. So I would prefer the solution with named graphs that can be implemented easily. Yes, the additional information will be very vague without context but it will at least be there. Regards, Michael Brunnbauer On Fri, Feb 20, 2015 at 09:53:05PM +0000, Stian Soiland-Reyes wrote: > Sorry, now I forgot my strawman! Too late on a Friday.. > > So say the user of an triple-order-preserving UI says: > > <document> prov:wasAttributedTo :alice, :charlie, :bob. > > .. And consider the order important because Bob didn't contribute as much > to the document as Alice and Charlie. > > In that case the above statements is not detailed enough and some new > property or resource is needed to represent this distinction in RDF. > > Here I would think OWL fear combined with desire to reuse existing > vocabularies mean that you don't get specific enough. Its OK to state the > same relation with two different properties, and even better to make a new > sub property that explains the combination. > > In the strawman, using more specific properties like pav:authoredBy and > prov:wasInfluencedBy would clarify the distinction much more than an > ordered list with an unspecified order criteria. > > In other cases the property is really giving a shortcut, say; > > <meeting> :attendedBy :john, :alice, :charlie . > > ..And the user is also encoding arrival time at the meeting by the list > order. > > But this is using :attendesBy to describe both who were there, and when > they arrived. In this case, the event of arriving could better be modelled > separately with a partial ordering. > > If you don't like double housekeeping (most programmers know the pitfalls > here), then using OWL or inference rules you can also infer attendance > from the arrival events. -- ++ 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 20:39:02 UTC