15-day Public Review for XACML Export Compliance US Profile V1.0

The OASIS eXtensible Access Control Markup Language (XACML) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

XACML 3.0 Export Compliance US (EC-US) Profile Version 1.0
Committee Specification Draft 04 / Public Review Draft 02
28 June 2012

Specification Overview:
This specification defines a profile for the use of XACML in expressing policies for complying with USA government regulations for export compliance (EC). It defines standard attribute identifiers useful in such policies, and recommends attribute value ranges for certain attributes.

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

Public Review Period:
The public review starts 6 September 2012 and ends 21 September 2012. 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 included in the release package.

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 complete package of the prose specification document and related files are available in the ZIP distribution file at:

https://www.oasis-open.org/committees/download.php/46826/xacml-3.0-ec-us-v1.0-csprd02.zip

Additional information about the specification and the OASIS 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 3.0 Export Compliance US (EC-US) Profile Version 1.0, we call your attention to the OASIS IPR Policy [3] applicable especially [4] 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] Public Reviews:
60-day public review, 23 October 2009: https://lists.oasis-open.org/archives/tc-announce/200910/msg00012.html

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

[4] http://www.oasis-open.org/committees/xacml/ipr.php
http://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Terms mode

15-day Public Review for ICOM for Interoperable Collaboration Services V1.0

The OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:

Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0
Committee Specification Draft 04 / Public Review Draft 04
08 August 2012

Specification Overview:
The Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services defines a framework for integrating a broad range of domain models for collaboration activities in an integrated and interoperable collaboration environment.

The framework is not intended to prescribe how applications or services conforming to its model implement, store, or transport the data for objects. It is intended as a basis for integrating a broad range of collaboration objects to enable seamless transitions across collaboration activities. This enables applications to maintain a complete thread of conversations across multiple collaboration activities.

The model integrates a broad range of collaboration activities, by encompassing and improving on a range of models which are part of existing standards and technologies. The model is modular to allow extensibility. The core concepts, metadata concepts, and their relations are included in the Core, while the specific concepts and relations for each area of collaboration activities are defined in separate extension modules.

The framework lowers the barrier for independent software vendors and open source communities to integrate collaboration services and to create collaboration tools that offer seamless user experience for diverse collaboration activities with minimal context switching.

TC Description:
The OASIS ICOM TC works to define a standard for integrated and interoperable enterprise collaboration.

Public Review Period:
The public review starts 6 September 2012 and ends 21 September 2012. 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 included in the release package.

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 complete package of the prose specification document and related files are available in the ZIP distribution file at:

http://www.oasis-open.org/committees/download.php/46823/icom-ics-v1.0-csprd04.zip

Additional information about the specification and the OASIS ICOM TC may be found at the TC’s public home page located at:

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

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

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/icom-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 Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services Version 1.0, we call your attention to the OASIS IPR Policy [3] applicable especially [4] 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 Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC
http://www.oasis-open.org/committees/icom/

[2] Public Reviews:
15-day public review, 11 May 2012: https://lists.oasis-open.org/archives/tc-announce/201205/msg00004.html
15-day public review, 20 November 2011: http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/201111/msg00010.html
30-day public review, 19 May 2011: http://lists.oasis-open.org/archives/tc-announce/201105/msg00002.html

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

[4] http://www.oasis-open.org/committees/icom/ipr.php
http://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Terms mode

IDtrust re-elects Peter Alterman (SAFE BioPharma) & Bruce Rich (IBM) to Steering Cmte

Register for KMIP V.Next webinar, 25 Sept

“Addressing New Complexities in Key Management Interoperability”

OASIS Launches Initiative to Standardize REST-based Open Data Protocol (OData)

27 August 2012 – The OASIS international consortium has launched a new initiative that will standardize OData, a REST-based protocol that simplifies the querying and sharing of data across applications for re-use in the enterprise, Cloud, and mobile devices. OData enables information to be accessed from a variety of sources including relational databases, file systems, content management systems, and traditional Web sites. Addressing the demands of cloud computing, OData helps create a more open and programmable Web by providing a common approach to exposing and consuming data.

