W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2002

RE: Issues with Annotations and the Schema Component

From: Biron,Paul V <Paul.V.Biron@kp.org>
Date: Thu, 3 Jan 2002 12:00:38 -0800
Message-Id: <8904C60CACA7D51191BC00805FEAAF43BFE1@crdc-exch-7.crdc.kp.org>
To: www-xml-schema-comments@w3.org
Cc: "'Alex Milowski'" <alex@milowski.com>
> -----Original Message-----
> From:	Alex Milowski [SMTP:alex@milowski.com]
> Sent:	Thursday, January 03, 2002 11:05 AM
> To:	www-xml-schema-comments@w3.org
> Subject:	Issues with Annotations and the Schema Component
> Since the schema component represents all the components that
> exist (with some bound) and so has no target namespace, what
> then is the target namespace of an annotation contained in the
> schema component?  It would seem that this target namespace
> is very important to making the annotation useable at all.
Annotation schema components do not have a target namespace property, so I'm
not sure what you're question is really asking.  Can you be more specific?

> It addition, it seems the annotations of any imported or
> included schema would be lost as the {annotations} property
> for the schema component is defined as the 'annotation' elements
> in the "children" and not those in the imported or included
> schemas documents as well.
I think the implication (intention?) is that all children of the
imported/included schema documents become children of the
importing/including schema.  However, you are probably correct that a strict
reading excludes them...I say this because of the wording used for the other
schema-level properties; e.g., {type definitions} says "The simple and
complex type definitions corresponding to all the <simpleType> and
<complexType> element information items in the [children], if any, plus any
included or imported definitions".
Received on Thursday, 3 January 2002 15:17:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:08:56 UTC