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

RE: Action Item: WCL URI matching

From: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
Date: Wed, 19 Jul 2006 14:47:02 +0200
Message-ID: <09700B613C4DD84FA9F2FEA521882819012DA4D9@ayalga.fundacionctic.org>
To: "Johannes Koch" <johannes.koch@fit.fraunhofer.de>, <public-wai-ert@w3.org>

 

> >>>Additionally the XG has requirements on scheme, port, query
> >>
> >>and fragment patterns, but as CarlosV noted in the past there are 
> >>other options, frequently used by crawler tools (e.g.
> >>path depth limits), that are not covered with the current 
> >>requirements.
> >>
> >>AFAIR, there should be a way to compress statements in an 
> EARL report, 
> >>so that not every resource/web unit has to be listed 
> explicitly. This 
> >>compression is most likely not lossless. I very much doubt 
> that we can 
> >>create a lossless compression. There are too many 
> parameters. And what 
> >>would be the benefit? If we wanted to know whether a 
> specific resource 
> >>is part of the subject of the compressed statement, we 
> would have to 
> >>run a crawler with all the specified parameters first? Hmm
> > 
> > AFAIR, this has something to do with semantics (logical groups of
> > resources) and not only compression.
> 
> I can group resources by listing them explicitly, or I can 
> compress this by using some shorter form (regexp or WCL/matching).

Obviously you can group resources just as a list, but then you will lose
the semantics of the group (i.e why you have grouped all them together).
If you want to keep explicit information and add semantic information,
you can combine the explicit list of resources with a WCL/matching.

CI.
Received on Wednesday, 19 July 2006 12:47:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:27 GMT