More than 57 members from around the world are now participating in the OASIS OData Technical Committee. Work has already begun. The group recently convened its first meeting where members agreed on a work agenda, elected co-chairs, and welcomed new supporters of the initiative.

“The timing was right to transition OData to a recognized, open-standards process, and OASIS was a natural choice,” noted Barbara Hartel of SAP AG, co-chair of the OASIS OData Technical Committee. “Our focus with OASIS is to build on version 3 of the core OData protocol. We intend to address requirements for extensions related to data aggregation, temporal data, JSON documents, and XML documents as streams.”

“The formation of the OASIS Technical Committee is an important next step in the advancement of OData as an open and interoperable protocol. We expect the work done by the OData Technical Committee to open up new possibilities in providing open data for the open web,” said Ram Jeya-raman of Microsoft Open Technologies, Inc., a subsidiary of Microsoft Corporation, co-chair of the OASIS OData Technical Committee.

OData began as an open project on the public OData site three years ago. OData producers, consumers and libraries (many of them open source) include Java, PHP, Drupal, Joomla, Node.js, .NET, SQL Server, MySQL, iOS, WP7, and Android.

Microsoft has contributed seven OData specification components, and IBM, Microsoft, and SAP have contributed four OData extension proposals to the OASIS OData Technical Committee.

“We’re seeing a wave of Cloud standardization projects at OASIS that use REST, AtomPub, and JSON technology,” said Laurent Liscia, OASIS executive director. “OData is an exciting addition to our portfolio. The response to the new Committee has been tremendous.”

The OData Technical Committee is open to all interested parties, and new members are encouraged to join at any time. Archives of the work are accessible to both members and non-members, and OASIS invites public review and comment on the work.

Support for OData

Axway
“The OASIS OData Technical Committee will openly review and enhance the OData submissions for REST-style access to URL identified data resources. OData leverages existing open standards, protocols and formats (AtomPub, XML, JSON and others) and, when combined with emerging web authorization standards, should provide useful technology conventions attracting a diverse range of developers.”
–Dale Moberg, Chief Architect, Axway

CA Technologies
“By tackling the problem of common data access, OASIS is taking a significant step in standardizing the way information is shared between applications and solutions. OData shows great potential in unlocking enterprise and cloud data across vendors and platforms, allowing our customers to more fully understand their business.”
— Don Kleinschnitz, Chief Development Officer, CA Technologies

IBM
“Five pillars of a modern IT shop are open source, open standards, open clouds, open data, and open APIs. IBM congratulates the OASIS community on its progress and efforts. Maturing the OData API as an open standard helps ensure it is an enterprise developer asset for software interoperability.”
— Todd Moore, Director Infrastructure Standards and Partnerships, IBM Software Group

Microsoft
“OData has become an important open protocol for several products across Microsoft to accomplish the goal of open data for the open Web. It’s encouraging to see numerous implementations across the industry, and this productive standards collaboration at OASIS.”
–Gianugo Rabellino, Senior Director of Microsoft Open Technologies, Inc.

Progress Software
“DataDirect works to ensure that it’s at the forefront of the development of all emerging data access stand-ards. As we’ve done with ODBC and JDBC, we want to help shape the future of standards in the cloud and provide our customers with the widest array of data access options available. We look forward to working with the OData Technical Committee to that end.”
–Jesse Davis, Director, DataDirect Research and Development, Progress Software

Red Hat
“Red Hat is pleased to be supporting the OData Technical Committee. We believe that the aims behind the Open Data Protocol are in line with the increased adoption of REST and other Web technologies in the enterprise space today, and we intend to work with the TC to ensure this continues.”
–Dr. Mark Little, Senior Technical Director, Red Hat

SAP
“SAP is committed to helping drive the standardization of OData at OASIS, and it’s good to see broad industry support for the OData Technical Committee. This is important to refine the OData specifications and ensure their applicability in diverse usage scenarios, which, in turn, is important for SAP customers. The broader the support for OData on application platforms, Web environments, and mobile device technologies, the more developers can rely on the standard and focus on building beautiful apps that consume data services exposed by SAP NetWeaver Gateway® technology.”
— Claus von Riegen, VP, Industry Standards and Open Source, SAP

