The DOCOM Ontology provides the main concepts and properties required to describe compound documents made from smaller fragments that are assembled to produce the final document. This report contains a detailed description of the DOCOM Ontology.
1 Introduction
1.1. Terminology and notation
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Namespace URIs of the general form "http://www.example.com/" represent some application-dependent or context-dependent URI as defined in RFC 2396.
The XML Namespace URIs that MUST be used by implementations of this specification is:
2. DOCOM ontology at a glance
An alphabetical index of DOCOM terms, by class (concepts) and by property
(relationships, attributes), are given below. All the terms are hyperlinked
to their detailed description for quick reference.
Classes: Adapter, Annotation, Document, DocumentaryProject, DocumentaryWorkproduct, File, Format, Gap, InputAdapter, IntermediateLanguageDocument, OutputAdapter, PersonProjectRoleAssociation, ProjectRole, SourceDocument, Tag, Ticket, View, Workflow,
Properties: annotates, hasAdapter, hasDocumentaryWorkproduct, hasFile, hasFormat, hasGap, hasMainFile, hasOnlineAccount, hasProject, hasProjectRole, hasRootGap, hasTag, hasTicket, hasWorkflow, inputFormat, isFilledBy, isFormatOf, isProducedBy, managedBy, outputFormat,
3. DOCOM ontology overview
The DOCOM Ontology definitions presented in this report are written using a computer language ([OWL]) that makes it easy for software to process some basic facts about the terms in the ontology, and consequently about the things described using the DOCOM vocabulary.
The following figure summarizes the concepts that are part of DOCOM and their relationships. Some auxiliary concepts are referenced by DOCOM, such as rdf:Resource (from [RDF Schema]) and foaf:Person (from [FOAF]), although they are not part of the DOCOM ontology.
3.1. Example
What follows is a very simple description of a compound document. Note that some resources are not completely described here for the sake of simplicity.
<rdf:RDF ... >
<DocumentaryProject rdf:about="http://example.org/projects/vulcano-partners">
<hasDocumentaryWorkproduct>
<DocumentaryWorkproduct rdf:about="http://example.org.org/projects/vulcano-partners/dwps/1">
<hasFormat rdf:resource="http://example.org/formats/xdoc"/>
<hasRootGap>
<Gap rdf:about="http://example.org.org/projects/vulcano-partners/dwps/1/rootGap">
<isFilledBy>
<IntermediateLanguageDocument rdf:about="http://example.org/intermediate_documents/1">
<hasFormat rdf:resource="http://example.org/formats/xdoc"/>
<isFormatOf>
<SourceDocument rdf:about="http://example.org/fragments/1">
<hasMainFile rdf:resource="http://www.example.org/20081103.xml"/>
<hasFormat rdf:resource="http://example.org/formats/xml"/>
<hasAdapter about="http://example.org/inputadapters/fromXml"/>
</SourceDocument>
</isFormatOf>
<hasGap>
<Gap rdf:about="http://example.org.org/fragments/1/gaps/2">
<isFilledBy rdf:resource="http://example.org/intermediate_documents/2"/>
</Gap>
</hasGap>
</IntermediateLanguageDocument>
</isFilledBy>
</Gap>
</hasRootGap>
</DocumentaryWorkproduct>
</hasDocumentaryWorkproduct>
</DocumentaryProject>
</rdf:RDF>
4. Cross-reference for DOCOM classes and properties
Property: docom:hasMainFile
URI: http://idi.fundacionctic.org/docom#hasMainFile
has main file - a source document and a view (being both documents) have, among all the integrating resources, one considered as main file.
- OWL Type:
- ObjectProperty
- sub-property-of:
- docom:hasFile
[back to top]
Copyright © 2008 by Fundación CTIC. This work
is licensed under CreativeCommons
Attribution-Share Alike 3.0, so you are granted to use, copy, distribute, transmit and adapt
this work, but you must attribute the work to the original authors and distribute the resulting
work under similar terms.
