URI Management Call 2016-08-23

Owned by Bill Branan
Jun 16, 2017
2 min read

Connection Info:

3-4pm Eastern
+1 (641) 715 3660, access code 651025  

Notetaker: Juliet Hardesty (Indiana University)

Attendees: 

Agenda:

Notes:

  • Functional Requirements doc: https://docs.google.com/document/d/1G2LHArFRW-WdttH_YhNmAjf-Oe9EPZWSZQVap7lenQ8/edit?usp=sharing
    • Edited in Functional Requirements doc
    • Discussion of Rightsstatement.org RFP and functional requirements list
    • slash vs hash might not matter for technical reasons
    • hash is fragment piece, so it’s not sent to server, it’s more like anchor - server never sees hash
    • supporting vocabularies (objects/property values) - large vocabs would need slashes probably
    • hash you can have page that lists everything, although it looks like any W3C recipe starts with a complete RDF serialization that can be delivered somehow
    • opaquenamespace uses slashes and not hashes
    • hashes are good if you are working in a single vocabulary, but we're going to be receiving requests for various kinds of predicates and controlled vocabs
    • Going with slash pattern - need to review recipes from W3C
      • Recipe #6 good for extensive controlled vocab, supplies SPARQL endpoint, probably not necessary to begin but could expand to include later
    • might actually be clearest if "predicate" is part of URI path to distinguish from an object/controlled vocab term
      • variety of requests might also result in predicate and controlled vocab terms that are similar, so including term "predicate" or "controlledvocab" could help distinguish
    • grouping for predicates and/or vocabs (even within a URI that specifies "predicate" or "controlledvocab")?
      • see example in Functional Requirements doc
      • difficult to change at URI level if grouping is not involved and needs to be added or grouping is included and needs to be removed
      • allows it to function like namespace
      • opaquenamespace groups by rdf:type (or wants to get to that point)
      • might be best to not have groupings for predicates and create UI to browse by rdf:type only
      • not sure about controlled vocabs but leaving for later
  • Predicate Decision Tree - Post for community feedback?
    • putting off to next meeting
  • Action items
    • Mock up example predicate in RDF to show expected output from system (use one of the predicates listed in use case)
    • Choose Recipe that best matches what we want to provide for slash-style URIs - Recipe #2, Recipe #4, or Recipe #5
  • Next meeting Tuesday, Sept. 6, 3pm Eastern