OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: How to govern tuples of objects as a single object

There is an open issue in latest spec WD6-3. There is a real world use case for governing multiple objects together. An example is from Geospatial domain where a service is described by its WSDL as well as by an XML file providing geographic metadata that conforms to the ISO 19139 specification. In this example we need to govern the WSDL + ISO19139 file together as if they were one object being governed by the governance collaboration.

I would like to propose the following text to be added as section 10.2 in the next draft of the spec.

With this text there would be two distinctly diferent uses of RegistryPackages in governance.

1. Using a RegistryPackage to assign a governance collaboration to its members (as already described in 10.2, 10.3 in WD6-3). In this use the RegistryPackage serves as a folder

2. Using a RegistryPackage as the targetObject for a governance collaboration where it acts like a tuple and its members are a set of objects that need to be governed as if they were a single object

Here is the proposed text to be added to the next draft WD6-4 .... Lets discuss today.

------------------------------Begin Proposed text ------------------------------------

10.2 Scope of Governance Collaborations

A governance collaboration may govern a single RegistryObject or it may govern a set of related RegistryObjects packaged together within a RegistryPackage as a single unit of governance. In either case, the target object of the governance collaboration is referred to as the governed object.

10.2.1 Packaging Related Objects as a Governance Unit

A client MUST publish a set of related RegistryObjects that are to be governed by the server as a single unit as follows:

  • The objects MUST be immediate members of the same RegistryPackage

  • The RegistryPackage MUST have a canonical slot with name “urn:oasis:names:tc:ebxml-regrep:rim:RegistryPackage:packageType”

  • The value of the packageType slot MUST be a unique identifier for the type of package of which the group of related objects are an instance

A server MUST treat RegistryPackages with a canonical slot with name “urn:oasis:names:tc:ebxml-regrep:rim:RegistryPackage:packageType” as the governed object.

Farrukh Najmi

Web: http://www.wellfleetsoftware.com

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]