Extension to RFC for Space-Time Coordinates

[Gerard Lemson]

The document for which comments are requested contains text and UML-like
diagrams. But it also has in section 7 a link to a document containing an
XML
schema for STC in XMLSpy format. It seems that there are significant
discrepancies
between the two different models, the one in XML schema and the UML. In
particular
it seems that the XML schema is much more detailed, look for example to
Referenceposition.

My question is how to evaluate the RFC.
Should the XML schema document be considered part of the RFC, in the sense
that it is
proposed as a standard as well ? Or is it supposed to be an implementation
as Jonathan
suggested in Kyoto. But in that case are we allowed/assumed to comment on
the proposed
implementation and its compatibility if not equivalence to the UML in the
main document ?

Whatever may be the case, is there a document with the XML schema in XML iso
in XMLSpy boxes ?

Thanks
-- Gerard


--
* Gerard Lemson                       * Tel: +49 (0)89 30000-3316
*
* MPI fuer extraterrestische Physik   * Fax: +49 (0)89 30000-3569
*
* Giessenbachstrasse                  *
*
* Postfach 1312                       *
*
* D-85741 Garching, GERMANY           * email: gerard.lemson at mpe.mpg.de
*


> -----Original Message-----
> From: owner-interop at eso.org [mailto:owner-interop at eso.org]On Behalf Of
> Jonathan McDowell
> Sent: Friday, May 27, 2005 9:06 PM
> To: interop at ivoa.net
> Subject: Extension to RFC for Space-Time Coordinates
>
>
>
> At the request of the Exec I am extending the existing RFC
> period for the Space-Time Coordinates document to Tuesday June 21.
> All comments received so far can, we believe, be addressed
> without significant changes, but we also suspect there are still
> many relevant people who have not read the document. Now is your
> chance!
>  Document: http://www.ivoa.net/Documents/latest/STC.html
>  RFC page: http://www.ivoa.net/twiki/bin/view/IVOA/STCMetadataRFC
> Please upload your comments to the RFC page.
>  - Jonathan McDowell, DM Working Group.
>