USE CASES -- Annotation of marked-up text, including TEI
From Open Annotation Collaboration
Contents |
General Session Notes
Notes Specific to Annotation Supporting Collaborative Development of Scholarly Editions
Notes Specific to Annotating Texts in the Brown Digital Repository
Discussion Notes
Questions:
- q for andy: how does rdf...tei solve the segmentation issue?
- andy: not attempting to be a replacement for xpointer as xpointer already does this, rather gives more purchase on the data in TEI
- leveraging the semantic forms, but still using xpointer to define the chunks of text at this time
- tei, semantic content marked-up but physical doc not marked-up, how to annotation between “page-break 3 and page-break 4?”
- this is an implementation problem,
- addressing problem key to text-based annotating projects, need to develop an ontology to describe the contraints
- need to identify what is part of the OAC model and what is outside of it because it is application specific (“programatic”)
- aus-e-lit using mimeTypes
- topic of sub-classes: defining sub-classes becomes too limiting and semantically limiting depending on the community the annotations come from
- Anna: agrees, suggesting that people working with text adopt an ontology to share rather than define specific types
- making a distinction between explanatory notes and textual notes is where sub-classing makes sense (i.e. same segment is highlighted but the “target” of the annotation is different)
- consumption of the annotations, how are they being used? how does the homogeneous nature of the annotations affect their use
- anna: no standard way of publishing these in the scholarly community, could publish them as a supplement to the scholarly edition
- andy: want to enable experimentation around the content of the repository, both the items in the repository and the annotations associated with them; no sense of how to publish yet, still experimenting with getting people to use it
- andy: empower core users as developers by providing their api and letting their users develop their own tools
- filtering -- mainly allowing users to turn layers of annotations on and off but could also be used to secure annotations but not the focus of OAC’s model
- web-based systems can be used to solve the security issue so no need to include it into the model
- need to understand the criteria under which to allow other servers to aggregate/harvest your annotations; need trust guidelines
- herbert: this is the decision of the individual building the OAC application
- paolo: legally speaking there is no way to protect triples so trust is important
- outside of the triples issues, the resources themselves can be under copyright, etc. -- how to discern that the resource provider is comfortable with the resources being harvested/aggregated and reused.
