|
Bob Hanisch (Data Curation & Preservation IG)
I am not an XML expert, but I have been assured by my colleagues who are that this document is all in order and fully vetted by those most involved in registry implementation. Thus I add my vote of approval.
Gerard Lemson (Theory IG)
Mireille Louys (Data Models WG)
I approve the document and have appreciated the clear organisation and
documentation of these pieces of XML, generaly difficult to read.
Keith Noddle (DAL WG)
I approve this document. Defining VOResource was always going to be a challenge and I think the team have done magnificently. With the exception of a couple of missing cross references, the document seems to tick all the correct boxes.
However, I feel the attention of the IVOA as a whole needs to be drawn to two key sentences in the document:
1. "Another intended use is as a language for services to describe themselves directly. VOResource may be used in other ways, in whole or in part, using the standard XML mechanisms (e.g., import, include)."
2. "...full and useful description of a specific resource will require additional metadata that is relevant only to a resource of its type. Thus, the VOResource schema has been especially designed to be extended."
Taken together these highlight key deliverables for the standard that can easily be lost if VOResource is viewed solely in the context of the Registry.
Francois Ochsenbein (VOTable WG)
Pedro Osuna (VOQL WG)
Ray Plante (Resource Registry WG)
Andrea Preite-Martinez (Semantics WG)
I approve.
Roy Williams (VOEvent WG)
I approve this document.
<--
--> |