A case for XTM 3.0

Post on 20-Jun-2015

859 views 0 download

Tags:

description

Improvements to XTM 2.0 are suggested in this paper. First, a set of criteria is defined for evaluating those improvements. It is followed by the suggestions themselves: align element names with the names used in TMDM, reduce the number of elements by introducing mixed content and using attributes whenever it is possible. Finally, some relevant irregularities are discussed.

transcript

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

1

A Case for XTM 3.0

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

2

Goals

1. Make the format more compact

2. Improve the parsing speed

3. Simplify the parser development

4. Improve the readability

5. Improve the learning curve

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

3

Align element names

itemIdentity   itemIdentifier→

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

4

Align element names

<itemIdentity href="#shakespeare-wrote-hamlet"/>

old

Align element names

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

5

Align element names

new

Align element names

<itemIdentifier href="#shakespeare-wrote-hamlet"/>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

6

Reduce the number of elements

value

topicRef

resourceRef

resourceData

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

7

Reduce the number of elements

oldold

<name> <value>TMRA'08</value></name>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

8

Reduce the number of elements

oldold

<name>TMRA'08</name>

new

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

9

Reduce the number of elements

old

<type><topicRef href="#location"/></type>...<scope> <topicRef href="#englisn"/> <topicRef href="#data-mining"/></scope>...<role> <type><topicRef href="#conf"/></type> <topicRef href="#tmra-2008"/></role>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

10

Reduce the number of elements

new

<type href="#location"/>...<scope href="#english"/><scope href="#data-mining"/>...<role href="#tmra-2008"> <type href="#conf"/></role>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

11

Reduce the number of elements

old

<occurrence> <scope> <topicRef href="#german"/> </scope> <resourceData>Leipzig</resourceData></occurrence><occurrence> <scope> <topicRef href="#english"/> </scope> <resourceRef href="http://en.wikipedia.org/wiki/Leipzig"/></occurrence>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

12

Reduce the number of elements

new

<occurrence><scope href="#german"/>Leipzig</occurrence><occurrence href="http://en.wikipedia.org/wiki/Leipzig"> <scope href="#german"/></occurrence>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

13

Simplify the association

<association> <type><topicRef href="#happens-in"/></type> <role> <type><topicRef href="#conf"/></type> <topicRef href="#tmra-2008"/> <role> </role> <type><topicRef href="#location"/></type> <topicRef href="#leipzig"/> </role></association>

old

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

14

Simplify the association

new

<association type="#happens-in"> <role player="#tmra-2008" type="#conf"/> <role player="#leipzig" type="#location"/></association>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

15

Ensure completeness

old

<topic id="tmra-2008"> <name type="short-name"> <scope href="#english"/> </scope href="#data-mining"/>TMRA'08</name> <name>TMRA 2008</name></topic>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

16

Ensure completeness

new

<topic id="tmra-2008"> <name type="short-name" scope="english data-mining">TMRA'08</name> <name>TMRA 2008</name></topic>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

17

Controversy around itemIdentity

Item identifier is a “locator assign to an information item in order to allow it to be referred to” (TMDM, section 3.6).

“One specific use of item identifiers is in the deserialization from the XML syntax where item identifiers are created that point back to the syntactical constructs that gave rise to the information items in the data model instance” (TMDM, section 5.1).

During merging of two topics A and B, a new topic C is created with its item identifiers properties set “to the union of the values of A and B's item identifiers properties” (TMDM, section 6.2).

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

18

Controversy around itemIdentity

Topic map A with the IRI uri://base1/<topicMap version="2.0"> <topic id="id1"> <subjectIdentifier href="http://www.tmra.de/2008/"/> </topic></topicMap>

Topic map B with the IRI uri://base2/<topicMap version="2.0"> <topic id="id1"> <subjectIdentifier href="http://www.tmra.de/2008/"/> </topic></topicMap>

Topic map C with the IRI uri://base3/<topicMap version="2.0"> <topic id="id1"> <subjectIdentifier href="http://www.tmra.de/2008/"/> <itemIdentity href="uri://base1/#id1"/> <itemIdentity href="uri://base2/#id1"/> </topic></topicMap>

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

19

Controversy around itemIdentity

Suggested solution:

1. One topic – one item identifier principal.2. Introduction of item origin.

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

20

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

21

Controversy around itemIdentity

<topicMap version="2.0"> <topic id="id1"> <subjectIdentifier href="http://www.tmra.de/2008/"/> <itemIdentity href="uri://base1/#id1"/> <itemIdentity href="uri://base2/#id1"/> </topic></topicMap>

old

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

22

Controversy around itemIdentity

<topicMap version="3.0"> <topic id="id1"> <subjectIdentifier href="http://www.tmra.de/2008/"/> <itemOrigin href="uri://base1/#id1"/> <itemOrigin href="uri://base2/#id1"/> </topic></topicMap>

new

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

23

Conclusion

1. Make the format more compact

2. Improve the parsing speed

3. Simplify the parser development

4. Improve the readability

5. Improve the learning curve> 50% reductionin size of an XTMdocument

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

24

Sample XTM 3.0

<topicMap xmlns="http://www.topicmaps.org/xtm/" version="3.0"> <topic id="shakespeare-wrote-hamlet"> <subjectIdentifier href="#shakespeare-wrote-hamlet"/> <instanceOf ref="academic-debate"/> <name scope="wikipedia">Shakespeare's authorship of Hamlet<variant>Shakespeare authorship question</variant> </name> <occurrence href="http://en.wikipedia.org/wiki/Shakespeare_authorship" type="wikipedia"/> </topic>...

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

25

Sample XTM 3.0... <association reifier="shakespeare-wrote-hamlet" type="written-by" id="shakespeare-wrote-hamlet-association"> <role player="shakespeare" type="author"/> <role player="hamlet" type="work"/> </association> <topic id="wikipedia"> <name>Wikipedia</name> </topic> <topic id="written-by"> <name>Written by</name> </topic> <topic id="shakespeare"> <name>William Shakespeare</name> </topic>...

Leipzig, DE, 15/10/2008A.Mikhailian, R.Pinchuk, X.Baldauf: “A case for XTM 3.0”

26

Sample XTM 3.0... <topic id="author"> <name>Author</name> </topic> <topic id="hamlet"> <name>Hamlet</name> </topic> <topic id="work"> <name>Work</name> </topic> <topic id="academic-debate"> <itemOrigin href="iri://abstract-topics/#debate"/> <name>Academic deabate</name> </topic></topicMap>