Page History

...

rdf

http://www.w3.org/1999/02/22-rdf-syntax-ns#

http://www.w3.org/2000/01/rdf-schema#

http://purl.org/dc/elements/1.1/

http://purl.org/dc/terms

http://purl.org/dc/dcmitype

http://www.w3.org/2011/content#

http://purl.org/co

http://www.w3.org/ns/oa

http://xmlns.com/foaf/0.1

...

<http://vivo.cornell.edu/individual/individual24416> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://xmlns.com/foaf/0.1/Person>Agent>

@prefix foaf:    <http://xmlns.com/foaf/0.1> .

<http://vivo.cornell.edu/individual/individual24416> a foaf:PersonAgent .
<http://vivo.cornell.edu/individual/individual24416> a foaf:Person .

NOTE:

•  ORE  uses foaf:Agent as the dc:creator.

QUESTIONS:

• What URI do we use for a user?  Does NETID make the URI unique?  Use VIVO URI.. see below.
• Do we want to keep any other foaf properties beyond setting the type to foaf person?  Consensus:  None extra needed in our triplestore.
• • ANSWER:  Each university will determine what to use as the URI for users.
    • Cornell: Will use VIVO URI's 
  It was suggested that we use VIVO URIs
  • • 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: ?
• 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

...