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

Terminology to be used with ITS markup (II)

From: Lieske, Christian <christian.lieske@sap.com>
Date: Mon, 23 Jan 2006 15:44:36 +0100
Message-ID: <0F568FE519230641B5F84502E0979DD1046C8F4E@dewdfe12.wdf.sap.corp>
To: <public-i18n-its@w3.org>

Dear all,

While working on the task to write an introduction to selection
(formerly know as "scoping") I made a general observation: from
my understanding we might benefit from one or two changes related
to the terminology we use.

Let's start with the following question:

	What is ITS markup meant to do?

>From my understanding, the ITS markup captures information related
to i18n or l10n. Following this line of thought, sth. like

	<body its:translate="no" translateSelector="./p">

can be analyzed two-fold, namely either as markup or as information
captured by ITS markup.

With respect to the view "this is ITS markup", we have to dive down
a bit. To me, it seems appropriate to destinguish:

	A. Data category identifier: "its:translate"
	B. Data category value: "no"
	C. Data category selector: "translateSelector"

The view "this is ITS information" could be captured by prose like the
following:

	The ITS markup 'its:translate="no"' captures the information
that
	something should not be translated.

I wonder if it is just me who senses a need to capture the two possible
views
(markup vs. information).

>From my understanding, we would benefit from a distinction (which could
be captured by using two different terms to talk about it), and an
accompanying
set of terms to talk about the three possible parts of ITS markup (see
above).
Of course, I would be in favour of following terminology established by
other
groups (however, so far I have not been able to research into this).

Best regards,
Christian
Received on Monday, 23 January 2006 14:44:51 UTC

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