RE: [VM] Proposed update to TF description

Hi Tom, all,

A little while ago I updated the PORT page [1] using the OEP page [2] as model, and suggest using a similar layout for VMTF.

[1] http://www.w3.org/2004/03/thes-tf/mission
[2] http://www.w3.org/2001/sw/BestPractices/OEP/

Also the new content you give below is a bit confusing - do the objectives, approach and scope sections describe the objectives/approach/scope of the TF as a whole, or the objective/approach/scope of a specific deliverable (namely the HTTP cookbook)?

Cheers,

Al.

> -----Original Message-----
> From: public-swbp-wg-request@w3.org
> [mailto:public-swbp-wg-request@w3.org]On Behalf Of Thomas Baker
> Sent: 23 November 2005 15:17
> To: SW Best Practices
> Subject: [VM] Proposed update to TF description
> 
> 
> 
> Dear all,
> 
> Since reporting on progress in the VM Task Force [1] I have
> been encouraged to update the VM Task Force Description
> [2] to bring it into line with what we are actually doing.
> 
> I propose to change the description as indicated below.
> Note that the objectives are tightly scoped to work on the
> current Editor's Draft [3].
> 
> Tom
> 
> [1] 
> http://lists.w3.org/Archives/Public/public-swbp-wg/2005Nov/0122.html
> [2] http://www.w3.org/2001/sw/BestPractices/VM/
> [3] 
> http://www.w3.org/2001/sw/BestPractices/VM/http-examples/2005-11-18/
> 
> ----
> 
> Proposed replacement texts for VM Task Force description
> 
>     COORDINATORS
> 
>     * Tom Baker (Goettingen State and University Library)
> 
>     MEMBERS
> 
>     * Libby Miller (Asemantics)
>     * Dan Brickley (W3C)
>     * Alistair Miles (CCL)
>     * Bernard Vatant (Mondeca)
>     * Ralph Swick (W3C)
> 
>     OBJECTIVES
> 
>     1. To define a set of good-practice "recipes" for 
> configuring an Apache
>        server for content negotiation such that:
> 
>       -- If a person tries to dereference the URI of a class or
>          property (i.e. via a Web browser), they end up at
>          the relevant bit of human-readable documentation.
> 
>       -- If a machine tries to dereference the URI of a class
>          or property, they end up with a serialisation of a set of
>          RDF statements describing that class or property, with
>          a provenance that allows differentiation of different
>          'versions' of an RDF schema/ontology.
> 
>       -- The dereferencing solution complies with TAG resolution on
>          httpRange-14 [6].
> 
>     2. To wrap those recipes in enough context to make
>        them usable by vocabulary maintainers to provide
>        documentation and schemas for their vocabularies.
> 
>     APPROACH
> 
>     Based on a comparison of documentation requirements for
>     existing vocabularies such as Dublin Core, SKOS, and FOAF,
>     this note describes a range of good-practice solutions for
>     providing documentation of the vocabularies both in human-
>     and machine-processable form.
> 
>     SCOPE
> 
>     Guidelines for providing documentation about terms in
>     vocabularies (Metadata Element Sets, Thesauri, Ontologies,
>     Published Subjects, and the like).
> 
>     DELIVERABLES
> 
>     A relatively concise technical note describing how to 
>     configure an Apache Web server for content negotiation.
> 
>     DEPENDENCIES (if any)
> 
>     * SKOS (Simple Knowledge Organisation System)
>       <http://www.w3.org/2004/02/skos/>
>     * SWBP Thesaurus Task Force (THES)
>       <http://www.w3.org/2004/03/thes-tf/mission>
>     * TAG decision on httpRange-14
>       <http://lists.w3.org/Archives/Public/www-tag/2005Jun/0039.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 Monday, 28 November 2005 16:40:30 UTC