Jumps: VOResourceV102RFC :: ResourceMetadata :: RegDMServices :: registry mail archive :: VOResourceV010
Meetings: InterOpMay2005ResReg :: InterOpMay2006ResReg

Registry Working Group WP3 (Metadata Specifications)

VOResource v1.0

• VOResourceV10Disc: Discussion of this release

Contents

News

• The Request for Comment (RFC) period was completed 10 Sept 2007; this is now a Recommendation.

The Specification Document

The following document is the current internal draft of the specification that will go through the IVOA standards process.

External Working Draft

VOResource: an XML Encoding Schema for Resource Metadata, Version 1.01

Internal Working Draft

VOResource: an XML Encoding Schema for Resource Metadata, Version 1.02, 20061030

The Schema

External Working Draft

The VOResource Schema: VOResource-v1.0r9.xsd

Internal Working Draft

The VOResource Schema: VOResource-v1.02r1.xsd

NOTE: Looking for all current extension schemas compatible with the latest version of the core VOResource schema? Refer to RegUpgradeSummer2006.

Sample Instance Documents

• organisation.xml
• webform.xml
• webservice.xml

These examples have been verified against v1.0r9 using Xerces. To verify, place VOResource-v1.0.xsd into the same directory as instance document.

Sample Java Classes

As a further test, Java classes for this schema were successfully generated using Axis' wsdl2java; the results can be found in VOResourceJava-r7.zip.

Summary of Changes

• made status required

R9

• made validatedBy required
• vr:AccessURL/@use: removed whitespace restriction, changed back from xs:string to xs:NMTOKEN (in which whitespace collapse is implicit)
• dropped vr:PaddedURI as equivalent to xs:anyURI
• dropped vr:PaddedString as equivalent to xs:token

R7

• integration of STC
• do not formally control relationshipType names in Schema
• flexible <date> format, require xs:dateTime on created, updated attributes (re-instated use of union)

R6

• initial test integration of STC
• removed use of union in date handling

R5:

• implementation of new Service model (Service with Capabilities)
• allow extensible relationshipType vocabulary via extension type

R4: For more info, see Kyoto presentation on VOResource v1.0

• All dates are UTC; encode with new type UTCDateTime
• Allow string values to be padded with spaces
• Added "served-by" relationship as requested
• Added validationLevel element to Resource
• Various corrections in occurances