Re: [VCARDDAV] use of DTD in draft-ietf-vcarddav-carddav-06, was: vcarddav WGLC on draft-ietf-vcarddav-{carddav, mkcol}

Hi Julian,

--On March 12, 2009 2:41:39 PM +0100 Julian Reschke <julian.reschke@gmx.de> 
wrote:

> 1) Section 2.2 (XML Namespaces and Processing) should be expanded to
> include statements about how the DTD fragments are to be understood,
> similar to Section 2 in draft-ietf-vcarddav-webdav-mkcol-04.

Fixed - I re-wrote section 2 to be more like the other draft. The separate 
sub-section on XML processing was removed as a result.

> 2) The XML spec reference needs to be updated to W3C.REC-xml-20081126,
> just as in draft-ietf-vcarddav-webdav-mkcol-04. (Note I'd recommend to
> use a shorter reference name, such as just "XML".

Reference updated. I am just using the xml2rfc default for <?rfc 
symrefs="yes"?>.

> 3) I had trang (<http://www.thaiopensource.com/relaxng/trang.html>) parse
> the DTD fragments for me (to do that just markup the artwork with the
> proper type of "application/xml-dtd", then use rfc2629xslt's
> extract-artwork.xslt
> (<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#extract-a
> rtwork>).
>
> A minor issue I found is that at least one element type definition
> (addressbook) appeared multiple times; this is not really a problem as
> long as they all say the same thing.
>
> On the other hand, address-data has three different definitions (see
> <http://tools.ietf.org/html/draft-ietf-vcarddav-carddav-06#section-10.4>)
> , depending on the context it's used in. I think this really should be
> avoided. The simplest fix for this seems to just use three distinct names.

Well we did have calendar-data in CalDAV do the same. I am OK with making a 
change if others think it is worth doing.

-- 
Cyrus Daboo

Received on Monday, 16 March 2009 02:03:29 UTC