15-day Public Review for Privacy Management Reference Model and Methodology (PMRM) V1.0

The OASIS Privacy Management Reference Model (PMRM) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Privacy Management Reference Model and Methodology (PMRM) Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
13 December 2012

Specification Overview:

The Privacy Management Reference Model and Methodology (PMRM, pronounced “pim-rim”) provides a model and a methodology for:

• understanding and analyzing privacy policies and their privacy management requirements in defined use cases; and

• selecting the technical services which must be implemented to support privacy controls.

It is particularly relevant for use cases in which personal information (PI) flows across regulatory, policy, jurisdictional, and system boundaries. PMRM picks up where broad privacy policies leave off. Most policies describe fair information practices and principles but offer little insight into actual implementation. PMRM provides a guideline or template for developing operational solutions to privacy issues. It also serves as an analytical tool for assessing the completeness of proposed solutions and as the basis for establishing categories and groupings of privacy management controls.

TC Description:

The OASIS PMRM TC works to provide a standards-based framework that will help business process engineers, IT analysts, architects, and developers implement privacy and security policies in their operations.

Public Review Period:

The public review starts 07 January 2013 and ends 22 January 2013. The specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review. Changes are highlighted in the diff-marked PDF file [3]. The record of comments received and their resolution by the TC can be found at [4].

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:

PDF (Authoritative):
http://docs.oasis-open.org/pmrm/PMRM/v1.0/csprd02/PMRM-v1.0-csprd02.pdf

HTML:
http://docs.oasis-open.org/pmrm/PMRM/v1.0/csprd02/PMRM-v1.0-csprd02.html

Editable source:
http://docs.oasis-open.org/pmrm/PMRM/v1.0/csprd02/PMRM-v1.0-csprd02.doc

ZIP distribution files (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/pmrm/PMRM/v1.0/csprd02/PMRM-v1.0-csprd02.zip

Additional information about the specification and the OASIS Privacy Management Reference Model (PMRM) TC may be found at the TC’s public home page located at:

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

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=pmrm

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/pmrm-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 Privacy Management Reference Model and Methodology (PMRM) V1.0, we call your attention to the OASIS IPR Policy [5] applicable especially [6] 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 Privacy Management Reference Model (PMRM) TC
http://www.oasis-open.org/committees/pmrm/

[2] Public Reviews:
30-day public review, 02 June 2012: https://lists.oasis-open.org/archives/tc-announce/201206/msg00001.html

[3] Red-lined diff file
http://docs.oasis-open.org/pmrm/PMRM/v1.0/csprd02/PMRM-v1.0-csprd02-DIFF.pdf

[4] Comment resolution log for Committee Specification Public Review Draft 01
http://docs.oasis-open.org/pmrm/PMRM/v1.0/csprd01/PMRM-v1.0-csprd01-comment-resolution-log-2012-11-25.xlsx

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

[4] http://www.oasis-open.org/committees/pmrm/ipr.php
Non-Assertion Mode
http://www.oasis-open.org/policies-guidelines/ipr#s10.3

Retail Block and Tier Prices Using EMIX Version 1.0 published as a Committee Note

OASIS Members,

We are pleased to announce the approval and publication of an OASIS Committee Note (CN) by the members of the OASIS Energy Market Information Exchange (eMIX) TC [1]:

Retail Block and Tier Prices Using EMIX Version 1.0
Committee Note 01
07 December 2012

Overview:

This Note describes how an application using the EMIX information model can receive Full Requirements Block & Tier Tariffs, (which we abbreviate Block & Tier) and describes how the information can be used by any model rich enough to encompass this sort of price information.

URIs:
The prose specification document and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/emix/emix-block/v1.0/cn01/emix-block-v1.0-cn01.pdf

HTML:
http://docs.oasis-open.org/emix/emix-block/v1.0/cn01/emix-block-v1.0-cn01.html

Editable source:
http://docs.oasis-open.org/emix/emix-block/v1.0/cn01/emix-block-v1.0-cn01.doc

Distribution ZIP files
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/emix/emix-block/v1.0/cn01/emix-block-v1.0-cn01.zip

Members of the OASIS Energy Market Information Exchange (eMIX) TC requested a Special Majority Vote to approve the Committee Note. The Committee Note Draft had been released for public review as required by the TC Process
[2]. The vote to approve at Committee Note (CN) level passed [3], and the approved CN is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] OASIS Energy Market Information Exchange (eMIX) TC
http://www.oasis-open.org/committees/emix/

