Work on the grouping of resources document has gone on for the last few weeks with significant questions still remaining. Specifically, attempts to devise a generic way to encode the data required to query any look up service has proved difficult, complex, messy, horrible - choose your adjective. As a result, the WG resolved to change the approach.
It will be possible to define a Resource Set in terms of the properties of the resources within in it (e.g. the set of resources that are in the French language) and we'll make it possible to define characteristics of the HTTP Response Headers or body content. However, any look up service will be described in a separate (linked) document that could be written in natural language, WSDL or some other format. The idea is that a look up service operated by an organisation that regularly creates Description Resources, such as trustmark operator, would be at a location repeatedly cited in its DRs. In some ways this is similar to the HTML Profile
Following further discussion of the use case
suggested by Liddy Nevile, the existing Use Cases and Requirements
will be updated. The new use case makes more explicit use of profile matching as well as making a clear distinction between first and third party labelling. The group members whose primary concern is using POWDER for highlighting resources that meet accessibility criteria are taking on this document revision.
Attention then turned to the Description Resources
document. First of all, the group will create a profile document that can be cited in an HTML HEAD tag that defines rel="powder". Our documentation and examples can then point to this. This working group will join others in arguing that HTML Profile should be retained by the HTML 5 Working Group and not deprecated. The forthcoming Technical Plenary has a session on HTML 5 and XHTML 2 and this seems like an ideal opportunity to raise it.
Discussion then turned to the more difficult issue of the HTTP Link Header. Efforts will be made to prove interest in this issue, in particular, by encouraging the re-issue of Mark Nottingham,'s IETF draft
on the subject (or something very much like it). By coincidence, it was being discussed by Mark Nottingham almost simultaneously in the W3C IETF/HTTP WG mailing list
and by him and Dan Connolly on this group's public mailing list
a little later so getting HTTP Link and HTTP Profile headers seems at least possible. However, the group decided that if it proves not to be so, our own suggestion of using HTTP Link headers will move to the (non-normative) primer document, scheduled for publication later this year.
Overall, the group is hoping to have new versions of the Grouping of Resources and Description Resources documents in the public domain by the end of the month and for these to be very close to being completed. The group will review them carefully at the face to face meeting in Boston in November and aim to move them to Last Call immediately afterwards.