Re: Other comments on EARL 1.0 Schema (editor's draft)

Hi Shadi,

On Tue, 12 Apr 2011 09:48:55 +0200, Shadi Abou-Zahra <shadi@w3.org> wrote:
> Hi Christophe,
> 
> Thank you for your comments, they have been added to the issues list:
>   - <http://www.w3.org/WAI/ER/EARL10/issues>
> 
> Please find below some initial responses:
> 
> 
> On 8.4.2011 16:03, Christophe Strobbe wrote:
>> Dear ERT WG,
>>
>> Below are a few non-editorial comments on EARL 1.0 Schema (editor's
draft
>> <http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Schema-20090908>).
>>
>> 1.1 Audience
>> (...)
> 
> Agree, this wording should be improved.
> 
> 
>> 2.2 Assertor class
>> Example 6: Bob using Cool Tool
>> The tool is identified by means of foaf:member:<foaf:member
>> rdf:resource="http://www.example.org/tool/#cool"/>
>> but foaf:member<http://xmlns.com/foaf/spec/#term_member>  does not seem
>> to
>> cover software. Could earl:Software be used here instead?
> 
> In RDF this means that "Cool Tool" is both an earl:Software (as per 
> example 5) and a foaf:Agent (because of the range of foaf:member).
> 
> It makes sense to identify the Software as an Agent in this case, so the

> example is semantically correct. Actually the group has previously 
> discussed making earl:Software a sub-class of foaf:Agent but decided 
> this may not be the case when the software is used as a test subject.
> 
> Having said all that, I agree that this example could be clarified or 
> changed to avoid confusion between RDF semantics and XML syntax...
> 

Thanks. I understand it better now.


> 
>> 2.3. TestSubject Class
>> How should EARL implementors identify a document that is not available
on
>> the internet? foaf:document does not seem to have an ID-like property.
>> Some
>> document formats, e.g. DAISY, get an automatically generated ID when
they
>> are created, but others, e.g. the OpenDocument Format, don't have an
ID.
>> In
>> ODF, it is possible to embed the EARL document in the ODF/ZIP format.
Can
>> this method be used instead of an ID?
> 
> RDF uses URIs to identify resources. A local file could have a local URI

> such as "file:///C:/myfiles/myfile.odf".

So assuming that urn:dtb:be-kuleuven-dtb20110424-001 (see
<http://www.niso.org/workrooms/daisy/Z39-86-2005.html#PkgId>) is a correct
URN, the following snippet

<earl:TestSubject rdf:about="urn:dtb:be-kuleuven-dtb20110424-001">
  <dct:title xml:lang="en">Producing DAISY Books for Students with
Dyslexia at K.U.Leuven</dct:title>
</earl:TestSubject>

would be a correct TestSubject (in this case, representing a DAISY book
with the ID be-kuleuven-dtb20110424-001).

> 
> Does this answer your question?
> 

I think so.


> 
>> 2.4. TestCriterion Class
>> The examples in this section rely on publicly available criteria. What
if
>> you use criteria that are only available inside an organisation and
that
>> are not necessarily retrievable through HTTP?
> 
> Again, the basis of EARL is URI, which supports protocols other than 
> HTTP (including proprietary ones if needed). The group had previously 
> decided that resources that cannot be represented by URIs are out of 
> scope of EARL. Do you have a specific scenario in mind?
> 

I think it is possible to generate URNs for internal criteria, so that
should answer my question.

Best regards,

Christophe



> Thanks,
>    Shadi
> 
> 
>> Best regards,
>>
>> Christophe
>>

-- 
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51 
www.docarch.be
Twitter: @RabelaisA11y

Received on Wednesday, 13 April 2011 15:15:39 UTC