[2] Public reviews
15-day public review, 22 June 2012: https://lists.oasis-open.org/archives/tc-announce/201206/msg00012.html
30-day public review, 31 October 2011: https://lists.oasis-open.org/archives/tc-announce/201110/msg00015.html

[3] CN ballot
https://www.oasis-open.org/committees/ballot.php?id=2325

Reference Architecture Foundation for Service Oriented Architecture V1.0 CS01 published

OASIS Members,

We are pleased to announce the approval and publication of a new Committee Specification by the members of the Service Oriented Architecture Reference Model TC:

Reference Architecture Foundation for Service Oriented Architecture Version 1.0
Committee Specification 01
04 December 2012

Overview:

This document specifies the OASIS Reference Architecture Foundation for Service Oriented Architecture (SOA-RAF). It follows from the concepts and relationships defined in the OASIS Reference Model for Service Oriented Architecture as well as work conducted in other organizations. While it remains abstract in nature, the current document describes the foundation upon which specific SOA concrete architectures can be built.

The focus of the SOA-RAF is on an approach to integrating business with the information technology needed to support it. These issues are always present but are all the more important when business integration involves crossing ownership boundaries.

The SOA-RAF follows the recommended practice of describing architecture in terms of models, views, and viewpoints, as prescribed in the ANSI/IEEE 1471-2000. It has three main views: the Participation in a SOA Ecosystem view which focuses on the way that participants are part of a Service Oriented Architecture ecosystem; the Realization of a SOA Ecosystem view which addresses the requirements for constructing a SOA-based system in a SOA ecosystem; and the Ownership in a SOA Ecosystem view which focuses on what is meant to own a SOA-based system.

The SOA-RAF is of value to Enterprise Architects, Business and IT Architects as well as CIOs and other senior executives involved in strategic business and IT planning.

URIs:
The prose specification and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/soa-ra-v1.0-cs01.pdf

HTML:
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/soa-ra-v1.0-cs01.html

Editable source:
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/soa-ra-v1.0-cs01.doc

Distribution ZIP files

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

http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/soa-ra-v1.0-cs01.zip

List of Non-Material Changes

This Committee Specification was approved with Non-Material Changes from its final public review. The list of changes can be found in:

http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/changesFromCSPRD03.xlsx

Members of the Service Oriented Architecture Reference Model Technical Committee [1] requested a Special Majority Vote to approve this specification as a Committee Specification. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the approved CS## is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] Service Oriented Architecture Reference Model
http://www.oasis-open.org/committees/soa-rm/

[2] Public reviews:
30-day public review, 14 September 2012: https://lists.oasis-open.org/archives/tc-announce/201209/msg00005.html
60-day public review, 23 August 2011: https://lists.oasis-open.org/archives/tc-announce/201108/msg00009.html
60-day public review, 13 November 2009: http://lists.oasis-open.org/archives/tc-announce/200911/msg00010.html
60-day public review, 9 May 2008: https://lists.oasis-open.org/archives/tc-announce/200805/msg00003.html

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=2322

Electronic Court Filing Version 4.01 Committee Specification 01 approved by the Electronic Court Filing TC

We are pleased to announce the approval and publication of a new Committee Specification by the members of the OASIS LegalXML Electronic Court Filing TC:

Electronic Court Filing Version 4.01
Committee Specification 01
20 November 2012

Overview:

Electronic Court Filing Version 4.01 defines a set of non-proprietary XML and Web services specifications, along with clarifying explanations and amendments to those specifications, that have been added to the ECF specification for the purpose of promoting interoperability among electronic court filing vendors and systems. ECF Version 4.01 is a maintenance release to address several minor schema and definition issues identified by implementers of the ECF 4.0 specification.

URIs:
The prose specification and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/ecf-v4.01-spec-cs01.doc

HTML:
http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/ecf-v4.01-spec-cs01.html

PDF:
http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/ecf-v4.01-spec-cs01.pdf

Additional artifacts:
– XML schemas:
http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/xsd/

– XML sample messages:
http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/xml/

– Model:
http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/model/

– Genericode code lists:
http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/gc/

