Re: [VCARDDAV] Fwd: Last Call: <draft-daboo-et-al-icalendar-in-xml-08.txt> (xCal: The XML format for iCalendar) to Proposed Standard

[Cyrus Daboo <[e-mail]>]

Hi Peter,

--On April 18, 2011 12:41:36 PM -0600 Peter Saint-Andre 
<[e-mail]> wrote:

>> Just FYI. This document is intended to be in sync with vcardxml
>> regarding XML structure, so folks here might want to review both
>> documents with that in mind...
>
> I notice that the definitions for value types, parameters, and
> properties are not always in sync. Do they need to be?
>
> Here are two examples.
>
> 1. The "boolean" value.
>
> a. vcardxml says:
>
> value-boolean = element boolean { xsd:boolean }
>
> b. icalendar-in-xml says:
>
>    value-boolean = element boolean {
>        ("TRUE" | "FALSE")
>    }
>
> The difference here is that W3C XML Schema defines two lexical
> represenations for boolean: either "true"/"false", or "1"/"0".
>
> http://www.w3.org/TR/xmlschema-2/#boolean

The xCal spec does not use xsd: elements in its RelaxNG schema. Should it? 
I see that Simon seems to have gone to greater lengths to specify string 
patterns and the like to constrain values. For xCal we choose not to do 
that, preferring to keep the base schema simple on the understanding that 
validation of iCalendar semantics would require something a lot more 
complex (e.g. requiring DTEND > DTSTART etc).

So the question here is should xCal adopt the xsd: style value specs in 
xCard, or should xCard drop back to using simple RelaxNG { text } elements, 
or does it not matter?

> 2. The "geo" parameter / property.
>
> a. vcardxml says:
>
> param-geo = element geo { value-uri }?
>
> b. icalendar-in-xml says:
>
>    property-geo = element geo {
>
>        element parameters { empty }?,
>
>        element value {
>            element latitude  { text },
>            element longitude { text }
>        }
>    }

GEO is itself defined differently in iCalendar (two floats) and vCard (geo 
uri) - so in this case the difference is valid. However, the xCal schema 
for GEO is wrong as it ought to use 'float' and not 'text'.

-- 
Cyrus Daboo