Index: trunk/build/buildTools/xjc.xml
===================================================================
--- (revision )
+++ trunk/build/buildTools/xjc.xml (revision 3159)
@@ -1,0 +1,146 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: trunk/resources/exsynchwsdefs/iCalendar-wscal-extensions.xsd
===================================================================
--- trunk/resources/exsynchwsdefs/iCalendar-wscal-extensions.xsd (revision 3116)
+++ trunk/resources/exsynchwsdefs/iCalendar-wscal-extensions.xsd (revision 3159)
@@ -66,5 +66,14 @@
-
+
+
+
+
+
+
+
+
Index: trunk/resources/timezones/bindings/simplebinding.xml
===================================================================
--- (revision )
+++ trunk/resources/timezones/bindings/simplebinding.xml (revision 3159)
@@ -1,0 +1,9 @@
+
+
+
+
+
+
Index: trunk/resources/timezones/tzservice.xsd
===================================================================
--- (revision )
+++ trunk/resources/timezones/tzservice.xsd (revision 3159)
@@ -1,0 +1,271 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The calendar system defines how rules, dates and times are to be
+ interpreted. Currently only the value "Gregorian" is supported,
+ referring to the Gregorian calendar scale. If this element is not
+ present in its normal context, then the value "Gregorian" MUST be assumed.
+
+
+
+
+
+
+
+
+ Provides the UTC date and time when a substantive change was made to the
+ timezone data.
+
+
+
+
+
+
+
+
+ Provides the UTC date and time that the timezone data was last modified.
+
+
+
+
+
+
+
+
+ Defines one or more localized names that are used when a timezone
+ identifier needs to be presented to a user. The xml:lang attribute is
+ used to indicate the language associated with each value. If multiple
+ names are provided for the same locale the first is considered the
+ preferred name.
+
+
+
+
+
+
+
+
+
+
+
+
+ The onset element defines the local time at which the observance takes effect.
+
+
+
+
+
+
+
+
+ The text value is the identifier of the timezone being referred to.
+
+
+
+
+
+
+
+
+ The utc-offset-from element defines the UTC offset in hours and minutes
+ before the start of this observance.
+
+
+
+
+
+
+
+
+ The utc-offset-to element defines the UTC offset in hours and minutes at
+ and after the start of this observance.
+
+
+
+
+
+
+
+
+ Defines alternative identifiers that can be used for the timezone. This
+ feature allows mapping of old identifiers onto new.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This defines the name, type and characteristics of an operation parameter.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The element used as the container for information defining an operation
+ and its parameters. .
+
+
+
+
+
+
+
+
+
+
+
+
+ The root (top-level) element used as the container for capabilities information.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This defines the element that provides summary information for a timezone
+ in the timezones list.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This defines the root (top-level) element used as the container for
+ a timezone listing.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ In an expanded timezone, the observance element specifies a single
+ timezone observance.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This element specifies expanded timezone data for the range specified in
+ a request.
+
+
+
+
+
+
+
+
+
+
+
+
+ This defines the root (top-level) element used as the container for
+ expanded timezone data.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Index: trunk/resources/timezones/xml.xsd
===================================================================
--- (revision )
+++ trunk/resources/timezones/xml.xsd (revision 3159)
@@ -1,0 +1,134 @@
+
+
+
+
+
+ See http://www.w3.org/XML/1998/namespace.html and
+ http://www.w3.org/TR/REC-xml for information about this namespace.
+
+ This schema document describes the XML namespace, in a form
+ suitable for import by other schema documents.
+
+ Note that local names in this namespace are intended to be defined
+ only by the World Wide Web Consortium or its subgroups. The
+ following names are currently defined in this namespace and should
+ not be used with conflicting semantics by any Working Group,
+ specification, or document instance:
+
+ base (as an attribute name): denotes an attribute whose value
+ provides a URI to be used as the base for interpreting any
+ relative URIs in the scope of the element on which it
+ appears; its value is inherited. This name is reserved
+ by virtue of its definition in the XML Base specification.
+
+ id (as an attribute name): denotes an attribute whose value
+ should be interpreted as if declared to be of type ID.
+ The xml:id specification is not yet a W3C Recommendation,
+ but this attribute is included here to facilitate experimentation
+ with the mechanisms it proposes. Note that it is _not_ included
+ in the specialAttrs attribute group.
+
+ lang (as an attribute name): denotes an attribute whose value
+ is a language code for the natural language of the content of
+ any element; its value is inherited. This name is reserved
+ by virtue of its definition in the XML specification.
+
+ space (as an attribute name): denotes an attribute whose
+ value is a keyword indicating what whitespace processing
+ discipline is intended for the content of the element; its
+ value is inherited. This name is reserved by virtue of its
+ definition in the XML specification.
+
+ Father (in any context at all): denotes Jon Bosak, the chair of
+ the original XML Working Group. This name is reserved by
+ the following decision of the W3C XML Plenary and
+ XML Coordination groups:
+
+ In appreciation for his vision, leadership and dedication
+ the W3C XML Plenary on this 10th day of February, 2000
+ reserves for Jon Bosak in perpetuity the XML name
+ xml:Father
+
+
+
+
+ This schema defines attributes and an attribute group
+ suitable for use by
+ schemas wishing to allow xml:base, xml:lang or xml:space attributes
+ on elements they define.
+
+ To enable this, such a schema must import this schema
+ for the XML namespace, e.g. as follows:
+ <schema . . .>
+ . . .
+ <import namespace="http://www.w3.org/XML/1998/namespace"
+ schemaLocation="http://www.w3.org/2001/03/xml.xsd"/>
+
+ Subsequently, qualified reference to any of the attributes
+ or the group defined below will have the desired effect, e.g.
+
+ <type . . .>
+ . . .
+ <attributeGroup ref="xml:specialAttrs"/>
+
+ will define a type which will schema-validate an instance
+ element with any of those attributes
+
+
+
+ In keeping with the XML Schema WG's standard versioning
+ policy, this schema document will persist at
+ http://www.w3.org/2004/10/xml.xsd.
+ At the date of issue it can also be found at
+ http://www.w3.org/2001/xml.xsd.
+ The schema document at that URI may however change in the future,
+ in order to remain compatible with the latest version of XML Schema
+ itself, or with the XML namespace itself. In other words, if the XML
+ Schema or XML namespaces change, the version of this document at
+ http://www.w3.org/2001/xml.xsd will change
+ accordingly; the version at
+ http://www.w3.org/2004/10/xml.xsd will not change.
+
+
+
+
+
+ Attempting to install the relevant ISO 2- and 3-letter
+ codes as the enumerated possible values is probably never
+ going to be a realistic possibility. See
+ RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
+ at http://www.iana.org/assignments/lang-tag-apps.htm for
+ further information.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ See http://www.w3.org/TR/xmlbase/ for
+ information about this attribute.
+
+
+
+
+
+ See http://www.w3.org/TR/xml-id/ for
+ information about this attribute.
+
+
+
+
+
+
+
+
+
+