Datatypes for Web Distributed Authoring and Versioning (WebDAV) Properties
draft-reschke-webdav-property-datatypes-09
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2005-08-16
|
09 | Amy Vezza | State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza |
2005-06-15
|
09 | Amy Vezza | IESG state changed to Approved-announcement sent |
2005-06-15
|
09 | Amy Vezza | IESG has approved the document |
2005-06-15
|
09 | Amy Vezza | Closed "Approve" ballot |
2005-06-10
|
09 | (System) | Removed from agenda for telechat - 2005-06-09 |
2005-06-09
|
09 | Amy Vezza | State Changes to Approved-announcement to be sent::Point Raised - writeup needed from IESG Evaluation by Amy Vezza |
2005-06-08
|
09 | David Kessens | [Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens |
2005-06-08
|
09 | Bill Fenner | [Ballot Position Update] New position, No Objection, has been recorded for Bill Fenner by Bill Fenner |
2005-06-08
|
09 | Michelle Cotton | IANA Comments: As stated in the IANA Considerations section, we understand this document to have NO IANA Actions. |
2005-06-07
|
09 | Brian Carpenter | [Ballot comment] Comment from review by Spencer Dawkins: In Section 7, "Compatibility Considerations", the following two considerations appear: Clients not aware of datatype handling … [Ballot comment] Comment from review by Spencer Dawkins: In Section 7, "Compatibility Considerations", the following two considerations appear: Clients not aware of datatype handling should not supply the "xsi: type" attribute on property elements (after all, this attribute belongs to the XML Schema-Instance namespace which has been defined for exactly this purpose). Old clients should also ignore additional attributes on property elements returned by PROPFIND (and similar methods), although the WebDAV specification only defines this behaviour for unknown elements (and is silent about unknown attributes). Servers not aware of datatype handling either drop the "xsi:type" attribute, or persist it along with the property value. However, they will never indicate successful parsing of the data type by returning back the type in the response to PROPPATCH. Thus, clients can supply type information without having to poll for server support in advance. I would feel quite a bit better if the "should" and "will never" actually referenced normative text in some specification somewhere - the document feels like it's relying on common implementation behaviors without these references, and that would be quite a bit more likely to trip over compatibility issues. I also wondered about "should" vs. "SHOULD", but decided that "requirements" for clients and servers that aren't aware of this capability are probably problematic anyway :-) |
2005-06-07
|
09 | Brian Carpenter | [Ballot Position Update] New position, No Objection, has been recorded for Brian Carpenter by Brian Carpenter |
2005-06-06
|
09 | Russ Housley | [Ballot Position Update] New position, No Objection, has been recorded for Russ Housley by Russ Housley |
2005-06-01
|
09 | Scott Hollenbeck | [Ballot Position Update] New position, No Objection, has been recorded for Scott Hollenbeck by Scott Hollenbeck |
2005-05-31
|
09 | Ted Hardie | [Ballot Position Update] New position, Yes, has been recorded for Ted Hardie |
2005-05-31
|
09 | Ted Hardie | Ballot has been issued by Ted Hardie |
2005-05-31
|
09 | Ted Hardie | Created "Approve" ballot |
2005-05-31
|
09 | (System) | Ballot writeup text was added |
2005-05-31
|
09 | (System) | Last call text was added |
2005-05-31
|
09 | (System) | Ballot approval text was added |
2005-05-31
|
09 | Ted Hardie | Placed on agenda for telechat - 2005-06-09 by Ted Hardie |
2005-05-31
|
09 | Ted Hardie | State Changes to IESG Evaluation from Publication Requested by Ted Hardie |
2005-05-31
|
09 | Ted Hardie | I've reviewed the wg archives and I believe that this document does not represent an end run around the working group; the working group was … I've reviewed the wg archives and I believe that this document does not represent an end run around the working group; the working group was kept in the loop on this draft on a consistent basis and reviews submitted were acted upon. |
2005-05-09
|
09 | Dinara Suleymanova | Draft Added by Dinara Suleymanova in state Publication Requested |
2005-04-29
|
09 | (System) | New version available: draft-reschke-webdav-property-datatypes-09.txt |
2004-09-27
|
08 | (System) | New version available: draft-reschke-webdav-property-datatypes-08.txt |
2004-08-30
|
07 | (System) | New version available: draft-reschke-webdav-property-datatypes-07.txt |
2004-02-12
|
06 | (System) | New version available: draft-reschke-webdav-property-datatypes-06.txt |
2003-09-29
|
05 | (System) | New version available: draft-reschke-webdav-property-datatypes-05.txt |
2003-03-24
|
04 | (System) | New version available: draft-reschke-webdav-property-datatypes-04.txt |
2002-10-08
|
03 | (System) | New version available: draft-reschke-webdav-property-datatypes-03.txt |
2002-06-25
|
02 | (System) | New version available: draft-reschke-webdav-property-datatypes-02.txt |
2002-01-31
|
01 | (System) | New version available: draft-reschke-webdav-property-datatypes-01.txt |
2001-08-16
|
00 | (System) | New version available: draft-reschke-webdav-property-datatypes-00.txt |