/
URI Management Call 2017-02-21

URI Management Call 2017-02-21

Jun 16, 2017

Connection Info:

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

Notetaker:  @Juliet Hardesty

Attendees: 

  • @sanderson

  • @Ryan Wick

  • @matienzo

  • @Don Brower

  • @Juliet Hardesty

Agenda:

  • Finalize documents for publication on wiki:

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

      • M1 - rights statement didn’t see this as requiring rdf/xml, just need to see a serialization when dereferencing URI, documentation is almost 9 years old

      • include discussion in white paper that we’re following M1, M2, and E1 -  @Juliet Hardesty - done

      • Need to add N-Triples to For machines section as document to be produced - done

      • To Do list isn’t brought over to wiki

      • Bring over Functional Requirements doc to wiki as PDF attachment (without To Do list) under URI Mgmt WG and update link in URI Selection Working Group -  @Don Brower - done

      • Gists for each property serialization should also be saved as PDF and placed on wiki?  @Don Brower can decide. - Added to Functional Requirements doc - done

    • Predicate Decision Tree - who has permission to request? Anyone?

      • added text about HMIG WG that will be formed so also added updated date at top (comments are not showing in View Only view and also won't show when brought over to wiki)

      • change contact at end to HMIG -  @Juliet Hardesty - done

      • Move to the wiki under URI Selection WG and update link in  URI Selection Working Group -  @Ryan Wick

        • remove questions at end and leave Review process and statement about WG in place when brought over to wiki

      • also save today’s version as PDF attachment under URI Mgmt WG -  @Ryan Wick

    • White paper to describe vocab manager - https://docs.google.com/document/d/1Q62Hqrd-yChCrfWQ1sxDhPl6CtS-3KrQWX6HdB-ZNQc/edit?usp=sharing

      • add a sentence to beginning about when the group finished its work -  @Juliet Hardesty - done

      • can we offer the survey data? we can maybe removing the final open comment question since that could be identifiable - but a spreadsheet of survey responses is available upon request

      • list out the survey questions -  @Juliet Hardesty - done

      • Move white paper over to wiki as PDF attachment under URI Mgmt WG -  @Don Brower - done

  • URI Selection Working Group

    • charter draft - change suggested review process based on comment?

      • yes, add bullet point to suggested review process -  @Juliet Hardesty - done

    • Post charter to form group or wait until later?

      • secondary domain name if there’s strong need, but not sure there is

        • maybe have the group come up with something else for a domain that is connected to linked data - more neutral domain name might be more open to people outside of community

        • same reason for using opaquenamespace at Oregon (not connected explicitly with Oregon or particular project)

      • working group could form and sit for a bit or discuss the status of things and what can happen in the meantime

      •  

        • info about status of things should go outside charter when inviting people to sign up

        • post charter on wiki and send out email with caveats -  @Juliet Hardesty and  @Ryan Wick - done

        • @Ryan Wick can start facilitating

        • requests can be processed up to the point of actually creating the URI