W3C home > Mailing lists > Public > public-wai-ert@w3.org > August 2006

Re: Use of dc:language in test subject?

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Thu, 31 Aug 2006 21:58:57 +0200
Message-ID: <44F73F81.5010700@w3.org>
To: Nils Ulltveit-Moe <nils@u-moe.no>
Cc: public-wai-ert@w3.org

Hi Nils,

If I understand correctly, you want to filter the language from the Web resource (the test subject) and duplicate this information within the EARL report to improve query performance.

Your initial question was whether the WG is considering adopting a property for this use case. The answer to this question is not at this time. However, I am curious if the WG participants see a need for such a property in the core EARL vocabulary.

Meanwhile, I think one way to do this would be to use the dc:language property within the test subject as you initially pointed out. Since this is redundant information, you will not break anything. At the same time, you can not expect other tools outside your application to process or provide this type of information. Here is a simple example for this application-specific extension:

    <!--// core earl:WebContent properties //-->
    <dc:title xml:lang="en">Page 1</dc:title>
    <dc:location rdf:resource="http://example.org/page1.html"/>
    <dc:format rdf:parseType="Literal">text/HTML</dc:format>
    <!--// application specific properties //-->
    <dc:language rdf:parseType="Literal">fr</dc:format>

Another way to approach this would be to rely on the content-language information provided by the server instead of processing the Web resource itself. This information could be easily recorded in the http:content-language property of the HTTPresponse in a Web Content class. I am not sure how consistent and accurate this information usually is though.


Nils Ulltveit-Moe wrote:
> Hash: SHA1
> Hi Shadi,
> We can probably use the lang attribute to the earl:TestSubject.
> The use case is that our pool of assessment modules parse the (X)HTML
> pages that we want to perform automatic assessments on. We would like
> harvest information about the content language of the page being
> assessed for statistical analysis in a data warehouse, and we would like
> to utilise the fact that the assessment module already had this
> information available.
> Best regards,
> Nils
> Shadi Abou-Zahra wrote:
>> Right. I bow before you humbly. ;)
>> The correct way would be to do this in the dc:description of the
>> earl:TestSubject instance that is referenced by the earl:subject
>> property. Here is a better example that shows both methods:
>> <earl:subject>
>>  <earl:TestSubject>
>>    <dc:title xml:lang="en">left nav bar</dc:title>
>>    <dc:description rdf:parseType="Literal"><![CDATA[<xhtml xml:lang="fr"
>> ...>...</xhtml>]]></dc:description>
>>  </earl:TestSubject>
>> </earl:subject>
>> Still, I do not see a use case for dc:language. Correct?
>> Best,
>>  Shadi
>> Johannes Koch wrote:
>>> Shadi Abou-Zahra wrote:
>>>> What about using the xml:lang attribute on the RDF nodes (for example
>>>> <earl:subject xml:lang="fr" .../>)?
>>>> Or even better, when possible, within the content itself. For example
>>>> <earl:subject><![CDATA[<xhtml xml:lang="fr"
>>>> ...>...</xhtml>]]></earl:subject>.
>>> The object for earl:subject is not defined to be a Literal. It must be
>>> an earl:TestSubject.
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> iD8DBQFE9zO8+uAhaUHEvIoRAuGNAJ9H/7w/hU8bXoPpWwQ5LNCombKO7QCglP6U
> ZtRJB1M+mWT33FgeEVtTUgY=
> =44h+

Shadi Abou-Zahra     Web Accessibility Specialist for Europe | 
Chair & Staff Contact for the Evaluation and Repair Tools WG | 
World Wide Web Consortium (W3C)           http://www.w3.org/ | 
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ | 
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ | 
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ | 
2004, Route des Lucioles - 06560,  Sophia-Antipolis - France | 
Voice: +33(0)4 92 38 50 64          Fax: +33(0)4 92 38 78 22 | 
Received on Thursday, 31 August 2006 19:59:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:54 UTC