Distribution ZIP files

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

http://docs.oasis-open.org/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cs01/ecf-v4.01-spec-cs01.zip

Members of the LegalXML Electronic Court Filing Technical Committee [1] requested a Special Majority Vote to approve this specification as a Committee Specification. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the approved CS01 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] LegalXML Electronic Court Filing TC
http://www.oasis-open.org/committees/legalxml-courtfiling/

[2] Public reviews:
15-day public review, 05 April 2012: https://lists.oasis-open.org/archives/tc-announce/201204/msg00003.html
15-day public review, 01 October 2011: http://lists.oasis-open.org/archives/tc-announce/201110/msg00001.html
30-day public review, 26 February 2011: http://lists.oasis-open.org/archives/tc-announce/201102/msg00001.html

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=2318

Read latest issue of OASIS News: 18 Dec

Bimonthly summary of announcements & deadlines

Call for Participation: Biometrics TC

A new OASIS technical committee is being formed. The OASIS Biometrics Technical Committee has been proposed by the members of OASIS listed in the charter below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode and language specified in the proposal will constitute the TC’s official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC’s first meeting.

Please note that the TC Charter received comments during its call for comment period. Comments and their disposition by the co-proposers can be found at https://lists.oasis-open.org/archives/oasis-charter-discuss/201212/msg00004.html.

The eligibility requirements for becoming a participant in the TC at the first meeting are:

(a) you must be an employee or designee of an OASIS member organization or an individual member of OASIS, and


(b) you must join the Technical Committee, which members may do by using the Roster “join group” link on the TC’s web page at [a].

To be considered a voting member at the first meeting:

(a) you must join the Technical Committee at least 7 days prior to the first meeting (on or before 05 February 2013); and


(b) you must attend the first meeting of the TC, at the time and date fixed below (12 February 2013).

Participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties.

Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC’s public home page [c].

Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation.
———-

[a] https://www.oasis-open.org/apps/org/workgroup/biometrics/index.php

[b] See http://www.oasis-open.org/join/


[c] http://www.oasis-open.org/committees/biometrics/

CALL FOR PARTICIPATION

The charter for this TC is as follows.

1) TC Charter

(1)(a) Name of the TC

OASIS Biometrics Technical Committee

(1)(b) Statement of Purpose

Despite existing efforts, opportunities remain for improving interoperability among biometric-related systems or system components.

The purpose of the OASIS Biometrics Technical Committee is to define, enhance, and maintain open standards that facilitate the use of biometrics and biometric operations over a service-oriented architecture, such as web services. Improving interoperability is a key enabler for making biometrics more viable within multi-factor authentication. The Technical Committee will help bring parity to biometrics as compared to other technologies, such as cryptographic certificate use and management, where web services standards are markedly more mature.

Because improving interoperability through open standards is a primary objective, the Technical Committee is dedicated to the concept that conformance to standards will imply a well-documented level of interoperability. Additionally, standards development in the Technical Committee should both minimize and segregate components where requiring unique knowledge hinders interoperability.

(1)(c) Scope of Work

The Technical Committee will provide a general, yet targeted forum for developing a suite of open standards that will foster and accelerate the use of biometrics and biometric services in a distributed environment.

(1)(d) List of Deliverables

* OASIS Specification for WS-Biometric Devices (WS-BD) based on contribution from NIST (estimated 12–18 months from submission) [1]

* Maintenance of the OASIS BIAS SOAP Profile [3] and related work products as required (immediately from first meeting)

* Other standards, guidelines, recommendations, and deliverables as initiated and approved by the Committee (dates of deliverable according to their introduction and coordination within the TC). Excluded is work currently being done in standards development venues (listed in (9)) unless in coordination with the appropriate SDO (e.g., INCITS M1 BIAS and OASIS BIAS SOAP profile projects).

(1)(e) IPR Mode

The Technical Committee will operate under the “RF on Limited Terms” mode of the OASIS IPR Policy [https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3].

(1)(f) Anticipated Audience or Users

The primary audience of the work produced by the Technical Committee will be the biometrics community, the authentication community, and the identity management community.

(1)(g) Language

English shall be the language used to conduct business within the Technical Committee. The Technical Committee may elect to form subcommittees to produce localized documentation of the Committee’s work in additional languages.

