registry-updatable data

[Aurelien Stebe]

I have a few comments on this :
- I think the "status" attribute should stay with the resource record, 
and a "liveliness", as was suggested at first, would be put in the 
recordCuration
- The "curator" element could be a ResourceName type, to get both the 
human readable name and the ivo-id.
- two verification levels : one for the metadata and one for the actual 
service

The problem I see with all this is that it would change the level of the 
resource metadata.
It was : VOResources/Resource .... it would become : 
VOResources/resourceRecord/profile
It might be a problem during the transition.

cheers,
Aurelien

KevinBenson wrote:

>Yes all sounds good,  as for the stampedidentifier area.  Yes you got what I
>am saying.  I am thinking now maybe it simply is just the same identifier
>that is in the ri:profile.  You might be right this is probably redundent; I
>keep trying to find the idea of possibly only querying for recordCuration
>such that an app/service might want to just get a listing of what
>identifiers (recordCuration) that has verificationLevel < 2 set by
>nvo.registry.
>
>But maybe for now we always bring back Resources, unless somebody could see
>a good idea of just having the recordCuration.
>
>cheers,
>Kevin
>
>  
>