Page History

...

Attendees

• Steven, Vitus, Christine, Dave, Nancy F., Vitus, Simeon, Kevin

Regrets

Simeon, Kevin, JeffJeff 

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.

...

• Discussion Issues: https://github.com/LD4/entity_metadata_management/labels/Needs%20discussion  (Didn't  discuss  in  detail.  Vitus  pointed  out  that  we  considered  as:target  in  previous  meetings,  links  below.)
  • https://github.com/LD4/entity_metadata_management/issues/94
  • https://github.com/LD4/entity_metadata_management/issues/93
    • See our notes from
      • 2023-03-13 Meeting: Order, Date types, Activity types/examples and as:target and Flattening Examples (Continued)
      • 2023-01-30 Meeting: Types and as:target and Flattening Examples (Continued)
• Getty/LOC compliance: https://docs.google.com/spreadsheets/d/1k7yHtsZP25ERZse62c3nKw4VbGHdEXNZK506JkXHcC0/edit?usp=sharing 
  • 2023-10-23 - 
    • LOC will implement the Entry Point
    • 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.
• 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:
    • 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?

...