- From: Brent Shambaugh <brent.shambaugh@gmail.com>
- Date: Sat, 19 Mar 2016 10:33:36 -0400
- To: public-rww <public-rww@w3.org>
- Message-ID: <CACvcBVqcoAiELSfCBMi+gkeUNJbKKWzkZRUCtNxVOZQsyGzhGg@mail.gmail.com>
Using scipeople:hasAuthored for each individual related triple would it seems, but that is painful. Or maybe not, as long as I tell the computer to do it :). -Brent Shambaugh Website: bshambaugh.org On Sat, Mar 19, 2016 at 10:29 AM, Brent Shambaugh <brent.shambaugh@gmail.com > wrote: > Thank you Melvin and Markus. Here are my thoughts. > > With owl:sameAs I can only link to my name or something very similar in a > different datasource. This could be perfectly fine, but my intention might > be to link to a collection of triples (say on a LDP server) because I mean > to direct the focus there. This might be built on the fly if I know , or am > able to infer every other triple that was linked by creating the owl:sameAs > link. > > Maybe more generally I might say bshambaugh.org/foaf.rdf#me > scipeople:hasAuthored http://bshambaugh.rww.io/ (great because it could > include multiple authors). A problem with this could be that it is not > generally recognized as a link in the linked data world. As an example, I > was using LodLive the other day, and it was programmaticly constrained to > follow only certain links (this makes sense b/c otherwise the graph would > be a mess to see). Perhaps rdfs:seeAlso could do, but it does not tell me > much semantically beyond a hyperlink IMHO. > If I wanted to create two LDP containers and have them be essentially the > same, then I could say http://localhost:8080/marmotta/ldpBrentsRWW-1 > owl:sameAs http://bshambaugh.rww.io/ . I could then include this in other > LDP containers. I might want to however build a set of triples that were > associated with me that exist somewhere regardless of where they are > stored. Working at the document level of linking LDP containers might not > do the trick. Using scipeople:hasAuthored for each individual related > triple would it seems, but that is painful. > > > @prefix scipeople: <http://lod.taxonconcept.org/ontology/sci_people.owl> > > -Brent Shambaugh > > Website: bshambaugh.org > > On Sat, Mar 19, 2016 at 5:52 AM, Markus Sabadello < > markus@projectdanube.org> wrote: > >> Reminds me of this (several years old) paper by Harry Halpin and others: >> https://www.w3.org/2009/12/rdf-ws/papers/ws21 >> >> "When owl:sameAs isn’t the Same: An Analysis of Identity Links on the >> Semantic Web" >> >> It argues that people have been using owl:sameAs for four slightly >> different purposes: >> - Same Thing As But Referentially Opaque >> - Same Thing As But Different Context >> - Represents >> - Very Similar To >> >> Markus >> >> >> On 19.03.2016 10:14, Melvin Carvalho wrote: >> >> >> >> On 19 March 2016 at 01:30, Brent Shambaugh <brent.shambaugh@gmail.com> >> wrote: >> >>> I just found it was wicked cool that I could link another linked data >>> platform server from another. I was messing around and I inserted >>> owl:sameAs. Is there a best practice? Please ignore my other nonsensical >>> triples :) >>> >> >> Yes, exactly owl : sameAs allows two URIs to be the same. >> >> >>> >>> curl -iX POST -H "Content-Type: text/turtle" -H "Slug: >>> BrentsRWW" --data @/var/www/data/brentrww.ttl >>> http://localhost:8080/marmotta/ldp/ >>> >>> with >>> >>> HTTP/1.1 201 Created >>> Server: Apache Marmotta/3.3.0 (build 0) >>> ETag: W/"1458340352000" >>> Last-Modified: Fri, 18 Mar 2016 22:32:32 GMT >>> Link: < >>> http://wiki.apache.org/marmotta/LDPImplementationReport/2014-09-16>; >>> rel="http://www.w3.org/ns/ldp#constrainedBy" >>> Link: <http://www.w3.org/ns/ldp#Resource>; rel="type" >>> Link: <http://www.w3.org/ns/ldp#RDFSource>; rel="type" >>> Link: <http://www.w3.org/ns/ldp#Container>; rel="type" >>> Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type" >>> Location: http://localhost:8080/marmotta/ldp/BrentsRWW-1 >>> Content-Length: 0 >>> Date: Fri, 18 Mar 2016 22:32:32 GMT >>> >>> cat brentrww.ttl >>> >>> @prefix dc: <http://purl.org/dc/terms/> . >>> @prefix foaf: <http://xmlns.com/foaf/0.1/> . >>> @prefix owl: <http://www.w3.org/2002/07/owl#> . >>> >>> <> a foaf:PersonalProfileDocument; >>> foaf:primaryTopic <#me> ; >>> dc:title 'Brent Files' . >>> >> >> Great use of primary topic here! >> >> >>> >>> <#me> a foaf:Person; >>> foaf:name 'Brent Shambaugh Files' ; >>> owl:sameAs <http://bshambaugh.rww.io> . >>> >> >> You'd probably want to link the sameAs to the corresponding #me value in >> the second server, rather than the root document. >> >> It is better to associate data with data, rather than, data with >> documents. Documents are the delivery mechanism for data. We should >> possibly right an FAQ on this, as it can be a source of confusion sometimes >> when starting out with linked data. >> >> >>> >>> >>> >>> >>> -Brent Shambaugh >>> >>> Website: bshambaugh.org >>> >> >> >> >> >> ------------------------------ >> [image: Avast logo] >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >> >> This email has been checked for viruses by Avast antivirus software. >> www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >> >> >
Received on Saturday, 19 March 2016 14:34:04 UTC