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

[Bug 2620] Necessity of dislocated scope / selectors *and* insitu scope / selectors

From: <bugzilla@wiggum.w3.org>
Date: Thu, 05 Jan 2006 10:47:18 +0000
To: public-i18n-its@w3.org
Cc:
Message-Id: <E1EuSeM-0007AT-Mi@wiggum.w3.org>

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





------- Additional Comments From christian.lieske@sap.com  2006-01-05 10:47 -------
Very good comment/idea which also occurred to me.

>From my understanding, it could give rise to a set of data categories which is 
related to ITS itself. From my point of view, this set looks somewhat 
like 'elementFormDefault', 'attributeFormDefault' etc. in XSD.

To be specific: We could think about a data category like 'Selector Type' which 
for example could be coded as an attribute 'selectorType' with the possible 
values 'in-situ, dislocated, both, unknown'.
Received on Thursday, 5 January 2006 10:47:25 UTC

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