| Group Name |
Group Description |
| Auto Repair Architecture and Specification SC |
|
| Auto Repair Terminology SC |
|
| Auto Repair Use Cases and Requirements SC |
|
| BCM EPR SC |
The BCM EPR subcommittee was created by the OASIS Business-Centric Methodology TC to examine and elaborate the Norwegian Electronic Process (EPR) work into a specification within the BCM work, expand the original BCM "Appendix A", and create concrete realization in an industry scenario of the BCM approach. Current EPR use cases include Home Healthcare services and Building and Construction Maintenance services. |
| BCM Liaisons SC |
|
| BCM Linking + Switching SC |
Welcome to the Linking and Switching Sub-team of BCM
Our work is focused on developing out the Appendix B functionality of the main BCM specifications. This includes state management and linking and switching using agent directed decisions. |
| BPEL4People Editors |
Statement of Purpose for the BPEL4People Editors Sub Committee
The collection of TC specification documents, including but not limited to TC drafts, individual submissions, Committee Specifications, is managed by the TC Editor function (the "TC Editor" aka "bpel4people-editors"). The TC Editor is a role that is occupied by the members of the Editors Sub Committee. Issues tracking and management is the responsibility of the Issues Editor, a role assigned by the TC. The Issues Editor is also a member of the Editors Sub Committee.
The TC Editor is addressed by electronic mail using the address: bpel4people-editors@lists.oasis-open.org.
The TC Editor has responsibility for incorporating agreed resolutions to TC issues. Among other activities it will be responsible for assigning document filenames, ascertaining whether said documents meet OASIS guidelines, remanding the documents to the authors if deemed necessary (e.g. if the document(s) don't meet these guidelines), publishing said documents on the TC website and denoting status thereof (e.g. whether the document(s) are a TC Draft, or Committee Specification) upon the BPEL4People TC approval.
Meeting Schedule
The SC will meet weekly. Please note that Kavi calendaring is not used.
SC meetings are scheduled every week to start at 12:00ET on Wed or immediately following the BPEL4People TC meeting on alternate weeks.
Time: 12:00 - 13:30 US ET (or later following a TC mtg)
Event Hosted by IBM (bridge to be opened by Dieter Koenig):
North American toll-free number: 866-245-5059
European toll-free number: (00)-800-4444-1010
International number: 416-343-2607
Conference ID: 2388736
Issues Management
The BPEL4People TC and the Editors SC use JIRA for issues management. This content can be accessed anonymously at http://www.osoa.org/jira/browse/BP.
Collaborative Workspace
The BPEL4People Editors SC uses Subversion (SVN) to collaborate on intermediate versions of documents. This content can be accessed anonymously at http://wsbpel4people.svn.sourceforge.net/viewvc/wsbpel4people/Specifications/.
Draft submissions for approval by the BPEL4People TC
Periodically, the SC will submit to the TC a list of changes applied to the specs/WSDL/XSDs for review. The rate and number of issues incorporated and submitted to the TC will depend on a number of factors. Ease of review will be the primary criterion dictating when a version of a document should be submitted to the TC for consideration.
The SC will aim to provide the TC at least one (1) week for review of the documents. Upon approval by the TC a designated editor will accept all changes approved and submit the document(s) to SVN hosted on SourceForge.net.
BPEL4People Editors SC Contacts |
| DITA Enterprise Business Documents SC |
Developing an enterprise business document meta-model in harmony with DITA |
| DITA Help SC |
|
| DITA Learning and Training Content Specialization SC |
Current Status
April 1, 2008 - The DITA Technical Committee has approved Design Proposal 12058 for inclusion of the DITA specialization for learning and training content in the formal design plan for DITA 1.2.
These supporting documents are all available on OASIS.org, with Public access:
Summary design proposal 12058
PDF of the design and language specification
DITA Open Toolkit plugin, with DTD and XSD schemas, sample content, and documentation sources
January - April, 2008 - We discuss processing, with the primary target to develop a "starter set" of DITA processing to support basic SCORM packaging, with interactions, according to our Phased Design Plan. The processing will get delivered separately from the DTD/schema designs and language specification, and made available to the community as part of a DITA Open Toolkit plugin module on a schedule TBD.
For more information, see the OASIS DITA Learning Content Subcommittee wiki.
Goals
The subcommittee formed in August, 2006 and adopted the goals below.
1. To develop a general top-level design for structured, intent-based authoring of learning content with good learning architecture, following DITA principles and best practices. Such a design would build on past work on topic-based content, reusable learning objects, and the learning content types needed to support them.
2. Establish guidelines that promote best practices for applying standard DITA approaches to learning content, which include:
- separation of presentation and content (as much as possible)
- separation of content and context
- single sourcing, repurposing, and reuse.
3. Develop support for processing DITA for general delivery as learning and training, including print and presentation delivery to support instructor-led training (ILT), web delivery for distance learning, and computer-based training delivery in general.
4. Develop targeted support for processing DITA learning content for delivery with standards-based learning, specifically targeting SCORM and QTI. Specifically, extend DITA processing to support basic SCORM sequencing, interactions, and required SCORM LMS runtime behaviors. Leverage QTI behaviors to drive the interactions. Address the issue of "levels" from a simple implementation to full SCORM and beyond.
5. Build on existing DITA infrastructure (editors, CMS, transforms) as much as possible so learning content developers do not have to start from scratch. |
| DITA Machine Industry SC |
This activity will help to galvanize the role of DITA specializations across
industries that have common issues for hardware-related description.
Such as: manufacturing system engineering,
engine- and machine construction, power plant equipments, apparatus
engineering, elevators and escalators etc. |
| DITA Semiconductor Information Design SC |
Creating DITA specializations for better information design and interoperability throughout the semiconductor industry |
| DITA Translation Subcommittee |
|
| DocBook Publishers SC |
Developing official variants of DocBook in support of the publishing industry |
| ebXML CPPA Automated Negotiation SC |
|
| ebXML CPPA Transaction Capability Models SC |
|
| ebXML CPPA Web Services Interaction SC |
|
| ebXML IIC Conformance Test Suites SC |
|
| ebXML IIC Interoperability Test Suites SC |
|
| ebXML IIC Testing Framework SC |
|
| ebXML Messaging Services AS4 SC |
|
| ebXML Registry CC Review SC |
To perform a verification of the UN/CEFACT Core Components specification Section 7. This will be done through the creation of an ebXML Registry Information Model (ebRIM) binding. |
| ebXML Registry Cooperating Registries SC |
|
| ebXML Registry REST SC |
|
| ebXML Registry Security Services SC |
|
| ebXML Registry Semantic Content Management SC |
The Semantic Content Management SC was established by the OASIS ebXML Registry TC. The SC will define use cases and requirements for managing semantic content within the ebXML Registry 4.0. It will seek to establish a formal liaison with relevant groups within the Semantic Web Activity (SWA) at W3C. Early in its life cycle, the SCMSC will actively engage the SWA relationship and solicit their help to validate requirements. The requirements must include the ability to utilize ontolgies for classifying RegistryObjects and to enable intelligent discovery using ontology based queries.
The SCMSC will identify specific Semantic Web technologies (e.g. RDF, OWL) that are necessary to support the requirements identified for semantic content management.
Ultimately, the SCMSC will deliver the detailed technical specification for adding semantic content management capabilities in the registry. The proposal will address changes to RIM, XML Schema, Relational Schema and Registry Service interfaces that will be necessary to support the new features.
The charter of the TC can be found at
http://www.oasis-open.org/committees/regrep/charter.php.
Proposed deliverables for the SC:
- Slide Presentation: Includes, Use cases, Requirements, Motivations, Assumptions and Overview of Technical proposal.
- Detailed Technical proposal on Semantic Content Management. This will incorporated into the specs as spec content once approved.
- Paper on "Semantic Content Management using the ebXML Registry". Venue for submission of paper will be determined later. |
| eGov Asia-Pacific SC |
|
| eGov Best Practices SC |
|
| eGov Core Components SC |
|
| eGov ebXML Registry SC |
|
| eGov Harmonising Taxonomies SC |
|
| eGov Infrastructure SC |
Within the scope of the E-Government Technical Committee, the Infrastructure Subcommittee focuses on common facilities applied in multiple government functions. Examples of common facilities include Security and Authentication, Privacy Assurance, Geospatial Facilities, Metadata Facilities, E-forms Facilities, Identity Services, Interface Management, Information Discovery, Records Management, Taxonomy Management, Registry and Repository Facilities, and Organization Directories, among others. |
| eGov Services SC |
|
| eGov Web Services SC |
|
| EKMI SKMS Audit Guidelines SC |
|
| EKMI SKMS Implementation and Operations Guidelines SC |
|
| EKMI SKSML Test Suite SC |
|
| EKMI Symmetric Key Services Markup Language (SKSML) SC |
This sub-committee is responsible for the creation of the Symmetric Key Services Markup Language (SKSML), an XML-based protocol for acquiring symmetric key-management services within a Symmetric Key Management System (SKMS). |
| EM Adoption SC |
Supporting the adoption of standards to enable information exchange which advance incident preparedness and response to emergency situations. Anyone OASIS members interested in this activity is encouraged to join the subcommittee. |
| EM GIS SC |
OASIS Emergency Management GIS Subcommittee |
| EM Infrastructure Framework SC |
|
| EM Messages and Notification SC |
The EM Notification Methods and Messages Subcommittee ("the Subcommittee") will address procedures and formats for exchanging new and updated information related to functions including public safety, emergency response and homeland security. |
| EM Reference Information Model SC |
|
| Enterprise Key Management Infrastructure Demo SC |
|
| FWSI Functional Elements SC |
|
| FWSI Implementation Methodology SC |
|
| Human Mediation SC |
Completed
The Mediation Subcommittee of the HumanMarkup Technical Committee is tasked to produce a Human Mediation Markup Language, HMML. To do this, the subcommittee will gather resources, identify and incorporate specific existing vocabularies such as formal legal discourse standards that represent established means for mediation. This will include contributions to the overall Human Markup Language. |
| HumanML Human Physical Characteristics Description SC |
Completed
The Human Physical Characteristics Description Markup Language (HPCDML) Subcommittee of the OASIS Human Markup TC will develop, design and provide specifications for HPCDML.
HPCDML will be designed to provide standardized description of physical characteristics of humans, with specific responsibility to harmonize and interoperate with widely accepted Public-Health, Medical, Biometric, Archeological, Human-Modeling and Public Safety standards.
HPCDML is a superset of HumanML and through markup language concepts will provide a communication medium for end users and software community to exchange information of greater depth and complexity than verbally-based symbolic language in isolation from non-verbal contextual information. This extended communication requires an accurate depiction of human physical behaviors. |
| IHC SNOMED SC |
|
| LegalXML Court Filing Blue Drafting SC |
This is a subcommittee of the OASIS LegalXML Electronic Court Filing Technical Committee. |
| LegalXML Court Filing Certification SC |
|
| LegalXML Court Filing Conformance SC |
|
| LegalXML Court Filing Document SC |
|
| LegalXML Court Filing e-Filing Process Models SC |
|
| LegalXML Court Filing Layered Interoperability SC |
|
| LegalXML Court Filing Outreach SC |
|
| LegalXML Court Filing Policy SC |
|
| LegalXML Court Filing Repository SC |
|
| LegalXML Court Filing Requirements SC |
This is a subcommittee of the OASIS LegalXML Electronic Court Filing Technical Committee. |
| LegalXML Court Filing Signatures SC |
The Signatures Subcommittee of the OASIS LegalXML Electronic Court Filing Technical Committee was established by the TC to
* Provide technical guidance as needed to implement the various signature profiles with regard matters such as security, efficiency, interoperability and service-oriented architectures.
* Address issues in applying any of the adopted signature profiles.
* Identify, collect and help resolve any discovered signature interoperability issues, including proposing, vetting or reviewing any additionally submitted or needed signature profiles, as appropriate.
* Identify providers of signature technologies that can service ECF 3.x profiles in a SOA architecture and provide information about each. |
| LegalXML Integrated Justice Exchange Document Methodology, Naming, and Design Rules SC |
|
| OASIS Application Vulnerability Description Language (AVDL) TC |
Completed |
| OASIS Asynchronous Service Access Protocol (ASAP) TC |
Completed
Describing a standard way to start, manage, and monitor long running services |
| OASIS Auto Repair Member Section |
|
| OASIS Automotive Repair Information TC |
Completed
The purpose of the OASIS Automotive Repair TC was to develop a standard format to enable access to emission-related repair, diagnostic and technical information with respect to the vehicles covered by the scope of Directive 70/220/EEC. The TC completed its work in June 2003. |
| OASIS Biometric Identity Assurance Services (BIAS) Integration TC |
Defining methods for using biometric identity assurance in transactional Web services and SOAs |
| OASIS Business Transactions TC |
Completed |
| OASIS Business-Centric Methodology (BCM) TC |
Defining methods to acquire interoperable e-business information systems within communities of interest |
| OASIS CGM Open Member Section |
This is the OASIS CGM Open Member Section |
| OASIS CGM Open WebCGM TC |
Advancing the vector graphics standard for online technical documents |
| OASIS Changfeng Open Standards Lab Member Section |
OASIS Members interested in joining this Member Section should send their request to member-services@oasis-open.org
The purpose of the COSL Member Section is:
* To serve as a focal point for discussions of SOA related open standard, technology, and implementation, End-to-End resource planning and other relevant issues as applicable in Asia.
* To assist in the dissemination of, and collection of responses for End-to-End Resource Planning (EERP). The EERP effort focuses on how to build a framework that manages all services that a company requires to produce and deliver the products or services to its ultimate consumers. Therefore, EERP includes the extended research on how to evaluate services and processes subject to business objectives, and how to composite and de-composite services subject to optimization.
* To facilitate and encourage the re-use and information sharing for SOA related standards, technologies and applications.
*To assist OASIS in promotion and adoption of open standards.
* To facilitate incubation research related to SOA implementation and End to End Resource Planning.
* Where the specific needs suggest additional work, to discuss, scope and if needed initiate additional standardization projects within OASIS. |
| OASIS Code List Representation TC |
Defining an XML format for interchange, documentation and management of code lists (a.k.a. controlled vocabularies or coded value enumerations) in any processing context |
| OASIS Conformance TC |
CompletedThe purpose of this TC was to provide a forum where interested parties can discuss issues that are pertinent to the interoperability and conformance of structured information standards. |
| OASIS Content Assembly Mechanism (CAM) TC |
Describing machine-processable information content flows into and out of XML structures |
| OASIS Controlled Trade Markup Language TC |
Completed
The purpose of this TC was to develop a unified trade control vocabulary that supports an international collection of business documents through the extension and expansion of an existing XML vocabulary. |
| OASIS Customer Information Quality (CIQ) TC |
Delivering royalty free, open, international, industry and application neutral XML specifications for representing, interoperating, and managing Party (Person/Organisation) Centric Information (Name, Address, Party Profile and Party Relationships) |
| OASIS Darwin Information Typing Architecture (DITA) TC |
Advancing a document creation and management specification that builds content reuse into the authoring process |
| OASIS DCML Adoption TC |
Completed.
Promoting the adoption of OASIS DCML standards in the data center to help organizations realize the promise of utility computing. |
| OASIS DCML Applications and Services TC |
Completed.
Defining extensions to represent and manage applications and services in a data center |
| OASIS DCML Framework TC |
Completed
Creating an XML-based data model and format for exchanging information about the contents of data centers and other IT resources and information used in managing those resources |
| OASIS DCML Member Section |
CompletedThe mission of the OASIS DCML Member Section was to accelerate the further development, adoption, application, and implementation of the Data Center Markup Language and related work. |
| OASIS DCML MS Steering Committee |
The DCML Member Section Steering Committee is responsible for the decision making, budgeting and governance issues so noted in the Rules of Procedure.
The Steering Committee is elected by members of OASIS who have designated their OASIS membership as supporting the work of the DCML Member Section. |
| OASIS DCML Network TC |
Completed.
Designing an XML-based format for the exchange of information about networking elements in a data center |
| OASIS DCML Server TC |
Completed.
Facilitating the representation and management of information about servers in a data center |
| OASIS Digital Signature Services (DSS) TC |
Completed
Defining an XML interface to process digital signatures for Web services and other applications |
| OASIS Digital Signature Services eXtended (DSS-X) TC |
Advancing digital signature services standards for XML |
| OASIS Directory Services Markup Language TC |
Completed
The purpose of this TC was to bridges the world of directory services with the world of XML by continuing work on the DSML specification to add support for querying and modifying directories. The DSML v2 specification was approved as an OASIS Standard in April 2002. |
| OASIS DocBook TC |
Providing a system for writing structured documents using SGML or XML |
| OASIS e-Government TC |
Completed
Providing a forum for governments to articulate and coordinate requirements for XML- and Web services-based standards |
| OASIS ebXML Business Process TC |
Providing a standards-based business process foundation that promotes the automation and predictable exchange of business collaboration definitions using XML |
| OASIS ebXML Collaboration Protocol Profile and Agreement (CPPA) TC |
Describing how trading partners engage in electronic business collaborations through the exchange of electronic messages |
| OASIS ebXML Core (ebCore) TC |
Managing modifications and maintenance for several ratified ebXML specifications |
| OASIS ebXML Implementation Interoperability and Conformance (IIC) TC |
Enabling software providers to create infrastructure and applications which interoperate with and adhere to the ebXML specifications |
| OASIS ebXML Joint Committee |
Coordinating the work of the OASIS ebXML Technical Committees |
| OASIS ebXML Messaging Services TC |
Defining the transport, routing and packaging of e-business transactions |
| OASIS ebXML Registry TC |
Defining and managing interoperable registries and repositories |
| OASIS Education TC |
Completed
The purpose of the OASIS Education XML TC was to represent international pre-Kindergarten through 12th grade (PK12) interests by developing XML requirements documentation for shared extensible user profiles, controlled vocabularies, taxonomies, and thesauri, and other needed specifications. |
| OASIS Election and Voter Services TC |
Enabling the exchange of data for public and private election services |
| OASIS Electronic Business Service Oriented Architecture (ebSOA) TC |
Completed
Advancing architectural patterns for using Service Oriented Architecture in electronic business |
| OASIS Electronic Procurement Standardization (EPS) TC |
Completed.
Researching and developing global e-procurement standards and processes |
| OASIS Emergency Management TC |
Enabling information exchange to advance incident preparedness and response to emergency situations |
| OASIS Emergency Member Section |
the mission of the OASIS Emergency Interoperability Member Section to accelerate the development, adoption, application, and implementation of emergency interoperability and communications standards and related work.
OASIS members who wish to affiliate their membershp with this Member Section or wish to join the mailing list should send their request to member-services@oasis-open.org |
| OASIS Enterprise Key Management Infrastructure (EKMI) Technical Committee |
Standardizing the management of symmetric encryption cryptographic keys across the enterprise |
| OASIS Entity Resolution TC |
Completed
Developing an XML specification for mapping resource references to known resources |
| OASIS eXtensible Access Control Markup Language (XACML) TC |
Representing and evaluating access control policies. |
| OASIS Extensible Resource Identifier (XRI) TC |
Defining a royalty-free URI-compatible scheme and resolution protocol for abstract structured identifiers used to identify and share resources across domains and applications |
| OASIS Forest Industries TC |
Standardizing electronic transfer of forest industry data from source to customer |
| OASIS Framework for Web Services Implementation (FWSI) TC |
Defining methods and functional components for broad, multi-platform, vendor-neutral cross-industry implementation of Web services |
| OASIS HumanMarkup TC |
Completed
Using XML to contextually convey cultural, social, kinesics, and psychological intent within communications |
| OASIS International Health Continuum (IHC) TC |
Providing a forum for the global healthcare community to articulate and coordinate requirements for XML- and Web services-based standards |
| OASIS LegalXML eContracts TC |
Completed
Enabling the efficient creation, maintenance, management, exchange, and publication of contract documents and terms |
| OASIS LegalXML Electronic Court Filing TC |
Using XML to create and transmit legal documents among attorneys, courts, litigants, and others. |
| OASIS LegalXML eNotarization TC |
Developing technical requirements to govern self-proving electronic legal information |
| OASIS LegalXML Integrated Justice TC |
Facilitating the exchange of data among justice system branches and agencies for criminal and civil cases |
| OASIS LegalXML Lawful Intercept TC |
Production of a structured, end-to-end lawful interception process framework consisting of XML standards and authentication mechanisms, including identifiable related XML standards and XML translations of ASN.1 modules.
Completed. |
| OASIS LegalXML Legal Transcripts TC |
CompletedThe purpose of this TC was to develop an XML compliant syntax for representing legal transcript documents either as stand-alone structured content, or as part of other legal records. |
| OASIS LegalXML Legislative Documents, Citations, and Messaging TC |
Standardizing markup for legislative documents and simple citation for non-legislative documents
Completed. |
| OASIS LegalXML Online Dispute Resolution TC |
Using XML to allow public access to justice through private- and government-sponsored dispute resolution systems
Completed. |
| OASIS LegalXML Subscriber Data Handover Interface TC |
Development of a specification for the production of a consistent XML Subscriber Data Handover Interface (SDHI), by telecommunication or Internet service providers, of information concerning a subscriber or communications identifier (e.g., a telephone number) in response to an XML request which includes, when necessary, authorization from a judicial, public safety, or law enforcement authority.
Completed. |
| OASIS Management Protocol TC |
Completed
The Management Protocol TC closed in February 2003 after moving its work to the WSDM TC.
The purpose of the Mgmt Protocol TC was to develop open industry standard management protocols to provide a web-based mechanism to monitor and control managed elements in a distributed environment based on industry accepted management models, methods, and operations. |
| OASIS Materials Markup Language TC |
Standardizing the exchange of all types of technical metrics and information for raw manufacturing materials |
| OASIS member practice |
This is a practice TC page. Feel free to test-drive features like joining the TC or posting documents etc. This is not the place to make any technical contributions or have any meaningful dialogue. Unlike real OASIS TCs, this group is not publicly shared. It is visible to OASIS members. |
| OASIS Open Building Information Exchange (oBIX) TC |
Enabling mechanical and electrical control systems in buildings to communicate with enterprise applications |
| OASIS Open CSA Member Section |
The OASIS Open Composite Services Architecture (Open CSA) Member Section advances open standards that simplify SOA application development. Open CSA promotes the further development and adoption of the Service Component Architecture (SCA) and Service Data Objects (SDO) families of specifications.
OASIS Members who wish to subscribe to the mail list, or whose company wishes to support the Open CSA Member Section should send an email request to member-services@oasis-open.org |
| OASIS Open Document Format for Office Applications (OpenDocument) TC |
Developing an XML-based file format specification for office applications |
| OASIS Open Reputation Management Systems (ORMS) TC |
Advancing the ability to use common data formats for representing reputation data |
| OASIS OpenCSA Liaison Subcommittee |
This group is open to any eligible OASIS member. If you wish to join this group, send your request to opencsa-liaison-chair@lists.oasis-open.org . Please be sure to note if you are requesting to be an Observer, Member or Voting Member representing your SCA Technical Committee. |
| OASIS OpenDocument Format (ODF) Adoption TC |
Collaborating to increase the demand for and availability of products that conform to the OpenDocument Format |
| OASIS organizational voting |
This group is for the purpose of voting on OASIS-wide ballots such as OASIS Board and TAB elections, approving specifications as OASIS Standards, etc. The members of this group are the voting representatives of each of the OASIS member organizations. |
| OASIS PKI Member Section |
CompletedThe work for this member section has been transitioned to our IDtrust member section. |
| OASIS Product Life Cycle Support (PLCS) TC |
Collaborating on the deployment of an international standard for product data exchange (ISO 10303) to support complex engineered assets from concept to disposal |
| OASIS Production Planning and Scheduling (PPS) TC |
Developing common object models and schemas for collaborative planning and scheduling in manufacturing |
| OASIS Provisioning Services TC |
Providing an XML framework for managing the provisioning and allocation of identity information and system resources within and between organizations |
| OASIS Public Key Infrastructure Adoption (PKIA) TC |
Advancing the use of digital certificates as a foundation for managing access to network resources and conducting electronic transactions |
| OASIS Published Subjects TC |
Advancing ISO 13250 for organizing, retrieving and navigating information resources by specifying recommendations, requirements and best practices for published subjects
Completed |
| OASIS RELAX NG TC |
Advancing a lightweight, easy-to-use XML schema language |
| OASIS Remote Control XML TC |
Developing XML-based standards to support the control of devices accessed remotely |
| OASIS Rights Language TC |
CompletedThe purpose of this TC was to define an industry standard for a digital rights language that supports a wide variety of business models and has an architecture that provides the flexibility to address the needs of the diverse communities that have recognized the need for a rights language. |
| OASIS Search Web Services TC |
Developing Web services definitions for search and retrieval applications |
| OASIS Security Services (SAML) TC |
Defining and maintaining a standard, XML-based framework for creating and exchanging security information between online partners |
| OASIS Semantic Execution Environment TC |
Developing guidelines, justifications, and implementation directions for deploying Semantic Web services in SOA |
| OASIS Service Component Architecture / Assembly (SCA-Assembly) TC |
Defining core SCA composition model to simplify SOA application development |
| OASIS Service Component Architecture / Bindings (SCA-Bindings) TC |
Standardizing bindings for SCA services and references to communication protocols, technologies and frameworks |
| OASIS Service Component Architecture / BPEL (SCA-BPEL) TC |
Specifying how SCA component implementations for SOA can be written using BPEL |
| OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC |
Standardizing C and C++ use within an SCA domain for SOA |
| OASIS Service Component Architecture / J (SCA-J) TC |
Standardizing Java (tm) use within an SCA domain for SOA |
| OASIS Service Component Architecture / Policy (SCA-Policy) TC |
Defining an SCA policy framework to simplify SOA application development |
| OASIS Service Data Objects (SDO) TC |
Simplifying how SOA applications handle data from heterogeneous sources, e.g., relational databases, Web services, and enterprise information systems |
| OASIS SOA Adoption Blueprints TC |
Completed
Developing, publishing and maintaining archetypal "blueprint" sets of requirements and functions to serve as generic, vendor-neutral instances of service-oriented solutions for real business requirements. |
| OASIS SOA Reference Model TC |
Developing a core reference model to guide and foster the creation of specific, service-oriented architectures |
| OASIS Solution Deployment Descriptor (SDD) TC |
Defining a standardized way to express software installation characteristics required for lifecycle management in a multi-platform environment |
| OASIS Tax XML TC |
Promoting interoperability of XML tax-related information |
| OASIS Telecommunications Services Member Section |
OASIS Members choosing to join this group should send a messages to member-services@oasis-open.org stating their intent to join.
The TMS facilitates the development of telecommunications SOA based services as described in the Member Section's Work Plan, over an extended period of time requiring the coordination of multiple Technical Committees (TCs) and various adoption and marketing activities it may choose to undertake.
|
| OASIS Test Assertions Guidelines (TAG) TC |
Improving the quality of standards by facilitating the creation and use of test assertions by OASIS committees and others |
| OASIS Testing and Monitoring Internet Exchanges (TaMIE) TC |
Defining an event-centric test case scripting markup and execution model |
| OASIS Topic Maps Published Subjects for Geography and Languages TC |
Completed
Advancing ISO 13250 for organizing, retrieving and navigating information resources by defining sets of published subjects for languages, countries, and regions |
| OASIS Topic Maps Vocabulary for XML Standards and Technologies TC |
Completed
Advancing ISO 13250 for organizing, retrieving and navigating information resources by defining essential subjects needed to create interchangeable ontologies |
| OASIS Translation Web Services TC |
Automating the translation and localization process as a Web service |
| OASIS UDDI Member Section |
CompletedFor more information on UDDI, visit our UDDI focus area. |
| OASIS UDDI Specification TC |
Defining a standard method for enterprises to dynamically discover and invoke Web services |
| OASIS UnitsML TC |
Defining an XML-based specification to enable the unambiguous representation of units of measure |
| OASIS Universal Business Language (UBL) TC |
Defining a common XML library of business documents (purchase orders, invoices, etc.) |
| OASIS Unstructured Information Management Architecture (UIMA) TC |
Standardizing semantic search and content analytics |
| OASIS Unstructured Operation Markup Language (UOML) TC |
Creating an open, XML-based operation standard for unstructured documents |
| OASIS Unstructured Operation Markup Language eXtended (UOML-X) TC |
Advancing an open, XML-based operation standard for unstructured documents |
| OASIS User Interface Markup Language (UIML) TC |
Developing a specification for an abstract meta-language that can provide a canonical XML representation of any user interface (UI) |
| OASIS Web Application Security (WAS) TC |
Completed |
| OASIS Web Services Business Process Execution Language (WSBPEL) TC |
Completed
Enabling users to describe business process activities as Web services and define how they can be connected to accomplish specific tasks |
| OASIS Web Services Composite Application Framework (WS-CAF) TC |
Completed
Defining an open framework for supporting coordinated and transactional compositions of multiple Web services applications |
| OASIS Web Services Distributed Management (WSDM) TC |
Completed
Defining a Web services architecture to manage distributed resources |
| OASIS Web Services Federation (WSFED) TC |
Extending identity management to enable federations of trust across organizations |
| OASIS Web Services for Remote Portlets (WSRP) TC |
Standardizing presentation-oriented Web services for use by aggregating intermediaries, such as portals |
| OASIS Web Services Interactive Applications TC |
CompletedUpon resolution of the WSIA TC membership that their work has completed (see the voting information and the summary), the OASIS WSIA TC is closed. The purpose of this TC was to create an XML and web services centric framework for interactive web applications; harmonize the specification as far as practical with existing web application programming models, with the work of the W3C, emerging web services standards, and with the work of other appropriate business information bodies. |
| OASIS Web Services Notification (WSN) TC |
Completed
Advancing a pattern-based approach to allow Web services to disseminate information to one another |
| OASIS Web Services Quality Model TC |
Defining common criteria to evaluate quality levels for interoperability, security, and manageability of services |
| OASIS Web Services Reliable Exchange (WS-RX) TC |
Advancing a protocol for reliable message exchange using Web services |
| OASIS Web Services Reliable Messaging (WSRM) TC |
Completed
Providing a standard, interoperable way to guarantee message delivery to applications or Web services |
| OASIS Web Services Resource Framework (WSRF) TC |
Completed
Defining an open framework for modeling and accessing stateful resources using Web services |
| OASIS Web Services Secure Exchange (WS-SX) TC |
Defining WS-Security extensions and policies to enable the trusted exchange of multiple SOAP messages |
| OASIS Web Services Security (WSS) TC |
Completed
Delivering a technical foundation for implementing security functions such as integrity and confidentiality in messages implementing higher-level Web services applications |
| OASIS Web Services Transaction (WS-TX) TC |
Defining protocols for coordinating the outcome of distributed application actions |
| OASIS WS-BPEL Extension for People (BPEL4People) TC |
Expanding the Business Process Execution Language to support human interactions |
| OASIS XML Common Biometric Format (XCBF) TC |
Completed.
Providing a standard way to describe information that verifies identity based on human characteristics such as DNA, fingerprints, iris scans, and hand geometry |
| OASIS XML Conformance TC |
Completed
The OASIS XML Conformance TC produced test suites for testing conformance or applications against the W3C XML Recommendation. The results of the TC's work can be viewed at http://www.oasis-open.org/specs/conformance.php The TC was chaired by Mary Brady of NIST, and was closed in March 2000. The TC charter is found on the TC's home page at http://www.oasis-open.org/committees/xml-conformance/index.html |
| OASIS XML Localisation Interchange File Format (XLIFF) TC |
Advancing a multi-lingual data exchange standard for localisation |
| OASIS XRI Data Interchange (XDI) TC |
Creating a standard for sharing, linking, and synchronizing data ("dataweb") over the Internet and other networks using XML documents and Extensible Resource Identifiers (XRIs) |
| OASIS XSLT Conformance TC |
Completed |
| oBIX Liaisons & Harmonizations SC |
|
| oBIX Marketing SC |
The oBIX Marketing Subcommittee’s purpose is to encourage market attention to and later adoption of the oBIX standard. One of its first goals is to encourage broader participation in the oBIX standard setting process to ensure that an appropriately broad (across controls vertical markets) participation is achieved. |
| oBIX Power Systems SC |
Power Systems Sub-Committee: This group will address topics related to the systems supporting the management of electrical power within commercial facilities. This will include the application topics of energy management, power quality and power reliability. Equipment covered will include power distribution assemblies, protective devices, power metering, backup generation equipment and uninterruptible power supplies. This sub committee will also look to the work being done in the GridWise organization to drive a common approach. |
| oBIX Reference Enterprise Specifications SC |
|
| oBIX Requirements SC |
Business Requirements Group. As oBIX exposes controls to the enterprise, it grants the enterprise permission to interact with those control systems. This committee will focus on developing use cases and prioritizing development efforts by the other subcommittees.
The List Archives contain our growing list of Use Cases for oBIX. Please read them, send us comments, or submit your own. |
| oBIX Roadmap and Deliverables SC |
This group consists of all committee chairs for the sub-committees of oBIX as well as parties who are gluttons for meetings. |
| oBIX Security SC |
Security Sub-Committee: Define the necessary extensions to the core services provided by the oBIX framework that would enable integration, interoperability and data mining across and between building security systems and other oBIX based building systems. The Sub-Committee will also provide an interface to exchange information with other existing and proposed XML/WS based initiatives and organizations in the security industry.
Scope: The Sub-Committee's scope will include Access Control, CCTV, Intrusion Detection, Fire Detection and Life Safety Systems. |
| oBIX XML Standards SC |
Our goal is to define a foundation of common types and services applicable to horizontal issues including discovery, points, historical trends, and alarming. |
| OpenDocument - Accessibility |
Statement of purpose
- Ongoing review of the OpenDocument specification for accessibility, both to discover potential accessibility issues and to improve the usability and functionality of creating, reading, and editing office documents for people with disabilities.
- To provide accessibility related feedback to the OpenDocument Technical Committee and implementors of the OpenDocument specification.
Deliverables
- Proposals for accessibility enhancements to the OpenDocument specification.
- Accessibility related guidelines for OpenDocument implementors and users.
Scope of work
The subcommittee's work is to ensure that OpenDocument schema allows to store the information that is required by applications aimed at allowing people with disabilities to access properly the content of OpenDocument documents. Manner and schedule of work
The work of the subcommittee will be primarily through a mail list set up by OASIS for subcommittee work. Access by the public will be through an openly available mail list archive. Conference calls will be scheduled on a regular basis as agreed by the subcommittee after its formation. |
| OpenDocument - Formula |
This is the subcommittee working on a specification for recalculated formulas (e.g., spreadsheet formulas) in office documents. See About OpenFormula for more information.
Please consider joining the subcommittee if you're interested; it's time to have a fully open standard for spreadsheet formulas.
|
| OpenDocument - Metadata |
Statement of purpose
--------------------
1. To gather use cases for the application of metadata in OpenDocument documents and OpenDocument aware applications.
2. To classify the use cases.
3. To derive metadata related requirements for future versions of OpenDocument from the use case classes.
4. To propose metadata related enhancements for OpenDocument for consideration by the Opendocument TC which address these requirements.
Deliverables
------------
1. A list of metadata use cases for OpenDocument documents and OpenDocument enabled applications, together with a classification of the use cases.
2. A list of metadata related requirements for future versions of OpenDocument, which will be prioritized by the OpenDocument TC.
3. Proposals for OpenDocument enhancements which address the requirements identified in deliverable 2.
Scope of work
-------------
The subcommittee's work is to collect use cases where metadata is passed or stored along with OpenDocument documents, to classify them as described above, and to derive a set of requirements for future versions of OpenDocument from these classes. The subcommittee's work further is to prepare proposal for OpenDocument enhancements which address these requirements. The use case and requirement documents shall be approved by the TC before the SC proceeds with the next specification stages.
The proposed enhancements must provide general solutions for the application of metadata in OpenDocument documents and OpenDocument aware applications in general. That is, they have to be neutral to specific metadata ontologies. The proposed enhancements further must not conflict with the processing model of OpenDocument documents for office applications.
Manner and schedule of work
---------------------------
The work of the subcommittee will be primarily through conference calls and a mail list set up by OASIS for subcommittee work, or other IT tools provided by OASIS for TC work. Access by the public will be through an
openly available mail list archive.
Conference calls will be scheduled on a regular basis as agreed by the subcommittee after its formation. |
| PKI Application Guidelines SC |
The charter of the Application Guidelines Subcommittee is to execute the Application Guidelines Implementation Plan adopted by the OASIS PKI TC.
In accordance with this charter, and with the recent approval of the OASIS PKI TC, this subcommittee has initiated a project in 2005, to identify - or create, if one does not exist - standards to enable the use of PKI for digitally signing, encrypting, or both, individual transactions within applications, so that the integrity and confidentiality of transactions are maintained, independent of transmission and storage media. |
| PKI Ask Vendors Implementation SC |
The PKI Ask Vendors Implementation SC was created by the OASIS Public Key Infrastructure Technical Committee to Subcommittee to execute the "AskVendors Implementation Plan" developed by the TC. Deliverables for the SC include:
1) Application Vendor Survey
2) List of application vendors with contacts
3) Survey Analysis Report
4) Recommendations to address survey results
The charter of the TC can be found at http://www.oasis-open.org/committees/pki/charter.php. |
| PKI Education SC |
The charter of the PKI Education Subcommittee is to execute the Education Implementation Plan adopted by the OASIS PKI TC. |
| PKI Issues SC |
The PKI Issues Subcommittee is charged with reviewing feedback on the draft PKI Action Plan and sending summaries and recommendations for changes to the PKI TC. |
| PKI Lower Costs SC |
The charter of the PKI Lower Costs Subcommittee is to execute the Lower Costs Implementation Plan adopted by the OASIS PKI TC. |
| PKI Publicity SC |
The PKI Publicity Subcommittee of the OASIS Public Key Infrastructure TC was created to assist the OASIS public relations staff with
the rollout of the PKI Action Plan. |
| PKI Survey SC |
The PKI Survey Subcommittee conducted several surveys in June and August 2003 to identify obstacles to PKI deployment and usage. The Subcommittee is currently dormant. It may reactivate if additional survey work is needed. |
| PKI Testing SC |
The charter of the PKI Testing Subcommittee is to execute the Testing Implementation Plan adopted by the OASIS PKI TC. |
| PLCS DEX Coordination SC |
The purposes of the PLCS DEX Coordination SC are:
-- Development of a DEX "cookbook" for development and integrated testing, including stages and typical timescales, based on existing PLCS inc material
-- Planning and coordination of DEX developments, including management of the
capability components of DEXes.
-- Deliverables:
-- Cookbook
-- Consolidated DEX development programme
-- Capability components |
| PLCS Fault States SC |
|
| PLCS Maintenance Plan SC |
|
| PLCS Operational Feedback SC |
|
| PLCS Product as Individual SC |
|
| PLCS Product Breakdown SC |
|
| PLCS Task Set SC |
|
| PLCS Technical Oversight Group SC |
|
| PLCS Work Package Definition and Report SC |
To develop Data Exchange Set definitions for requesting and reporting product support work packages based on ISO 10303 AP239. |
| Rights Examples SC |
|
| Rights Extensions SC |
|
| Rights Governance and Liaison SC |
|
| Rights Profiles SC |
|
| Rights Requirements SC |
|
| Rights Specification SC |
|
| SAML Adoption SC |
|
| SCA Assembly Editors |
|
| SCA Assembly Testing |
|
| SCA Bindings Editors |
|
| SCA BPEL Editors |
|
| SCA J Editors |
|
| SCA Policy Editors |
|
| SOA Blueprints Applicants (temp) |
|
| SOA-RM Editors Subcommittee |
This is a subcommittee of the OASIS SOA Reference Model Technical Committee. |
| SOA-RM Reference Architecture Subcommittee |
|
| Tax Business Analysis SC |
|
| Tax Technical Analysis SC |
|
| Tax XBRL Liaison SC |
|
| UBL Administration SC |
|
| UBL Adoption SC |
The membership of the UBL Adoption SC constitutes the editorial board of UBL XML.org, the online community for the Universal Business Language (UBL) OASIS Standard.
Please visit http://ubl.xml.org to contribute to this community forum. |
| UBL Chairs SC |
|
| UBL Chinese Localization SC |
UBL 中文化科技委员会, 我们的工作包括以下各样:
- 翻译 UBL 1.0 Package 里面的文件成为中文
- 建立一个中文资源网站, 并在其上提供 UBL 的新闻和使用例子
- 研究现在 UBL 文件中的语义是否适合在中国使用
如果你对我们的工作有兴趣, 欢迎透过电邮与我们联络, 我们的电邮是 ubl-cnlsc@lists.oasis-open.org. |
| UBL Code List SC |
The UBL Code List Subcommittee has been established by the OASIS Universal Business Language TC to
- To complete the code list position paper in light of input received [for publication as] a TC Draft.
- To define a standard schema template for code lists (and possibly adjunct data) based on existing NDR specifications.
- To work with NDRSC on any changes to the NDRs.
- To work with LCSC to create "standard" and "stock" code lists for inclusion with UBL 1.0 FCS.
- To define a maintenance and versioning strategy for the code lists included in UBL. |
| UBL Context Drivers SC |
|
| UBL Context Methodology SC |
|
| UBL Danish Localization SC |
The UBL Danish Localization Subcommittee has been created by the OASIS Universal Business Language TC to produce content in the Danish language for UBL. |
| UBL Forms Presentation SC |
To rapidly develop and document formal technology-agnostic Formatting Specifications and foster their implementations.
Complete Charter Document (in another window) |
| UBL Human Interface SC |
To develop and document formal technology-agnostic specifications for the input and the presentation of UBL information, and to foster implementations of these specifications from industry. |
| UBL Implementors SC |
The UBL Implementors Subcommittee has been established by the OASIS Universal Business Language TC to
- Monitor public discussions of UBL implementation and develop the UBL response to salient postings.
- Collate issues discovered during the UBL implementation phase and convey them to the UBL LCSC, NDRSC, and FPSC. |
| UBL Italian Localization Subcommittee |
Il Sottocomitato Italiano di Localizzazione UBL è stato creato dal Comitato Tecnico per il Linguaggio di Business Universale (UBL) di OASIS per fornire contenuti UBL in lingua italiana e promuovere UBL in Italia.
 Specifiche
