/
URI Management Call 2016-11-01

Samvera Community Wiki

URI Management Call 2016-11-01

Jun 16, 2017

Connection Info:

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

Notetaker:

Attendees: 

  • @Juliet Hardesty

  • @Ryan Wick

  • @sanderson

Regrets:

  • @matienzo

  • @Don Brower

Agenda:

  • Functional Requirements doc: https://docs.google.com/document/d/1G2LHArFRW-WdttH_YhNmAjf-Oe9EPZWSZQVap7lenQ8/edit?usp=sharing

    • Review feedback and updates

      • Discussed new comments on downtime/availability and hosting vs support; also discussed new use case

      • Downtime/availability

        • Should Duraspace host this? keep server up and running but would app responsibilities fall on another group?

        • host might not be support

        • need to talk to someone (Hydra Steering) - Julie email

      • New use case re: API for returning terms with labels - 

        • questioning authority gem is hitting LCSH API endpoint (20 results returned)

        • we think how we’re setting things up this can also be used with questioning authority

        • no relevancy in questioning authority

        • not for ranking but for order (name or term vs term in description of vocab)

        • relevancy could be handled by app in search - endpoint would have way to handle relevancy

          • endpoints that work in relevancy - linked data fragments spec

          • could do this with SPARQL endpoint but then questioning authority would have to contain relevancy code

    • Property example mock-ups - Julie starting

      • 2 terms (ss:arkivoChecksum and ss:importURL)

      • both terms in single RDF serialization - either ttl or nt - use nt since that spells out all triples and is easier to use programmatically

      • nt for each term

      • html for each term

      • GitHub Gist to show how these would look

  • Begin working on review process in Predicate Decision Tree, 8c - https://docs.google.com/document/d/1oMvVlGuBwD5U1251oxNmTZn7WgkNTj6tF-k1hOYjnac/edit

    • anyone can request, no authentication needed but contact info needs to be provided with request

    • ask HMIG if there’s interest for a WG to support review process

    • ask HMIG for feedback on req doc and decision tree

    • review criteria

      • info about places they have looked

      • info about any properties that are close but won’t work

      • all required info is included