Time: 9 AM PDT / Noon EDT

Call-In Info: 712-775-7035 (Access Code: 960009)

Documents/Homework:

Mapping recommendations (original)
Mapping recommendations (clean, sent for comment)
Feedback form

Moderator: Eben English

Notetaker: Eben English (Etherpad: https://etherpad.wikimedia.org/p/MODS_and_RDF_Call__2018-10-01)

Attendees:

Emily Porter (Emory)
Simon O'Riordan (Emory)
Danny Pucci (BPL)
Eben English (BPL)

Agenda (with notes)

Feedback Form Responses (no new entries as of 8/17)
1. https://docs.google.com/spreadsheets/d/1DRAzr3ExEAjK2RUs63gxcymoDwprQjVRPDsU_3dDGVU/edit?usp=sharing
Email Responses (no new entries as of 8/17)
1. https://docs.google.com/spreadsheets/d/146uvvKt5ZVvWjm9WV28fWHgCP8fYQ_JXkc5GcMv98Wc/edit?usp=sharing
Action items from last meeting:
1. Add a paragraph explaining relatedItem/collection predicates e.g. "part of" concerns and challenges
  1. Eben added an explanatory paragraph to both the direct and minted options for relatedItem with further explanation and clarification
2. Review use of opaque namespace requests in simple and minted options - we may need to allow for more literals
  1. The "expected value" listed in the tables for each element should be interpreted as what we are recommending, not necessary the full range of the predicate.
  2. We still need to submit these to the URI Selection Working Group
    1. We will need to define the range when these are submitted.
3. Revisit recordInfo discussion
  1. See notes below
Outstanding Comments on Recommendations document
1. <mods:recordInfo>
  1. For the direct mapping, we will keep the mapping the same, but add further clarification in the introductory paragraph indicating that the use of some of the BF predicates could be interpreted as incorrect
  2. For the minted object mapping, group (reluctantly) agreed to create a minted metadata object to better align with correct semantics
2. <mods:title> (minted object)
  1. "supplied" designation
    1. Use of bibliotek-o predicates is not recommended due to vocabulary having no further planned development or support
    2. BF has no support for this concept
    3. Could simply recommend that supplied status be indicated by brackets in title value and/or explanatory note
    4. Could use opaquenamespace
    5. Eben will inquire about the status of bibliotek-o
    6. Hold off on any changes until we have further information and/or participation
  2. Title types (alternative, translated, etc)
    1. We did not map these concepts, which seems odd.
    2. Group agreed to change to include use bf:variantType (range = literal) to indicate type
3. <mods:name>
  1. Comment about use of skos:exactMatch and skos:closeMatch is correct, these should only be used to link concepts, not real-world-objects
  2. Group agreed to change document to use owl:sameAs and rdfs:seeAlso for linking between RWOs
TODOs:
1. Add comments to recordInfo direct mapping DONE
2. Update recordInfo minted object mapping to use minted metadata object DONE
3. Add bf:variantType to <mods:title> minted examples DONE
4. Remove instances of skos:exactMatch and skos:closeMatch where appropriate; replace with owl:sameAs and rdfs:seeAlso DONE
5. Submit opaque predicates to URI WG
Samvera Connect session
1. Eben and Emily are working on this, will share slides when closer to final version
Next meeting: Monday October 29

Browser not supported