ontologies.model.owl Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of model Show documentation
Show all versions of model Show documentation
In this project we can find the data exchange model (in both UML and XSD), the generic services interfaces (WSDL) and the WebLab ontologies (OWL).
The newest version!
]>
WebLab Exchange model v1.2.1
1.2.1
WebLab Exchange model v1.2.1 - May 2011
This version includes annotable object of the model i.e. Resources and their relationships.
It also provides some properties to be used in annotations.
WEBLAB: Service oriented integration platform for media mining and intelligence applications Copyright (C) 2004 - 2011 Cassidian, an EADS company
Links a Resource to one of its Annotation.
Links a SpatialSegment to one of its Coordinate.
Links a Resource to one of its LowLevelDescriptor.
Links a ResultSet to its PieceOfKnowledge.
Links a MediaUnit to one of its Segment.
Links a TrackSegment to one of its Segment
Links a Query to its parent ComposedQuery.
Links a ComposedQuery to one of its Query.
Links a resource to its parent ComposedResource or SimilarityQuery
Links a ComposedResource or a SimilarityQuery to one of its Resource.
Links a MediaUnit to its parent Document.
Links a Document to one of its sub-MediaUnit.
Links a resource to its parent ResultSet.
Links a ResultSet to one of its Resource.
The end value of a LinearSegment (char in UTF-8) or a TemporalSegment (milliseconds).
The start value of a LinearSegment (char in UTF-8) or a TemporalSegment (milliseconds).
The timestamp of a SpatioTemporalSegment
A weight used for Query combination.
Should be an ARFF content for a LowLevelDescriptor and a RDF/XML content for a PoK.
The unique identifier of a Resource or a Segment.
The string query in a free text syntax.
The optional content as a bytes array.
The String content of the text. Might be empty, in that case an annotation referring to the whole large
content should be present.
This is a simple restriction of String to reduce the values to the three boolean operators AND/OR/NOT.
Note that in a n-ary context, the unary operator NOT is considered as a AND NOT.
AND
OR
NOT
Abscissa value in pixels, with 0 at the left border. Other measure references are possible.
Ordinate value in pixels, with 0 at the bottom border. Other measure references are possible.
Annotation
An Annotation will contain a set of RDF statements which refer to a specific resource or part of resource
(segment) known as the subject of the annotations. Thus, an Annotation object is fully dependent on the resource it describes.
So an Annotation is a PieceOfKnowledge but where most of the statements in its data refer to the resource it depends on.
Annotation is one of the major objects manipulated through the WebLab platform since it will allow adding any particular information
on any type of WebLab resource. For example, many process services will add Annotations in order to link the extracted information
to the resource processed (i.e. a language recognition service will annotate a document in order to note the language identified,
or perhaps that the language could not be recognised).
Audio
An Audio unit describes audio content out of media document. It allows describing the structure and may contain the bytes of the
Audio part (note that it's not recommended with big content). As a resource it can be annotated to describe the audio content.
It can also be described using low level descriptors. The original content may be in content field or a reference using an annotation
should be made to the content.
ComposedQuery
1
This kind of Query is only an aggregation of Queries using a n-ary boolean operator to combine them. Composing Queries using various
ComposedQueries will enable to deal with brackets. Please note that when dealing with the operators AND and OR, the number of used
Queries should be at least two; used with a simple Query it will have no effects. NOT is an unary operator, so the list
of Queries should be reduced to one, but when using it in a more-that-one-query list, a AND NOT operator will be used.
Composed resource
1
A ComposedResource defines a simple aggregate of resources and allows to regroup them within the same unit. Since a multimedia
document is a resource, the simplest ComposedResource will be a corpus of documents such as videos about the same program during
one year. It could also be a set of useful resources needed by a service such as a set of annotations or a document with an attached
PoK that allows to analyse it. As a resource, a ComposedResource could be annotated to provide, for example, meta-information on its
content or the reasons of the aggregate.
Coordinate
A coordinate is a simple container of two dimensional coordinates aiming at localising information spatially in a mediaUnit;
for instance in an image or a video. Those dimensions are generally expressed in pixels, given the fact that it starts at
bottom-left with (0;0). Other measures somehow references are possible.
Document
A Document is assumed to be a resource which handles the references of all the units that have been built on it through the multiple
processes. A Document could be annotated to provide, for example, meta-information on the original document source, the author or
the original creation date... This object is the most commonly exchanged object in usual WebLab-based applications.
Elementary Query
This kind of Query is simply not a ComposedQuery. It contains a weight (with default value at 1.0) which could be used for Query
combination.
Image
An Image unit describes a visual static content out of media document. It does not have any particular attribute but only allows
describing the structure. As a resource, it can be annotated to describe the content. It can also be described using low level
descriptors. The original content may be in the content field or a reference using annotation should be made to the content.
Linear segment
A LinearSegment is a position which can be described by a start and end reference in accordance to a number of UTF-8 characters
metric. It is the kind of segment that should be used for text units. As a resource, LinearSegments could be annotated to provide
information on a particular part a text, like a word for instance.
Low Level Descriptor
A LowLevelDescriptor is composed of a set of features that have been extracted from a document or a part of document. It aims
at representing low level annotation (not at a semantic level but at a numerical level) mainly for computing similarity between
objects. For instance, Text could use LowLevelDescriptor to store TFIDF values, Image could use LowLevelDescriptor to handle
color histograms. As a resource, a LowLevelDescriptor could be annotated to provide, for example, meta information on its creation
date, its version or its application domain. The content of a LowLevelDescriptor may is only constrainted to be XML. We recommend
to use the XARRF schema.
Media Unit
This is the major object manipulated through the WebLab platform. It is mainly assumed that almost all processing services should
accept the MediaUnit as a common argument and provide enhanced MediaUnit as a result. A MediaUnit can be defined as the structural
annotable representation of any multimedia content. It is a resource and thus can be retrieved by an URI and annotated by any kind
of descriptive annotations or low level descriptors. As described in the following sections any particular type of media
(i.e. picture, text, video segment, audio sample or video frame...) will inherit from this object. It could have a composed unit
as parent when it is contained in a group of units. Finally, it could contain annotable segments which will allow describing
sub-parts of its own content.
Piece of Knowledge
A PieceOfKnowledge (or PoK) object should be understood as the definition provided by the W3C in its resource description framework.
One can note that we involve the RDF methodology concepts and design formalisms which should not be misunderstood as the RDF/XML
serialisation format. Each PoK is composed of a set of RDF statements composed of a set of triples: subject, property and object.
Thus, any description can be applied on any resource as soon as the property and object elements refer to a consistent vocabulary in a
certain domain. This vocabulary could be expressed in accordance to a specified ontology. However, one of the project's guidelines
is extensibility, thus PieceOfKnowledge should be extendable using any OWLS or RDFS. The set of triple statements describing a
resource will be contained in the PieceOfKnowledge object serialised in the RDF/XML format. Since a PoK is a resource, it can also
contain Annotations. The contained statements can be seen as meta-Annotations describing, for example, how and when the first level
of annotations has been created (which service with what resource or configuration).
Query
A Query is a resource which contains request data. This data describes each specific specialisation of query, in a specific format.
The Query object is then abstract and several specialisations will be used to describe any types of queries. A proposal is to adopt
common standards in order to provide consistent definitions over all the WebLab platform. XQuery and SPARQL formats have been
identified as promising candidates respectively for structured and semantic search. As a resource, a Query could be annotated to
provide, for example, meta-informations such as its syntax or its creation date.
Resource
A resource refers to any object that could be manipulated in the WebLab platform. It will be identified by a unique URI.
It can hold some annotations that will describe the resource itself at a semantic level. It can also hold some low level
descriptors that are describing itself at a lower level. It will be a common interface which will be inherited by almost all
WebLab objects. Any reference to a resource will use its URI.
Result Set
A ResultSet is a specific resource used to describe results of a Query. The results should be described semantically in the PoK
linked to the ResultSet. See the WebLab ontology for the properties on ResultSet. Additional and specific information could be added
for results presentation in the Resources list. As a Resource, a ResultSet could be annotated to provide more information. But any
information about the results and the query by themselves shall be in PoK field.
Segment
A Segment is an object that do not have any content and which is linked to a media unit. It allows pointing the content of a unit at
much finer level. Information and annotation about this Segment should be part of the media that handles this Segment. It
provides a way to assign annotation on a very high level of structure description. The object will contain positioning information
which allows localising itself in its parent unit. As media type are very different, the position itself will be specialised to them
and thus, provide localisation adapted to the media. This object cannot be used itself (this is an abstract object). However, some
implementations with real capabilities are developed in order to match every media class.
Similarity Query
This Query is dedicated for search by similarity and thus its content is one or more resources.
Spatial segment
2
A SpatialSegment is aiming to localise any meaningful content in a spatial document (mainly Image). For example, one can think to
a picture showing some people. Specific segment can be localised with coordinate descriptors defining the silhouettes of each person
in the picture. Then, specific annotations can be applied to each segment (i.e. to declare that those are human beings). It is the
kind of segment that may be used for image and video unit. When there are only two coordinates associated to the spatialSegment,
it means that the shape is a disk. The first coordinate is the centre and the second one is one point of the circle. Otherwise,
coordinates are describing a closed shape since the last coordinate of the list will be linked to the first one.
Spatial temporal segment
A SpatioTemporalSegment aims to give the instant location of an object in a spacial document
(i.e. Video). For example, one can think of a video showing a moving object. Specific segment can be localised with coordinate
descriptors defining the border of the object in each of the video images where it appears. Then, specific annotation can be applied to
each segment. The way to define the location is the same than the SpatialSegment one.
String Query
This Query is dedicated for any Query expression language which can be expressed in a simple string such as full text queries,
XQuery or SPARQL. Details on the language used to express the Query should be provided in an Annotation on the Query.
Temporal segment
A TemporalSegment is a segment that is described by a start and end reference in accordance to a millisecond metric. It is the kind
of position that may be used for audio and video units.
Text
A Text unit is the simplest specification of the media unit dedicated to full text data. Its unique attribute is a string which is
in most cases the text extracted from the original document content. This content is optional, since sometimes it might be too
large to be handled in this field. In that case, we encourage to link it through the same mecanism as Audio/Video/Image content.
A simple text document such as HTML page could be described by a document which contains a unique Text unit. As a resource, a Text
unit could be annotated and could also be described with low level descriptors.
Track segment
2
A TrackSegment provides a way to assign a single annotation on a set of linked segments. A TrackSegment is a
kind of segment and pool several other segments in order to allow the desciption of an entity that appears several times in the annotated
content.
Video
A Video unit describes a dynamic visual content out of media document. As a resource it can be annotated to describe the content.
It can also be described using low level descriptors. The original content may be in the content field or a reference using
annotation should be made to the content.
© 2015 - 2025 Weber Informatics LLC | Privacy Policy