[Registry-dev] Name value pairs and tags

[Chathura C. Ekanayake]

Hi Paul,

Paul Fremantle wrote:
> I was at a SOA day last week and there was a considerable discussion 
> of "SOA Governance" by which a lot of people simply meant having a 
> registry and a process around which services met which criteria.
>
> One of the things that it seems people need to do this is simply the 
> ability to capture name=value properties (String,String) against an 
> resource. For example, the ability to capture in a standard place that 
> this service has passed a compliance test, or that another service has 
> been approved to move into production.

We have a java.util.Properties variable in the Resource class. So that 
the resources can have name=value properties associated with them. Once 
media type processing is introduced, we can also enforce certain 
properties for given media types. For example, WSDL resources should 
have a compliance_test_status property, which can be set to passed or 
failed.

Thanks,
Chathura

>
> We could capture these using some kind of additional resource (an XML 
> or JSON file), however it occurred to me that there is a lot of 
> similarity with tags, so maybe it would be better to expand the tag 
> concept to cover values as well (e.g. tag={optional value}
>
> Paul
>