- From: Steve Harris <steve.harris@garlik.com>
- Date: Wed, 1 Aug 2012 12:14:51 +0100
- To: David Booth <david@dbooth.org>
- Cc: Hugh Glaser <hg@ecs.soton.ac.uk>, Melvin Carvalho <melvincarvalho@gmail.com>, Natasa Bulatovic <bulatovic@mpdl.mpg.de>, "<semantic-web@w3.org>" <semantic-web@w3.org>
On 2012-07-31, at 15:30, David Booth wrote:
> I find the idea of using subPropertyOf quite creative and intriguing,
> and it may be a good solution in some cases. But it does have the
> downside of requiring inference (to recognize that :knows3412 is a
> subPropertyOf foaf:knows), whereas the named graph approach doesn't.
Not necessarily, if you exercise some restraint in the degree to which you apply subPropertyOf, it can be done in straight SPARQL 1.0 with little pain:
SELECT * WHERE {
<alice> ?p <bob> .
?p rdfs:subPropertyOf :married .
?p dc:date ?date .
}
- Steve
--
Steve Harris, CTO
Garlik, a part of Experian
+44 7854 417 874 http://www.garlik.com/
Registered in England and Wales 653331 VAT # 887 1335 93
Registered office: Landmark House, Experian Way, Nottingham, Notts, NG80 1ZZ
Received on Wednesday, 1 August 2012 11:15:22 UTC