W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2006

[Bug 3461] Role of termInfo

From: <bugzilla@wiggum.w3.org>
Date: Fri, 14 Jul 2006 19:49:00 +0000
CC:
To: public-i18n-its@w3.org
Message-Id: <E1G1Tem-0007y1-8P@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3461

           Summary: Role of termInfo
           Product: ITS
           Version: LastCall
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ITS tagset
        AssignedTo: fsasaki@w3.org
        ReportedBy: ysavourel@translate.com
         QAContact: public-i18n-its@w3.org


Issue #18 of i18nCore comments
http://www.w3.org/International/reviews/0606-its/

Section 6.4.1: We think we are running against danger if we broaden the scope
of the data definition so widely that any kind of information can be associated
with 'terms'. The whole point of ITS is to clarify what to expect from markup.
Given your comment above, If tools don't know what to do with the data they
have read in, what have we gained by using ITS?

We think that we should say that the information at the end of the termInfo
link is a definition or relevant text to support the understanding of the term
identified.

If we are too vague about what is pointed to, we will lose the advantage we
were aiming for of tools understanding what the ITS markup is saying.

(For example, some enterprising developer may decide that the terminology
mechanism here provides a nice way of associating designer's notes with inline
text. That would be a bad idea because one point of creating the ITS spec is
that translation tools should understand what type of information they are
receiving, and handle it automatically. He should use the locInfo mechanism for
that.)
Received on Friday, 14 July 2006 19:49:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:07 UTC