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

Re: Note on its:term

From: Felix Sasaki <fsasaki@w3.org>
Date: Sat, 16 Jun 2012 09:10:49 +0200
Message-ID: <CAL58czqQZoe2HfgCXsLuTd551sicCDScRcxb8_BJoT_t5W8Z7g@mail.gmail.com>
To: Arle Lommel <arle.lommel@dfki.de>
Cc: Multilingual Web LT Public List <public-multilingualweb-lt@w3.org>
Hi Arle,

this is now ISSUE-24, please use this identifier in your mails.

ITS 1.0 has an existing solution (term identification and referring to
related definitions), and XLIFF markup can be mapped to it following the
approach described at
http://www.w3.org/TR/2007/REC-its-20070403/#associating-its-with-existing-markup

This does not require a change to the "term" data category, see the ITS 1.0
example below:

<its:termRule selector="mrk[@mtype='term']" termInfoPointer="xyz"/>

"selector" selects all "mrk" elements of type "term". "termInfoPointer"
points to existing information. That of course can be embedded markup, so
it fulfills the requirement your mention below.

So one way to move forward would be not to change the terminology data
category at all, but create guidance on how to use it in combination with
XLIFF 1.2 or 2.0.

Any thoughts, esp. from Arle and Yves (who has some experience in using
above pointers)?

Felix


2012/6/14 Arle Lommel <arle.lommel@dfki.de>

> Hello all,
>
> We got a request today from Christian Lieske in the XLIFF Inline Markup SC
> call to see if its:term could be expanded in its applicability to allow for
> pointers to non-textual content. E.g., Christian said he would like to be
> able to point to a graphic or sound file as a reference for a term. In
> addition, the XLIFF mrk (type=term) allows for embedding definitions,
> something currently not allowable with its:term. Making this change would
> help draw us closer closer to what XLIFF allows and let us add some
> sophistication to the terminology model.
>
> Perhaps Christian can elaborate his ideas a bit, but I wanted to get this
> on record for the update of term in ITS 2.0. I believe at this point if
> this were to move forward, we'd need to look for implementations that could
> add and use a definition attribute.
>
> Best,
>
> Arle
>



-- 
Felix Sasaki
DFKI / W3C Fellow
Received on Saturday, 16 June 2012 07:11:16 UTC

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