- From: <w3t-archive+esw-wiki@w3.org>
- Date: Wed, 28 Sep 2005 07:42:27 -0000
- To: w3t-archive+esw-wiki@w3.org
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.
The following page has been changed by YvesSavourel:
http://esw.w3.org/topic/its0509SpecScoping
The comment on the change is:
Something to get the ball rolling...
------------------------------------------------------------------------------
= Scoping Mechanism =
+ === Levels ===
+
+ We identified four main location where ITS information could need to be specified.
+
+ * In an external file (e.g. to address general information for DTD-based document types)
+
+ * In schemes files (e.g. XML Schema and Relax-NG documents).
+
+ * "In a header" of a document instance, i.e. grouped somewhere at the top the document. (e.g. to address cases where ITS info has to be overwritten at a high level in a document (vs. at the element level).
+
+ * At the element level in a document instance. (e.g. to overwrite the ITS info for that element).
+
+
+ === Example with translatibility ===
+
+ To specify translability we currently defined the following:
+
+ * By default, all element are translatable and all attribute are not translatable.
+
+ * We have a {{{translate}}} attribute with a "yes|no" value to provide overwriting information. This can be used at the element level, and within schema files (e.g. when defining a XSD <element>).
+
+ {{{<para id="a1" its:translate="no"
+ >Do not translate this, <span its:translate="yes">except this part</span>, etc.</para>}}}
+
+
+ Several questions regarding the scope:
+
+ * The cases for "external file" and "in a header" level are not supported yet.
+
+ * What do we do for attributes? Should overwriting the don't-translate default for attribute with an ITS mechanism be even allowed?
+
Received on Wednesday, 28 September 2005 15:53:37 UTC