-
Notifications
You must be signed in to change notification settings - Fork 1
Summary
Status: Ready for consideration by working group
Example:
r:47e1cf2
a :Commit ;
:delete << :bob :age 23 >> ;
:add << :bob :age 24 >> ,
<< :bob :friend _:f >> ,
<< _:f :age 22 >> .
Implications: This use case requires complete opaqueness, including for blank nodes, as blank nodes in the commit deltas refer to specific blank nodes in a graph. There does not appear to be a need for multiple occurrences of the same triple. It is unclear which version of transparency is best here.
Status: Ready for consideration by working group
Example:
[] rdf:type crm:E17_Type_Assignment ;
crms:effect << ex:Ioannes_68 rdf:type ex:Gender_Eunuch >> ;
crm:P14_carried_out_by <ex:Paphlagonian_family> ;
rdfs:label "Castration gender assignment" .
Implications: Events are semantic entities, so this use case requires complete transparency. There can be two events with the same base triple, so unique quoted triples cannot be used directly, requiring occurrences of triples to be used instead.
Status: Ready for consideration by working group
Example - not captured correctly as labelled property graphs are multi-graphs.
:a :b :c {| :d 1 |} .
:a :b :c {| :e 1 |} .
Implications: Labelled property graphs do not store the string version of literals, so literals are treated transparently. Labelled property graphs can have multiple edges with the same start node, end node, and relationship type, so unique quoted triples cannot be used directly, requiring occurrences of triples to be used instead.
Status: Ready for consideration by working group
Example of results for a federated SPARQL query
| personA | personB | name | sourceOfName |
|---|---|---|---|
:Alice |
:Bob |
"Bob" |
http://example.org/endpoint2/sparql |
:Bob |
:Alice |
"Alice" |
http://example.org/endpoint1/sparql |
Implications:
This use case is about adding a new feature to SPARQL to capture source information, although CONSTRUCT queries using source information are naturally captured as annotations on triples.
Status: Ready for consideration by working group
Example:
<Q14739#SIP9E6E0C5B850FBF4F> up:fullName "3-beta-hydroxysterol Delta (14)-reductase"
{| up:attribution [ up:manual true ;
up:evidence ECO:0000303 ;
up:source citation:16784888 ]
|} .
Implications: This is a use case like provenance, but asks for transparent treatment of quoted triples. It thus goes against the characterization of provenance as needing a semi-opaque treatment of quoted triples. It is unclear whether provenance can be placed directly on triples or whether there is a need for something like occurrences of triples.
Status: Ready for consideration by working group
Example:
<print> bibo:isbn "123"
{| q:occurrence [ bf:status st:invalid ] ;
bf:source [ :backCoverOf <print> ]
|} .
Implications: Some of this use case can be handled by creating occurrences of triples as a place to put annotations. Other parts raise the issue of whether an event can be modeled as something attached to a triple relating two (main?) entities involved in the event.
Status: In progress
Example:
adr:Event1
a schema:Event ;
schema:location adr:Place1 .
<< adr:Event1 schema:location adr:Place1 >>
prov:wasDerivedFrom adr:Dataset#1 ,
adr:Dataset#2 ;
prov:wasGeneratedBy [ a prov:Activity ;
prov:used adr:AssertionAlgorithm#1 ;
prov:endedAtTime "2023-09-20T20:00:00-04:00"^^xsd:dateTime ] .
<< adr:Event1 schema:location adr:Place2 >>
prov:wasDerivedFrom adr:Dataset#3 ,
adr:Dataset#4 .
Implications: This is another provenance use case. It is unclear what version of transparency is desired and whether occurrences are needed.
Status: Ready for consideration by working group
Example:
_:s1
a wikibase:Statement ;
rdfstar:occurence_of << wd:USA wd:president wd:JoeBiden >> ;
wikibase:rank wikibase:PreferredRank ;
wd:start_date "2021-01-20"^^xsd:dateTime ;
wd:predecessor wd:DonaldTrump ;
prov:wasDerivedFrom wdref:a_reference .
Implications: Wikidata is transparent about literals and has no way of asserting object equality, so has no preference on transparency of IRIs. Wikidata allows multiple statements with the same subject, predicate, and object, so information will be associated with occurrences of triples.
Status: Ready for consideration by working group
Example:
<introduction-to-physics>
a :Text ;
bf:classification <literature-education-physics> .
<< <literature-education-astrology> bf:assigner <annif> >>
rdfs:comment "Not correct." .
<literature-education-physics>
a :Topic ;
dc:creator <education-consortium> ;
dc:created "2023-05-20T08:44:06Z" .
<introduction-to-physics>
a :Text ;
bf:classification <literature-education-physics> {| bf:assigner <annif> ;
dc:date "2023-05-20T08:44:06Z"
|} .
Implications: This is a provenance use case. When multiple sources and multiple recorders are involved, provenance becomes more central, and the veracity of statements also comes into question. The transparency of literals and IRIs has yet to be determined. The provenance examples suffer from using two independent links to create a single relationship.
Status: Ready for consideration by working group
Example:
<7d5d0d651caa>
a :Text {| :statedIn <data?version=2> |} .
<< <7d5d0d651caa> a :Work >>
:statedIn <data?version=1> ;
:retractedIn <data?version=2> .
<< <7d5d0d651caa> :subject <semantics> >>
:suggestedBy <classifyer> {| :statedIn <data?version=2> |} .
Implications: This is similar to, but slightly different from, provenance use cases. Opacity is the opacity of the underlying semantics of quoted triples. Whether this is a benefit depends on what transparency is wanted in the use case.
Status: Ready for consideration by working group
Example:
<< _:b1 :givenName "Alice" >>
rdfg:subGraphOf _:d1 .
<< _:b1 :familyName "Liddell" >>
rdfg:subGraphOf _:d1 .
<< _:b1 :birthDate "1852-05-04" >>
rdfg:subGraphOf _:d1 .
_:d1
dc:source <https://en.wikipedia.org/wiki/Alice_Liddell> ;
dc:date "2023-10-23" .
Implications: This is a variation on other use cases where information is associated with multiple triples. This can be done in a number of ways. With quoted triples, a good way is to have a different stand-off relationship from a quoted triple to the group of triples. Transparency probably depends on the needs of the underlying information.