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


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

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

Subject: OASIS TC Call For Participation: OASIS XDI TC

A new OASIS technical committee is being formed. The OASIS XRI Data 
Interchange (XDI) Technical Committee has been proposed by the following 
members of OASIS: Geoffrey Strongin, AMD; Dave McAlpin, Davis McPherson, 
and Loren West, Epok; Xavier Serrett, Gemplus; Peter Davis, Neustar; Nat 
Sakimura, Tetsu Watanabe, Kouichi Nishikata, Tomonori Seki, and Jun 
Eijima, NRI; Marc Le Maitre, Drummond Reed, and Sean Vanderdasson, 
Cordance; Lark Allen, Wave Systems; Bill Washburn and Michael Willett, 
XNSORG; and Owen Davis, Planetworks.

The proposal for a new TC meets the requirements of the OASIS TC Process 
(see http://oasis-open.org/committees/process.shtml), and is appended to 
this message. The TC name, statement of purpose, scope, list of 
deliverables, audience, and language specified in the proposal will 
constitute the TC's charter. The TC Process allows these items to be 
clarified (revised); such clarifications (revisions), as well as 
submissions of technology for consideration by the TC and the beginning 
of technical discussions, may occur no sooner than the TC's first meeting.

As specified by the OASIS TC Process, the requirements for becoming a 
member of the TC at the first meeting are that you must 1) be an 
employee of an OASIS member organization or an Individual member of 
OASIS; 2) notify the TC chair of your intent to participate at least 15 
days prior to the first meeting; and 3) attend the first meeting of the 
TC. For OASIS members, to register for the TC go to the TC's public web 
page at http://www.oasis-open.org/committees/xdi and click on the button 
for "Join This TC" at the top of the page. You may add yourself to the 
roster of the TC either as a Prospective Member (if you intend to become 
a member of the TC) or an Observer. A notice will automatically be sent 
to the TC chair, which fulfills requirement #2 above.

OASIS members may also join the TC after the first meeting. Note that 
membership in OASIS TCs is by individual, and not by organization.

Non-OASIS members may read the TC's mail list archive, view the TC's web 
page, and send comments to the TC using a web form available on the TC's 
web page; click the "Send A Comment" button. The archives of the TC's 
mail list and public comments are visible at 

Further information about the topic of this TC may be found on the Cover 
Pages under the title "Data Sharing, Mediation, and Synchronization" at 

A FAQ for the TC is available on the TC's web page at 

A white paper for the TC is available at 


Karl F. Best
Vice President, OASIS
office  +1 978.667.5115 x206     mobile +1 978.761.1648
karl.best@oasis-open.org      http://www.oasis-open.org

Proposal to form the OASIS XRI Data Interchange (XDI) Technical Committee

The following comprises the TC Charter


OASIS XRI Data Interchange (XDI) Technical Committee


As the Internet increasingly becomes the common data interchange 
platform for all devices, domains, and networks, there is a growing need 
for a simple, standard way to share data that is common to multiple 
applications, directories, databases, Web services, and XML schemas 
while at the same time permitting the authorities for this data to 
secure, protect, and control its use.

The purpose of the OASIS XDI TC is to define a generalized, extensible, 
location-, application-, and transport-independent service for sharing, 
linking, and synchronizing data over the Internet and other data 
networks using XML documents and XRIs (Extensible Resource Identifiers), 
a URI-compatible abstract identifier scheme defined by the OASIS XRI 
Technical Committee. With XDI, data from any data source can be 
identified, described, linked, and synchronized into an active, 
machine-readable "dataweb" just as content from any content source can 
be identified and linked into the human-readable Web today.

A particular purpose of XDI is to allow the controls needed to mediate 
access and usage of shared data to be expressed as XDI links. These data 
sharing controls can govern authority, authentication, authorization, 
access control, usage control, transmission, synchronization, and rights 
management. The integration of such controls into a common, generalized 
data-oriented service can provide a new platform for trusted data 
sharing networks and applications.

In no event shall this Technical Committee finalize or approve any 
technical specification if it believes that the use, distribution, or 
implementation of such specification would necessarily require the 
unauthorized infringement of any third party rights known to the 
Technical Committee, and such third party has not agreed to provide 
necessary license rights on perpetual, royalty-free, non-discriminatory 


As a data sharing service, XDI is intended to be very simple and 
generalized, much like HTTP or SMTP. Similarly, the XDI meta-schema is 
intended to be a very simple and generalized XML schema that can be used 
either to carry or to describe data encoded in other XML schema 
languages or referenced externally (much as HTML can either carry 
content or reference it externally). Such a "lingua franca" for XML data 
interchange can be used to solve many problems related to mapping and 
sharing of data and metadata across domains, directories, schemas, 
ontologies, applications, and languages (both human and machine).

Therefore, although the potential uses of XDI are very broad, the scope 
of work of the OASIS XDI TC is relatively narrow. Specifically, it is 
limited to:

* Defining the XDI meta-schema for describing and linking XRI-identified 

* Defining XRI resolution rules within XDI documents.

* Defining the WSDL for XDI service and bindings to common transport 
protocols such as HTTP, SOAP, and SMTP/MIME.

* Defining the XDI service dictionary –- the set of globally-shared XDI 
resources that can be used to define, control, secure, and protect data 
sharing relationships using XDI.

* Maintaining additional versions of these specifications as they evolve 
over time.

The OASIS XDI TC may also publish white papers, example usage scenarios, 
and other documentation to support XDI implementation and adoption.


The initial deliverables of the OASIS XDI TC and their completion dates are:

