Page History

...

What URI do we use for a user?
- ANSWER: Each university will determine what to use as the URI for users.
  - Cornell: Will use VIVO URI's for faculty and staff. Doesn't work for students.
    - Ex. VIVO URI - http://vivo.cornell.edu/individual/rjv23 – rjv23 is a netid
    - Ex. VIVO URI - http://vivo.cornell.edu/individual/individual24416 – 24416 is not a netid
    - Ex. VIVO URI - http://vivo.cornell.edu/individual/EleanorRayle - EleanorRayle is not a netid
    - For the purposes of our experiment, if the user doesn't exist in VIVO, then they can't create a Virtual Collection.
  - Harvard: ?
  - Stanford: ?

Expand

title	Reconciled Questions

Do we want to keep any other foaf properties beyond setting the type to foaf person?
- ANSWER: None extra needed in our triplestore. We can revisit this if it becomes clear by the implementation that we need to keep additional information.

Virtual Collection's metadata

...

Code Block

language	none
title	Turtle

@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> .

...

Expand

title	Reconciled Questions

What properties should be used to express the virtual collection metadata? Possibilities and answer as Selected Property…

Concept	Potential Properties	Selected Property	Comments
Title	rdfs:label, dc:title, dcterms:title	dcterms:title	Based on ORE ontology specification
Description	rdfs:comment, dc:description, dcterms:description	dcterms:description	Based on ORE ontology specification
Owner	dc:creator, dcterms:creator	dc:creator	Based on ORE ontology specification

Virtual Collection's list of items

...

Example 1-co: A Virtual Collection as an ordered collection of items using Collection Ontology's List with one item

Expand

title	Expand to see n-triples...

Code Block

language	none
title	n-triples

<http://localhost:3000/individual/vc155> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://purl.org/co#List>
<http://localhost:3000/individual/vc155> <http://purl.org/co#size> "1"^^xsd:nonNegativeInteger
<http://localhost:3000/individual/vc155> <http://purl.org/co#firstItem> <http://localhost:3000/individual/vci162>
<http://localhost:3000/individual/vc155> <http://purl.org/co#item> <http://localhost:3000/individual/vci162>
<http://localhost:3000/individual/vc155> <http://purl.org/co#lastItem> <http://localhost:3000/individual/vci162>

<http://localhost:3000/individual/vci162> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://purl.org/co#ListItem>
<http://localhost:3000/individual/vci162> <http://purl.org/co#index> "1"^^xsd:positiveInteger
<http://localhost:3000/individual/vci162> <http://purl.org/co#itemContent> <http://da-rdf.library.cornell.edu/individual/b3652730>

...

Code Block

title	Turtle using Collection ontology's List class

@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

...

Example 2-ore: A Virtual Collection as an ordered collection of items using ORE Ontology's Aggregation with multiple ordered items

Expand

title	Expand to see n-triples...

Code Block

language	none
title	n-triples

<http://localhost:3000/individual/vc155> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.openarchives.org/ore/terms/Aggregation> .
<http://localhost:3000/individual/vc155> <http://www.openarchives.org/ore/terms/aggregates> <http://da-rdf.library.cornell.edu/individual/b3652730> .
<http://localhost:3000/individual/vc155> <http://www.openarchives.org/ore/terms/aggregates> <http://da-rdf.library.cornell.edu/individual/b3652234> .
<http://localhost:3000/individual/vc155> <http://www.openarchives.org/ore/terms/aggregates> <http://da-rdf.library.cornell.edu/individual/b3652543> .

<http://localhost:3000/individual/pxy162> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.openarchives.org/ore/terms/Proxy> .
<http://localhost:3000/individual/pxy162> <http://www.openarchives.org/ore/terms/proxyFor> <http://da-rdf.library.cornell.edu/individual/b3652730> .
<http://localhost:3000/individual/pxy162> <http://www.openarchives.org/ore/terms/proxyIn> <http://localhost:3000/individual/vc155> .
<http://localhost:3000/individual/pxy162> <http://www.iana.org/assignments/relation/next> <http://localhost:3000/individual/pxy163> .

<http://localhost:3000/individual/pxy163> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.openarchives.org/ore/terms/Proxy> .
<http://localhost:3000/individual/pxy163> <http://www.openarchives.org/ore/terms/proxyFor> <http://da-rdf.library.cornell.edu/individual/b3652234> .
<http://localhost:3000/individual/pxy163> <http://www.openarchives.org/ore/terms/proxyIn> <http://localhost:3000/individual/vc155> .
<http://localhost:3000/individual/pxy163> <http://www.iana.org/assignments/relation/next> <http://localhost:3000/individual/pxy164> .

<http://localhost:3000/individual/pxy164> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.openarchives.org/ore/terms/Proxy> .
<http://localhost:3000/individual/pxy164> <http://www.openarchives.org/ore/terms/proxyFor> <http://da-rdf.library.cornell.edu/individual/b3652543> .
<http://localhost:3000/individual/pxy164> <http://www.openarchives.org/ore/terms/proxyIn> <http://localhost:3000/individual/vc155> .

Code Block

title	Turtle using ORE ontology's Aggregation class

@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> 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://localhost:3000/individual/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 <http://localhost:3000/individual/vc155> .

...

QUESTIONS:

Should Virtual Collection's type be a subclass of co:List instead of a co:List?
- If so, what is the type? Consensus: Subclass of co:List Ontology to be defined by ontology group.
- Is it LD4L specific? Consensus: YES to be defined by ontology group.
- How is LD4L defining new types? Naming convention, namespace, etc.? Final definitions by ontology group.
  - For now, use namespace=LD4L in Ruby with link <http://ld4l.org/ontology/... – to be defined by ontology group
  - Class name=ld4l:VirtualCollection
  - type URI=<http://ld4l.org/ontology/VirtualCollection>
  - instance URI=<http://localhost:3000/individual/vc123> –
    - 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 :

...

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 mind.

Page tree

Versions Compared

Old Version 43

New Version 44

Key

Virtual Collection's metadata

Virtual Collection's list of items

Example 1-co: A Virtual Collection as an ordered collection of items using Collection Ontology's List with one item

Example 1-ore: A Virtual Collection as an ordered collection of items using ORE Ontology's Aggregation with one item

Example 2-ore: A Virtual Collection as an ordered collection of items using ORE Ontology's Aggregation with multiple ordered items