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

Re: [ACTIOn-275] Generic stand-off elements

From: Felix Sasaki <fsasaki@w3.org>
Date: Wed, 7 Nov 2012 14:16:54 +0100
Message-ID: <CAL58czoJBk1q50OHwkmm8KjwsuhPznAq-hUsftyGLTsavh4xmQ@mail.gmail.com>
To: Yves Savourel <ysavourel@enlaso.com>
Cc: public-multilingualweb-lt@w3.org
Hi Yves, all,

sorry for the delay this causes, but I'm against generalizing to
"standofflist".

>From a consumers perspective I can understand the benefit: have a method
that resolves the references, graps the standoff list(s) and is done.

I'm worried about producers, tools or humans. I am not able to say on the
top of my had what attributes can appear on "item". If I count correctly,
currently it would be seven attributes from provenance, and five from
"quality issue". But if I'm producing an "item" element, can it contain
both? Should a consuming application just pass all attributes or validate
against a schema for item validates against proveance or quality issues?
What does that mean for conformance testing?

All these questions are not needed if there are separate wrapper elements
as in the current draft. Also, your questions a) and b) can be solved by
adding to
http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#html5-markup
a statement that what is said here also relates to standoff markup with
provenance and quality issue, and by renaming the section accordingly.

Again, sorry for the delay this causes.

Best,

Felix


Am 02.11.2012 22:30 schrieb "Yves Savourel" <ysavourel@enlaso.com>:

> Hi all,
>
> I had the action item to summarize the proposal for having common
> stand-off elements that was started here:
>
> http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Oct/0296.html
>
> The idea is to have a single ITS element (e.g. <its:standOffList> but any
> other meaningful name will do), that would be used for all stand-off
> annotations.
>
> It would hold one or more <its:item/> (e.g. or some more meaningful but
> still generic name) where the attributes of the data category being
> specified can be set.
>
>
>
> Here is the example 68
> (
> http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#EX-translation-agent-provenance-html5-local-2
> )
> With the proposed notation:
>
> <!DOCTYPE html>
> <html>
>   <head>
>     <meta charset=utf-8>
>     <title>Test</title>
>     <script id=its-standoff-no-2 type=application/xml>
>       <its:standOffList xml:id="pr1">
>         <its:item
>             transToolRef="http://www.onlinemtex.com/2012/7/25/wsdl/"
>             transOrg="acme-CAT-v2.3"
>             transRevToolRef="http://www.mycat.com/v1.0/download"
>             transRevOrg="acme-CAT-v2.3"
>             provRef="
> http://www.examplelsp.com/excontent987/production/prov/e6354"/>
>       </its:standOffList>
>       <its:standOfflist xml:id="pr2">
>         <its:item
>             transPerson="John Doe"
>             transOrgRef="http://www.legaltrans-ex.com/"
>             transRevPerson="Tommy Atkins"
>             transRevOrgRef="http://www.vistatec.com/"
>             provRef="
> http://www.examplelsp.com/excontent987/legal/prov/e6354
> http://www.vistatec.com/job-12-7-15-X31/reviewed/prov/re8573469"/>
>         <its:item
>             transRevPerson="John Smith"
>             transRevOrgRef="http://john-smith.qa.example.com"/>
>       </its:standOffList>
>     </script>
>   </head>
>   <body>
>     <p its-translation-provenance-records-ref="#pr1"> This paragraph was
> translated from the machine.</p>
>     <p its-translation-provenance-records-ref="#pr2">This text was
> translated directly by a person.</p>
>   </body>
> </html>
>
>
> A side note on HTML5 and stand-off: here the example is not going to work
> (regardless of the element names) because we said that we needed to have a
> single root element per <script>. So:
>
> a) either we need yet another special element (or maybe its:rules can be
> used?) to enclose the two element with xml:id,
>
> or b) we put each standOffList in a separate <script>, and duplicate the
> xml:id of the list in the id of the <script>. Since the ID in the <script>
> section are technically a different document (i.e. it will produce a
> separate DOM, this shold be OK, no?
>
>
> Cheers,
> -yves
>
>
>
>
Received on Wednesday, 7 November 2012 13:17:24 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:25:03 UTC