[VM] Telecon agenda - Tue 2006-01-17 1400 UTC

SWBPD VM 2006-01-17 telecon agenda

Tuesday, 14:00 UTC (15:00 Berlin)
Zakim: +1.617.761.6200
Conference code 8683# ('VMTF')

Recent telecons
-- 2006-01-10: http://lists.w3.org/Archives/Public/public-swbp-wg/2006Jan/0005.html

Next telecons (weekly) - note change of time:
-- 2005-01-24 Tue 1500 UTC http://www.w3.org/Guide/1998/08/teleconference-calendar#D20060124
-- 2005-01-31 Tue 1500 UTC http://www.w3.org/Guide/1998/08/teleconference-calendar#D20060131


1. Editor's Draft "HTTP configuration cookbook"

   On Jan 10, we decided that between now and end of January
   we would discuss reviewer comments and formulate responses
   to reviewers on the list.  BPDWG will probably be extended
   by three months, so there will be an opportunity to make
   revisions.  We want to go for "note" status [4] within the 
   charter period for the BPD working group.

   1.1. Name of the cookbook

        -- Best Practices for Serving RDFS and OWL Vocabularies?
           Best Practice Recipes for Serving RDFS and OWL Vocabularies?
           Does the "recipe" metaphor translate well?

        -- RDFS and OWL Cookbook: Best Practice Recipes for Serving Vocabularies?

2. Responses to reviews

   1.1. David Booth review
        -- Global suggestions
           G1. To discuss trade-offs between hash and slash URIs
               Response: Ralph has addressed this with added text in the

           G2. To avoid purl.org recipes, which violate TAG resolution 
               with 302 redirect code.
               Response: In the Jan 10 telecon, the TF felt this issue
               should be addressed somewhere, as purl.org is used by DC
               and RSS.  We thought the problem should be described in the
               body of the paper, with some detail in an appendix.  See

               Since then, Ralph has has second thoughts;
               he now thinks the importance of persistence of URIs should be
               emphasized but without citing purl.org, and that we should
               work with DC and RSS to solve that, but independently of cookbook.

        -- Specific recipes
           Recipe 3.  Interpretation of a fragment identifier in the
                      presence of 303 redirects is unclear, so recipe
                      should note that browser may or may not apply
                      fragment identifier to secondary URI.

        -- Editorial suggestions
           E1. Shorter URIs in the examples would be better.
               Alistair would rather leave the longer URIs for now because
               a UK server is configured to support them, see
               Ralph suggests using w3c URIs in the final version (with
               shorter URIs for the examples).

           E2. At the beginning of each recipe, say what the URIs would return.

               Alistair proposes to illustrate this graphically, so added images
               David Booth actually intended simply to spell out which URIs
               are redirected to.  Ralph wonders whether the images really add any
               new information.

   1.2. Andreas Harth review
        -- The document has too many choices - suggests
           cutting down to 3 or 4 covering 80% of the cases.
        -- Suggests content negotiation instead of mod_rewrite
        -- Suggests mod_alias instead of mod_rewrite.
        -- Maybe put purl.org examples into an appendix.

3. TAG httpRange-14 decision [10]

   There have been recent comments on the list about the TAG
   decision by David Booth: [11] summarizing best practice
   issues around the decision, [12] on minting http URIs,
   and [13] on 302 versus 303 redirects; by David Wood: [15]
   with a use case for RDF; and and by Jacco van Ossenbruggen
   [14], reviewing the comments by David Wood and David Booth.

   In BPD, the idea arose to write a TAG-like "finding"
   to explain the impact of the httpRange-14 decision.
   David Booth and David Wood wrote drafts independently.
   Probably not enough time in BPD to start a new document,
   so could they be incorporated into cookbook?  David Booth
   agreed to go to propose a short section for us to consider.
   General agreement that we should avoid getting too
   historical -- just cover practical results.  Some of
   what David Booth has written could plausibly be recast
   as introductory material on how to choose reasonable
   namespace names.

4. Testing
   ACTION: Ralph to test recipes with W3C configuration.

[10] http://lists.w3.org/Archives/Public/www-tag/2005Jun/0039.html
[11] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Dec/0055.html
[12] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Dec/0056.html
[13] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Dec/0123.html
[14] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Dec/0085.html
[15] http://lists.w3.org/Archives/Public/public-swbp-wg/2005Sep/0010.html

Dr. Thomas Baker                      baker@sub.uni-goettingen.de
SUB - Goettingen State                            +49-551-39-3883
and University Library                           +49-30-8109-9027
Papendiek 14, 37073 Göttingen

Received on Tuesday, 17 January 2006 12:32:09 UTC