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

Hi Felix, Phil, all,

> <html xmlns="http://www.w3.org/1999/xhtml">...
> <script type="application/xml" id="its-standoff-1">
>   &lt;its:locQualityIssues xml:id="lq1" xmlns:its="
> http://www.w3.org/2005/11/its"&gt;
>    &lt;its:locQualityIssue
>     locQualityIssueType="misspelling"
>     locQualityIssueComment="'c'es' is unknown. Could be 'c'est'"
>     locQualityIssueSeverity="50"/&gt;
>    &lt;its:locQualityIssue
>     locQualityIssueType="typographical"
>     locQualityIssueComment="Sentence without capitalization"
>     locQualityIssueSeverity="30"/&gt;
>   &lt;/its:locQualityIssues&gt;
> </script>...</html>

I'm looking at how this new encapsulation of the stand-off localization quality issues (or how global rules in Pedro's case) could be used within <script> and I have the following two notes to start:

-- a) script type:

We need a way to specify the content of the script is ITS. I don't think it's reasonable to expect ITS processors to just try any script content.

It seems the type attribute must be a valid MIME type. Maybe this is the occasion to use the ITS MIME type we've defined long ago?
Actually I can't recall exactly what its status is, but if it's not accepted yet we should push it forward. See http://lists.w3.org/Archives/Public/public-i18n-its-ig/2011Dec/0000.html for the latest news about it.


-- b) src

The content of the script can be in an external file. I assume we should not use this for ITS content. Is that right? For linked rules we have the link element. We need to make it clear in the specification then.


Cheers,
-yves

Received on Monday, 8 October 2012 17:36:21 UTC