TechnicalSpecification - Revision history

L.suhrbier: /* Annotated Elements Specification */

2012-12-03T14:45:01Z

Annotated Elements Specification

← Older revision		Revision as of 16:45, 3 December 2012
Line 143:		Line 143:
	The "element selector" will be realised in form of an XPath expression according to section [[#Annotation context selection\|Annotation context selection]]. Therewith, the following special use cases will be interpreted by AnnoSys' selector implementation as follows :		The "element selector" will be realised in form of an XPath expression according to section [[#Annotation context selection\|Annotation context selection]]. Therewith, the following special use cases will be interpreted by AnnoSys' selector implementation as follows :
	# If the XPath expression selects an XML element for which no value is assigned in the relating XML Schema, only a text comment may be given in order to make an annotation in natural language.		# If the XPath expression selects an XML element for which no value is assigned in the relating XML Schema, only a text comment may be given in order to make an annotation in natural language.
	# Selecting the root element ("/") will be recognised as to address the entire data record.		# Selecting the root element ("/") will be recognised as to address the entire data record. In particular, a general comment about the referenced document will be stated like this.

	"Value proposal" enables annotators to propose a new value to any XML element selected by the element selector. While the intended usage is to propose the replacement of the selected XML element values by the given value, curently the value proposal is expected to be represented as text string.		"Value proposal" enables annotators to propose a new value to any XML element selected by the element selector. While the intended usage is to propose the replacement of the selected XML element values by the given value, curently the value proposal is expected to be represented as text string.

L.suhrbier: /* Message types */

2012-11-19T13:48:44Z

Message types

← Older revision		Revision as of 15:48, 19 November 2012
Line 319:		Line 319:
	\|-		\|-
	\| ANNOTATION_PARTLY_ACCEPTED \|\| annotation partly accepted by collection manager		\| ANNOTATION_PARTLY_ACCEPTED \|\| annotation partly accepted by collection manager
			\|-
	\| ANNOTATION_REJECTED \|\| annotation rejected by collection manager		\| ANNOTATION_REJECTED \|\| annotation rejected by collection manager
	\|}		\|}

L.suhrbier: /* Exchange Format */

2012-11-19T13:46:16Z

Exchange Format

← Older revision		Revision as of 15:46, 19 November 2012
Line 160:		Line 160:

	As mentioned above, the upcoming version of the W3C Open Annotation will yield some substantial changes. In particular, these changes will provide solutions to problems not adequately solveable with the current Community Draft 1. The following diagrams will show the current interpretation of Open Annotation Community Draft 1 as implemented in the first AnnoSys protoype. Due to the pending changes, it will not be discussed in detail. Nevertheless, some comments regarding necessary extensions and the mentioned implementation issues will be given.		As mentioned above, the upcoming version of the W3C Open Annotation will yield some substantial changes. In particular, these changes will provide solutions to problems not adequately solveable with the current Community Draft 1. The following diagrams will show the current interpretation of Open Annotation Community Draft 1 as implemented in the first AnnoSys protoype. Due to the pending changes, it will not be discussed in detail. Nevertheless, some comments regarding necessary extensions and the mentioned implementation issues will be given.
	[[Image:OpenAnnotation~~-simplified~~.png\|frame\|none\|''W3C Open Annotation representation of Annotation Metadata'']]		[[Image:OpenAnnotation.png\|frame\|none\|''W3C Open Annotation representation of Annotation Metadata'']]

	While the application of W3C Open Annotation regarding the annotation meta data defined in the AnnoSys data model could have been implemented in a quite straight forward manner, the realisation of the list of annotated elements caused some problems.		While the application of W3C Open Annotation regarding the annotation meta data defined in the AnnoSys data model could have been implemented in a quite straight forward manner, the realisation of the list of annotated elements caused some problems.
Line 168:		Line 168:
	Second, W3C Open Annotation supports addressing multiple (specific) targets. Unfortunately, it lacks to offer an opportunity to relate different bodies to individual targets by limiting the total number of bodies in an annotation to one. Thus, AnnoSys had to create multiple OA annotations in order to represent the data model's list of annotated elements. The relationship between the annotated elements and the original annotation holding the metadata information has been realised by "misusing" the ''oa:hasSemanticTag'' property "linking" annotated elements to meta annotation. As a consequence, a number of unrequired annotation instances would have to be created within the RDF model. The upcoming standard release will permit multiple bodies and provide means to related bodies to specific targets.		Second, W3C Open Annotation supports addressing multiple (specific) targets. Unfortunately, it lacks to offer an opportunity to relate different bodies to individual targets by limiting the total number of bodies in an annotation to one. Thus, AnnoSys had to create multiple OA annotations in order to represent the data model's list of annotated elements. The relationship between the annotated elements and the original annotation holding the metadata information has been realised by "misusing" the ''oa:hasSemanticTag'' property "linking" annotated elements to meta annotation. As a consequence, a number of unrequired annotation instances would have to be created within the RDF model. The upcoming standard release will permit multiple bodies and provide means to related bodies to specific targets.

	[[Image:~~OpenAnnotationElement-simplified~~.png\|frame\|none\|''W3C Open Annotation representation of Annotated Elements'']]		[[Image:OpenAnnotatedElement.png\|frame\|none\|''W3C Open Annotation representation of Annotated Elements'']]

	= Repository =		= Repository =

L.suhrbier: /* Data Model */

2012-11-19T13:45:36Z

Data Model

← Older revision		Revision as of 15:45, 19 November 2012
Line 64:		Line 64:
	While the metadata specification provides general meta information (e.g. determining the annotated record and document), it will be augmented by a list of elements recording the annotation's context selections. The following sections will provide more detailed information on both parts.		While the metadata specification provides general meta information (e.g. determining the annotated record and document), it will be augmented by a list of elements recording the annotation's context selections. The following sections will provide more detailed information on both parts.

	[[Image:~~Annotation_Elements~~.png\|frame\|none\|''Annotation Data Model'']]		[[Image:Annotation_Data_Model.png\|frame\|none\|''Annotation Data Model'']]

	== Annotation Metadata Specification ==		== Annotation Metadata Specification ==

L.suhrbier: /* Overview */

2012-11-19T12:55:58Z

Overview

← Older revision		Revision as of 14:55, 19 November 2012
Line 1:		Line 1:
	= Overview =		= Overview =
	Based on the requirements identified as part of the ~~[[FunctionalSpecification\|~~Functional Specification]], the AnnoSys system will be implemented along the Technical Specification described in this document. Thereby, AnnoSys will be built up on following interacting system components:		Based on the requirements identified as part of the Functional Specification, the AnnoSys system will be implemented along the Technical Specification described in this document. Thereby, AnnoSys will be built up on following interacting system components:
	* Repository		* Repository
	* Data Sharing		* Data Sharing

L.suhrbier: Created page with "= Overview = Based on the requirements identified as part of the Functional Specification, the AnnoSys system will be implemented along the Technical ..."

2012-11-19T12:51:52Z

Created page with "= Overview = Based on the requirements identified as part of the Functional Specification, the AnnoSys system will be implemented along the Technical ..."

Show changes