W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2005

draft requirement related to 'purpose specification/mapping'

From: Lieske, Christian <christian.lieske@sap.com>
Date: Thu, 7 Apr 2005 11:54:05 +0200
Message-ID: <0F568FE519230641B5F84502E0979DD102993DA6@dewdfe12.wdf.sap.corp>
To: <public-i18n-its@w3.org>


Dear all,

During the F2F, I touched on a dimension which I tend to term 'purpose
specification' and sometimes 'mapping'. Since the F2F participants got
the impression that this is something to follow up on, I have
put together a draft ...

Best regards,
Christian
---

Challenge/Issue
===============

>From a localization point of view, many XML vocabularies include markup
which requires special attention, since the markup is associated with a
specific type of content. Examples:

a. elements which are associated with embedded/binary graphics
b. elements which are associated with specific text styles (e.g.
underline and bold)
c. elements which are associated with linking (e.g. the 'a' in HTML)
d. elements which are associated with lists
e. elements which are associated with tables
f. elements which are associated with with generated content (e.g. an
element that fires a query to a database in order to pull in the data
for a product catalogue)

Some reasons why this type of markup may require special attention:

a. the localization tool may be able to render specific text styles in a
standard way (e.g. increased font weight for bold)
b. embedded binary images may have to follow a specific workflow
c. content generation queries may have to be adapted

Since it is hardly imaginable that all content developers will be able
to work with the same elements and attributes for this specific type of
content, the ITS should include markup which allows people to specify
the purpose of specific elements. 

Notes
=====

For the specific case of linking something to look at already exists:
HLink (cf. http://www.w3.org/TR/2002/WD-hlink-20020913/)

Quick Guideline Thoughts
========================

The purpose specification could look like the following example:

<its:purposeSpec>
	<servesPurpose origVoc="img" its="graphic"/>
	<servesPurpose origVoc="em" its="inline"/>
	<servesPurpose origVoc="b" its="inline"/>
</its:purposeSpec>

Here, we specify that the original vocabulary (e.g. HTML) maps to ITS.
The 'img' in HTML e.g. maps to 'graphic' in ITS.
Received on Thursday, 7 April 2005 09:54:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:44 GMT