This is an archive of an inactive wiki and cannot be modified.

Note: This wiki page has now been superseded by a list of Open Recipes Issues maintained on the SWD issues tracker.

Best Practice Recipes Issues

This page contains a list of issues related to the "Best Practice Recipes for Publishing RDF Vocabularies" deliverable

This document is structured as follows:


Contents:


Current Working Draft

W3C Working Draft 14 March 2006


Submitting new issues

Anyone can submit a new issue for consideration. Please see the IssuesProcess page for a description of the process and instructions for submitting new issues.


Overview of issues

Issue

Source

Date

Status

Owner

COOKBOOK-I1.1-Apache configuration

W3C Working Draft 14 March 2006

14 Mar 2006

Resolved

DiegoBerrueta

COOKBOOK-I1.2-Extended configuration

W3C Working Draft 14 March 2006

14 Mar 2006

Closed

COOKBOOK-I1.3-Default behavior

W3C Working Draft 14 March 2006

14 Mar 2006

Open

RalphSwick

COOKBOOK-I1.4-Recipe 6 Incomplete

W3C Working Draft 14 March 2006

14 Mar 2006

Open

DiegoBerrueta

COOKBOOK-I2.0-QA Review comments from Karl Dubost

QA review issues carried over from SW BPD

12 May 2006

Open

JonPhipps

COOKBOOK-I2.1-Should supply a general server configuration template

QA Review issues carried over from SW BPD

12 May 2006

Open

RalphSwick

COOKBOOK-I3.1-Serving the most current snapshot

Serving multiple snapshots

16 Jan 2007

Raised

COOKBOOK-I3.2-Online server testing

unit tests

16 Jan 2007

Open

DiegoBerrueta

COOKBOOK-I3.3-mod_rewrite required

unit tests

11 Dec 2006

Open

JonPhipps

STATUS Vocabulary

RAISED

Submitted, but not currently being discussed.

OPEN

Actively being worked on.

PENDING

Activity suspended, perhaps until some other controlling issue is resolved.

POSTPONED

Activity suspended. Will not be resolved by this working group. Left for the next revision.

CLOSED

Resolved.

SUBSUMED-BY uid

Allows some freedom in clearing up sets of issues.


Detailed Issues

ToDo's from the current draft

COOKBOOK-I1.1-Apache configuration

Name

COOKBOOK-I1.1 Apache configuration

Description

Verify minimal required overrides.

Raised By

WD editors

Date

14 Mar 2006.

Status

Resolved

Owner

DiegoBerrueta

Resolution

Action on Jon to remove the line starting with "@@TODO" from the "Apache configuration" section of the cookbook working draft

Reference(s)

W3C Working Draft 14 March 2006

Recipes -- working on issue COOKBOOK-I1.1

Proposed resolution by DiegoBerrueta on 12 Jan 2006.

COOKBOOK-I1.2-Extended configuration

Name

COOKBOOK-I1.2 Extended configuration

Description

If you are using a slash namespace and want to provide both RDF and HTML content, where the HTML content is served as individual hyperlinked documents for each class or property, and where the RDF is served as bounded descriptions of each class or property, see recipe 6 (@@TODO).

Raised By

WD editors

Date

14 Mar 2006.

Status

Closed

Owner

JonPhipps

Resolution

Action on Jon to remove the "@TODO" from "Extended Configuration" since this issue is effectively the same as COOKBOOK-I1.4-Recipe 6 Incomplete

Reference(s)

Extended configuration

COOKBOOK-I1.3-Default behavior

Name

COOKBOOK-I1.3 Default behavior

Description

Performing content negotiation based on the value of the 'User-agent:' header field is not generally considered good practice, @@TODO why.

Raised By

WD editors

Date

14 Mar 2006.

Status

Open

Owner

RalphSwick

Resolution

Action on Ralph to write brief description of how UA-based negotiation limits the creation of new User Agents in the future, citing past negative experience.

Reference(s)

Default behavior

