The first order of business was to welcome our new Team Contact, Matt Womer. Known to some group members through the Mobile Web Best Practices Group
Matt recently joined W3C from France Telecom's Boston office.
The first agenda item was a decision to define a Resource Set as a sub class of OWL Class rather than an RDFS Class. Andrea Perego took the group through the reasons for this but essentially an OWL Class is more closely defined and can allow closed world logic to be performed.
The RDF properties currently under discussion for the Resource Sets are things like 'hasAnySchemeFrom' and 'hasAnyHostFrom'. Can these be shortened without losing meaning? Probably yes, but should they? A similar discussion has been held recently in Ubiquitous Web
circles and the DDWG
which lead to an action to contact Rhys Lewis to find out more!
The next discussion concerned whether there should be an RDF property 'hasExactQuery'. We already have queryContains (and queryNotContains) but should we have a more definite version as well? It was resolved that yes we should, however, we should also note that, by their very nature, Web pages generated by resolving URIs with query strings are dynamic and that a Resource Set may not therefore be fully defined even using this method.
How should a Resource Set defined by URIs be affected if resolving the URIs leads to a redirection? Should the processor re-calculate whether the resource is or is not a member of the RS or not? The suggestion was made that a 301 9permanent) redirect should be included in the resource set but that other 300 codes should not. This will be discussed further on the mailing list.
Finally the group talked about the forthcoming stakeholder meeting in Washington. The signs are very promising that there will be a co-sponsor for this, however the timing needs to be brought forward to the afternoon of Tuesday 10th July.
It wasn't possible to resolve the outstanding issues and move to first public working draft of the Grouping of Resources document - maybe next week!