From Last Meeting
- Lynette - Update activity streams document to more closely follow the standard.
- Activity Streams - Extensions for Authoritative Data Change Management (minimal extensions)
- Mock SPARQL Update Queries for Common Changes (working document)
- Existing Change Management Approaches (working document)
- Types of Changes (working document)
Notes were taken directly in the Activity Streams document as comments with general discussions captured here.
From audience perspective…
Is there an audience that would prefer a notification only?
For LC, Stream has just URI and that that entity was updated.
Doesn’t seem like it would be a big deal to have to do two steps to get each change… 1) read the notification in the activity stream, 2) follow relationship URL to get the rdf_patch
Complete History vs. Recent Notifications
Complete history =
- baseline download + all changes since baseline as they happen
- multiple changes to an entity means the entity appears in the activity stream multiple times
- changes are dated to indicate when the change occurred
- includes patch if available
- maybe baseline download
- may include all entities that have changed since the baseline was created
- if an entity has changed more than once, it is collapsed into a single notification with the latest change date
- no patch data
Need to provide the authoritative patch sequence. If I modified on July 1, and then take a patch on Aug 1, how can I refer to the changes if the changes in the later patch if they were adjusted in a way in the July patch.
Providing RDF patch could be optional. For authorities that can provide a patch, then we provide a spec for what that would look like. For authorities that do not track low level information, this would be no worse than what they currently have.
- 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.