Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
News3 Nov 2004: VOResource-v0.10.xsd was updated with a bug fix to allow multiple occurances of the Type element. As a bug fix (that happens to be backward compatible), the version number is not changed.The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
Example documents
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ... </vr:SkyService>...now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
About the root elementAs mentioned above, VOResource defines no global elements. The proper root element is expected to be defined by the application, as necessary, via its own application schema. For example, a particular application might define the following schema:<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://astroservices.org/ResourceApplication" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:ra="http://astroservices.org/ResourceApplication" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10"> <xs:annotation> <xs:documenation> application schema using VOResource </xs:documenation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v0.10" /> <xs:element name="ResourceDescription" type="vr:Resource"/> <xs:element name="Resources"> <xs:complexType> <xs:sequence> <xs:element ref="ra:ResourceDescription" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>In this example, two global elements have been defined, either which can be used as a root element. The application would use this simple schema to verify its documents. Note that in the example instance documents listed above, an application schema is not needed. That's because the root element in each case specifies its type using an xsi:type attribute. According to the XML Schema standard, this is sufficient to verify the document.
It is expected that registry applications will use "resource" as the root element, just like in the examples listed above.
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
|
Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
News3 Nov 2004: VOResource-v0.10.xsd was updated with a bug fix to allow multiple occurances of the Type element. As a bug fix (that happens to be backward compatible), the version number is not changed.The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
Example documents
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9... | |||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||
< < | <!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> | ||||||||||||||||||||||||||
> > | <-- the old way --> | ||||||||||||||||||||||||||
... | |||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||
> > | |||||||||||||||||||||||||||
...now looks like this...
<!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
About the root elementAs mentioned above, VOResource defines no global elements. The proper root element is expected to be defined by the application, as necessary, via its own application schema. For example, a particular application might define the following schema:<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://astroservices.org/ResourceApplication" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:ra="http://astroservices.org/ResourceApplication" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10"> <xs:annotation> <xs:documenation> application schema using VOResource </xs:documenation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v0.10" /> <xs:element name="ResourceDescription" type="vr:Resource"/> <xs:element name="Resources"> <xs:complexType> <xs:sequence> <xs:element ref="ra:ResourceDescription" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>In this example, two global elements have been defined, either which can be used as a root element. The application would use this simple schema to verify its documents. Note that in the example instance documents listed above, an application schema is not needed. That's because the root element in each case specifies its type using an xsi:type attribute. According to the XML Schema standard, this is sufficient to verify the document.
It is expected that registry applications will use "resource" as the root element, just like in the examples listed above.
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
<--
|
Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
News3 Nov 2004: VOResource-v0.10.xsd was updated with a bug fix to allow multiple occurances of the Type element. As a bug fix (that happens to be backward compatible), the version number is not changed.The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
Example documents
| |||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ......now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
About the root elementAs mentioned above, VOResource defines no global elements. The proper root element is expected to be defined by the application, as necessary, via its own application schema. For example, a particular application might define the following schema:<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://astroservices.org/ResourceApplication" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:ra="http://astroservices.org/ResourceApplication" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10"> <xs:annotation> <xs:documenation> application schema using VOResource </xs:documenation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v0.10" /> <xs:element name="ResourceDescription" type="vr:Resource"/> <xs:element name="Resources"> <xs:complexType> <xs:sequence> <xs:element ref="ra:ResourceDescription" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>In this example, two global elements have been defined, either which can be used as a root element. The application would use this simple schema to verify its documents. Note that in the example instance documents listed above, an application schema is not needed. That's because the root element in each case specifies its type using an xsi:type attribute. According to the XML Schema standard, this is sufficient to verify the document.
It is expected that registry applications will use "resource" as the root element, just like in the examples listed above.
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
<--
|
Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
| |||||||||||||||||||||||
Added: | |||||||||||||||||||||||
> > | News | ||||||||||||||||||||||
Added: | |||||||||||||||||||||||
> > | 3 Nov 2004: VOResource-v0.10.xsd was updated with a bug fix to allow multiple occurances of the Type element. As a bug fix (that happens to be backward compatible), the version number is not changed. | ||||||||||||||||||||||
The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
Example documents
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ......now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
About the root elementAs mentioned above, VOResource defines no global elements. The proper root element is expected to be defined by the application, as necessary, via its own application schema. For example, a particular application might define the following schema:<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://astroservices.org/ResourceApplication" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:ra="http://astroservices.org/ResourceApplication" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10"> <xs:annotation> <xs:documenation> application schema using VOResource </xs:documenation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v0.10" /> <xs:element name="ResourceDescription" type="vr:Resource"/> <xs:element name="Resources"> <xs:complexType> <xs:sequence> <xs:element ref="ra:ResourceDescription" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>In this example, two global elements have been defined, either which can be used as a root element. The application would use this simple schema to verify its documents. Note that in the example instance documents listed above, an application schema is not needed. That's because the root element in each case specifies its type using an xsi:type attribute. According to the XML Schema standard, this is sufficient to verify the document.
It is expected that registry applications will use "resource" as the root element, just like in the examples listed above.
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
<--
| |||||||||||||||||||||||
Changed: | |||||||||||||||||||||||
< < |
| ||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
|
Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
Example documents
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ......now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
About the root elementAs mentioned above, VOResource defines no global elements. The proper root element is expected to be defined by the application, as necessary, via its own application schema. For example, a particular application might define the following schema:<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://astroservices.org/ResourceApplication" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:ra="http://astroservices.org/ResourceApplication" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10"> <xs:annotation> <xs:documenation> application schema using VOResource </xs:documenation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v0.10" /> <xs:element name="ResourceDescription" type="vr:Resource"/> <xs:element name="Resources"> <xs:complexType> <xs:sequence> <xs:element ref="ra:ResourceDescription" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>In this example, two global elements have been defined, either which can be used as a root element. The application would use this simple schema to verify its documents. Note that in the example instance documents listed above, an application schema is not needed. That's because the root element in each case specifies its type using an xsi:type attribute. According to the XML Schema standard, this is sufficient to verify the document.
It is expected that registry applications will use "resource" as the root element, just like in the examples listed above.
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
<--
| |||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||
|
| |||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||
< < | Jumps: IvoaResReg :: registry mail archive :: ResourceMetadata :: RWP03RefBack :: RWP03Disc Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg | ||||||||||||||||||||||||||
> > | Jumps: IvoaResReg :: registry mail archive :: ResourceMetadata :: RWP03RefBack :: RWP03Disc | ||||||||||||||||||||||||||
Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
| |||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||
< < | |||||||||||||||||||||||||||
> > | |||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||
Example documents
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ......now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
About the root elementAs mentioned above, VOResource defines no global elements. The proper root element is expected to be defined by the application, as necessary, via its own application schema. For example, a particular application might define the following schema:<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://astroservices.org/ResourceApplication" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:ra="http://astroservices.org/ResourceApplication" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10"> <xs:annotation> <xs:documenation> application schema using VOResource </xs:documenation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v0.10" /> <xs:element name="ResourceDescription" type="vr:Resource"/> <xs:element name="Resources"> <xs:complexType> <xs:sequence> <xs:element ref="ra:ResourceDescription" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>In this example, two global elements have been defined, either which can be used as a root element. The application would use this simple schema to verify its documents. Note that in the example instance documents listed above, an application schema is not needed. That's because the root element in each case specifies its type using an xsi:type attribute. According to the XML Schema standard, this is sufficient to verify the document.
It is expected that registry applications will use "resource" as the root element, just like in the examples listed above.
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
<--
|
Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
| |||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||
> > | |||||||||||||||||||||||||||||||||||||||||||||
The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
Example documents
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ......now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
About the root elementAs mentioned above, VOResource defines no global elements. The proper root element is expected to be defined by the application, as necessary, via its own application schema. For example, a particular application might define the following schema:<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://astroservices.org/ResourceApplication" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:ra="http://astroservices.org/ResourceApplication" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10"> <xs:annotation> <xs:documenation> application schema using VOResource </xs:documenation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v0.10" /> <xs:element name="ResourceDescription" type="vr:Resource"/> <xs:element name="Resources"> <xs:complexType> <xs:sequence> <xs:element ref="ra:ResourceDescription" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>In this example, two global elements have been defined, either which can be used as a root element. The application would use this simple schema to verify its documents. Note that in the example instance documents listed above, an application schema is not needed. That's because the root element in each case specifies its type using an xsi:type attribute. According to the XML Schema standard, this is sufficient to verify the document.
It is expected that registry applications will use "resource" as the root element, just like in the examples listed above.
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
<--
|
Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
Example documents
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ......now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
| |||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||
> > |
About the root elementAs mentioned above, VOResource defines no global elements. The proper root element is expected to be defined by the application, as necessary, via its own application schema. For example, a particular application might define the following schema:<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://astroservices.org/ResourceApplication" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:vr="http://www.ivoa.net/xml/VOResource/v0.10" xmlns:ra="http://astroservices.org/ResourceApplication" elementFormDefault="qualified" attributeFormDefault="unqualified" version="0.10"> <xs:annotation> <xs:documenation> application schema using VOResource </xs:documenation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v0.10" /> <xs:element name="ResourceDescription" type="vr:Resource"/> <xs:element name="Resources"> <xs:complexType> <xs:sequence> <xs:element ref="ra:ResourceDescription" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema>In this example, two global elements have been defined, either which can be used as a root element. The application would use this simple schema to verify its documents. Note that in the example instance documents listed above, an application schema is not needed. That's because the root element in each case specifies its type using an xsi:type attribute. According to the XML Schema standard, this is sufficient to verify the document.
It is expected that registry applications will use "resource" as the root element, just like in the examples listed above. | ||||||||||||||||||||||||||
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
<--
|
Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions
The SchemasVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas:
Example documents | |||||||||||||||||||||||
Changed: | |||||||||||||||||||||||
< < |
| ||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
Changed: | |||||||||||||||||||||||
< < |
| ||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
Changed: | |||||||||||||||||||||||
< < |
| ||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
Changed: | |||||||||||||||||||||||
< < |
| ||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
Changed: | |||||||||||||||||||||||
< < |
| ||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
Changed: | |||||||||||||||||||||||
< < |
| ||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
Changed: | |||||||||||||||||||||||
< < |
| ||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ......now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
Useful ToolsConversion Stylesheets
Background Materials
What's Ahead in Future Versions
<--
| |||||||||||||||||||||||
Added: | |||||||||||||||||||||||
> > |
| ||||||||||||||||||||||
Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg | ||||||||||
Changed: | ||||||||||
< < | Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions | |||||||||
> > | Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard Extensions | |||||||||
Changed: | ||||||||||
< < | VOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.9) and a set of standard extensions. The current internal Working Draft is v0.10 ("version zero-point-ten"). | |||||||||
> > |
| |||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > | Contents | |||||||||
Deleted: | ||||||||||
< < |
| |||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > | The Schemas | |||||||||
Changed: | ||||||||||
< < | Background Materials | |||||||||
> > | VOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.10) and a set of standard extensions. | |||||||||
Added: | ||||||||||
> > | These schemas are have been released from the official IVOA schema distribution area. To validate documents compliant with this release you need each of the following schemas: | |||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
Added: | ||||||||||
> > |
| |||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > | The following two extensions are extensions that define specific, standard tabular sky services. | |||||||||
Added: | ||||||||||
> > |
Example documents
What's New in this ReleaseThe primary change is the way extensions are handled: we have dropped the use of substitution groups and replaced them with the use of xsi:type. What looked like this in release v0.9...<!-- the old way --> <VOResource xmlns="..." > <vs:SkyService> ......now looks like this... <!-- the new way --> <resource xsi:type="vs:SkyService" xmlns="..." > ...That is, you now see both specific type (SkyService) and the base concept it extends (resource) in the same element. Here's an abridged list of changes made. (A more complete description can be found here.)
| |||||||||
Useful Tools | ||||||||||
Added: | ||||||||||
> > | Conversion Stylesheets | |||||||||
| ||||||||||
Added: | ||||||||||
> > |
Background Materials
What's Ahead in Future Versions
| |||||||||
<--
|
| ||||||||
Changed: | ||||||||
< < | Jumps: IvoaResReg :: registry mail archive :: ResourceMetadata :: RWP03RefBack :: RWP03Disc Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg | |||||||
> > | Jumps: IvoaResReg :: registry mail archive :: ResourceMetadata :: RWP03RefBack :: RWP03Disc Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg | |||||||
Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard ExtensionsVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.9) and a set of standard extensions. The current internal Working Draft is v0.10 ("version zero-point-ten").
Background Materials
| ||||||||
Added: | ||||||||
> > | Useful Tools
| |||||||
<--
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
Deleted: | ||||||||
< < | ||||||||
|
Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard ExtensionsVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.9) and a set of standard extensions. The current internal Working Draft is v0.10 ("version zero-point-ten").
Background Materials
<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
Meetings: Registry19032003 :: InterOpMay2003ResReg :: InterOpMay2004ResReg Registry Working Group WP3 (Metadata Specifications)VOResource v0.10 and its Standard ExtensionsVOResource, in general, refers to a family of schemas that includes the core schema (VOResource-v0.9) and a set of standard extensions. The current internal Working Draft is v0.10 ("version zero-point-ten").
Background Materials
<--
|