No subject
Marco
mleoni at eso.org
Mon Jun 16 19:45:07 PDT 2003
Approve:ivordomo
Date: Mon, 16 Jun 2003 16:06:06 -0400
From: "Wil O'Mullane" <womullan at skysrv.pha.jhu.edu>
To: Tony Linde <ael at star.le.ac.uk>
Cc: registry at ivoa.net
Subject: Re: Registry WG: Attention/Action
Message-ID: <20030616160606.B3026 at skysrv.pha.jhu.edu>
References: <004d01c33437$1ca5cf20$6124d28f at gnowee>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <004d01c33437$1ca5cf20$6124d28f at gnowee>; from
ael at star.le.ac.uk on Mon, Jun 16, 2003 at 07:43:00PM +0100
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
> 1. Should the RSM document be a Working Draft (WD), ie a document
approved
> by this group as the basis for a future standard?
Absolutely
> 2. Should RSM (Resource and Service Metadata) be renamed to RM
(Resource
> Metadata)?
NO.
> 3. What structure should the next WD take: a flat one based on Ray's
> VOResource.xsd or a hierarchical one similar to the one's I've
posted
> recently?
VoResourse.XSD is not flat. Its not pretty either but its been around
longer than your proposal, I like VOResource and it Matches pretty
good with the RSM.
We also Agreed our models should be given in XSD form.
So it would seem appropriate to work with VOResource for now.
>
> 4. Should the metadata for a resource be unambiguous and each item
named for
> 4a. Should the basic resource metadata be based on Dublin Core or
should
These seem to be correctly handled at present in the RSM and Roys
prototype.
Again VOResource defines a core for all resources and extentions for
special bits for other resources such as services.
> 5. Should the group discuss the structure of resource metadata now
and only
> issue a new WD when that discussion is more stable or should we
issue a new
> version of RSM/RM and get people to build software based on that
proposal
> and then discuss the structure?
I was under the impression RSM was fairly stable and we have already
built software on it.
We need to get on with all this IVOA work there is not enough time to
design the perfect system and implement any reasonable amount of it.
wil
More information about the registry
mailing list