Re: Fixing dc:location issue with earl:Locator class

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Shadi,

This sounds like a good idea, since it would provide a flexible pointing
mechanism.

Kind regards,
Nils

Shadi Abou-Zahra wrote:
> 
> Hi,
> 
> As CarlosI raised in a previous mail [1], the dc:location property is
> not really defined by DC. We need to define an equivalent earl:location
> to describe a URI location.
> 
> At the same time, we agreed to develop an earl:Locator class that
> describe the occurrence of the result within the test subject. This
> class is to be a stub for several types of pointers such as XPointer,
> XPath, line/column numbers, byte offset, etc.
> 
> It occurs to me that this earl:Locator class should also have an
> earl:URI property. This would allow us to reuse the Locator to describe
> the test subject itself. Here an example:
> 
> <earl:Assertion rdf:ID="someID">
>  <earl:subject>
>    <earl:location>
>      <!--// this is the location of the subject //-->
>      <earl:URI rdf:resource="http://example.org" />
>    </earl:location>
>    <!--// other earl:subject properties //-->
>  </earl:subject>
>  <earl:result>
>    <earl:location>
>      <!--// this is the location of the result //-->
>      <earl:line>23</earl:line>
>      <earl:column>5</earl:column>
>      <!--// more pointers if available //-->
>    </earl:location>
>    <!--// other earl:result properties //-->
>  </earl:result>
>  <!--// rest of the earl:assertion properties //-->
> </earl:Assertion>
> 
> Thinking even further, the proposed earl:range/earl:scope (we should
> find a good name for this!) could be a further value type for the
> earl:Locator class.
> 
> Any issues with this approach?
> 
> Regards,
>  Shadi
> [1] <http://lists.w3.org/Archives/Public/public-wai-ert/2006Jan/0025>
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD9bUs+uAhaUHEvIoRAkz3AKCKOcIufiD7EgCxu6gl0rzbHQHuCQCfR/WM
M3lyvlDCEx/QzgZ2ygFah/o=
=7V4Z
-----END PGP SIGNATURE-----

Received on Friday, 17 February 2006 10:36:21 UTC