(2) Non-Normative Information Regarding TC

(2)(a) Similar or Applicable Work

OASIS has other committees that are related to Biometrics but the committees are run in a very narrow scope: for example, BIAS. This narrow scope may constrain some of the creativity within a TC. It is planned that other biometrics-related work done by other TCs will be moved into this new TC to provide a central location. Other committees from within OASIS can then have a single source of biometrics standards work being performed. Committees focusing on, but not limited to, authentication, e-authentication, and privacy and identity may be able to leverage this work within their own projects. Within the US, INCITS M1 working groups focus on biometrics activities but not related to web services; this is the same within ISO/IEC JTC 1 SC 37. The new committee plans to coordinate and maintain liaison relationships with both committees as well as other committees as discovered.

Activity supporting biometric standardization [5] is underway in many venues worldwide, in de jure bodies (international, national, regional) and in de facto SSOs/SDOs, industry trade groups, inter-agency projects, etc [6]. The OASIS Biometrics TC will seek to align its technical activities and deliverables with these other standardization initiatives in order to support harmonized vocabularies, avoid pointless duplication of effort, and promote interoperability of biometric data exchange and machine processing.

Further, the OASIS Biometrics TC will seek to establish working relationships with other standardization projects in the form of TC Liaisons as may be appropriate for any of its specification development activities.

(2)(b) Date, Time, and Location of First Meeting
The first meeting of the Biometrics will be held by teleconference on February 12, 2013 at 11:00 AM EST. NIST will sponsor the meeting.

(2)(c) Ongoing Meeting Plans and Sponsors

The TC expects to meet monthly by conference call. Sponsorship is to be determined at the first meeting.

(2)(d) Proposers of the TC

1. Kevin Mangold, kevin.mangold@nist.gov, US National Institute of Standards and Technology (NIST)

2. Ross Micheals, ross.micheals@nist.gov, US National Institute of Standards and Technology (NIST)

3. Brad Wing, bradford.wing@nist.gov, US National Institute of Standards and Technology (NIST)

4. Cathy Tilton, cathy.tilton@daon.com, Daon

5. Ryan Triplett, Triplett_Ryan@bah.com, Booz Allen Hamilton

6. Raul Sanchez-Reillo, raul.sanchezreillo@gmail.com, Carlos III University of Madrid

7. Anne Wang, anngwang@cogentsystems.com, 3M Cogent

8. Bob Gupta, bobg@viometric.com, Viometric

9. Anil John, anil.john@gsa.gov, US General Services Administration (GSA)

10. Jeffrey Shultz, jeffrey.k.shultz.ctr@mail.mil, US Department of Defense – Defense Forensices and Biometrics Agengy (DFBA)

(2)(e) Statements of Support

“I, Mary Brady, mary.brady@nist.gov, NIST’s primary representative to OASIS, approve the Biometrics TC charter and endorse all NIST proposers listed in (2)(d).”

“I, Cathy Tilton, cathy.tilton@daon.com, Daon’s primary representative to OASIS, approve the Biometrics TC charter and endorse all Daon proposers listed in (2)(d).”

“I, William Barnhill, barnhill_william@bah.com, Booz Allen Hamilton’s primary representative to OASIS, approve the Biometrics TC charter and endorse all BAH proposers listed in (2)(d).”

“I, Raul Sanchez-Reillo, raul.sanchezreillo@gmail.com, Carlos III University of Madrid’s primary representative to OASIS, approve the Biometrics TC charter and endorse all Carlos III University of Madrid proposers listed in (2)(d).”

“I, Colin Hopkinson, cghopkinson@mmm.com, of 3M, approve the Biometrics TC charter and endorse all 3M Cogent proposers listed in (2)(d).”

“I, Bob Gupta (bobg@viometric.com), Viometrics’s primary representative to OASIS, approve the Biometrics TC charter and endorse all Viometrics proposers listed in (2)(d).”

“I, Anil John, anil.john@gsa.gov, GSA’s primary representative to OASIS, approve the Biometrics TC charter and endorse all GSA proposers listed in (2)(d).”

“I, Gerald Smith, gerald.l.smith180.civ@mail.mil, as Primary Voting Representative for DoD to OASIS, approve the Biometrics TC charter and endorse all DoD proposers listed in (2)(d).”

