Page Comparison

...

There will be some general common metadata around authorship and review, and we need to consider what information is in an Annotation entity and which must be modeled in the association of an Annotation to some object (e.g., a CollectionObject).

We will need to broadly model the association of metadata with an object. We need to consider the association of an Annotation entity, but also must model associate of a Reference like an URL, or a bibliographic reference, a Resource (like an image, a recording, or a document), etc. How do we capture the common aspect of the association so it is easy to find all annotations (associations) for an object? We *could* just enumerate all the association services, but this is a bit messy to maintain. It would be nicer to have a more general notion that support variants (subclasses). This can be done with an association-type, but then we need to figure out how that gets messy.

...

• Try to be explicit and exhaustive, but not pedantic.
  • Patrick Schmitz (Unlicensed): If there is an active discussion or comment, you may want to call it out as a sub-bullet. This example also uses a color macro to call it out, and provides a link to a given user to indicate that this is a particular contributor's position.

Subtopic

• More assumptions around peripheral subject
  • Ex. An example of the case
• Yet another assumption
  • Details of the assumption
    • Nitty-gritty detail 1
    • Nitty-gritty detail 2

...

• Notes on how typed Annotations might be used for some of the data elements of the core CollectionObject are
  provided in the Services Team Design Meeting of May 7, 2009 /wiki/spaces/collectionspace/pages/666274229.

If we have relevant sections in Spectrum or another such document, link to them here (or cite section numbers, etc.):