COOKBOOK-I1.4-Recipe 6 Incomplete

Name

COOKBOOK-I1.4 Recipe 6 Incomplete

Description

@@TODO this recipe is included as a placeholder, as its best practice implementation currently requires further investigation, discussion and testing, but is anticipated to be an important part of this document, 'completing the set' of the most commonly needed configurations.

Raised By

WD editors

Date

14 Mar 2006.

Status

Open

Owner

DiegoBerrueta

Resolution

Action on Diego to perform "further investigation, discussion and testing" and write a first draft of the recipe

Reference(s)

Recipe 6

Historical from SWBPD

COOKBOOK-I2.0-QA Review comments from Karl Dubost

Name

COOKBOOK-I2.0-QA Review comments from Karl Dubost

Description

In May 2006, Karl Dubost posted a series of comments and suggestions about the Recipes draft to the Semantic Web Best Practice and Deployment Working Group mailing list.

Raised By

Karl Dubost

Date

12 May 2006.

Status

Open

Owner

JonPhipps

Resolution

Action on Jon to implement the specific QA suggestions in the draft and provide feedback to Karl

Reference(s)

QA Review issues carried over from SW BPD

COOKBOOK-I2.1-Should supply a general server configuration template

Name

COOKBOOK-I2.1-Should_supply a general server configuration template

Description

The Recipes are specific to an Apache server, but may be applicable in non-Apache environments. It would be useful to provide a general-purpose configuration template for use by people setting up non-Apache servers"
...here there's a good opportunity to create a template and/or invite people to submit bindings to the Mailing List, id est how people applied this recipe in this particular server environment, Web Apps Framework, HTTP Servers only, etc. That would help other people to find the information. With a proposed template, it would help people to collect, gather the information.

Raised By

Karl Dubost

Date

12 May 2006.

Status

Open

Owner

RalphSwick

Resolution

Action on Ralph to provide a wiki page and suggest a methodology for submitting non-Apache alternative recipes. We won't provide a general-purpose template beyond the existing recipes.

Reference(s)

QA Review issues carried over from SW BPD

Issues raised by the current editors

COOKBOOK-I3.1-Serving the most current snapshot

Name

COOKBOOK-I3.1 Serving the most current snapshot

Description

There is a brief discussion in the Extended Requirements about differentiating between versions (E2), and the recipes discuss creating and serving a 'snapshot' of the vocabulary. But there is no discussion regarding the use of naming conventions and redirects to serve the most current snapshot of a vocabulary.

Raised By

JonPhipps

Date

16 Jan 2007.

Status

Raised

Owner

Resolution

This should probably contain a pointer to the 3.1 "Basic Principles for Managing an RDF Vocabulary" Deliverable

Reference(s)

Serving multiple snapshots

COOKBOOK-I3.2-Online server testing

Name

COOKBOOK-I3.2-Online server testing

Description

The recipes provide example URIs and example responses. Diego has written some httpUnit tests and it would be very useful to make these available online to provide a server validation service.

Raised By

JonPhipps

Date

16 Jan 2007.

Status

Raised

Owner

DiegoBerrueta

Resolution

Action on Diego to provide a timeline for implementing a public service.

Reference(s)

http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0048.html

COOKBOOK-I3.3-mod_rewrite required

Name

COOKBOOK-I3.3-mod_rewrite required

Description

Apache configuration should add that mod_rewrite must be loaded and enabled

Raised By

DiegoBerrueta

Date

11 Dec 2006.

Status

Open

Owner

JonPhipps

Resolution

Action on Jon to add this to the doc. Ralph suggests perhaps supplying instructions on how to implement mod_rewrite.

Reference(s)

http://lists.w3.org/Archives/Public/public-swd-wg/2006Dec/0048.html

Related discussions

From current mail list

From the web

From W3C Face-to-Face Meeting

CategoryRecipes

I should note (with gratitude) that this structure has been "modeled" (more-or-less completely copied) after the excellent OWL issues page -- JonPhipps 2007-01-01 18:57:44