Sample RIDDL File

[Dave Ings <ings@ca.ibm.com>]

One of the things I'll discuss at today's TC is that the guidance from OASIS regarding RDDL files (more specifically which metadata tags are required) is a bit vague. But for those of you who've actually never seen a RDDL file, attached is the first (incomplete) draft of ours based on the OASIS template.

The problem to be resolved (by me talking to OASIS staff) is that the OASIS template states "insert RDDL metadata here" without specifying what metatags are required by OASIS. Further complicating this is that (AFAIK) this RDDL not a formal W3C recommendation so clear guidance is hard to find.

Fortunately this is all ancillary to the spec, so nothing prevents us from completingg our CS today.

(See attached file: wsb4p-v11-rddl.html)

Regards, Dave Ings,
Emerging Software Standards
Email: ings@ca.ibm.com
Yahoo Messenger: dave_ings

Title: [OASIS Specification Title]

WS-BPEL Extension for People (BPEL4People)

October 28, 2009

Introduction

This document describes version 1.1 of the BPEL4People namespace. It also contains a directory of links to related resources using the Resource Directory Description Language (RDDL) 2.0.

Namespace URI Versioning Policy

It is the intent of the OASIS BPEL4People Technical Committee that the [BPEL4People namespace URI will not change arbitrarily with each subsequent revision of the corresponding WSDL or XML Schema documents but rather change only when a subsequent revision, published in conjunction with a Committee Draft, results in non-backwardly compatible changes from a previously published Committee Draft.

Under this policy, the following are examples of backwards compatible changes that would not result in assignment of a new namespace URI:

• addition of new global element, attribute, complexType and simpleType definitions
• addition of new operations within a WSDL portType or binding (along with the corresponding schema, message and part definitions)
• addition of new elements or attributes in locations covered by a previously specified wildcard
• modifications to the pattern facet of a type definition for which the value-space of the previous definition remains valid or for which the value-space of the preponderance of instance would remain valid
• modifications to the cardinality of elements for which the value-space of possible instance documents conformant to the previous revision of the schema would still be valid with regards to the revised cardinality rule

Related Resources for BPEL4People

Normative Reference:

WS-BPEL4People v1.1

Title:

OASIS WS-BPEL Extension for People V1.1

Stage:

OASIS Committee Draft 5

Date:

28 October 2009

This version:

http://docs.oasis-open.org/bpel4people/bpel4people-1.1-spec-cd-05.html

Previous version:

http://docs.oasis-open.org/bpel4people/bpel4people-1.1-spec-cd-04.html

Technical Committee

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=bpel4people

Chair(s):

Dave Ings, IBM

Editors:

 

Martin Chapman, Oracle

Luc Clement, Active Endpoints

Dave Ings, IBM

Dieter Koenig, IBM

Vinkesh Mehta, Deloitte Consulting LLP

Ralf Mueller, Oracle

Ravi Rangaswamy, Oracle

Michael Rowley, Active Endpoints

Ivana Trikovic, SAP

Additional Formats:

http://docs.oasis-open.org/bpel4people/bpel4people-1.1.doc

http://docs.oasis-open.org/bpel4people/bpel4people-1.1.pdf

Comments list:

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

Comments Archive:

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

XML Schema(s):

 

Related Namespaces (include RDDL metadata)

[list related namespaces and include hyperlinks along with RDDL metadata]