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

[Bug 2621] On conformance levels: Have a simple conformance: in situ, with default selectors

From: <bugzilla@wiggum.w3.org>
Date: Fri, 13 Jan 2006 11:16:56 +0000
To: public-i18n-its@w3.org
Cc:
Message-Id: <E1ExMvQ-0001TA-Ev@wiggum.w3.org>

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





------- Additional Comments From christian.lieske@sap.com  2006-01-13 11:16 -------
I agree with Felix that conformance can be defined independently
from an attribute like the "markupType" sketched in Yves' mail.

Furthermore, I like Felix' suggestion to destinguish between markup conformance 
and processing conformance.

Wrt. to the granularity of the conformance model, however, I am currently in 
favour of a fine grained model (rather than the coarse grained/monolithic one 
proposed by Felix). Such a model (which might be inspired by for example 
http://www.w3.org/TR/2001/REC-xsl-20011015/slice8.html#conform) from my point 
of view would allow an evolutionary path to implementations. Rationale: If it 
turns out that efforts for the implementation of processing conformance which 
takes into account e.g. proper selector handling (ie. all flavours of mixing in-
situ with dislocated selectors) are high, we may not see many implementations 
quickly. If, by contrast, however, we define a basic conformance level in such 
a way that implementation is easy (since e.g. only in-situ selectors need to be
supported) we may see implementations more quickly. From my understanding, 
already basic implementations (e.g. ones just supporting "its:translate") would 
be help us to reach our goal of enhancing internationalization and localization.
Received on Friday, 13 January 2006 11:17:05 UTC

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