[contents]

About This Document

This pages captures outstanding issues in the HTTP Vocabulary in RDF Working Draft of 20 December 2006. The Evaluation and Repair Tools Working Group (ERT WG) intends to address these issues in future updates of the working draft. Please send comments and feedback to the the mailing list of the ERT WG. The archives for this list are publicly available. This document is an on-going work in progress and is subject to change at any time without advance notice.

Table of Contents

1. Introduction
   • 1.1. Namespaces
   • 1.2. Use Cases
2. Basic HTTP 1.1 (RFC 2616)
   • 2.1. Request Class
   • 2.2. Response Class
   • 2.3. Header Properties
     • 2.3.1. Request Headers
     • 2.3.2. Response Headers
     • 2.3.3. Unbound Headers
   • 2.4. Body Property
   • 2.5. URI Property
3. Header Extensions (RFC 4229)
   • 3.1. Request Extensions
   • 3.2. Response Extensions
   • 3.3. Unbound Extensions
4. Field Messages (RFC 822)

Appendices

1. Schema in RDF/XML
   • A.1. HTTP Schema
   • A.2. URI Schema
   • A.3. RFC 822 Schema
2. Schema Limitations
   • Appendix B.1: Header Sequences
   • Appendix B.2: Security and Privacy
3. Practical Example
4. References

1. Introduction

• [ISSUE-008] [Editorial] Avoid as much as possible form of the type "This document presents", talk about the subject right away. (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0017)
• [ISSUE-009] [Editorial] s/not inteded/not intended/ (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0017)
• [ISSUE-010] [Editorial] Change "[RDF]" to "Resource Description Framework (RDF): Concepts and Abstract Syntax [RDF]" and "[RDF-PRIMER]" to "RDF Primer [RDF-PRIMER]". (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0017)

1.1. Namespaces

• [ISSUE-012] Coordinate RFC822 work with An XML format for mail and other messages. (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0018)

1.2. Use Cases

• [ISSUE-011] [Editorial] Improve wording to better describe the use cases. (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0016)
• [ISSUE-017] New use case about scutters. (Kjetil: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0033)

2. Basic HTTP 1.1 (RFC 2616)

The are currently no open issues for this section of the document.

2.1. Request Class

The are currently no open issues for this section of the document.

2.2. Response Class

• [ISSUE-001] How to correlate requests and responses? Perhaps having an http:response property in the http:Request class. (Philippe: http://lists.w3.org/Archives/Public/public-wai-ert/2006Dec/0092, Tim)
• [ISSUE-003] The HTTP response definition in section 2.2 is missing http:version. (Philippe: http://lists.w3.org/Archives/Public/public-wai-ert/2006Dec/0092)
• [ISSUE-004] Example 2.2 is missing a http:responseCode. (Philippe: http://lists.w3.org/Archives/Public/public-wai-ert/2006Dec/0092)
• [ISSUE-018] Create a StatusCode class and reference it via http:responseCode. (Danny: http://lists.w3.org/Archives/Public/public-wai-ert/2007Feb/0004)

2.3. Header Properties

• [ISSUE-005] Add '-header' to header property names. (Danny: http://lists.w3.org/Archives/Public/public-wai-ert/2006Dec/0117)

2.3.1. Request Headers

The are currently no open issues for this section of the document.

2.3.2. Response Headers

The are currently no open issues for this section of the document.

2.3.3. Unbound Headers

The are currently no open issues for this section of the document.

2.4. Body Property

• [ISSUE-002] Requiring base64 since it makes it unusable for XSLT processors. (Philippe: http://lists.w3.org/Archives/Public/public-wai-ert/2006Dec/0094)
• [ISSUE-013] Clarify why base64 is necessary (testing binary data!) (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0019)
• [ISSUE-016] Consider rdf:parseType for including XML content (Kjetil: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0033).

2.5. URI Property

• [ISSUE-006] Rethink a URI class with properties for each part. (Phil: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0000)

3. Header Extensions (RFC 4229)

The are currently no open issues for this section of the document.

3.1. Request Extensions

• [ISSUE-007] [Editorial] Correct section numbering. (Phil: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0000, Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0017)

3.2. Response Extensions

• [ISSUE-007] [Editorial] Correct section numbering. (Phil: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0000, Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0017)

3.3. Unbound Extensions

• [ISSUE-007] [Editorial] Correct section numbering. (Phil: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0000, Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0017)

4. Field Messages (RFC 822)

• [ISSUE-012] Coordinate RFC822 work with An XML format for mail and other messages. (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0018)
• [ISSUE-014] RFC 822 is superseded by RFC 2822. (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0020)
• [ISSUE-015] Move "Field messages" to a separate document "RFC 2822 Vocabulary in RDF". (Karl: http://lists.w3.org/Archives/Public/public-wai-ert/2007Jan/0020)

Appendices

The are currently no open issues for this section of the document.

A. Schema in RDF/XML

The are currently no open issues for this section of the document.

A.1. HTTP Schema

The are currently no open issues for this section of the document.

A.2. URI Schema

The are currently no open issues for this section of the document.

A.3. RFC 822 Schema

The are currently no open issues for this section of the document.

B. Schema Limitations

The are currently no open issues for this section of the document.

B.1: Header Sequences

The are currently no open issues for this section of the document.

B.2: Security and Privacy

The are currently no open issues for this section of the document.

C. Practical Example

The are currently no open issues for this section of the document.

D. References

The are currently no open issues for this section of the document.