A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Atom Publishing Format and Protocol Working
Group of the IETF.
Title : The Atom Publishing Protocol
Author(s) : B. de Hora, J. Gregorio
First minor nit:
Section 8.1:
When the POST request contains an Atom Entry Document, ...
that should read POST response and not POST request
- James
[EMAIL PROTECTED] wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of
I note that the examples in the spec were likely cut-n-pasted from the
wiki, for instance:
Content- Length: nnn
Content- Type: application/atom+xml; charset=utf-8
Content- Location: http://example.org/edit/first-post.atom
The space following the Content- is intended to get
Ok, reading it again I think you're right, either way, however, the
construction of the sentence looks odd. Shortening it up to use your
wording below would likely be better:
The response to a POST request containing an Atom Entry Document
SHOULD contain a Content-Location header that
James M Snell wrote:
Antone,
Very good write up. The fact that xml:base on div is not valid XHTML is
somewhat irrelevant given that there is an identical problem with
xml:lang. For instance, if I have content xml:lang=endiv
xml:lang=fr.../div/content and I drop the div silently, then I've
got
Hi James,
I understand what you mean. We'll patch the English on that sentence
next time around.
cheers
Bill
James M Snell wrote:
Ok, reading it again I think you're right, either way, however, the
construction of the sentence looks odd. Shortening it up to use your
wording below would
Well, the subject says it all; here they are:
- It were nice if the example in 7.1 would include @xml:lang, since both
workspace/@title and collection/@title are Language-Sensitive.
Granted, there might be a Content-Language response header (not shown)
to do the job, but IMHO the example
Andreas Sewe wrote:
Well, the subject says it all; here they are:
- It were nice if the example in 7.1 would include @xml:lang, since both
workspace/@title and collection/@title are Language-Sensitive. Granted,
there might be a Content-Language response header (not shown) to do the
job,
On 30/6/06 1:34 AM, Bill de hÓra [EMAIL PROTECTED] wrote:
Which are clients supposed to respect in a conflict, the
Content-Language header or the xml:lang, ie, does XML On The Web Failing
Miserably, Utterly, And Completely extend to Content-Language+xml:lang?
xml:lang, if you think of xml
Eric Scheid wrote:
On 30/6/06 1:34 AM, Bill de hÓra [EMAIL PROTECTED] wrote:
Which are clients supposed to respect in a conflict, the
Content-Language header or the xml:lang, ie, does XML On The Web Failing
Miserably, Utterly, And Completely extend to Content-Language+xml:lang?
xml:lang, if
A couple of comments...
Section 6
Archive documents are feed documents that contain less recent entries
in the feed. The set of entries contained in an archive document
published at a particular URI MUST NOT change over time.
I definitely understand the motivation for the MUST NOT
A few more comments:
Section 4:
Note that when an IRI is used for resource retrieval over HTTP, the
IRI is first converted to a URI according the procedure defined in
[RFC3987] section 3.1. The resource that the IRI locates is the same
as the one located by the URI obtained after
12 matches
Mail list logo
