Re: Transliteration-only content

Hi all,

thinking in terms of conformance, I think "completely separate data
category" makes most sense. We have currently a very simple description what
"implementing ITS processing" means, see
http://www.w3.org/TR/its/#conformance-product-processing-expectations
[

   -

   *2-1:* A processor MUST
<http://www.w3.org/TR/its/#rfc-keywords>implement at least one data
   category <http://www.w3.org/TR/its/#def-datacat>. For each implemented data
   category <http://www.w3.org/TR/its/#def-datacat>, the following
MUST<http://www.w3.org/TR/its/#rfc-keywords>be taken into account:
   -

      *2-1-1:* processing of at least one selection mechanism
(global<http://www.w3.org/TR/its/#selection-global>or
      local <http://www.w3.org/TR/its/#selection-local>).
      -

      *2-1-2:* the default selections for the data
category<http://www.w3.org/TR/its/#datacategories-defaults-etc>.

      -

      *2-1-3:* the precedence definitions for selections defined in Section
      5.4: Precedence between
Selections<http://www.w3.org/TR/its/#selection-precedence>,
      for the type of selections it processes.
       -

   *2-2:* If an application claims to process ITS markup for the global
   selection mechanism, it MUST
<http://www.w3.org/TR/its/#rfc-keywords>process an XLink
   href <http://www.w3.org/TR/its/#rules.attributes> attribute found on a
   rules <http://www.w3.org/TR/its/#rules> elements.

Statements related to this conformance type
MUST<http://www.w3.org/TR/its/#rfc-keywords>list all data
categories <http://www.w3.org/TR/its/#def-datacat> they implement, and for
each data category <http://www.w3.org/TR/its/#def-datacat> which type of
selection they support.
]

If we add the new attribute to "Translate", this gets messed up. So having
an independent data category will be clearer in terms of separation of
features.

Felix

2011/5/3 Jirka Kosek <jirka@kosek.cz>

> Shaun McCance wrote:
>
> >> Maybe more importantly, it seems also that both values would apply to
> >> 'translatable' text. They really look like additional qualifiers to a
> >> translatable content. I would imagine they could also be just a new
> >> optional attribute in the translateRule data category.
> >
> > That makes sense to me.
>
> But it would then prevent us from having similar local data category. I
> think that this should be
>
> - either completely separate data category
>
> - or we just add new value to translate data category, e.g.
>  its:translate="yes|no|translit-only"
>
>                                Jirka
>
> --
> ------------------------------------------------------------------
>   Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
> ------------------------------------------------------------------
>       Professional XML consulting and training services
>  DocBook customization, custom XSLT/XSL-FO document processing
> ------------------------------------------------------------------
>  OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
> ------------------------------------------------------------------
>
>