URI Management Call 2016-12-13

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

Attendees: 

Agenda and Notes:

  • Functional Requirements doc: https://docs.google.com/document/d/1G2LHArFRW-WdttH_YhNmAjf-Oe9EPZWSZQVap7lenQ8/edit?usp=sharing
    • Updated use cases - looks good
    • Is "RDF that doesn’t work well for Hydra/Fedora environment (PREMIS, MODS)" use case still relevant?
      • added a comment in the Functional Requirements doc to explain this more precisely and review the examples listed (MODS doesn't seem to be a good example anymore); review again at next meeting and make changes to doc
    • Property example mock-ups (ss:arkivoChecksum and ss:importURL using Slash Recipe #5)
    • index.html with complete RDF serialization: 2016-11-11.nt, 2016-11-11.jsonld, 2016-11-11.ttl
    • Property HTML Files:
    • Property RDF Serialization:
    • Mock-ups are in good shape now and can be offered as example outputs for development
    • Predicate Decision Tree update - added skos:example and dcterms:description to list of requested information
      • need better description for Comment field, especially since it is required
      • maybe swap rdfs:comment and dcterms:description? need to keep main definition simple so use rdfs:comment for required description and dcterms:description is for more long form explanation; rdfs:comment = succinct description of term
    • Hosting and Support update from Hydra-steering
      • Julie talked to kestlund briefly about development plan
      • domain suggestions? http://hydravocab.org? Subdomain of projecthydra.org?
        • subdomain is easier path to take - vocab.projecthydra.org? uri.projecthydra.org? 
        • can suggest both and ask for comments in meeting note communication
        • ask full WG for more suggestions
        • send to Karen/Hydra-steering - not sure how decision should be made
      • Plan is to implement Phase 1 by end of March
    • Predicate review process update from HMIG meeting
      • need to place call for meeting in January (before next HMIG meeting) to organize working group/task force
      • any interest in leading from this group? maybe
      • could this group be morphed to handle that? is this predicate review group really a working group or another kind of group - there is no end date but it will produce things
      • it is somewhat similar to handling pull requests and code merges but there should be evidence provided about what has been found by the requester that shows no mapping is available
      • should be folks with metadata expertise to do review
      • maybe people get sunsetted off of group instead of the group itself so folks can cycle off and others can come on
      • URI Selection Working Group (working title)
      • start charter and outline review process
    • Write-up to describe vocab manager - https://docs.google.com/document/d/1Q62Hqrd-yChCrfWQ1sxDhPl6CtS-3KrQWX6HdB-ZNQc/edit?usp=sharing
      • Don reviewing and writing on this
      • Julie adding screenshots from finalized mock-ups