Web metadata semantics-on the road to well formed topic maps

Widhalm, Richard; Mueck, Thomas A.

doi:10.1109/wise.2001.996741

Cited by 1 publication

(5 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [19] and [20], the TMUML meta model has been presented, including a detailed description as well as the according class diagrams. It is a meta model for Topic Maps, directly derived from the UML meta model.…”

Section: Topic Maps and The Tmuml Meta Modelmentioning

confidence: 99%

“…Base names and its subvariants are all represented by TopicName (which may be part of a name hierarchy). See [19] and [20] for a detailed description of the TMUML meta model. The TMUML meta model enables our process for validating the well-formedness of a topic map.…”

Section: Topic Maps and The Tmuml Meta Modelmentioning

confidence: 99%

“…But changing T O 2 to T T 2 would be an appropriate measurement, requiring every class-instance relation from T O 2 to some T T 2super to be transformed by the merging operation to a subtype relation from the resulting T T 2 to the original T T 2super . This works, because a TO does not have any further capabilities in the TMUML meta model than a TT has, and a TT may also play a role within an association instance (see also [19]). Fig.…”

Section: Tt -To At -To Ot -Tomentioning

confidence: 99%

“…As a TO has no instances and no more capabilities in the TMUML meta model than an AT, the TO can be converted to and AT after merging the TO and the AT. Note that an AT can also be a member of a TopicAssociationEndInstance (see [19]). The same is true for an OT and a TO.…”

Section: Tt -To At -To Ot -Tomentioning

confidence: 99%

“…Intuitively, in this situation we will try to specialize T T 1 and convert it to AT 1 . As AT 1 .properties() will (after the conversion from a TT to an AT) obviously be empty, AT 1 simply will have the same properties as AT 2 after the merge (for the definition of AT.properties, which yields the TopicAssociationEnds of an AT, taking inheritance into account, see [19] or [20] ). On the other hand, T T 1 and all its subtypes must not have any instances (TOs), because this would mean these TOs should actually be TopicAssociations after the merge, which is not possible.…”

Section: Tt -At Tt -Otmentioning

confidence: 99%

See 4 more Smart Citations

Merging Topics in Well-Formed XML Topic Maps

Widhalm¹,

Mueck²

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Topic Maps are a standardized modelling approach for the semantic annotation and description of WWW resources. They enable an improved search and navigational access on information objects stored in semi-structured information spaces like the WWW. However, the according standards ISO 13250 and XTM (XML Topic Maps) lack formal semantics, several questions concerning e.g. subclassing, inheritance or merging of topics are left open. The proposed TMUML meta model, directly derived from the well known UML meta model, is a meta model for Topic Maps which enables semantic constraints to be formulated in OCL (object constraint language) in order to answer such open questions and overcome possible inconsistencies in Topic Map repositories. We will examine the XTM merging conditions and show, in several examples, how the TMUML meta model enables semantic constraints for Topic Map merging to be formulated in OCL. Finally, we will show how the TM validation process, i.e., checking if a Topic Map is well formed, includes our merging conditions.

show abstract

Section: Topic Maps and The Tmuml Meta Modelmentioning

confidence: 99%

Section: Topic Maps and The Tmuml Meta Modelmentioning

confidence: 99%

Section: Tt -To At -To Ot -Tomentioning

confidence: 99%

Section: Tt -To At -To Ot -Tomentioning

confidence: 99%

Section: Tt -At Tt -Otmentioning

confidence: 99%

See 3 more Smart Citations