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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

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


Subject: RE: [xacml] 30-day Public Review for XACML Intellectual Property Control (IPC) Profile V1.0


On behalf of TSCP (www.tscp.org), please find enclosed our feedback to the XACML Intellectual Property Control (IPC) Profile Version 1.0 Committee Specification Draft 03 / Public Review Draft 03. We would be happy to contribute examples regarding the section below on "Usability of the profile".

 

Usability of the profile

        We expected that some element of the _expression_ of the access rules to be normatively defined (instead of as non-normative examples, like in section 4). TSCP can contribute an example.

        TSCP expects to see elements of workflow, guidance, or business policy on, how to use this technical profile

Clarification

        Lines [72], [119]. Repeated and overlapped definitions between Affiliation-type, Organization-type and Organizational-relationship:

        Picture line [186]. Lack of consistency. surely you want to show Organization-relationship expressed on relation between subject and organization (i.e. “employee” or “contractor”, instead of “organization”)

Data Model

        Line [237]. Is there a need to express patents between organizations? If so we expect to express multiple attributes instead of a single one, which type to be a string or URI (instead of a Boolean), that could convey the patent number

        Line [186]. How is the organization-relationship attribute associated with the contract that binds two organizations together? This concept does not appear

        Lines [303], [311]. In order to allow for time-zone support, is it possible to express dates as “XMLSchema#dateTime” instead of “XMLSchema#date”? Note that this is how the example line [493] expresses dates

Interoperability

        Lines [258], [324]. TSCP would like to contribute how it expresses organization identifiers to better promote interoperability, by mean of a URI (example: “urn:duns:834951691”)

Implementation question

        Lines [337], [895]. How can the PEP determine the subject attribute “organizational-relationship”, that is business context and resource dependent (i.e. this is not an autonomous attribute of the subject, as the value depends upon the resource and in particular, of the organization owning the resource)?

 

With regards,

Jean-Paul Buu-Sao

TSCP Information Labeling and Handling - Lead Architect

 

-----Original Message-----
From: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org] On Behalf Of Chet Ensign
Sent: Thursday, July 19, 2012 20:19
To: tc-announce@lists.oasis-open.org; members@lists.oasis-open.org; xacml@lists.oasis-open.org
Subject: [xacml] 30-day Public Review for XACML Intellectual Property Control (IPC) Profile V1.0

 

The OASIS eXtensible Access Control Markup Language (XACML) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day public review:

 

XACML Intellectual Property Control (IPC) Profile Version 1.0 Committee Specification Draft 03 / Public Review Draft 03

17 May 2012

 

Specification Overview:

 

This specification defines a profile for the use of XACML in expressing policies for intellectual property control (IPC). It defines standard attribute identifiers useful in such policies, and recommends attribute value ranges for certain attributes.

 

TC Description:

 

The XACML Technical Committee defines schemas for representing authorization and entitlement policies. This Profile deals with defining Policies for securing Intellectual Property assets.

 

Public Review Period:

 

The public review starts 20 July 2012 and ends 19 August 2012.

 

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

 

URIs:

 

The prose specification document and related files are available here:

 

Editable Source (Authoritative):

http://docs.oasis-open.org/xacml/3.0/ipc/v1.0/csprd03/xacml-3.0-ipc-v1.0-csprd03-en.doc

 

HTML:

http://docs.oasis-open.org/xacml/3.0/ipc/v1.0/csprd03/xacml-3.0-ipc-v1.0-csprd03-en.html

 

PDF:

http://docs.oasis-open.org/xacml/3.0/ipc/v1.0/csprd03/xacml-3.0-ipc-v1.0-csprd03-en.pdf

 

ZIP distribution file (complete):

For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:

http://docs.oasis-open.org/xacml/3.0/ipc/v1.0/csprd03/xacml-3.0-ipc-v1.0-csprd03-en.zip

 

Additional information about the specification and the OASIS eXtensible Access Control Markup Language (XACML) TC may be found at the TC's public home page located at:

http://www.oasis-open.org/committees/xacml/

 

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled "Send A Comment" at the top of the TC public home page, or directly at:

http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=xacml

 

Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:

http://lists.oasis-open.org/archives/xacml-comment/

 

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of XACML Intellectual Property Control (IPC) Profile Version 1.0, we call your attention to the OASIS IPR Policy [2] applicable especially [3.0] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification.

 

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.

 

========== Additional references:

 

[1] OASIS eXtensible Access Control Markup Language (XACML) TC http://www.oasis-open.org/committees/xacml/

 

[2] http://www.oasis-open.org/who/intellectualproperty.php

 

[3] http://www.oasis-open.org/committees/xacml/ipr.php

http://www.oasis-open.org/who/intellectualproperty.php#s10.2.3

RF on Limited Terms

 

/chet

----------------

Chet Ensign

Director of Standards Development and TC Administration

OASIS: Advancing open standards for the information society http://www.oasis-open.org

 

Primary: +1 973-996-2298

Mobile: +1 201-341-1393

 

---------------------------------------------------------------------

To unsubscribe, e-mail: xacml-unsubscribe@lists.oasis-open.org

For additional commands, e-mail: xacml-help@lists.oasis-open.org

 



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