Semantic Annotation for Knowledge Management: Requirements and a Survey of the State of the Art

User interfaces for semantic authoring of textual content: A systematic literature review

“…semantic markup [3]) aim to annotate existing documents using a set of predefined ontologies. The basic ingredients of a semantic annotation system are ontologies, the documents and the annotations that link ontologies to documents [66]. Here, we need two kinds of ontologies [67]: Annotation ontologies (i.e.…”

“…Usually, a user wants to perform the task of writing some text and not to annotate content. Integrating semantic authoring process into the commonly used packages is one approach to encourage users to view semantic authoring as part of the authoring process not as an afterthought process [66].…”

“…So, there is no added user effort involved in creating a semantic content versus a conventional approach, because the real work is done by the software through capturing semantics that is already being provided by the user [31,6,66]. This will minimize user actions as well as memory load thereby increasing the efficiency, user satisfaction, learnability and utility of the system.…”

“…For example, in a medical context there may be one ontology for general metadata about a patient and other technical ontologies that deal with diagnosis and treatment. SCA systems need to be able to support multiple ontologies [66,9,26,47,1,57,19,42,6,32]. In a generic SCA system, the user interface must be completely decoupled from the ontological models.…”

“…A generic SCA system should provide users with userfriendly interfaces to modify the structure (classes and properties) of ontologies [66,67,15,6]. In this case, the system also needs to deal with consistency issues which might arise between ontologies and annotations with respect to ontology changes (a.k.a.…”