ATTENDEES: Wendy, Oliver, Jon, Dan G. Jay, Larry
DMT-104 Clarification of usage of annotation
Annotation is not clear about its usage in relation to the contents of the object it is annotating. What is the intended use of Annotation content in terms of clashes in date, name, version and other duplicative information? The documentation on the purpose and use of Annotation needs to be clarified.
Need rules for usage. Send to MT for action.
The solution should NOT be to put it everywhere (duplication of content). Documentation should be done in depth for particular properties which duplicate information also found in the object (name, version date, etc.).
DMT-117 Is there a conflict in collection relationships with the capabilities of annotation
Annotation supports a number of relationships between object (those supported by Dublin Core) such as hasPart, isPartOf, etc. Does this conflict with the collection pattern and Binary/NaryRelation? This came up in a discussion of D4Q2-65 Closed and TC thinks it should be discussed and documented by the MT. Discussion - The Fundamental question is what do we need to annotate
- Sometimes a metadata document will have some of the elements we include in an annotation.
- Who, when, why:
- for the creation of the metadata documents and
- For the creation of the metadata instance of a class and
- For documenting instances of data, studies, or view
- Prevent infinitely regressive annotation (documenting something at multiple levels of recursion)
- If we have that capability in the model can we prevent "this" from happening
- We have created an infinite loop in the model for annotation
- What we have right now are classes that are annotated identifiable - that annotation is about the instance of that class
- There are also a number of other classes that use Annotation other than as an inheritance from Annotated Identifiable
- Need the ability to annotate an instance of a document as an edition of the metadata separate from the creator of the intellectual content (like the difference between section 1 and section 2 of Codebook)
- The need to annotate a variety of things
- document creation of an conceptual instrument
- Someone else could use that conceptual instrument and you want to document the packaging of the conceptual instrument - you are shipping it out in another binding (XML, RDF, or a packaging of information)
- Permanent and transient instances - publishing for distribution
- On one hand anything can be annotated that contains a set of metadata and would carry an annotation
- Creation of a DDI document the root not could contain document information so we could bring an annotation to every container element
- Shift from Identifiable class Annotation it is now a complex data type which solves one of the problems initially seen in creating DocumentInformation - that of having a stack of unassociated Annotations with links to various places
- The context of the annotation is now clearer because its a complex data type
- We need the documentation to be clearer about the instance of the class or the metadata document and give examples in the description of annotation
- This would be a good way to refer to Dublin Core in general, correspondence with DC. Example could include reuse of something
- Can this be used to support a provenance chain of source?
- There is a whole document on this from Dagstuhl work and this should be referenced from the document. Some should be added to our documentation in parts. This is published in IQ
- Hoyle, Larry, Mary Vardigan, Jay Greenfield, Sam Hume, Sanda Ionescu, Jeremy Iverson, John Kunze, Barry Radler, Wendy Thomas, Stuart Weibel, Michael Witt DDI and Enhanced Data Citation IASSIST Quarterly, Vol. 39_3-4 pp. 30 - 46 <http://iassistdata.org/sites/default/files/vol39_3-4_hoyle2.pdf>.
- Review this for any specific content for High level documentation.
- There is an "official title of an annotation" corresponds more to the Dublin Core elements and purpose of resource location, its means of assigning credit so a title alone is meaningless
- Name is/can be a machine actionable context specific means of denotation
- Would an instance variable have a Name "linguistic signifier" Title has "full authoritative title"
DMT-117 - Its a parallel issue. The Collection relationships are machine actionable regarding relationships between items in a DDI collection whereas the context of the relation information in annotation is far reaching. The relationships in Catalog are much more structural and imply certain actionability
- Different types of annotation are appropriate in different contexts. Annotation properties should be thought of within the full relational context of annotation. Individual properties may have similar classes in DDI but are used independently in other contexts.
- Annotation should not be used to express similar uses of a specific class that parallels a property in Annotation.
NEXT WEEK: ACTION: Wendy will summarize above discussion and provide text for various uses. These will reviewed next week for agreement and specific actions
Prepare FROM 2017-02-01
DMT-116 - discuss to clarify intent and realization - wlt draft up and review where changes would be need (related issues) |