W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > April 2012

Re: [issue 3] What ontology should describe the metadata values (entity types)

From: Arle Lommel <arle.lommel@gmail.com>
Date: Fri, 27 Apr 2012 09:51:01 -0800
Cc: public-multilingualweb-lt@w3.org
Message-Id: <3C44B293-37EB-4482-8DBE-AC3CF4C84780@gmail.com>
To: David Lewis <dave.lewis@cs.tcd.ie>
> However, this leave us with the problems of addressing other important file formats such as TBX, TMX and XLIFF.  Does anyone have experience of best practice in using external references to elements in such formats, e.g. using Xpointer, URI with specific conventions for resolving element ID? 


For at least TBX, this is relevant:

http://www.xml-intl.com/docs/specification/TBX-Link.html

This was never officially adopted by LISA (I think there was one outstanding action item, but I don't recall what it was), but it represents one attempt to deal specifically with this issue. The basic approach was to link to termid attributes in a TBX file, which provides an unambiguous pointer into a TBX repository.

An example from the draft specification shows how simple it really is:

<?xml version='1.0' encoding='UTF-8'?>
<doc xmlns:tbx="urn:lisa-tbxlink-tags">
    <tbx:tbx termbase="http://purl.org/xml-intl.com/tbx-link:8700" version="1.0" 
    date="2004-12-18T13:06:52Z" tool-name="XYZ Term Finder" tool-version="1.32" language="en_US">
    <p>An example paragraph with an embedded
	<tbx:term termid="a125fg" termbase="http://purl.org/xml-intl.com/tbx.xml">
	    term
	</tbx:term>
       that is linked to a non-default TBX repository.
    </p>
    <p>A second 
        <tbx:term termid="fde12a">
	   example
	</tbx:term>
       that uses the default TBX repository as specified in the "Termbase"
       attribute of the main "tbx:tbx" element.
    </p>
    </tbx:tbx>
</doc>

Best,

Arle
Received on Friday, 27 April 2012 17:51:35 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:24:55 UTC