/* Ousía Copyright (C) 2014, 2015 Benjamin Paaßen, Andreas Stöckel This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . */ /** * @file Document.hpp * * This header contains the class hierarchy of actual document classes. A graph * of connected instances of these nodes is a "Document". How the different * DocumentEntity instances may be connected within the graph is subject to the * specification in the respective Domain(s) (see also the Domain.hpp). * * A Document, from top to bottom, consists of "Document" instance, * which "owns" the structural root node of the in-document graph. This might * for example be a "book" node, if the respective document implements the * "book" domain. That root node in turn has structure nodes as children as well * as annotations that refer to the content of that structure node. * * Consider this simplified XML representation of a document (TODO: Use * non-simplified XML as soon as possible): * * * * * * This is some text with some emphasized and * strong text. * * * * * * * * As can be seen the StructureEntities inherently follow a tree structure that * is restricted by the implicit context free grammar of the "book" Domain * definition (e.g. it is not allowed to have a "book" node inside a "section"; * refer to te Domain.hpp for more information). * * Another interesting fact is the special place of AnnotationEntities: They are * Defined by start and end Anchors in the text. Note that this allows for * overlapping annotations and provides a more intuitive (and semantically * sound) handling of such span-like concepts. * Note that the place of an AnnotationEntity within the XML above is not * strictly defined. It might as well be placed as a child of the "book" node. * In general it is recommended to use the lowest possible place in the * StructureTree to include the AnnotationEntity for better readability. * * @author Benjamin Paaßen (bpaassen@techfak.uni-bielefeld.de) */ #ifndef _OUSIA_MODEL_DOCUMENT_HPP_ #define _OUSIA_MODEL_DOCUMENT_HPP_ #include #include #include #include "Domain.hpp" #include "Typesystem.hpp" namespace ousia { namespace model { class StructuredEntity; class AnnotationEntity; /** * A DocumentEntity is the common superclass for StructuredEntities and * AnnotationEntities. Similarly to DescriptorEntity in the Domain.hpp it * defines that each node in the Document graph may have attributes (in form * of a struct Variant), and fields. * The fields here are a vector of vectors. The first vector implements all * fields while the inner vector contains all children in this field. * We provide, however, convenience functions for better access via the field * name. * */ class DocumentEntity : public Node { private: Owned descriptor; const Variant attributes; std::vector> fields; Rooted getFieldDescriptor(const std::string &fieldName); public: DocumentEntity(Manager &mgr, std::string name = "", Handle parent, Handle descriptor, Variant attributes) : Node(mgr, std::move(name), parent), descriptor(acquire(descriptor)), attributes(std::move(attributes)) { // TODO: Validation at construction time? // insert empty vectors for each field. for (int f = 0; f < descriptor->getFieldDescriptors.size(); f++) { fields.push_back(ManagedVector(this)); } } Rooted getDescriptor const() { return descriptor; } const Variant &getAttributes() const { return attributes; } Variant getAttributes const { return attributes; } /** * This allows a direct manipulation of the internal data structure of a * DocumentEntity and is not recommended. TODO: Delete this? */ std::vector> &getFields() { return fields; } /** * This returns true if there is a FieldDescriptor in the Descriptor for * this DocumentEntity which has the given name. If an empty name is * given it is assumed that the 'default' FieldDescriptor is referenced, * where 'default' means either: * 1.) The only TREE typed FieldDescriptor (if present) or * 2.) the only FieldDescriptor (if only one is specified). * * @param fieldName is the name of a field as specified in the * FieldDescriptor in the Domain description. * @return true if this FieldDescriptor exists. */ bool hasField(const std::string &fieldName = "") { return getFieldDescriptor(fieldName) != nullptr; } /** * This returns the vector of entities containing all members of the field * for which the FieldDescriptor has the specified name. If an empty name is * given it is assumed that the 'default' FieldDescriptor is referenced, * where 'default' means either: * 1.) The only TREE typed FieldDescriptor (if present) or * 2.) the only FieldDescriptor (if only one is specified). * * Note that the output of this method might well be ambigous: If no * FieldDescriptor matches the given name an empty ManagedVector is * returned. This is also the case, however, if there are no members for an * existing field. Therefore it is recommended to additionally check the * output of "hasField" or use the overloaded version of this method with * a FieldDescriptor as input. * * @param fieldName is the name of the field as specified in the * FieldDescriptor in the Domain description. * @return a ManagedVector of all StructuredEntities in that field. If the * field is unknown or if no members exist in that field yet, the * ManagedVector will be empty. Note that the ManagedVector is * returned as a reference, so it is possible to manipulate this * DocumentEntities content using this function. */ ManagedVector &getField(const std::string &fieldName = "") { Rooted fd = getFieldDescriptor(fieldName); if (fd == nullptr) { return ManagedVector(this); } return getField(fd); } /** * This returns the vector of entities containing all members of the field * with the given FieldDescriptor. * * If the FieldDescriptor does not belong to the Descriptor of this node * an exception is thrown. * * @param fieldDescriptor is a FieldDescriptor defined in the Descriptor for * this DocumentEntity. * @return a ManagedVector of all StructuredEntities in that field. */ ManagedVector &getField( Rooted fieldDescriptor); }; /** * A StructuredEntity is a node in the Structure Tree of a document. For more * information please refer to the header documentation above. */ class StructuredEntity : public DocumentEntity { private: ManagedVector annotations; public: StructuredEntity(Manager &mgr, std::string name = "", Handle parent, Handle descriptor, Variant attributes) : DocumentEntity(mgr, std::move(name), parent, descriptor, attributes), annotations(this) { } ManagedVector &getAnnotations() { return annotations; } }; /** * This is a wrapper for primitive types (Variants) inside the document graph. * The most straightforward example for this is the actual document text, e.g. * inside a paragraph. In that case this would represent a mere string. */ class DocumentPrimitive : public StructuredEntity { public: DocumentPrimitive(Manager &mgr, Handle parent, Variant content) : StructuredEntity(mgr, "", parent, nullptr, content) { } Variant getContent() const { return getAttributes(); } const Variant& getContent() const { return getAttributes(); } // TODO: Override such methods like "getField" to disable them? } /** * An AnnotationEntity is a span-like instance that is not bound by the elements * of the Structure Tree. An annotation may very well overlap and cross the * limits of StructureEntities. A typical example for AnnotationEntities are * the markups "emphasized" and "strong". In HTML like markup languages these * concepts are handeled as structure elements, like this: * * emphasized and strong * * which is neither intuitive nor semantically sound. Therefore we take the * approach of anchoring the Annotation entities in the text like this: * * emphasized and strong * * * * Which signifies that indeed the text "emphasized and" is emphasized, not * the two text exerpts "emphasized" and "and" separately. * */ class AnnotationEntity : public DocumentEntity { public: /** * An Anchor is an elementary StructuredEntity without any children that * marks a point in the text content of the document that can later be * referenced by an AnnotationEntity as it start and end point. * Please refer to the AnnotationEntity documentation for more information. */ class Anchor : public StructuredEntity { public: /** * @param mgr is the Manager instance. * @param name is the Anchor id. * @param parent is the parent of this Anchor in the Structure Tree (!), * not the AnnotationEntity that references this Anchor. */ Anchor(Manager &mgr, std::string name = "", Handle parent) : StructuredEntity(mgr, name, parent, nullptr, Variant()) { } }; private: Owned start; Owned end; public: AnnotationEntity(Manager &mgr, std::string name = "", Handle parent, Handle descriptor, Variant attributes, Handle start, Handle end) : DocumentEntity(mgr, std::move(name), parent, descriptor, attributes), start(acquire(start)), end(acquire(end)) { } Rooted getStart() { return start; } Rooted getEnd() { return end; } }; } } #endif /* _OUSIA_MODEL_DOCUMENT_HPP_ */