Feedback on Harvesting - providing metadata to harvest

[Tony Linde]

Absolutely right, Elizabeth. A registry will maintain a list of the
AuthorityIDs that it 'owns' and this list will replicate with the resource
records so other registries will know they cannot create such an AuthorityID
nor can they assign a resource to that AuthorityID.

All this is explained in:
  http://www.ivoa.net/Documents/PR/Identifiers/PR-Identifiers-20031031.html

Cheers,
Tony. 

> -----Original Message-----
> From: Elizabeth Auden [mailto:eca at mssl.ucl.ac.uk] 
> Sent: 29 January 2004 12:40
> To: Martin Hill
> Cc: Tony Linde; registry at ivoa.net
> Subject: Re: Feedback on Harvesting - providing metadata to harvest
> 
> 
> Hi Martin,
> 
> > We at the ROE were trying to fill in some example metadata 
> for the 6dF 
> > archive, for harvesting, but are finding it difficult to understand 
> > what the fields are for.  Is there a document describing 
> each element?  
> > We found this:
> 
> The VOResource version 9 file can be found here: 
http://www.ivoa.net/xml/VOResource/, and the other related IVOA schemas are
also on that site.  The identifier is made of the AuthorityID (which should
be unique, but I don't currently know if watertight guidelines for choosing
one - somebody else may be able to better advise) and a ResourceKey, which
is a name that should be unique within your AuthorityID.  For example, if
your AuthorityID is "Astrogrid", then you can have a ResourceKey with value
"MartinHill" or "1XMM_service" even if another AuthorityID like "ESO" also
has a MartinHill or 1XMM_service. That's my understanding, anyway!

cheers,
Elizabeth