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

Re: [ACTION-256]: Compile and circulate itsTool examples togehter with proposal text

From: Dave Lewis <dave.lewis@cs.tcd.ie>
Date: Wed, 07 Nov 2012 11:16:43 +0000
Message-ID: <509A431B.3040003@cs.tcd.ie>
To: Jirka Kosek <jirka@kosek.cz>
CC: Felix Sasaki <fsasaki@w3.org>, "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
Hi Jirka,
Thanks for that.

So to check, does the solution suggested by Yves, i.e. reflecting the 
toolInfo id in the script id,
and only having one toolInfo element per script as discussed in.
solve this problem?


On 05/11/2012 15:59, Jirka Kosek wrote:
> On 2.11.2012 14:29, Dave Lewis wrote:
>> For HTML this works when the tool info is external to the file. However,
>> it doesn't work when the tool information is held with the file. Here we
>> could use the XML in htm:script element solution that we use for mark-up
>> in some of the data categories (e.g. Quality Issue). In this case we
>> would need to specify in the spec the element type the IRI refers to.
>> So we would need the following wording:
>> "Where the IRI in not used in a its:toolRefs attribute in an XML
>> document or not for pointing to an external resource in a its-tool-refs
>> attributed in a HTML document, then it MUST refer to a its:toolInfo
>> element."
> This is not technically possible. In HTML its:toolInfo inside <script>
> element and is not exposed as a markup, it's just plain text inside
> <script> which doesn't have ID and can't be directly addressed.
> 			Jirka
Received on Wednesday, 7 November 2012 11:17:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:08:24 UTC