SDL
“SDL, provider of Global Information Management solutions, is pleased to see the OASIS effort to standardize the AtomPub-based OData protocol, while at the same time improving and expanding on the protocol’s existing capabilities. SDL has pioneered the use of OData in its Web Content Management product SDL Tridion, believing that this will eventually lead to better integration and interoperability across information providers and information consumers in the enterprise and in the web.”
— Dennis van der Veeke, CTO at SDL

Additional information:
OASIS OData Technical Committee

About OASIS:
OASIS is a not-for-profit, international consortium that drives the development, convergence and adoption of open standards for the global information society. OASIS promotes industry consensus and produces worldwide standards for cloud computing, content technologies, business transactions, security, privacy, SOA, the Smart Grid, emergency management, and other applications. OASIS open standards offer the potential to lower cost, stimulate innovation, grow global markets, and protect the right of free choice of technology. OASIS members broadly represent the marketplace of public and private sector technology leaders, users, and influencers. The consortium has more than 5,000 participants representing over 600 organizations and individual members in 100 countries.

Press contact:
communications@oasis-open.org

Read latest issue of OASIS News: 17 Aug

Bimonthly summary of announcements & deadlines

Members Approve Biometric Identity Assurance Services (BIAS) SOAP Profile as OASIS Standard

15 August 2012 – Members of the OASIS international standards consortium have approved the Biometric Identity Assurance Services (BIAS) SOAP Profile as an OASIS Standard, a status that signifies the highest level of ratification. The BIAS SOAP Profile defines a method for performing biometric operations within a Services Oriented Architecture (SOA) using XML and SOAP Web services messaging.

The BIAS SOAP Profile is a specific implementation (or binding) of ANSI INCITS 442-2010. The INCITS standard defines the requirements for BIAS operations and data elements which can be implemented using any encoding scheme or messaging protocol, whereas the OASIS standard defines a conformant implementation. These SOAP-based services enable a software application (requester) to invoke biometric identity assurance operations provided by a local or remote BIAS service provider (responder).

“Biometric systems are becoming more complex as they are integrated into larger identity management and credentialing systems. They are increasingly being used in large-scale systems built on an SOA,” explained Kevin Mangold of the US NIST, co-chair of the OASIS BIAS Integration Technical Committee. “In these environments, the BIAS SOAP Profile makes it possible for data to be shared and resources and services to be reused within and across organizations.”

“We are excited to achieve the milestone of becoming an official OASIS Standard,” said Catherine Tilton of Daon, co-chair of the OASIS BIAS Integration Technical Committee. “The BIAS SOAP Profile is much needed for facilitating service-based communication between heterogeneous biometric systems and subsystems. We look forward to BIAS being widely adopted within a variety of applications.”

To aid in the development of operational BIAS implementations, the US NIST has developed a basic reference implementation of the OASIS BIAS specification, implementing all of its major biometric capabilities (i.e., enroll/verify/identify). The provided source contains a cross-language solution comprising a standalone Web service (VB.NET) and client (Adobe Flex). This implementation is freely available for download.

BIAS is intended to be used in open systems alongside related standards such as the Web services for Biometric Devices (WS-BD) from US NIST. WS-BD handles the biometric capture device interface (front-end functionality), while BIAS addresses the backend biometric services.

Participation in the OASIS BIAS Integration Technical Committee is open to all interested parties. Archives of the Committees’ work are accessible to both members and non-members, and OASIS invites public review and comment. Going forward, the Committee intends to broaden its scope, potentially to include a BIAS REST Profile.

Additional information
OASIS BIAS Integration Technical Committee

BIAS SOAP Profile, WSDL and XML schema files

About OASIS
OASIS is a not-for-profit, international consortium that drives the development, convergence and adoption of open standards for the global information society. OASIS promotes industry consensus and produces worldwide standards for identity, security, cloud computing, business transactions, Smart Grid, content management, and other applications. OASIS open standards offer the potential to lower cost, stimulate innovation, grow global markets, and protect the right of free choice of technology. OASIS members broadly represent the marketplace of public and private sector technology leaders, users and influencers. The consortium has more than 5,000 participants representing over 600 organizations and individual members in 100 countries.

