Error column in VOResource

[Tony Linde]

VOTable is not included in VOResource because VOTable is crap at
representing metadata. I agree with Ray that we want to limit metadata creep
for the moment because until we get the DM resolved and have a way of
representing the DM as a schema, we shouldn't increase the metadata in the
registry.

When we do have a decent way of representing metadata then I think the
registry should provide an interface for returning all metadata from a
resource and all that metadata should be in VOResource format - but that
will simply 'include' it from the DM schema.

T.

> -----Original Message-----
> From: owner-registry at eso.org [mailto:owner-registry at eso.org] 
> On Behalf Of Roy Williams
> Sent: 18 May 2004 15:37
> To: Martin Hill; registry at ivoa.net
> Subject: Re: Error column in VOResource
> 
> 
> > Would it be a good idea to include a reference to the 
> associated error 
> > column in a column's description?  eg:
> 
> But what happens when there is an error ellipse, RA, Dec, and 
> the three components RA.RA and Dec.Dec and RA.Dec of the covariance.
> 
> What we have thought of in VOTable is an adjunct structure 
> written in RDF that expresses relationships between the 
> columns, betwwen the columns and UCDs and other relationships.....
> 
> In fact, looking at your XML, may I politely ask why you have 
> chosen not to use the already established VOTable schema? I 
> had always assumed that the reason VOTable is included in 
> VOResource is so that table metadata could be understood by 
> the same software that reads the tables themselves.
> 
> Roy
>