- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 2 Sep 2019 00:30:51 -0400
- To: public-rdf-star@w3.org
- Message-ID: <9192f9e1-730d-e4bc-2e5b-3ffea426d400@openlinksw.com>
On 9/1/19 2:46 PM, Olaf Hartig wrote: > Ted, > > On fredag 30 augusti 2019 kl. 16:43:34 CEST Ted Thibodeau Jr wrote: >> Olaf, Kingsley, others -- >> >> Perhaps instead of the overloaded ex:claims predicate now >> being hammered at, and I think distracting from the meatier >> subjects at hand, you might switch to using an example >> predicate like ex:asserts which local-part is at least >> *less* over-loaded and hopefully therefore more clearly >> and intuitively understood? > An excellent suggestion! ;-) > > Thanks, > Olaf Olaf, Is the following an accurate working example ? ## Turtle Start ## @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix : <#> . <> a foaf:Document . <> foaf:name "Document about Alice"@en . <> foaf:primaryTopic :Alice . :Alice rdf:type foaf:Person . :Alice foaf:name "Alice" . :Bob rdf:type foaf:Person . :Bob foaf:name "Bob" . :Bob foaf:age "23"^^xsd:integer . # Context clarity regarding :asserts relation :asserts a rdf:Property . :asserts rdfs:domain foaf:Person . :asserts rdfs:range rdf:Statement . # :Alice :asserts << :Bob foaf:age"23"^^xsd:integer >> . # is suggested syntax sugar what follows :Alice :asserts [ a rdf:Statement; rdf:subject :Bob ; rdf:predicate foaf:age ; rdf:object "23"^^xsd:integer ] . ## Turtle End ## Kingsley > > >> I am suggesting this in significant part because I like >> to think and speak of triples/quads as assertions, which >> obviously have provenance (e.g., the asserter, at a place, >> at a time, in a document), among other attributes. >> >> I dislike thinking or speaking of triples/quads as facts, >> because facts do not typically have provenance as such -- >> they simply *are* -- and because triples/quads can be just >> as easily used to encode falsehoods and nonsensicals as >> truths (e.g., >> >> { PREFIX ex: <#> >> ex:the_sea ex:is ex:boiling_hot . >> ex:pigs ex:have ex:wings . >> } >> >> ), >> and the simple (ahem) fact that such statements have been >> encoded as triples/quads should not be sufficient to >> indicate that they are (or ever have been, or ever will >> be) true -- nor even *asserted* to be true. >> >> (I might, for instance, encode a number of falsehoods as >> triples within a named graph, which is then used to test >> whether other named graphs should be considered more or >> less trustworthy, based on the number of such falsehoods >> contained in the graph under test.) >> >> >> (Who is this "Ted" guy? I've been employed by OpenLink >> Software, working with Kingsley et al since late 2000, and >> involved in a number of W3 XGs, CGs, and WGs in that time. >> Recent highlights include late-term co-chairing of the >> SHACL WG, and active contributions to the Verifiable Claims >> WG and the Credentials CG.) >> >> Regards, >> >> Ted > -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 2 September 2019 04:31:17 UTC