- From: Syd Bauman <Syd_Bauman@Brown.edu>
- Date: Tue, 21 Oct 2008 14:40:37 -0400
- To: public-i18n-its-ig@w3.org
Thanks for the information, gentlemen.
YS> The call is the 4th Tuesday of each month. That makes it Oct-28
YS> (next week) this month.
Ah, thanks. That gives me a better chance of making it. (Still not
great.)
SB> Yes, much clearer. I am a bit curious, though. Why is itsTve
SB> attribute itsTve { "yes" | "no" }
SB> rather than
SB> attribute itsTve { xsd:boolean }
FS> there is no specific reason for that, both should work fine.
OK, but the devil is in the details. xsd:boolean permits the values
"true", "false", "1", and "0". It does not permit "yes" (nor "01" nor
"2"). The canonical values are "true" and "false".
> Yes, that's true. We can change that as well.
OK, good. I think it is fine to leave it as is, BTW, but it requires
that we document the heck out of it.
> See in the wiki "The XSLT-based "decoration" approach was pioneered
> by Spritser, a general ITS 1.0 implementation provided by Sebastian
> Rahtz (Oxford University). "
Ah, thanks!
> The translate decorator is a simplified implementation of what
> Spritser offers. It's only advantage: easy of use and a very
> specific use case. One question we have to think about is how to go
> on from here (Christian might remember this ;) ): write more
> decorators (e.g. "within text" decorator), or make more
> documentation about Spritser and replace the Translate decorator
> with it. I think both are fine and are rather a question of time,
> e.g. Sebastians time.
I have no intelligent thoughts on routes forward at this time.
Received on Tuesday, 21 October 2008 18:46:41 UTC