Accomplishments RSM v0.7 First draft XML Schema completed: VOResource.xsd NVO: Working prototype resource using VOResource as format for metadata exchange using Open Archives Initiative (OAI) Protocol for Metadata Harvesting

Resource & Service Metadata v0.7 Purpose Define resource architecture Common set of metadata that applies to all resources Identity – (ID & Title) Curation – who’s responsible Content – what resource contains (includes coverage) Some resources (services) will be expressed with extended set of metadata Draw on Data Model work

Resource & Service Metadata v0.7 Changes Architecture: everything is a resource… …that is describable and identifiable. Service is a type of resource little direct affect on metadata Additional metadata related to Education & Public Outreach affect primarily Type, Format, & Service Metadata service descriptions include additional metadata which will depend on the service type. 2 Catagories: Interface & Capabilities identified some common concepts that could be reused: ServiceStandardURL, ServiceStandardID, ServiceInterfaceURL, ServiceBaseURL, HTTPGetResults, ServiceMSR

VOResource: an XML Schema for RSM Goals: an extensible schema for use with Registries good definition style for metadata schemas What we have to date: 2 schemas VOResource (v0.1): the RSM metadata VOStdService (v0.3): prototype of service-specific metadata mainly for Simple Image Access xsd files posted on RWP03 Twiki summary document on Twiki with diagrams please comment! More refinement is needed

Specific Classes of Resources inherit from Resource in XML Schema-speak: extend genericResource type put into Resource substitution group can be used in place of Resource can add metadata that is specific to that class of Resource Service metadata to be handled this way.

Service Resource adds 2 sets of metadata: -- Capability -- Interface StdCapability -- extends generic Capability -- meant for Standard Services (e.g. Simple Image Access)

Classes of Interfaces URL that returns GLU Record URL to HTML Form URL of WSDL document

Action Items RSM: VOResource.xsd updates: Open Issues: all projects: review RSM document for completeness/sanity v0.8 VOResource.xsd updates: alignment with v0.7 fill in other incomplete items (e.g. connect to STC) feedback needed! Open Issues: standard for identifiers handling units: standardize? handling mirror sites, sites with similar resources How to interpret missing values Question of granularity: is hierarchy the key?

SIA Interface: expressed in terms of a generic class of Interface VOTable PARAM elements used to describe input parameters Reuse of VOTable elements: -- Registry can execute SIA metadata query (which returns a VOTable) and extract FIELD and PARAM elements and insert directly into registration record. -- (Required slight modification to VOTable.xsd: targetNamespace)

The Generic Resource Metadata (in 3 slides) Identity Metadata PublisherID currently attribute of Resource (managedBy) Curation Metadata

Content Metadata minus Coverage

Content to be defined in external, Coverage Content to be defined in external, specialized schemas use STM ResourceProfile here

Simple Image Access -- specified in SIAP document Content: VOTable FIELD elements Simple Image Access -- specified in SIAP document -- defined in separate schema inherited from StdCapability extended metadata