[Bug 5680] fix errors in schematron variable substitution support text & example

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





--- Comment #12 from John Arwe <johnarwe@us.ibm.com>  2009-01-28 14:27:20 ---
Suggestions (i.e. I think these might improve readability, but nothing I'd lay
in the tracks over):

(1)
Appendix F, between heading and first example, where it talks about model
processors "using" languages... that feels 'strange'.

from:
a Schematron rule with the purpose of making the Schematron rule available to
model processors using different languages. 

to:
message text resulting from Schematron rule evaluation, allowing a model
processor to support multiple locales without changes to either the model
processor or the Schematron rules.

So it then reads:
The following example, examples demonstrate how localization can be applied to 
message text resulting from Schematron rule evaluation, allowing a model
processor to support multiple locales without changes to either the model
processor or the Schematron rules.
Summarized below are the benefits resulting from using the sml:locid attribute
localization support:

(2) 
Appendix F, between heading and first example, where it talks about rules (vs
message text) being agnostic... that feels 'strange'.

from:
   1.       The Schematron rule is language agnostic 
to:
   1.       The Schematron rule message text is locale-independent

from:
aware of the locale of a potential model processor. 
to:
concerned with the rule evaluator's run-time locale.

from:
generically, to be consumed by any producer 
to:
generically, consumable by any evaluator (including a model processor)

So it then reads:
   1.       The Schematron rule message text is locale-independent in the sense
that the author does not have to be concerned with the rule evaluator's
run-time locale.
The Schematron rule is defined generically, consumable by any evaluator
(including a model processor) for which a translation file is available at the
location defined by the sml:locid value's {namespace URI}.

(2) 
Appendix F, between heading and first example, item 2

from:
   2.      There is a clear separation between the translation process and the
Schematron rule. 
to:
   2.      There is a clear separation between message text translation,
Schematron rule authoring, and Schematron rule evaluator code. 

from:
There are no changes required to be applied to the Schematron rule when
translations for other languages are made available. 
to:
The Schematron rules require no changes when translations for other languages
are made available. The same Schematron rule can be used by multiple
evaluators, each supporting a distinct set of languages.

So it then reads:
   2.      There is a clear separation between message text translation,
Schematron rule authoring, and Schematron rule evaluator code. 
The Schematron rules require no changes when translations for other languages
are made available. The same Schematron rule can be used by multiple
evaluators, each supporting a distinct set of languages.  To support a new
language, all that needs to be done is to add a new translation file under the
location identified by the sml:locid value's {namespace URI}.

(3)
Appendix F, between the first 2 examples (grey boxes, on line)
from: In this          example, the {namespace URI} 
to:   In this concrete example, the {namespace URI} 

(4)
Appendix F, after the second example (grey boxes, on line)
from:      In this concrete example,
to:   Also in this concrete example,
and
from: translation resources. For this specific example, there
to  : translation resources, and                        there
I was getting weary of the "in this concrete/specific" repetition.  I kept the
first simply to provide linkage across the example (barely kept it).

(5)
Appendix F, after the second example, numbered list
from: The  http://...lang_fr.txt file contains
to:   File http://...lang_fr.txt      contains

(6)
Appendix F, StudentIDErrorMsg examples
Looks like 1 token per line.  Did MSM's new XSLT do something unexpected?
Also see it happening again a bit later, but not all the time.  Hmmm.

(7) maybe...do what you think is sensible, I could read it as 1 or 2 ex's now
from: F. Localization and Variable Substitution Sample  (Non-Normative)
to  : F. Localization and Variable Substitution Samples (Non-Normative)
With Yves' comment, we now have >1


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 28 January 2009 14:27:30 UTC