W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > October 2012

Re: ACTION-233: Update quality issue example to use the solution (XML in "script" tag) for standoff markup

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 9 Oct 2012 15:37:37 +0200
Message-ID: <CAL58czqEgk4P+ARgA6LUmW0ZBVS-te4fuvzD6LpeSqdCDUTQpA@mail.gmail.com>
To: Mauricio del Olmo <mauricio.delolmo@linguaserve.com>
Cc: public-multilingualweb-lt@w3.org
Dear Mauricio,

somehow your mail did not reach the list, so I am forwarding it here.

>From what you say below it seems that Linguaserve doesn't have the use case
of "script containing ITS global rules" anymore.

So just to see priorities: who would need script for
1) ITS Rules inside HTML5
2) other ITS markup, e.g. standoff quality issue markup

If nobody has the need for 2), I would revert the example at
http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#EX-locQualityIssue-html5-local-2
see
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Oct/0089.html
But it would also mean that the schema for ITS+HTML5 would need the
standoff attributes. Thoughts?

- Felix

2012/10/9 Mauricio del Olmo <mauricio.delolmo@linguaserve.com>

> Hi, Felix.****
>
> ** **
>
> With regards to this subject, I’ve sent an email to the public WG account (
> public-multilingualweb-lt@w3.org) today updating the approach we are
> going to use in our implementation (Drupal XML with embedded HTML content
> instead of HTML 5).****
>
> ** **
>
> This is what I’ve said:****
>
> ** **
>
> Hello all.****
>
> ** **
>
> I’ve updated the use case in the Wiki because it was outdated. In
> agreement with Cocomore in Prague we decided to change the interchange
> format from HTML 5 to XML exported from Drupal. Sorry for the confusion
> caused from it.****
>
> Instead we’ll have HTML fragments inside XML CDATA nodes and the global
> ITS rules will be in the XML. In the HTML content only will be local rules.
> ****
>
> ** **
>
> This is the new, but not definitive, text:****
>
>
> http://www.w3.org/International/multilingualweb/lt/wiki/LSP_Localization_Chain_Side_Use_Case_Demonstration
> ****
>
> Once we have a more stable implementation, we’ll provide xml examples and
> use of the metadata. By TPAC in Lyon this will be a more stable and close
> to the final implementation version.****
>
> ** **
>
> We have dropped the “Progress Indicator” metadata also.****
>
> ** **
>
> Thank you and sorry again.****
>
> ** **
>
> Regards.****
>
> *__________________________________*
>
> *Mauricio del Olmo Martínez*
>
> *Dpto. Técnico/I+D+i*
>
> *Linguaserve Internacionalización de Servicios, S.A.*
>
> *Tel.: +34 91 761 64 60 ext. 0421
> Fax: +34 91 542 89 28 *
>
> *E-mail: **tecnico@linguaserve.com***
>
> *www.linguaserve.com*
>
> * *
>
> *«En cumplimiento con lo previsto con los artículos 21 y 22 de la Ley
> 34/2002, de 11 de julio, de Servicios de la Sociedad de Información y
> Comercio Electrónico, le informamos que procederemos al archivo y
> tratamiento de sus datos exclusivamente con fines de promoción de los
> productos y servicios ofrecidos por LINGUASERVE INTERNACIONALIZACIÓN DE
> SERVICIOS, S.A. En caso de que Vdes. no deseen que procedamos al archivo y
> tratamiento de los datos proporcionados, o no deseen recibir comunicaciones
> comerciales sobre los productos y servicios ofrecidos, comuníquenoslo a
> clients@linguaserve.com, y su petición será inmediatamente cumplida.»*
>
> * *
>
> *"According to the provisions set forth in articles 21 and 22 of Law
> 34/2002 of July 11 regarding Information Society and eCommerce Services, we
> will store and use your personal data with the sole purpose of marketing
> the products and services offered by LINGUASERVE INTERNACIONALIZACIÓN DE
> SERVICIOS, S.A. If you do not wish your personal data to be stored and
> handled, or you do not wish to receive further information regarding
> products and services offered by our company, please e-mail us to
> clients@linguaserve.com. Your request will be processed immediately.”*
>
> *__________________________________*
>
> ** **
> ------------------------------
>
> *From: *Felix Sasaki <fsasaki@w3.org> ****
>
> *Date: *Tue, 9 Oct 2012 09:08:16 +0200****
>
> *To: *pedro.diez<pedro.diez@linguaserve.com>****
>
> *Cc: *David Lewis<dave.lewis@cs.tcd.ie>; David.Filip<David.Filip@ul.ie>***
> *
>
> *Subject: *Re: ACTION-233: Update quality issue example to use the
> solution (XML in "script" tag) for standoff markup****
>
> ** **
>
> Hi Pedro (offline, only to co-chairs),****
>
> ** **
>
> in Prague Linguaserve emphasized the need to put ITS Rules inside HTML.
> Linguaserve's current solution****
>
> ** **
>
>
> https://www.w3.org/International/multilingualweb/lt/wiki/LSP_Localization_Chain_Side_Use_Case_Demonstration
> ****
>
> ** **
>
> is not valid HTML. This thread is about an alternative: to put ITS rules
> into the "script" element. Can your guys look into this and reply to the
> thread on the list whether this works for them?****
>
> ** **
>
> Thanks a lot in advance,****
>
> ** **
>
> Felix****
>
> 2012/10/9 Yves Savourel <ysavourel@enlaso.com>****
>
> Hi all,
>
> I've tried to implement the global rules in <script> as we discussed.
>
> It is certainly looking like a hack, and I think to make it really work
> we'll have to have a few processing expectations. For example:
>
> -- 1) As already mentioned: the type of the script would be set to the ITS
> MIME Type (application/its+xml)
>
> -- 2) There should be only one root element in the script. That is we
> shouldn't have two <its:rules> element one after the other. It's too
> complicated to deal with more.
> So if one wanted to have several its:rules, just use several <script>
> element.
> Same for the stand-off localization quality issue (if we end up using that
> hack for that too).
>
> -- 3) Someone very smart should come up with a description of how exactly
> the ITS markup MUST be encapsulated in the script content, so:
>  a) it respects the restriction for content of script (
> http://dev.w3.org/html5/spec/single-page.html#restrictions-for-contents-of-script-elements
> )
>  b) ITS tools can obtain the XML string out of that content in a unique
> and simple way.
>
> I'm using comments to encapsulate the code for now, instead of escaping
> the content. I think this is where we need to have a single way to do
> things.
>
> For the localization quality issues (if we use ,script> for that). I
> assume we could set the id of the script to the same id value defined in
> the <its:locQualityIssues> element, that way, the element referring to the
> stand-off markup could point directly to the proper script element.
>
>
> If anyone wants to try it out (like with the example pasted at the end of
> this email), I've posted the latest snapshot of Okapi that implements this
> here: http://okapi.opentag.com/snapshots/
> For the source code, look the compileRulesInScripts() method here:
>
> http://code.google.com/p/okapi/source/browse/okapi/filters/its/src/main/java/org/w3c/its/ITSEngine.java?name=dev
>
>
> cheers
> -yves
>
> --- example:
>
> <!DOCTYPE html>
> <html lang="en">
>   <head>
>     <meta charset="utf-8">
>     <title>Title</title>
>     <script type="application/its+xml">
>     <!--
> <its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"
>   xmlns:h="http://www.w3.org/1999/xhtml">
>  <its:translateRule translate="no" selector="//h:code"/>
> </its:rules>
>     -->
>     </script>
>     <script type="application/its+xml">
>     <!--
> <its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"
>   xmlns:h="http://www.w3.org/1999/xhtml">
>  <its:translateRule translate="yes" selector="//h:code"/>
>  <its:translateRule translate="no" selector="//h:b"/>
> </its:rules>
>     -->
>     </script>
>   </head>
>   <body>
>     <p>Text with <code>code</code> and <b>bold</b>.</p>
>   </body>
> </html>
>
>
> ****
>
>
>
> ****
>
> ** **
>
> --
> Felix Sasaki****
>
> DFKI / W3C Fellow****
>
> ** **
>



-- 
Felix Sasaki
DFKI / W3C Fellow
Received on Tuesday, 9 October 2012 13:38:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:55 UTC