Registries have very little capacity to store metadata. For example,
it's difficult to store in a registry why I should use a particular
service, how I should use a particular service, when I shouldn't use a
particular service, business SLAs (slightly different from operational
SLAs), etc. Repository metadata can also be used to advertise/promote
services. The registry stores the physical and logical capabilities of
the service whereas the repository gives a designer a complete view of a
particular service. Combined, they provide a single point of information
about the service's capabilities and intended uses.
--
email: [EMAIL PROTECTED]
________________________________
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of
Stefan Tilkov
Sent: Saturday, March 31, 2007 12:50 AM
To: [email protected]
Subject: Re: [service-orientated-architecture] ESB Standard
Definition - SOA capabilities and its categorization
On Mar 30, 2007, at 5:32 PM, Bill Barr wrote:
>
> There seems to be a misunderstanding by many that a Service
> registry is something that a human is going to interact with
directly.
>
> Agreed. Registries are machine-readable and repositories are
human-
> readable. The two need to be aggregated into a single
capability.
>
The one registry I know pretty well, Systinet's UDDI registry,
always
had a user interface -- so I don't see this as a major
distinction.
In my understanding, registries store references to all kinds of
service artifacts and some additional metadata, while
repositories
store the actual artifacts themselves.
Stefan
--
Stefan Tilkov, http://www.innoq.com/blog/st/
<http://www.innoq.com/blog/st/>
