STC in VOResource records

[Arnold Rots]

Gretchen,

What do you mean by "requiring to enforce uniqueness"?
The problem, from the Registry's point of view, is that STC _is_
enforcing uniqueness.

  - Arnold

Gretchen Greene wrote:
> Ray,
> 
> Thank you for the summary and thanks to the discoverer of the problem before
> the rest of us catch up!
> 
> I would advocate requiring the STC and VOResource to enforce uniqueness in
> their schemas for these ids rather than a programmatic temporary solution.
> In respect of the issue for expediency,  how long would it take to make the
> schema change (VOResource?, STC?).  It sounds like there are known methods.
> 
> This has to happen sometime,  so should we wait until all the registries and
> applications are in full operation to make the schema change?  
> 
> I'm open to whatever solution is decided upon but leaning toward a
> preference of having the schemas corrected.  
> 
> Since we are only now preparing to release VOResource 1.0 registries,  it is
> a perfect time to get in a last change.  As for the STC schema constraint,
> this conflict will not be unique to registries.  
> 
> -Gretchen
> 
--------------------------------------------------------------------------
Arnold H. Rots                                Chandra X-ray Science Center
Smithsonian Astrophysical Observatory                tel:  +1 617 496 7701
60 Garden Street, MS 67                              fax:  +1 617 495 7356
Cambridge, MA 02138                             arots at head.cfa.harvard.edu
USA                                     http://hea-www.harvard.edu/~arots/
--------------------------------------------------------------------------