[caldeveloper-l] XML schemas for WebDAV/CalDAV/CardDAV

[Michael Douglass]

I got into schemas for the calws stuff and at that time attempted to 
create xsd schemas for those protocols. I managed to do so for a small 
subsection of caldav (queries I believe) but my recollection (and it's 
going back a while so the details may be wrong) is that the xml 
structure violates some of the requirements for XSD. Elements can be 
simple or complex in these protocols. There are some elements that have 
a different definition depending on context etc.

Having experienced the benefits of xsd in the jaxb world I'd have argued 
strongly for such schemas and a more formal approach to defining the 
protocols. I don't know if relaxng will have the same issues.

Also some of my problems might have been some of the constraints applied 
by the soap world but I don't think that was so.


On 12/1/17 10:50, David Given wrote:
> Hello,
>
> I'm aware that the DAV protocols aren't suitable for use with schema 
> validators, due to the requirement to handle extension elements. 
> Nevertheless, it would be really useful to have a definitive schema 
> (either XSD or DTD) both for reference and as input for non-validating 
> automation.
>
> The RFCs contain DTD fragments, but they're explicitly non-definitive 
> and are there for documentation purposes only. And I don't really want 
> to put together my own because then it'll be wrong. I've found some 
> third party CalDAV schemas, all of which have comments saying that 
> they're wrong, so I don't want to use those either.
>
> Does such a thing exist?
>
> Thanks!
>
>
>
> _______________________________________________
> caldeveloper-l mailing list
> caldeveloper-l at lists.calconnect.org
> http://lists.calconnect.org/listinfo.cgi/caldeveloper-l-calconnect.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.calconnect.org/pipermail/caldeveloper-l-calconnect.org/attachments/20171203/e988d04a/attachment.html>