(2)(f) TC Convener

Kevin Mangold, kevin.mangold@nist.gov, US National Institute of Standards and Technology (NIST) will be the convener.

(2)(g) Member Section Affiliation

(2)(h) Initial Contributions

NIST will contribute its “Specification for WS-Biometric Devices (WS-BD)” [1] as a starting point for one of the key TC deliverables.

(2)(i) FAQ Document

(2)(j) Work Product Titles

=============================
References
=============================

[1] Specification for WS-Biometric Devices (WS-BD)
NIST Special Publication 500-288, Version 1, March 2012
http://www.nist.gov/itl/iad/ig/upload/NIST-SP-500-288-v1.pdf

Summary: “WS-Biometric Devices is a protocol which focuses on
the single process shared by all biometric systems: acquisition
(“capturing a biometric sample with the intention of creating
either a biometric reference or biometric probe”). The
specification provides a framework for deploying and invoking
core synchronous operations via lightweight web service
protocols for the command and control of biometric sensors.
The design of this specification is influenced heavily by the
REST architecture; deviations and tradeoffs were made to
accommodate the inherent mismatches between the REST design
goals and the limitations of devices that are (typically)
oriented for a single-user.”

[2] NIST Biometric Web Services
Including Reference Implementation for Biometric Identity Assurance Services
http://www.nist.gov/itl/iad/ig/bws.cfm

[3] Biometric Identity Assurance Services (BIAS) SOAP Profile Version 1.0
OASIS Standard, 24 May 2012
http://docs.oasis-open.org/bias/soap-profile/v1.0/os/biasprofile-v1.0-os.html

Summary: This profile specifies how to use the Extensible Markup
Language (XML) defined in ANSI INCITS 442-2010 — Biometric
Identity Assurance Services to invoke Simple Object Access
Protocol (SOAP)-based services that implement BIAS operations.
These SOAP-based services enable an application to invoke
biometric identity assurance operations remotely in a Services
Oriented Architecture (SOA) infrastructure. This OASIS BIAS
profile specifies the design concepts and architecture, data
model and data dictionary, message structure and rules, and
error handling necessary to invoke SOAP-based services that
implement BIAS operations. Together, the BIAS standard and
the BIAS profile provide an open framework for deploying and
remotely invoking biometric-based identity assurance capabilities
that can be readily accessed across an SOA infrastructure.”

[4] Biometrics in a Networked World (Kevin Mangold)
http://www.planetbiometrics.com/article-details/i/1271/

[5] ** Biometric Standards: General References **

[6] Getting Started: Biometric Standards (Catherine J. Tilton)
http://www.planetbiometrics.com/article-details/i/499/

[7] Biometric Standards: Interview with Christoph Busch
http://www.planetbiometrics.com/article-details/i/1172/

[8] Advance of Biometric Standards: Fernando Podio
http://www.planetbiometrics.com/article-details/i/1130/

[9] ** Biometric Standardization Venues **

[10] ISO/IEC JTC1 SC 37 (Biometrics)
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_tc_browse.htm?commid=313770
http://www.christoph-busch.de/standards-sc37wg3.html

[11] ISO/IEC JTC 1/SC 17 (Cards and Personal Identification)
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_tc_browse.htm?commid=45144

[12] ISO/IEC JTC 1/SC 27 (IT Security Techniques)
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_tc_browse.htm?commid=45306

[13] ISO TC 68/SC 2 (Financial Services, Security)
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_tc_browse.htm?commid=49670

[14] INCITS/M1, Biometrics Technical Committee
http://standards.incits.org/a/public/group/m1

[15] ITU-T Study Group 17 (SG17)
http://www.itu.int/net/ITU-T/info/sg17.aspx

[16] BioAPI Consortium
http://www.bioapi.org/

[17] International Biometric Industry Association (IBIA)
http://ibia.org/

[18] NIST Information Technology Laboratory (ITL) for Biometrics
http://www.nist.gov/biometrics-portal.cfm

[19] US Defense Forensics and Biometrics Agency (DFBA)
http://www.biometrics.dod.mil/

[20] US National Information Exchange Model (NIEM) Biometrics Domain
https://www.niem.gov/communities/biometrics/Pages/about-bm.aspx

