In people’s mind, there still exists a clear distinction between document markup (e.g., XML), that we commonly use for defining the structure of a document, and the semantic markup (e.g., RDF), usually needed when we want to represent, in a particular formalism, the meaning (or, better, a subjective interpretation) of the natural language text of a document1. Document markup and semantic markup are, actually, two sides of the same coin, although most of the people see them living in two separated levels. In fact, even if the document markup is used, in the most cases, for structuring a document, it is not deny to have some markup elements for characterising a range of text to represent a real-world entity, e.g. a person.
Within a text, the element <person>2 and the class foaf:Person3 are (habitually) used for conveying the same meaning, at least from the markup author’s perspective. What really differs between them is that the semantic markup defines a formal representation of their semantics (e.g., in OWL 2 Direct Semantics), while, usually, the document markup does not. In fact, as all the XML-like languages, the markup semantics (that exists but, in this case, is inaccessible) is left to the human interpretation of a natural language definition or, in the worst case, of the markup on its own.
Thus, starting from the following premises:
- that we use markup for saying something about what it contains/refers to, and
- that markup semantics always exists, independently from the kinds of markup taken into consideration,
what is the actual profound reason that explain why document markup and semantic markup are considered different?
Footnotes