Page History

...

• How do we represent deprecation and deletes?
  • From last time 
    • We were leaning toward our recommendation really only focusing on the consumer needs, leaving room for the data producer to define their own needs/internal implementation
      • Create and/or Add be used for new things
      • Update for any type of update
      • Delete and/or Remove for no longer in use entities
• TODO - Steven to bring brought this discussion to the Slack Channel after the last meeting to try to get some asynchronous decisions.
  • https://github.com/LD4/entity_metadata_management/pull/75
    • Should we remove the Create vs. Add section?
      • If you don't want someone to know about an entity yet, and you're using Create for internal operations, don't add it to the consumer stream. TODO add language to the Create vs. Add section.
    • Is it ok to collapse 5.3 and 5.4 into one section?
      • Section "Making an entity obsolete"
        • Remove vs. Delete
          • These can be at the same time, the important point for the consumer is the moment when an entity is obsolete. This allows the provider to have separate states.
          • Deletes in theory, would result in 404. The spec should support add/update/remove even if the http isn't done "correctly".
          • Getty uses Delete for Deprecation.
            • Could they be open to Deprecation activities? (Would require code updates and using an ActivityStream extension) TODO Steven to ping David.

...