Attendees

• Steven, Dave, Nancy F, Simeon, Kevin

Regrets

Vitus, Christine

ACTION ITEMS (From Last Time):

• • TODO look at existing language around non-normative to reflect sections 6 and 7 accordingly. Dave and Kevin worked on section 6. Dave's section is a little more abstract (less focused on Getty) and Kevin's section is very specific to LC's implementation.

Agenda & Notes

• Getty/LOC compliance: https://docs.google.com/spreadsheets/d/1k7yHtsZP25ERZse62c3nKw4VbGHdEXNZK506JkXHcC0/edit?usp=sharing 
  • 2023-11-10
    • Update from Dave and Kevin
      • In section 6.2 delete "the date of the activity for an entity will be the date of the most recent change". Change 
      • In section 6.2 change "the consumer maintains a persistent reference to the last page published in the stream (last_page) to"the consumer maintains a persistent reference to the last page processed in the stream"
      • Kevin will make LOC section more streamlined, similar to Getty section
    • Update/recommendations from David Newbury

      • "the one tweak you might want to make in the document is the one that IIIF made, to declare that the base ActivityStream context is last in a list, yours is second-to-last, and others go above, since the JSON-LD algorithm always defaults to the last entry and provide a bit more protection against accidental overrides, but it's not essential"

        • Simeon made a pull request to make clear extensions go first, and AS and EMM order isn't important because there are no term conflicts.

      • "...I would want to think a bit about including a github.io URL into permanent documents—I trust y'all, but I worry about relying on Microsoft/Github's commitment to sustaining that domain indefinitely."

        • Going to consider domain, and support it for a couple years, and hope the spec has significant usage and a need for a home. Simeon and Steven will propose a domain at the next meeting. 
        • Simeon will make a PR to update links.
  •  2023-10-23
    • LOC will implement the Entry Point, and will probably recommend some change in Entry Point language.
    • Re: context, we could make loosen the MUST for the EMM context, to say MUST use Activity Streams and if using extension terms like Deprecate point to EMM context.
      • Is there prior art around this. IIIF uses Activity Streams and then adds other namespaces for extensions. TODO (Simeon) Update recommendation and context to take this approach. → https://github.com/LD4/entity_metadata_management/issues/120
  • 2023-10-10 - Didn't discuss in detail. This spreadsheet is meant to illustrate where Getty and LOC's implementations diverge from our MUST recommendations. We can ask whether they are willing to make changes to comply, and/or possibly where we could restate our requirements, (e.g. if implementations aren't using the Deprecate activity (SHOULD, not MUST), and meet the other requirements, do we care if they use the AS context only?)
    • Unless LOC and Getty make changes to comply with the recommendations, we'll need to make clear that we're point to their implementations to illustrate specific points, and that they do not fully comply.
    • Can encourage Getty to list the EMM context alongside Activity Streams
• Plan for remaining work for this phase.
  • Clean up https://ld4.github.io/entity_metadata_management/0.1/#consuming-entity-change-sets
    • 2023-10-23 Discussion/Update:
      • TODO (Dave and Kevin) Will update to be more descriptive of mutable and direction
      • TODO (Steven) Update section 5 to be Appendix 1
    • 2023-10-10 Update: https://github.com/LD4/entity_metadata_management/blob/section_6/docs/0.1/index.md
      • Dave added language about non-normative, 
      • Review and weigh in on
        • Where Discussion section should be? (leaning toward up with the intro)
        • Is the immutable vs. latest update only covered well?
        • Focus more on the abstract, and point to Getty and LOC implementations as examples of the different implementation decisions.
          • E.g. "At this time LOC uses the reverse, mutable", provide URIs of the Entry Points and/or Change Sets.
        • Immutable and temporal direction aren't inherently coupled.
          • Describe them separately
          • 4 quadrants... mutable forward, mutable reverse, immutable forward, immutable reverse.
        • What do we say about publishing OrderedCollectionPages and thresholds. Do we say don't publish until you've met the threshold for a new page?
  • General editing for grammar and consistency, https://ld4.github.io/entity_metadata_management/0.1/
    • Nancy, Christine, and Jeff will take the lead.
      • Check for broken links
  • Proofread json examples
    • Jeff will take the lead.
  • Other issues from spec read through:
    • Excerpt format https://github.com/LD4/entity_metadata_management/issues/104
      • TODO: Jeff and Steven to address this when doing json copy editing.
    • Consistent examples captions https://github.com/LD4/entity_metadata_management/issues/98
      • TODO: Christine and Nancy will address this in copy editing
  • Are we missing anything?

Meeting Materials

• Recommendations: https://ld4.github.io/entity_metadata_management/0.1/
• Examples: https://ld4.github.io/entity_metadata_management/examples.html
• Pull requests: https://github.com/LD4/entity_metadata_management/pulls
• Issues: https://github.com/LD4/entity_metadata_management/issues
• How to contribute: https://github.com/LD4/entity_metadata_management#contributing

Notes

Inline above in agenda