Press contact
Carol Geyer
OASIS Senior Director
carol.geyer@oasis-open.org

60-day Public Review for Advanced Message Queueing Protocol (AMQP) v1.0 Candidate OASIS Standard (COS)

Members of the OASIS Advanced Message Queuing Protocol (AMQP) TC [1] have recently approved a Special Majority Ballot [2] to advance OASIS Advanced Message Queueing Protocol (AMQP) Version 1.0 Committee Specification 01 as a Candidate OASIS Standard (COS). The COS now enters a 60-day public review period in preparation for a member ballot to consider its approval as an OASIS Standard.

OASIS Advanced Message Queueing Protocol (AMQP) Version 1.0
Candidate OASIS Standard 01
07 August 2012

Specification Overview:

AMQP (Advanced Message Queueing Protocol) is an efficient, reliable, wire level messaging protocol supporting common middleware messaging interaction patterns: messaging, request/response, publish/subscribe, transactions, and store and forward. It allows middleware applications to communicate with each other without having to have the same infrastructure on both ends (i.e. it provides vendor-neutral communications).

Like all communication protocols, AMQP describes the message syntax and sequence for performing their different assigned tasks. AMQP is capable of being used in both synchronous (point-to-point) and asynchronous (broker based) architectures and is independent of any particular broker architecture. AMQP is of special importance in providing enterprise and cloud messaging services.

Five statements of use for this COS were received from IIT Software GmbH., INETCO Systems Ltd., Microsoft, Red Hat and Storm MQ [3].

Public Review Period:

The 60-day public review starts 14 August 2012 and ends 13 October 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 complete Candidate OASIS Standard is available in PDF, HTML (six parts), and XML (six parts) formats in the OASIS Library at:

http://docs.oasis-open.org/amqp/core/v1.0/cos01/

PDF:

http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-complete-v1.0-cos01.pdf

The HTML AMQP Overview file, which contains links to all other HTML parts, may be accessed at:

http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-overview-v1.0-cos01.html

Distribution ZIP file:

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

http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-cos01.zip

Additional information about the specification and the OASIS Advanced Message Queueing Protocol (AMQP) TC may be found at the TC’s public home page:

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

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 page, or directly at:

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

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

http://lists.oasis-open.org/archives/amqp-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 Test Assertions Part 1: Test Assertions Model Version 1.0, we call your attention to the OASIS IPR Policy [4] applicable especially [5] 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.

==============

[1] OASIS Advanced Message Queuing Protocol (AMQP) TC

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

[2] Candidate OASIS Standard ballot

https://www.oasis-open.org/committees/ballot.php?id=2272

[3] Links to Statements of Use

IIT Software GmbH:
https://lists.oasis-open.org/archives/amqp/201207/msg00049.html

INETCO Systems Ltd.:
https://lists.oasis-open.org/archives/amqp/201207/msg00054.html

Microsoft:
https://lists.oasis-open.org/archives/amqp/201207/msg00053.html

Red Hat:
https://lists.oasis-open.org/archives/amqp/201207/msg00060.html

StormMQ:
https://lists.oasis-open.org/archives/amqp/201207/msg00044.html

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

[5] http://www.oasis-open.org/committees/amqp/ipr.php
RF on RAND Terms
https://www.oasis-open.org/policies-guidelines/ipr#s10.2.2

Join “Big Data and Standards Forum”

New LinkedIn Group explores role of standards in big data

Read latest issue of OASIS News: 2 Aug

Bimonthly summary of announcements & deadlines

The OASIS Provisioning Services TC has closed

At the request of the Technical Committee, the OASIS Provisioning Services TC has been closed.