[21] UN International Civil Aviation Organization (ICAO)
[Machine Readable Travel Documents (MRTDs), Biometrics and Border Security]
http://www.icao.int/Meetings/mrtd-Zimbabwe2012/Pages/default.aspx

[22] Unique Identity Authority of India (UIDAI) Aadhaar Project
http://uidai.gov.in/aadhaar.html

[23] VoiceXML Forum [Voice Biometrics]
http://www.voicexml.org/

30-day Public Review for REST Profile of XACML v3.0 Version 1.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:

REST Profile of XACML v3.0 Version 1.0
Committee Specification Draft 01 / Public Review Draft 01
15 November 2012

Specification Overview:

This specification defines a profile for the use of the OASIS eXtensible Access Control Markup Language (XACML), versions 3.0 [XACMLv3] and earlier. Use of this profile requires no changes or extensions to the XACML standard.

This specification begins with a non-normative discussion of the topics and terms of interest in this profile. The normative section of the specification describes the details of web services that conforming implementations must support.

TC Description:

The XACML Technical Committee defines a core XML schema for representing authorization and entitlement policies.

Public Review Period:

The public review starts 14 December 2012 and ends 13 January 2013.

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/xacml-rest/v1.0/csprd01/xacml-rest-v1.0-csprd01.doc

HTML:
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd01/xacml-rest-v1.0-csprd01.html

PDF:
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd01/xacml-rest-v1.0-csprd01.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/xacml-rest/v1.0/csprd01/xacml-rest-v1.0-csprd01.zip

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

https://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 located via the button labeled “Send A Comment” at the top of the TC public home, or directly at:

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xacml

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

https://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 REST Profile of XACML v3.0 Version 1.0, we call your attention to the OASIS IPR Policy [2] applicable especially [3] 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
https://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
RF on Limited Terms Mode
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3

30-day Public Review for Topology and Orchestration Specification for Cloud Applications V1.0

The OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day public review:

Topology and Orchestration Specification for Cloud Applications Version 1.0
Committee Specification Draft 06 / Public Review Draft 01
29 November 2012

Specification Overview:

The concept of a “service template” is used to specify the “topology” (or structure) and “orchestration” (or invocation of management behavior) of IT services (or simply “services” from here on). Typically, services are provisioned in an IT infrastructure and their management behavior needs to be orchestrated in accordance with constraints or policies from there on, for example in order to achieve service level objectives. This specification introduces the formal description of Service Templates, including their structure, properties, and behavior.

TC Description:

The OASIS TOSCA TC works to enhance the portability of cloud applications and services. TOSCA will enable the interoperable description of application and infrastructure cloud services, the relationships between parts of the service, and the operational behavior of these services (e.g., deploy, patch, shutdown)–independent of the supplier creating the service, and any particular cloud provider or hosting technology.

The TC is currently focused on the creation of a non-normative Primer that illustrates suggested use and provides examples based on the TOSCA language. It has also launched an Interoperability Subcommittee.

Public Review Period:

The public review starts 14 December 2012 and ends 13 January 2013.

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:

PDF (Authoritative):
http://docs.oasis-open.org/tosca/TOSCA/v1.0/csprd01/TOSCA-v1.0-csprd01.pdf

HTML:
http://docs.oasis-open.org/tosca/TOSCA/v1.0/csprd01/TOSCA-v1.0-csprd01.html

Editable source:
http://docs.oasis-open.org/tosca/TOSCA/v1.0/csprd01/TOSCA-v1.0-csprd01.doc

XML schema:
http://docs.oasis-open.org/tosca/TOSCA/v1.0/csprd01/schemas/

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/tosca/TOSCA/v1.0/csprd01/TOSCA-v1.0-csprd01.zip

Additional information about the specification and the Topology and Orchestration Specification for Cloud Applications (TOSCA) TC may be found at the TC’s public home page:

https://www.oasis-open.org/committees/tosca

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

https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=tosca

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

https://lists.oasis-open.org/archives/tosca-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 Topology and Orchestration Specification for Cloud Applications V1.0, we call your attention to the OASIS IPR Policy [2] applicable especially [3] 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 Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
https://www.oasis-open.org/committees/tosca

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

[3] http://www.oasis-open.org/committees/tosca/ipr.php
RF on Limited Terms Mode
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.3

SAML V2.0 Asynchronous Single Logout Profile Extension Version 1.0 Committee Specification 01 published

