
 
  Flexible reuse of content: different ontologies 
and terminologies should be able to coexist, 
complement one another, and co–develop on 
separate sites.  
  Ease of implementation and deployment: 
contents usable by third party tools, help 
divide and conquer big ontologies.  
For TermFactory web ontology based terminology 
management, we found a need for editing tools for 
non-ontologists to edit term ontologies that would be 
simpler and more accessible to terminologists than 
mainstream ontology editors. We designed 
RDF/XHTML and its Web API as an answer to this 
need. As the format and tools are quite generic with 
little that is specific to term ontologies in particular, 
we propose to present them here to the ontology 
developer community at large.  
3 RDF FORMATS 
RDF has several serialization formats (file formats) 
which vary in the way in which resources and triples 
are encoded. For historical reasons, XML is the 
official syntax for RDF. For multilingual ontologies, 
RDF/XML is not a good choice. A concrete flaw of 
RDF/XML for multilingual (or non-Latin, in 
general) ontologies is that there is no provision for 
coding property names containing non-Latin 
characters. The only RDF/XML representation for 
property names is XML element name (QName), 
which has a restricted character repertoire. Non-
Latin property names require lengthy and unreadable 
character encodings. A simple expedient would be to 
extend RDF/XML with property elements identified 
by full URIs, e.g. 
<ex:label>term</ex:label> 
could be written as  
<rdf:Property 
 rdf:about=http://example.com#label”> 
   term 
</rdf:Property> 
A simpler alternative to RDF/XML is Turtle 
(2010), a textual format for RDF graphs close to the 
triple format. Turtle is terse and human readable. 
Yet it too has limitations. Resource names cannot be 
abbreviated with prefixes if they contain Turtle 
reserved characters. It would be as well for Turtle 
not to reserve punctuation characters, since Turtle 
punctuation is conventionally separated by 
whitespace anyway.  
4 ONTOLOGY EDITING 
Syntax editing of ontology triples can yield 
unexpected results. Deletion of facts in general 
involves difficult problems of nonmonotone 
reasoning or belief revision. The best one can do is 
avoid redundancies by using some normal form.  
A normal form is a unique choice among 
equivalent representations. Reduction to normal 
form by term rewriting is what many reasoners in 
effect do. RDF/OWL databases are supposed to keep 
graphs in a nonredundant form to support updates.   
The standard serializations of RDF do not 
provide a unique normal form. Textual normal forms 
for RDF have been proposed (Carroll/Stickler 2004, 
Dau 2006, Gutierrez et al. 2011). Semantic normal 
forms for some description logics have been 
proposed (Hitzler/Eberhart 2007, Bienvenu 2008).  
We have argued that the standard serializations 
of RDF are not well suited for multilingual ontology 
editing as such. Special purpose ontology editors 
avoid problems by building their own graphical 
editing interfaces often borrowing from Eclipse. 
Many standalone ontology editors exist, both open 
source and commercial.  
5 EDITING IN RDF/XHTML 
In designing TF, we did not want to build yet 
another application. Instead, we wanted to choose or 
adapt a serialization format for the web that is 
familiar to users, has support in general purpose web 
editing tools, without yet compromising machine 
processability.  
XHTML seems to best fill the bill. As an 
extension of XML, it supports Unicode and can be 
manipulated with common XML tools. As the native 
representation format of browsers, can be depended 
on to provide good support for display. XHTML can 
be edited with a wide range of standalone tools and 
browser extensions. The HTML 5 standard (2012) is 
to merge with XHTML and provide built in support 
for direct editing.  
The RDF/XHTML format represents RDF 
models in the form of a sorted HTML list of tree-
structured entries, isomorphic with Turtle. It 
supports WYSIWYG editing through a user 
definable XHTML skin (Figure 1). The idea is 
similar to that applied in XML editors like 
XMLmind (2012).  
The layout of the XHTML document can be 
customised with templates also written in RDF. The 
output of the XHTML writer can be varied with a 
number of parameters: 
KEOD2012-InternationalConferenceonKnowledgeEngineeringandOntologyDevelopment
366