Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Feedback on first draft



Strategizing release

  • list of implementations similar to W3C
    • How close is LOC and Getty?  Can they serve as implementations?
  • producers are often consumers - adopting this will facilitate their own usage
  • allows for common tool sets that consume change documents
  • reach out for feedback from major authorities, prioritizing those with larger change rates as they will benefit more from this
    • some are mid-decision about how they will approach providing data to the public, so this could be good timing to influence their approach
  • producers concerns
    • want to know that consumers will consume
    • reach out to individually
    • developer time is generally already committed, how to get it on their workplan?
  • consumer concerns
    • want to know that producers will use it
    • reach out through conferences, user groups
    • if high adoption, only need one consuming implementation to consume all producer streams
  • create reference implementation for LOC and Getty to demonstrate value
  • feedback 
    • for initial documentation (e.g. 6 week period for review and feedback before 1.0 version)
    • for reference implementations allowing documentation to be modified over time (e.g. need additional change types, changes to processes for producing and consuming)



...

Future Topics

  • Notification to a single institution when a requested entity that was missing becomes available.  This will likely be outside the main change management stream.
  • Value of diagraming to express changes as a means of conveying information around where data is being produced, where it goes, etc.
  • Partial splits and partial merges.

...