...
Planning | Description | Requirements | UI Mockup | Triples Examples | ORE Triples Queries Examples
...
Table of Contents
Table of Contents |
---|
...
Name | Prefix | URL | Details | Comments |
---|---|---|---|---|
RDF | rdf | http://www.w3.org/1999/02/22-rdf-syntax-ns# | specification | |
RDF Schema | rdfs | http://www.w3.org/2000/01/rdf-schema# | specification | |
Dublin Core | dc | http://purl.org/dc/elements/1.1/ | specification | |
Dublin Core Terms | dcterms | http://purl.org/dc/terms | specification | Required by OA |
Dublin Core Types | dctype | http://purl.org/dc/dcmitype | specification | Required by OA |
Content | cnt | http://www.w3.org/2011/content# | specification | Required by OA |
ORE | ore | http://www.openarchives.org/ore/ 1.0terms/vocabulary#otherRelationships | specification | Recommended as an alternative to the Collections ontology by Rob. Represents both ordered and unordered items using the Aggregation class. |
IANA | iana | http://www.iana.org/assignments/relation/ | specification | ORE uses this ontology for first, last, next, and prev predicates. |
Collections | co | http://purl.org/co | Can represent unordered items using the Bag class and ordered items using the List class. | |
Open Annotation | oa | http://www.w3.org/ns/oa | specification | |
Friend of a Friend | foaf | http://xmlns.com/foaf/0.1 | specification | Also used by OA |
...
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix dc: <http://purl.org/dc/elements/1.1/> . @prefix dcterms: <http://purl.org/dc/terms> . <http://localhost:3000/individual/vc155> dcterms:title "My Virtual Collection" ; dcterms:description "These are resources I am gathering together for personal use." ; dc:creator <http://vivo.cornell.edu/individual/individual24416> . |
QUESTIONS:
- Should dc:creator be used for ownership role?
- ANSWER: NO - per Paolo
- REASON: Muddy concept. Did the user create the resource or add the resource to the collection?
- ALTERNATIVE: Under exploration. Paolo recommends looking at...
- PROV ontology - provenance
- PAV ontology - provenance, authoring, and versioning
Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
| ||||||||||||||||
Expand | ||||||||||||||||
| ||||||||||||||||
|
...
Collections ontology | ORE ontology | ||
---|---|---|---|
– | unordered and ordered collections are represented by two separate class constructs, Bag and List respectively | + | unordered and ordered collections are represented by the same class construct, Aggregation |
+ | item property names are easy to understand (e.g., index, itemContent, nextItem) | – | item property names are cryptic (e.g., proxyFor, proxyIn, next) |
– | order is determined by an item property pointing to the next item, i.e., nextItem. | – | order is determined by an item property pointing to the next item, i.e., next |
– | URI for the item is not associated with the collection class (e.g., List, Bag). +URI for the item is associated withcan be associated directly to the collection class through co:element. co:element is defined through a chain: has sub-property chains [has item o has item content]. That means that the inference layer can resolve both (Paolo). | + | URI for the item is associated with the collection class (i.e., Aggregation) via of the aggregates property. (i.e., Aggregation) via of the aggregates property. |
+ | URI for the item is associated with the item class (i.e., Item) via the itemContent property. | + | URI for the item is associated with the item class (i.e., Proxy) via the proxyFor property. |
...
...
Ordered Collection Examples
...
Example 1-co: A Virtual Collection as an ordered collection of items using Collection Ontology's List with one item
...
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
|
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix co: <http://purl.org/co> . <http://localhost:3000/individual/vc155> a co:List ; co:size "1"^^xsd:nonNegativeInteger ; co:firstItem <http://localhost:3000/individual/vci162> ; co:item <http://localhost:3000/individual/vci162> ; co:lastItem <http://localhost:3000/individual/vci162> . <http://localhost:3000/individual/vci162> a co:ListItem co:index "1"^^xsd:positiveInteger ; co:itemContent <http://da-rdf.library.cornell.edu/individual/b3652730> . |
...
Example 1-ore: A Virtual Collection as an ordered collection of items using ORE Ontology's Aggregation with one item
...
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
|
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix ore: <http://www.openarchives.org/ore/terms/> . <http://localhost:3000/individual/vc155> a ore:Aggregation ; ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652730> . |
Example 2-co: A Virtual Collection as an ordered collection of items using Collection Ontology's List with multiple ordered items
...
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix co: <http://purl.org/co> . <http://localhost:3000/individual/vc155> a co:List ; co:size "4"^^xsd:nonNegativeInteger ; co:firstItem <http://localhost:3000/individual/vci162> ; co:item <http://localhost:3000/individual/vci162> ; co:item <http://localhost:3000/individual/vci163> ; co:item <http://localhost:3000/individual/vci164> ; co:item <http://localhost:3000/individual/vci165> ; co:lastItem <http://localhost:3000/individual/vci165> . <http://localhost:3000/individual/vci162> a co:ListItem ; co:index "1"^^xsd:positiveInteger ; co:itemContent <http://da-rdf.library.cornell.edu/individual/b3652730> ; co:nextItem <http://localhost:3000/individual/vci163> . <http://localhost:3000/individual/vci163> a co:ListItem ; co:index "2"^^xsd:positiveInteger ; co:itemContent <http://da-rdf.library.cornell.edu/individual/b3652234> ; co:nextItem <http://localhost:3000/individual/vci164> . <http://localhost:3000/individual/vci164> a co:ListItem ; co:index "3"^^xsd:positiveInteger ; co:itemContent <http://da-rdf.library.cornell.edu/individual/b3652543> ; co:nextItem <http://localhost:3000/individual/vci165> . <http://localhost:3000/individual/vci165> a co:ListItem ; co:index "4"^^xsd:positiveInteger ; co:itemContent <http://da-rdf.library.cornell.edu/individual/b3652884> . |
...
Example 2-ore: A Virtual Collection as an ordered collection of items using ORE Ontology's Aggregation with multiple ordered items
...
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix ore: <http://www.openarchives.org/ore/terms/> . @prefix iana: <http://www.iana.org/assignments/relation/> . <http://localhost:3000/individual/vc155> a ore:Aggregation ; ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652730> ; ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652234> ; ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652543> . <http://localhost:3000/individual/pxy162>vci162> a ore:Proxy ; ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652730> ; ore:proxyIn <http://localhost:3000/individual/vc155> ; iana:next <http://localhost:3000/individual/pxy163>vci163> . <http://localhost:3000/individual/pxy163>vci163> a ore:Proxy ; ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652234> ; ore:proxyIn <http://localhost:3000/individual/vc155> ; iana:next <http://localhost:3000/individual/pxy164>vci164> . <http://localhost:3000/individual/pxy164>vci164> a ore:Proxy ; ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652543> ; ore:proxyIn <http://localhost:3000/individual/vc155> . |
...
Unordered Collection Examples
Example 3-co: A Virtual Collection as an unordered collection of items using Collection Ontology's Bag with one item
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Code Block | ||
---|---|---|
Code Block | ||
| ||
| ||
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix co: <http://purl.org/co> . <http://localhost:3000/individual/vc155>vc255> a co:Bag ; co:size "1"^^xsd:nonNegativeInteger ; co:firstItem <http://localhost:3000/individual/vci162> ; co:item <http://localhost:3000/individual/vci162> ; co:lastItem <http://localhost:3000/individual/vci162>vci262> . <http://localhost:3000/individual/vci162>vci262> a co:ListItemItem ; co:indexitemContent "1"^^xsd:positiveInteger ; co:itemContent <http://<http://da-rdf.library.cornell.edu/individual/b3652730> . |
...
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix ore: <http://www.openarchives.org/ore/terms/> . <http://localhost:3000/individual/vc155>vc255> a ore:Aggregation ; ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652730> . |
...
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix rdf: <http://localhost:3000/individual/vci163> www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix co: <http://purl.org/co#nextItem> co> . <http://localhost:3000/individual/vci164> vc255> a co:Bag ; co:size "4"^^xsd:nonNegativeInteger ; co:item <http://localhost:3000/individual/vci164> vci262> ; co:item <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://purl.org/co#ListItem> localhost:3000/individual/vci263> ; co:item <http://localhost:3000/individual/vci164> vci264> ; co:item <http://localhost:3000/individual/purl.org/co#index> "3"^^xsd:positiveInteger vci265> . <http://localhost:3000/individual/vci164> <http://purl.org/co#itemContent> vci262> a co:ListItem ; co:itemContent <http://da-rdf.library.cornell.edu/individual/b3652543> b3652730> . <http://localhost:3000/individual/vci164> vci263> a co:ListItem ; co:itemContent <http://purl.org/co#nextItem> da-rdf.library.cornell.edu/individual/b3652234> . <http://localhost:3000/individual/vci165> <http://localhost:3000/individual/vci165> vci264> a co:ListItem ; co:itemContent <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://purl.org/co#ListItem> da-rdf.library.cornell.edu/individual/b3652543> . <http://localhost:3000/individual/vci165> vci265> a<http://purl.org/co#index> "4"^^xsd:positiveInteger <http://localhost:3000/individual/vci165> <http://purl.org/co#itemContent> co:ListItem ; co:itemContent <http://da-rdf.library.cornell.edu/individual/b3652884> . | ||||
Code Block | ||||
|
(Paolo) This can be simplified to (see https://code.google.com/p/collections-ontology/wiki/SetExample1) :
<http://localhost:3000/individual/
...
vc255> a co:
...
Bag ; co:
...
element
...
<http://da-rdf.library.cornell.edu/individual/b3652730> ; co:
...
element
...
<http://
...
da-rdf.library.cornell.edu/individual/
...
b3652234> ; co:
...
element
...
<http://
...
da-rdf.library.cornell.edu/individual/
...
b3652543> ; co:
...
element
...
<http://
...
da-rdf.library.cornell.edu/individual/
...
b3652884> .
(Lynette) My understanding of the difference between Set and Bag is that Set cannot have repeating items, but Bag can.
- Can set have repeating items?
- Do we need to have repeating items?
- Use Case: A professor creates a reading list which includes a work early in the semester and then repeats it later in the semester.
(Paolo) I apologize that should have been a co:Set to be clearer. For Bags you need to have an instance of Item to support for repeated elements. Once you flatten down to co:element the repeated items become one. The idea of the co:element (defined as chain) in general is to provide a shortcut to the elements. In that case we are interested in finding the existence (one of them), the repetitions are irrelevant at that level.
(Rebecca) I see on the description of the Collections Ontology that "the Collections Ontology (CO) defines unordered collections (Set and Bag) and ordered collections (or List)." It seems awkward to select an ontology in which the type of the collection has to change if ordering is added to an originally unordered collection, or vice versa. That seems to me an advantage of the ORE ontology.
(Paolo) that is a fair point but the description is not accurate, the approach has been described in the paper, here it is:
The relationships between the mathematical entities and those defined by Collections Ontology - and detailed in the following sections of the paper - can be defined as follow:
co:Set ⊂ Set
co:Bag ⊂ Bag
co:Set ∩ co:Bag = ∅
co:List = co:Bag ∩ Sequence
There are precise pragmatic reasons motivating this design choice. First of all, we chose not to model the mathematical identity function in CO for a specific reason: to allow one to use CO even when modelling scenarios that describe “collections in terms of the constructive boundaries of those plural entities that form themselves a whole". Therefore, it is possible to consider two sets of people, composed exactly by the same people, as two different research groups without contradictions. .... Second, from an implementation standpoint, the data structures managing co:Set and co:Bag are very different.
In other words, if you define a Bag and you add ordering you get a List. See axioms here: http://www.essepuntato.it/lode/owlapi/http://purl.org/co/#d4e499
Set is all another story though. That is correct.
(Rob) The repeating items case makes ORE very strange, as it means creating two proxies for the same resource such that it can be in the chain twice.
<x> a ore:Aggregation ;
ore:aggregates <a> ; // should be repeated at the end
ore:aggregates <b> ;
ore:aggregates <c> .
<p1> a ore:Proxy ;
ore:proxyFor <a> ;
ore:proxyIn <x> ;
iana:next <p2> .
<p2> a ore:Proxy ;
ore:proxyFor <b> ;
ore:proxyIn <x> ;
iana:next <p3> .
<p3> a ore:Proxy ;
ore:proxyFor <c> ;
ore:proxyIn <x> ;
iana:next <p4> .
<p4> a ore:Proxy ;
ore:proxyFor <a> ;
ore:proxyIn <x> .
(Rebecca) I don't actually find this so strange. If proxies are the means to specify relationships, such as sequencing, among the aggregated resources, then if an aggregated resource has more than one relationship to other resources, as in occurring at multiple positions in a sequence, it seems natural that it would have a proxy for each.
(Paolo) I do find it strange but not 'that strange'. In CO you can infer the top part so the co:element will have only three objects (with no repetition). But the actual declarative structure will list all of them.
Example 4-ore: A Virtual Collection as an unordered collection of items using ORE Ontology's Aggregation with multiple unordered items
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Example 4-ore: A Virtual Collection as an unordered collection of items using ORE Ontology's Aggregation with multiple unordered items
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix ore: <http://www.openarchives.org/ore/terms/> . @prefix iana: <http://www.iana.org/assignments/relation/> . <http://localhost:3000/individual/vc155>vc255> a ore:Aggregation ; ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652730> ; ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652234> ; ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652543> . <http://localhost:3000/individual/pxy162> a ore:Proxy ; ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652730> ; ore:proxyIn <http://localhost:3000/individual/vc155> ; iana:next <http://localhost:3000/individual/pxy163> . <http://localhost:3000/individual/pxy163> a ore:Proxy ; ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652234> ; ore:proxyIn <http. |
Expand | ||
---|---|---|
| ||
|
...
Comments
Comments as Free Form Text Annotation
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
vc155> ;
iana:next <http://localhost:3000/individual/pxy164> .
<http://localhost:3000/individual/pxy164> a ore:Proxy ;
ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652543> ;
ore:proxyIn
|
QUESTIONS:
...
|
...
- what ever I want for now
- suggest use of individual in URI meaning an instance of a class (used by VIVO too)
- id starts with alpha because syntax something:vc123 – cannot have number directly after :
Comments
Comments as Free Form Text Annotation
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Code Block | ||||
---|---|---|---|---|
| ||||
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> ns#> . @prefix dcterms: <http://purl.org/dc/dcmitype/Text> terms> .<http://localhost:3000/individual/vci165/comment/changeme:93/body> @prefix dctypes: <http://www.w3 purl.org/1999/02/22-rdf-syntax-ns#type> dc/dcmitype> . @prefix cnt: <http://www.w3.org/2011/content#ContentAsText> content#> .<http://localhost:3000/individual/vci165/comment/changeme:93/body> @prefix oa: <http://www.w3.org/2011/content#chars> "This is my favorite book." . ns/oa> . <http://localhost:3000/individual/vci165/comment/changeme:93/body> cm93> a oa:Annotation ; oa:hasTarget <http://purl.org/dc/terms/format> "text/plain" . | ||||
Code Block | ||||
| ||||
localhost:3000/individual/vci162> ;
oa:hasBody <http://localhost:3000/individual/ab205> ;
oa:annotatedBy <http://vivo.cornell.edu/individual/individual24416> ;
oa:annotatedAt "2014-07-21T12:00:00Z"^^xsd:dateTime
oa:motivatedBy oa:commenting .
<http://localhost:3000/individual/ab205> a dctypes:Text, cnt:ContentAsText ;
cnt:chars "This is my favorite book." ;
dcterms:format "text/plain" .
|
...
URI Generation
BaseURI
Environment | Base URI |
---|---|
development | http://localhost:3000/individual/ |
testing | TBA |
production | TBA |
Identifier
_BASE_URI_ + _CONCEPT_ABBR_CODE_ + _GENERATED_NUMBER_
CONCEPT | ABBR_CODE | Example URI | Comments |
---|---|---|---|
Virtual Collection | vc | http://localhost:3000/individual/ |
...
vc155 | ||
Virtual Collection Item | vci | http://localhost:3000/individual/ |
...
vci262 | |||
Comment | cm | http://localhost:3000/individual/cm394 | |
Tag | tg | http://localhost:3000/individual/ |
...
tg328 | |||
Annotation Body | ab | http://localhost:3000/individual/ab325 |
QUESTIONS:
- Is it best practice to use the format specified for identifier?
- The alternative could be to use the URL for the webpage with a .nt extension if a webpage representation exists AND use the above format if a webpage does not exist.
- OR force the webpage URL to match this format whenever possible AND continue to use the .nt extension to show the triples.
- We can punt the final decision on this question until implementation is further along.
...
Access Thoughts
QUESTIONS:
...
NOTE: This doesn't really come into play until Use Case 1.2, but I want to think about the other access issues with this in mindmin