Versions Compared

Key

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

...

  • Date properties
    • When to use the following in our context (TODO: Steven to inventory Getty's date property usage; Kevin to inventory LC date property usage):
      • endTime property definition
        • Getty usage - used on each Activity, the value is the same as for the "created" property (see issues with "created" below)
        • LOC usage - not used presently.
      • startTime property definition
        • Getty usage - not used presently.
        • LOC usage - not used presently.
      • published property definition
        • Getty usage? - not used presently.
        • LOC usage - used for each Activity Object like "Add" or "Remove" or "Update."  I.e., not used for each Object of an Activity.   Represents when the Activity Object was 'published.'
      • updated property definition
        • Getty usage - not used presently.
        • LOC usage - used for each Object of an Activity.  Represents the (last) 'update' date of the Object which is the focus of the Activity.
      • deleted property definition
        • Getty usage - not used presently.
        • LOC usage  - not used presently.
      • 'created' - is used by Getty, but understood not to be an AS property; this will be dropped by JSON-LD tooling (ok, because redundant with endTime value)
  • TODO from last meeting: Dave will create a 7.0, and we can compare it to 7.1 and an eventual 7.2 (for Getty's activity stream). Then we can decide what might be removed and/or added to an appendix
  • Continue to discuss examples (updated)
    • Examples: https://gist.github.com/sfolsom/c91be2d1dd0f6984fdcd5a367d34cbaeTODO JSON for multiple types needs to be and array.07338b416ca605d92984c24c346ba5fe 
      • From previous meeting: Multi typing is probably not the best way to work through the Deprecation, Merging, and Splitting. They may happen over time. Creations of objects that  are the new targets needs to happen before Splits and Merges.
        • X and Y replaced by Z (full merge), X and Y are deprecated
        • Parts X are now considered Z (partial Split)
        • Parts X are now considered Z (Partial split), and all of Y are Z (replaced), Y is deprecated
        • X is now either Y or Z (full Split), X is deprecated
        • What happens in the moment?
          • E.g. two names for the same person. You deprecate one and then point to the remaining authority
          • E.g. undifferentiated name, some of the things linked to can now be attributed to a specific other name.
          • E.g. undifferentiated name, all thinks linked to are now attributed to two or more other names.
          • E.g. undifferentiated name, status changed to because everything is attributed to 
          • E.g. shared pseudonyms TODO flesh out possible changes that occur related to shared pseudonyms.
          • E.g. two units within and organization, the two existing units are collapsed into one (the authorities remain), and a new one is used.
            • Time period for applicability can be recorded. 

...