-
NOTA:
La Specifica UBL 2.0 ed il Dizionario Internazionale dei Dati di business (IDD) sarà disponibile nei prossimi mesi in lingua italiana.
- Supporto
Trovate materiale di supporto a UBL presso: ubl-ssc
- Corsi
- Sono disponibili corsi e seminari gratuiti su UBL tenuti dall'Ente ENEA.
Lingua: italiano
Corsi su UBL e ebXML
Per informazioni contattare:
arianna.brutti@bologna.enea.it
- Su richiesta è possibile organizzare corsi avanzati tenuti direttamente da esperti del Comitato Tecnico di UBL (anche presso la Vs. sede)
Lingua: inglese
Per informazioni contattare:
roberto@javest.com
- Conferenze
- 25 Ottobre 2007 - Italian UBL Workshop
- c/o Sede Centro ENEA
Lungotevere Thaon di Revel, 76
Roma
Informazioni e Presentazioni: www.ubl-italia.org
- 21-24 Aprile 2008 - UBL International
- c/o CNEL
Viale Davide Lubin, 2
Roma
Iscrizioni: www.ublconference.org
|
| UBL Japanese Localization SC |
The UBL Japanese Localization Subcommittee has been established by the OASIS Universal Business Language TC to produce content in the Japanese language for UBL. |
| UBL Korean Localization SC |
The UBL Korean Localization Subcommittee has been established by the OASIS Universal Business Language Technical Committee to produce content in the Korean language for UBL. |
| UBL Liaison SC |
|
| UBL Library Content SC |
The purpose of this subcommittee is to rapidly develop standard XML business library content by taking an existing library as a starting point and modifying it to incorporate the best features of other existing business and core component libraries.
Set of deliverables:
* Create a Library of Basic Information Entities.
* XML (XSD) Schemas for business document types based on these BIEs.
* Example instance for each schema.
* Customization methodology.
* Documentation for business documents.
* Publication into Public Registries. |
| UBL Localization List |
The UBL Localization List was established by the OASIS Universal Business Language TC for the purposes of coordinating efforts across the TC's various localization subcommittees. |
| UBL Marketing SC |
|
| UBL Naming and Design Rules SC |
The purpose of the NDR SC is to recommend to the TC rules and guidelines for normative-form schema design, instance design, and markup naming, and write and maintain documentation of these rules and guidelines. |
| UBL Procurement SC |
The UBL Procurement Subcommittee was created by the OASIS Universal Business Language (UBL) Technical Committee. See http://lists.oasis-open.org/archives/ubl/200508/msg00031.html. |
| UBL Small Business Subcommittee |
The UBL Small Business Subcommittee was created by the OASIS Universal Business Language (UBL) Technical Committee. See
http://lists.oasis-open.org/archives/ubl/200502/msg00057.html. |
| UBL Spanish Localization SC |
The UBL Spanish Localization Subcommittee has been created by the OASIS Universal Business Language TC to produce content in the Spanish language for UBL.
El SubComité Español de Localización UBL ha sido creado por el Comité Técnico Lenguaje Comercial Universal (UBL) de OASIS para producir contenido UBL en idioma español y para promocionar UBL en España y Sudamérica. |
| UBL Support SC |
|
| UBL Tools and Techniques SC |
|
| UBL Transportation SC |
The UBL Small Business Subcommittee was created by the OASIS Universal Business Language (UBL) Technical Committee. See
http://lists.oasis-open.org/archives/ubl/200508/msg00032.html |
| WS Transaction Implementers Subcommittee |
The WS-TX Implementers Subcommittee was formed by the OASIS Web Services Transaction(WS-TX) Technical Committee to focus on implementation issues for implementers and interested parties. |
| WS-CAF Editors SC |
The WS-CAF Editors Subcommittee was established by the OASIS Web Services Composite Applications Framework TC as a working list for specification editing. |
| WS-CAF Implementation SC |
The WS-CAF Implementation Subcommittee has been formed by the OASIS Web Services Composite Application Framemork TC to discuss implementation issues related to the work of the WS-CAF TC and possible interoperability demonstrations of that work. |
| WS-RX Editors SC |
The WS-RX Editors Subcommittee was established by the OASIS Web Services Reliable Exchange TC as a working list for specification editing. |
| WS-RX Implementation SC |
The WS-RX Implementation Subcommittee was formed by the OASIS Web Services Reliable Exchange (WS-RX) Technical Committee to focus on implementation issues. |
| WS-TX Editors SC |
The WS-TX Editors Subcommittee is a subcommittee of the OASIS Web Services Transactions TC, for specification and issues
editors and interested parties. The subcommittee will use its mailing list for communicating subcommittee information that is not of interest to the wider TC. |
| WSBPEL Abstract List |
Completed
This is an informal break-out discussion list for WSBPEL TC participants interested in working on abstraction of WSBPEL. |
| WSBPEL Implementations List |
Completed
The purpose of this list is to facilitate implementation issue discussion for the WSBPEL TC. Please contact Diane Jordan (drj@us.ibm.com) if you would like additional information or are interested in joining this list. |
| WSBPEL Liaison Coordination List |
Completed
The purpose of this list is to coordinate liaison activity for the WSBPEL TC. Please contact Diane Jordan (drj@us.ibm.com) if you would like additional information or are interested in joining this list. |
| WSBPEL Primer SC |
Completed
The purpose of this group is to develop a non-normative primer for the WS-BPEL spec.
The BPEL Primer subgroup will hold weekly conference calls – Wednesdays from 8-9 AM PT.
Note that normative BPEL calls may be scheduled at this time and will take priority over BPEL Primer calls (both calls use the same conf call numbers - see below).
Meetings are published on the "main" BPEL TC calendar, not the calendar for this subgroup.
Dial in info is: USA & Canada Toll Free Number: +1 866 500 6738, Pass code: 600345, All Others (toll): +1 203 480 8000, Pass code: 600345.
We can also use the irc at http://webconf.soaphub.org/conf/room/wsbpel if necessary. |
| WSBPEL Requirements and Issues Coordination List |
Completed
The purpose of this list is to collect and track requirements and issues for the WSBPEL TC and its specification. Please contact Diane Jordan (drj@us.ibm.com) if you would like additional information or are interested in joining this list. |
| WSBPEL Specification Editing List |
Completed
The purpose of this list is to work on the detailed editing of the WSPBPEL specification drafts. Please contact Diane Jordan (drj@us.ibm.com) if you would like some additional information or are interested in joining this list. |
| WSBPEL State Diagram List |
Completed
The purpose of this list is to coordinate activity for the WSBPEL TC on state diagrams and the Coordination Protocol (formerly Appendix C of the draft spec). Please contact Diane Jordan (drj@us.ibm.com) if you would like additional information or are interested in joining this list. |
| WSBPEL Use Cases List |
Completed
The purpose of this list is to define and manage Usage Scenarios for the WSBPEL TC and its specification. Please contact John Evdemon (jevdemon@microsoft.com) if you would like some additional information or are interested in joining this list. |
| WSRM Interoperability Demo SC |
The Web Services Reliable Messaging Interoperability Subgroup provides a forum for the interoperability test of implementations of the Web Services Reliability Specification, the demonstration of this interoperability and the promotion of the specification. |
| WSRP Conformance SC |
|
| WSRP Cross-Portlet Coordination SC |
|
| WSRP Description and Transport Issues SC |
|
| WSRP Interfaces SC |
|
| WSRP Interoperability SC |
|
| WSRP Markup SC |
|
| WSRP Primer SC |
The subcommittee will create the WSRP Primer, a companion document to the WSRP specification. |
| WSRP Publish/Find/Bind SC |
|
| WSRP/WSIA Joint Interfaces SC |
|
| XCBF Liaison SC |
XCBF TC Liaison SC Members
Tyky Aichelen
Phil Griffin
Monica Martin
Bancroft Scott - SC Chair
Liaison - ITU-T Study Group 17 (SG17) Question 10 (Q10)
Dr Paul Gérôme
Liaison - OASIS Security Joint Committee (SJC)
Tyky Aichelen
Phil Griffin
Monica Martin
|
| XLIFF Profiles SC |
|
| XLIFF Segmentation SC |
|
| XRI Editors SC |
|