1. XDI Use Cases and Requirements 1.0 – 15 May 2004
2. XDI Service Specification 1.0 (includes XDI Meta-Schema Definition,
    XDI Addressing Specification, and XDI WSDL Definition and Bindings)
    – 15 September 2004
3. XDI Service Dictionary 1.0 – 15 Nov 2004
4. XDI Primer 1.0 – 15 Dec 2004


The work of the OASIS XDI TC will be used by developers and implementers 
of Web, Web services, and Semantic Web technologies. It will be 
particularly relevant to architects of trusted computing infrastructure, 
distributed directory and PKI systems, enterprise application 
integration (EAI) systems, shared ontologies, and other cross-domain 
data sharing systems and services.


All meetings (both face-to-face and phone meetings) as well as official 
correspondences amongst OASIS XDI TC participants will be conducted in 

The following is additional non-normative information related to 
starting the TC.


The work done in the OASIS XDI TC is related to the following work done 
in other OASIS TCs:

1. XRIs and the OASIS Extensible Resource Identifier TC. The OASIS XDI 
TC’s work is based directly on the specifications for abstract, 
persistent, location-independent identifiers published by the OASIS XRI TC.

2. SAML (OASIS Security Services TC), WS-Security (OASIS Web Services 
Security TC), and the OASIS Public Key Infrastructure TC. The OASIS XDI 
TC intends to leverage this work by using SAML assertions and 
WS-Security specifications in the XDI/SOAP binding, and to explore the 
use of XDI for distributed PKI systems.

3. XACML (OASIS eXtensible Access Control Markup Language TC) and the 
OASIS Rights Language TC. XDI can encapsulate existing or emerging 
access control and rights expression languages directly into its data 
sharing controls.

4. DSML and the OASIS Directory Services Markup Language TC. XDI can 
provide a high-level directory abstraction interface that can 
interoperate with DSML and LDAP, and XDI can add data sharing controls 
not currently specified by DSML or LDAP.

5. SPML and the OASIS Provisioning Services TC. XDI can provide a common 
format for interchange of SPML attributes, and XDI forms can trigger 
SPML provisioning requests.

6. Topic Maps and the OASIS Topic Maps Published Subjects TC. XRIs, XDI 
documents, and the XDI protocol can provide a robust mechanism for 
implementing topic maps, and in particular fulfill the OASIS Topic Maps 
Published Subjects TC’s recommendations for Published Subject Indicators 
(PSIs) and Publish Subject Identifiers (PSIDs).

In addition, the OASIS XDI TC anticipates building on work done at the 
W3C, including the entire family of Web services standards (XML, XML 
Schemas, SOAP, WSDL). The XDI TC will also closely examine the use of 
RDF for data description and OWL for ontology description.

The proposers of the OASIS XDI TC anticipate that the TC will form 
liaisons with:

* The Trusted Computing Group (TCG) Infrastructure Working Group for 
establishing common use cases and ensuring interoperability of TCG and 
XDI specifications in trusted computing infrastructure.

* The Telemanagement Forum (TMF) for establishing common use cases and 
requirements for using XDI as a mechanism for implementing the TMF SID 
(Shared Information/Data Model) component of the TMF NGOSS (New 
Generation Operations System and Software) program.

* The International Security, Trust, and Privacy Alliance (ISTPA) to 
adapt the ISTPA Privacy Framework as a reference model for XDI privacy 
architecture and development of usage control vocabulary in the XDI 
Service Dictionary.


The proposers of the OASIS XDI TC expect the following work will be 
contributed to the TC at its first meeting:

1. The XNS 1.0 and 1.1 Technical Specifications will be contributed by 
the XNS Public Trust Organization (XNSORG).

2. An initial XDI meta-schema definition and supporting documentation 
will also be contributed by XNSORG.


The first OASIS XDI TC meeting will be held on the 20th of February 
2004, via telecon, at 2pm PT (GMT-8:00).


1. Face-to-Face Meetings
        a. April 29-30, 2004 (tentative)

2. Phone Meetings bi-weekly, tentatively 2pm PT (GMT-8:00).


AMD, Epok, Cordance, and XNSORG


1. Geoffrey Strongin, AMD (geoffrey.strongin@amd.com)
2. Dave McAlpin, Epok (dave.mcalpin@epok.net)
3. Davis McPherson, Epok (davism@epok.net)
4. Loren West, Epok (loren.west@epok.net)
5. Xavier Serrett, Gemplus (Xavier.SERRET@gemplus.com)
6. Peter Davis, Neustar (peter.davis@neustar.biz)
7. Nat Sakimura, NRI (n-sakimura@nri.co.jp)
8. Tetsu Watanabe, NRI (tetsu@nri.com)
9. Kouichi Nishikata, NRI (k-nishikata@nri.co.jp)
10. Tomonori Seki, NRI (t2-seki@nri.co.jp)
11. Jun Eijima, NRI (j-eijima@nri.co.jp)
12. Marc Le Maitre, Cordance (marc.lemaitre@cordance.net)
13. Drummond Reed, Cordance (drummond.reed@cordance.net)
14. Sean Vanderdasson, Cordance (sean.vanderdasson@cordance.net)
15. Lark Allen, Wave Systems (lallen@wavesys.com)
16. Bill Washburn, XNSORG (bill.washburn@xns.org)
17. Michael Willett, XNSORG (michael.willett@xns.org)
18. Owen Davis, Planetworks (owen@idcommons.org)


1. Drummond Reed, Cordance


1. Drummond Reed, Cordance
2. Geoffrey Strongin, AMD

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