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


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-comresolve message

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

Subject: [regrep-comresolve] Re: FW: [regrep] Using IDREF foraccessControlPolicy


There is no change needed. The way it works is:

-We do not spec ACP today and expect that it is defined out of band with
registry and associated with your object

-We require that ACP have an id like other registry objects

-Any Submitted object may reference an ACP by specifying its ID as an IDREF

-The ACP is never submitted in a SubmitObjectRequest so it can never be in the
same document

-The ID/IDREF linkage is validated by having an ObjectRef with id same as the id
in accessControlPolicy attribute on the RegistryObject.

What this allows is for us to support custom ACP in V2.0 and link a custom ACP
to submitted objects assuming the custom ACP gets into the registry using
registry specific means.

So we dont need to change anything. Validation will work fine if there is an
ObjectRef with the same id as the accessControlProperty attribute value.

If you agree then we can send above explanation out.

"Damodaran, Suresh" wrote:

> Hi guys,
> It seems he is worried about schema validation,
> and it has nothing really to do with accessControlPolicy?
> Perhaps we can remove IDREF?
> What do you think?
> -Suresh
> Sterling Commerce
> -----Original Message-----
> From: Max Voskob [mailto:mvoskob@msi.com.au]
> Sent: Friday, June 14, 2002 3:15 AM
> To: regrep@lists.oasis-open.org
> Subject: [regrep] Using IDREF for accessControlPolicy
> Hi all!
> I'm sorry for littering this honorable mailing list with my silly questions,
> but I'm a bit confused about the schemas. Could someone tell me where I'm
> wrong, please?
> In particular I'm confused about using IDREF type for accessControlPolicy.
> Assume a situation when I get an object with an accessControlPolicy
> attribute
> that references another attribute of type ID which is not in the document.
> The whole document becomes INVALID when logically it is valid.
> Using IDREF in this case forces me, as an implementer, to choose either:
> 1. do not use any validation of registry responses
> OR
> 2. always include a description of all referenced accessSecurityPolicies.
> I would prefer neither of them! I'd like to be able to reference something
> outside of the document and still use schema validation.
> Regards,
> Max Voskob
> MSI Business Solutions:
> Level 12, 67 Albert Ave
> Chatswood NSW 2067
> We are a One to One Business solutions and Consulting Company
> that assists our clients to become Customer-Centric with
> appropriately tailored strategies,services and enabling technologies.
> Office Phone:   +61 2 94128333
> Facsimile:              +61 2 94134275
> Web Site:       http://www.msi.com.au/
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>


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

Powered by eList eXpress LLC