This was the first conference call the group has had for a couple of weeks and a lot was discussed.
First of all it was agreed that a POWDER processor MUST understand and process POWDER and MAY do this by processing POWDER-S. Publishing POWDER-S is, of course possible, however, this should be done with caution since its processing requires understanding the semantic extensions (i.e. although it's valid RDF/OWL it doesn't mean as much if you don't implement the extensions mapping strings to URIs etc.) Publishing POWDER-S directly may not therefore have the desired semantics.
The group then spent time looking at the Primer which, it is strongly hoped, will be published as a first working draft at the end of this month. There was some discussion following comments made on the public list [1 2
] and a new internal draft is in preparation. The group is looking into whether it might be appropriate (and helpful) to include examples of using real world vocabularies (to describe fictitious Web sites), e.g. Dublin Core
, Creative Commons
etc. Those examples are all non-profit - would it be appropriate to give examples using commercial vocabularies such as (WG members) Technosite
There was a brief look at the HTTP Link issue which is raging on the TAG mailing list
The group was pleased to welcome Tim Boland of NIST
to its membership. Tim brings a wide range of skills, experiences and interests to the group from fields including XML technologies, Quality Assurance and Accessibility.
For this meeting, we were also joined by Eric Eric Prud'hommeaux
who offered further advice on the issue of IRI canonicalisation. This is clearly a many-faceted topic. IRIs are defined, IRI -> URI is defined, HTML form encoding is defined and so on, but where is it appropriate to use each? It seems that the POWDER approach is likely to end up suggesting that processors make a 'best effort' to canonicalise IRIs within the context in which they operate - and this may lead to false negatives. The group is grateful to Eric for offering to continue supporting this aspect of our work.
Finally, an important Resolution was passed, congratulating Andrea Perego and his wife, Barbara, on the birth of their son Alessandro!