The Provisioning Services TC was formed in 2001 to develop a standard, XML-based framework for creating and managing information that represents user identities and related entities. Service Provisioning Markup Language (SPML) version 1.0 was approved as an OASIS Standard by the membership in 2003 (https://www.oasis-open.org/news/pr/service-provisioning-markup-language-spml-ratified-as-oasis-standard).

SPML 1.0 was the first standard to describe a comprehensive set of identity management operations based on a vendor-independent model. SPML 2.0, approved by the membership in 2006, built further by separating protocol definition from payload description, and by providing DSML and XSD profiles. SPML 2.0 has been widely implemented by application software and identity management vendors and is the standard of record in this area. More recently, the technical committee published proposals (RESTpml, SIMPLEST) for a simpler REST-oriented binding of SPML 2.0.

Links to SPML version 1.0, SPML version 2.0 and Service Provisioning Markup Language (SPML) Version 2 Errata, approved by the TC in December 2007 can be accessed on the TC’s home page at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=provision#technical.

As is standard OASIS policy, the archives of the Technical Committee will remain publicly visible on TC’s web site at http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=provision. The TC’s email list has been closed but the archive will remain available at http://lists.oasis-open.org/archives/provision/. The comments email will remain open and will be accessible at http://lists.oasis-open.org/archives/provision-comment/.

We congratulate all the members and leaders of the TC for their contributions and dedication to the development and delivery of the SPML Standards.

15-day Public Review for FFM Integration Interface Specification V1.0

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

Field Force Management Integration Interface Specification Version 1.0
Committee Specification Draft 02 / Public Review Draft 02
09 July 2012

Specification Overview:
This document describes the Field Force Management Integration Interface (FFMII). FFMII provides a flexible interface between Enterprise Resource Management System (ERMS) and Field Force Management System (FFMS).

The role of ERMS is to take a holistic view at work scheduling and resource allocation from the corporate point of view. For this purpose it needs to manage individual units of work performed without strong supervisory guidance (Field Work) in a way aligned with the business objectives of the company. The role of FFMS is to communicate with available set of workers (Field Force) and to provide individual workers (Assignees) performing Field Work with technical means of accessing information about and sending feedback on work assigned to them. While ERMS defines the structure, content and resource allocation of dispatched work, FFMS is responsible for communicating that information to the field and enforcing any specified constraints on user provided feedback.

For facilitating structured communication between ERMS and FFMS in heterogeneous scenarios, FFMII defines flexible mechanisms that enable Work Request modeling (data content, workflow), exchange, work history collection, and collection of data from the field. Information carried with work requests, work request structure (work-flow, schedule) and data to be collected can all be defined dynamically ‘as data’. This data driven architecture makes FFMII very flexible and adaptable to numerous industries. Additional FFMII capabilities include Field-Initiated Requests that facilitate structured requests and reporting information outside the usual work flow, such as reporting absence, requesting additional work, or providing a sales lead. Reference Data Management provides means to establish custom data repositories with arbitrary content. This enables e.g. input value selection, content validation, or delivery of documents to Field Force. Furthermore, flexible Integration Topologies are supported. Further flexibility is provided by scalability of FFMII itself: Basic features of FFMII are mandatory, and some features are optional. This allows both simple basic implementations and a range of more complete implementations.

Public Review Period:
The public review starts 1 August 2012 and ends 16 August 2012. 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 included in the release package.

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 complete package of the prose specification document and related files are available in the ZIP distribution file at:

https://www.oasis-open.org/committees/download.php/46595/FFMII-Specification-v1.0-csprd02.zip

Additional information about the specification and the Field Force Management (FFM) TC may be found at the TC’s public home page:

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

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:

http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ffm

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

http://lists.oasis-open.org/archives/ffm-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 Field Force Management Integration Interface Specification Version 1.0, we call your attention to the OASIS IPR Policy [3] applicable especially [4] 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 Field Force Management (FFM) TC
http://www.oasis-open.org/committees/ffm/

[2] Public Reviews:
30-day public review, 29 May 2012: https://lists.oasis-open.org/archives/tc-announce/201205/msg00014.html

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

[4] http://www.oasis-open.org/committees/ffm/ipr.php
http://www.oasis-open.org/policies-guidelines/ipr#s10.2.3
RF on Limited Mode

No results with the selected filters