RE: [regrep] ebXML Registry tutorial - update

["Richard Martell" <rmartell@galdosinc.com>]

> -----Original Message-----
> From: Peter Kacandes [mailto:pkacande@adobe.com]
> Sent: Wednesday, 04 May, 2005 17:24
> To: regrep@lists.oasis-open.org
> Subject: RE: [regrep] ebXML Registry tutorial - update
>
>  Again, I think it is imperative to be clear that what we are
> talking about
> is profiles of Domain Specific Information Models.
>

Hi,

What is the essential purpose of a profile? To tailor the use of one
or more base specifications in some application domain. This means
one can restrict (or extend) the base specifications in such a manner
that the profile does not contradict any of them (e.g., violate a
mandatory constraint).


> Otherwise, it could easily be interpreted as meaning that it
> is talking
> about how to develop a profile of the Registry itself.


For regrep, this would entail extending/restricting ebRIM
and ebRS. In practice, some profiles will be "lighter" than
others and do little more than embellish the canonical artifacts;
others may cast a wider net:

* mapping domain-specific information models to ebRIM; this
  will typically give rise to new object types and/or type
  definitions.

* allow new behaviours if warranted (i.e. stored queries, new query
  facilities, add new interfaces or augment existing ones, make
  use of other standards, etc.)


Now, we will probably want to impose some rules regarding how valid
profiles are constructed. Where should we draw the line? For example,

* only certain canonical schemes may be extended
* only certain RIM types may be extended
* ebRS interfaces cannot be modified (but new ones may be added)


> Without knowing any
> better, the best I would gather from a title like that is
> that perhaps it is
> somehow talking about doing something analogous to how WS-I develops
> profiles of WS specs, but in this case its about a profile of
> the Registry
> spec.
>


This is essentially the case, I think. There is a family of base specs
that may be profiled: ebRIM, ebRS and their dependencies (XACML, SAML,
SOAP, ...). Although for the latter we may urge adoption of existing
profiles from WS-I, IETF, W3C, OASIS, etc.


Hope this clarifies things a bit more.

--
Richard