We are pleased to announce the approval and publication of a new Committee Specification by the members of the OASIS Security Services (SAML) TC:

SAML V2.0 Asynchronous Single Logout Profile Extension Version 1.0
Committee Specification 01
22 November 2012

Overview:

This document defines an extension to the SAML 2.0 Single Logout Protocol that allows the initiator to indicate that it does not expect to receive a response from the session authority. This improves user interface interoperability in deployments that want the identity provider to control the user experience during logout.

URIs:
The prose specification and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/cs01/saml-async-slo-v1.0-cs01.odt

HTML:
http://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/cs01/saml-async-slo-v1.0-cs01.html

PDF:
http://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/cs01/saml-async-slo-v1.0-cs01.pdf

XML schema:
http://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/cs01/xsd/

Distribution ZIP files

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

http://docs.oasis-open.org/security/saml/Post2.0/saml-async-slo/v1.0/cs01/saml-async-slo-v1.0-cs01.zip

Members of the Security Services (SAML) Technical Committee [1] requested a Special Majority Vote to approve this specification as a Committee Specification. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the approved CS01 is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] Security Services (SAML) TC
http://www.oasis-open.org/committees/security/

[2] Public reviews:
30-day public review, 28 September 2012: https://lists.oasis-open.org/archives/tc-announce/201209/msg00009.html

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=2320

Read latest issue of OASIS News: 5 Dec

Bimonthly summary of announcements & deadlines

Content Management Interoperability Services (CMIS) Version 1.1 approved and published

We are pleased to announce the approval and publication of a new Committee Specification by the members of the Content Management Interoperability Services (CMIS) TC:

Content Management Interoperability Services (CMIS) Version 1.1
Committee Specification 01
12 November 2012

Overview:

The Content Management Interoperability Services (CMIS) standard defines a domain model and Web Services, Restful AtomPub and browser (JSON) bindings that can be used by applications to work with one or more Content Management repositories/systems.

The CMIS interface is designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. It is not intended to prescribe how specific features should be implemented within those CM systems, nor to exhaustively expose all of the CM system’s capabilities through the CMIS interfaces. Rather, it is intended to define a generic/universal set of capabilities provided by a CM system and a set of services for working with those capabilities.

URIs:
The prose specification and related files are available here:

PDF (Authoritative):
http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/CMIS-v1.1-cs01.pdf

HTML:
http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/CMIS-v1.1-cs01.html

Editable source (tex):
http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/tex/CMIS-v1.1-cs01-source.zip

Additional artifacts:
XML schemas, WSDL and Orderly schema:
http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/schema/

XML and JSON examples:
http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/examples/

Distribution ZIP files

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

http://docs.oasis-open.org/cmis/CMIS/v1.1/cs01/CMIS-v1.1-cs01.zip

Members of the Content Management Interoperability Services (CMIS) Technical Committee [1] requested a Special Majority Vote to approve this specification with Non-Material Changes as a Committee Specification. The specification had been released for public review as required by the TC Process [2]. The vote to approve as a Committee Specification passed [3], and the approved CS## is now available online in the OASIS Library as referenced above.

Our congratulations to the TC on achieving this milestone.

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

[1] Content Management Interoperability Services (CMIS) TC
http://www.oasis-open.org/committees/cmis/

[2] Public reviews:
30-day public review, 10 September 2012: https://lists.oasis-open.org/archives/tc-announce/201209/msg00003.html

[3] Approval ballot:
https://www.oasis-open.org/committees/ballot.php?id=2311

Extended public review for EDXL Distribution Element V2.0

Due to the extensive changes made to the Committee Specification Draft since its last public review, the Emergency Management TC has requested that the public review for Emergency Data Exchange Language (EDXL) Distribution Element Version 2.0, announced on 09 November 2012 in https://lists.oasis-open.org/archives/tc-announce/201211/msg00001.html be extended through 11 January 2013. In addition the TC has requested that the review apply to the entire Committee Specification Public Review Draft and not simply the sections changed since the last review.

The prose specification document and related files are available here:

Editable source (Authoritative):
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.odt (Authoritative)

HTML:
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.html

PDF:
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.pdf

XML Schemas:
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/schema/

XML Examples:
http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/examples/

No results with the selected filters