OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Clarification on SubstitutableMsg/Value



The test says:

"If present, the order of each element must match the order of
substitution values required by the message referenced by MsgId.  Note
that messages in some languages might have parameters in different order
than others.  In this case the parameter order shall be implied from the
order of the parameters established by the English version of the
message."

This makes no sense. What if I have a polite English and a rude English
version of the message? What if I don't have any English version
(gasp!)?

"Incorrect password entered %1 consecutive times by user %2"
Vs.
"This bonehead of %2 entered the wrong password %1 freaking times in a
row! Recommend turning him/her into pet food before further decay."

The solution seems pretty simple. Each message pattern (read language)
specifies what value it wants where based on its order. Like in the
example above. No need to make one language be the tie-breaker.

So I propose to change the text to:

"Each MsgId and MsgIdType defines in its rules how to map parameters to
compose the message based on the order of the <value> elements."

Also, it seems to make sense to restrict the type of Value to
xs:anySimpleType, don't you think?

William


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]