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

ITS requirements categorization

From: Masaki Itagaki <imasaki@qwest.net>
Date: Tue, 1 Mar 2005 09:41:39 -0700
To: public-i18n-its@w3.org
Message-ID: <E1D6ATA-0007DJ-4Y@frink.w3.org>

(This is the same posting addressed to the member ML. My double apology...)

>- Everyone: Try to come up with the start of a classification of the
> different requirements we have.

I've done a bit of categorization for my own understanding, so let me start
out this with some high-level categorization. I might have mis-categorized
some items due to the lack of understating points, while some should be
categorized differently as the discussion develops later. We have already
discussed some new requirements, but I have not included those here, yet.
Any comments and changes are welcome:

1. General Requirements: The same as the section 2.1

2. Requirements for localizability: I gathered items that could lead to
"physical" proposals that processes and tools may require (such as tags,
attributes, DTD designs, etc). 

2.1 Localization annotation: I believe this is what Yves mentioned as
"Communication from/to localizers." 
2.3 Information for rendering: Simply saying, these are what tools parse. We
may need one more subcategory for this level.

3. Best Practices: These are advisory recommendation regarding DTD/Schema
design and others. 


1. General Requirements
2. Requirements for Localizability
   2.1 Localization annotation
	[2.4] Provision of a SPAN-like element
	[2.5] Note to localisers

   2.2 Information for rendering
	[2.2] Direct identification of content that should not be translated
	[2.3] Indirect identification of content that should not be
	[2.8] Tags with linguistically-dependent scope
	[2.12] Describing other cultural aspects of the content
	[2.13] Citations
	[2.14] References to UI messages in documentation
	[2.17] Allowed characters
	[2.18] Term identification
	[2.19] Inline and subflow elements
	[2.20] Word breaking
	[2.21] White space handling
	[2.22] Unicode characters vs. markup
	[2.23] Markup to support international script features

3. Best practices
	[2.6] Attributes and translatable text
	[2.7] Emphasis & document conventions
	[2.9] Unique identifiers
	[2.10] Character encoding declarations
	[2.11] Declaring the language of the content
	[2.24] Support for localisable resource data 
Received on Tuesday, 1 March 2005 16:43:36 UTC

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