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: Call to Vote: Two ballots for OASIS Standard - Electronic Court Filing V4.01 and Content Management Interoperability Services (CMIS) V1.1


OASIS Members:

This Call to Vote covers two OASIS Standard ballots: Electronic Court Filing Version 4.01 and Content Management Interoperability Services (CMIS) Version 1.1. I have combined these announcements to make it easy for you to review and address both in a single communication. 

The ballots can be found at the following URLs. Details about the Candidate OASIS Standards can be found further in this email. 

=== Electronic Court Filing Version 4.01 
Internal OASIS link: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=2407

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=2407

=== CMIS 
Internal OASIS link: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=2408

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=2408


This is a call to the primary or alternate representatives of OASIS Organizational Members to vote. The Technical Committees have satisfied all requirements of the OASIS TC Process and these Candidate OASIS Standards are now submitted to the voting representatives of OASIS organizational members.

The minimum number of affirmative votes required to approve these ballots is 49 (15% of 323 member organizations).


=== Additional Ballot Details:

===== Electronic Court Filing Version 4.01 

The OASIS LegalXML Electronic Court Filing TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS membership to a membership vote for OASIS Standard:

Electronic Court Filing Version 4.01
Candidate OASIS Standard 01
17 January 2013

This is a call to the primary or alternate representatives of OASIS Organizational Members to vote. The Technical Committee has satisfied all requirements of the OASIS TC Process and the Candidate OASIS Standard is now submitted to the voting representatives of OASIS organizational members.

-- Voting Details --

The ballot opens on 09 May 2013 at 00:00 GMT and closes on 23 May 2013 at 23:59 GMT. You can access the ballot to cast your vote at:

Internal OASIS link: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=2407

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=2407

The minimum number of affirmative votes required to approve this ballot is 49  (15% of 323).

Each OASIS organizational member has one vote. OASIS members should ensure that their organization's voting representative votes according to the organization's wishes. If you do not know the name of your organization's voting representative is, go to the My Account page at

http://www.oasis-open.org/members/user_tools

then click the link for your Company (at the top of the page) and review the list of users for the name designated as "Primary".

-- Information about the Candidate OASIS Standard and the LegalXML Electronic Court Filing TC  -- 

This specification describes the technical architecture and the functional features needed to accomplish a successful system for submitting electronic
filings to courts of law. It defines both the normative (required) and non-normative (optional) business processes it supports. The non-functional requirements associated with electronic filing transactions, as well as the actions and services needed to accomplish the transactions, such as network and security infrastructures, are defined in related specifications, namely: 

- Service interaction profile specifications that define communications infrastructures, within which electronic filing transactions can take place;  
- Document signature profile specifications that define mechanisms for stating or ensuring that a person signed a particular document. 

This specification supports a number of automated information exchanges such as:

- Transmission of documents in electronic form from law firms and from other persons and organizations to a court for entry ("official filing") into the
court's official case records; 
- Recording of documents in electronic form from members of the court and court administrators into the court's official case records;  
- Transmission of data needed to complete (or demonstrate the previous completion of) financial transactions involving filing fees or the payment of
any other court fees, fines and financial obligations;  
- Transmission of the metadata needed to initiate a new case record in a court's automated case management system (CMS) when the document being transmitted is one that commences a new case in that court;  
- Messages returned to the sender that confirm a court's receipt of the sender's filing message; 
- Messages notifying the sender of events such as the entry of the document(s) submitted by the sender into the court record (or an error message stating that the document[s] could not be accepted for filing and stating the reason[s] why);  
- Transmission of copies of documents submitted for filing to the other parties in a case who are registered to receive service electronically. 

This specification defines a set of core structures that are common to most types of court filings and defines specific structures that apply to filing
documents in the following types of court cases: 

- Appellate 
- Bankruptcy 
- Civil (including general civil, mental health, probate and small claims) 
- Criminal (both felony and misdemeanor) 
- Domestic relations (including divorce, separation, child custody and child support, domestic violence and parentage, i.e., maternity or paternity) 
- Juvenile (both delinquency and dependency) 
- Violations (including traffic, ordinances and parking) 

The basic structure will support other types of court filings and is extensible through court-specific and case-type-specific extensions. 

National Information Exchange Model (NIEM) conformance, as defined by the NIEM Implementation Guidelines (NIEM Guide), is a core objective of this
specification. The NIEM is an XML standard designed specifically for justice information exchanges. ECF V4.01 uses the NIEM version 2.0 where the structures and definitions correspond to the requirements of ECF V4.01. 

OASIS Universal Business Language (UBL) is an OASIS Standard that provides a single ubiquitous language for business communication, and takes into account the requirements common to all enterprises. ECF V4.01 employs OASIS Universal Business Language (UBL) to describe filing payments and payment receipts. 

The W3C XML Signature Syntax and Processing (XMLSIG) specification describes a mechanism for signing electronic documents. ECF V4.01 employs the XMLSIG specification to describe digital signatures applied to the entire ECF V4.01 message. 

OASIS Reference Model for Service Oriented Architecture (SOA-RM) is a framework for understanding significant entities, and the relationships between those entities, within a service-oriented architecture. ECF V4.01 describes such an architecture and includes terminology that conforms to the SOA-RM. 

OASIS Code List Representation (Genericode) is a model and XML schema that can be used to encode a broad range of code list information. All ECF V4.01 code lists that are not defined in the NIEM are provided in Genericode 1.0 format. 

ECF V4.01 received Statements of Use from Intresys Inc., ImageSoft Inc., and URL Integration Inc. [2]. 

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

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

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

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

Distribution ZIP files:

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/legalxml-courtfiling/specs/ecf/v4.01/ecf-v4.01-spec/cos01/ecf-v4.01-spec-cos01.zip 

-- Additional information -- 

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

TC Charter
https://www.oasis-open.org/committees/legalxml-courtfiling/charter.php 

[2] Statements of Use: 
Intresys Inc.:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201301/msg00015/StatementOfUse.IntresysToECFTC.DOCX

ImageSoft Inc.:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201209/msg00017/ECF_Statement_of_Use.pdf

URL Integration Inc.:
https://lists.oasis-open.org/archives/legalxml-courtfiling/201208/msg00042.html


===== Content Management Interoperability Services (CMIS) Version 1.1 

The OASIS Content Management Interoperability Services (CMIS) TC members [1] have approved submitting the following Candidate OASIS Standard to the OASIS membership to a membership vote for OASIS Standard:

Content Management Interoperability Services (CMIS) Version 1.1
Candidate OASIS Standard 01
01 February 2013

This is a call to the primary or alternate representatives of OASIS Organizational Members to vote. The Technical Committee has satisfied all requirements of the OASIS TC Process and the Candidate OASIS Standard is now submitted to the voting representatives of OASIS organizational members.

-- Voting Details --

The ballot opens on 09 May 2013 at 00:00 GMT and closes on 23 May 2013 at 23:59 GMT. You can access the ballot to cast your vote at:

Internal OASIS link: https://www.oasis-open.org/apps/org/workgroup/voting/ballot.php?id=2408

Publicly visible link: https://www.oasis-open.org/committees/ballot.php?id=2408

The minimum number of affirmative votes required to approve this ballot is 49 (15% of 323 member organizations).

Each OASIS organizational member has one vote. OASIS members should ensure that their organization's voting representative votes according to the organization's wishes. If you do not know the name of your organization's voting representative is, go to the My Account page at

http://www.oasis-open.org/members/user_tools

then click the link for your Company (at the top of the page) and review the list of users for the name designated as "Primary".

-- Information about the Candidate OASIS Standard and the OASIS Content Management Interoperability Services (CMIS) TC -- 

CMIS specifies a protocol-layer interoperability interface for content management. It addresses the widespread “content silo” problem whereby enterprise contents are trapped in disparate repositories. CMIS also facilitates the emerging “content in the cloud” paradigm and mobile computing. The CMIS v1.0 OASIS Standard contains a domain model with a set of services, and two protocol bindings: a WSDL-based Web Services binding (serviceoriented), and a “RESTful” Atom Publishing Protocol binding (resource-oriented). The interface is designed to be easily layer-able on top of most content management systems to provide a common interface for generic content management functions. CMIS is not intended to expose or replace all the capabilities of every proprietary full-function content management system. A summary of CMIS v1.0 can be found at http://www.oasis-open.org/committees/download.php/36826.

Since the publication of the CMIS v1.0 standard, many repository vendors have offered CMIS v1.0 services for their products, and many application developers have used CMIS v1.0 to access/manage content. Based on the CMIS v1.0 experience and feedback, the v1.1 specification is developed to further enrich the CMIS functionality and protocol support. Specifically, CMIS v1.1 adds to CMIS v1.0 the following new features:

- Type Mutability
Allow CMIS clients to create, modify, and delete Type Definitions and Property Definitions for a given repository.

- Repository Features
Allow CMIS clients to discover any extensions or additional CMIS-based standards supported on each repository.

- Secondary Object Type
Named sets of properties that can be dynamically added and removed from individual CMIS objects.

- Retention and Hold
Use secondary types to support Retention and Hold on CMIS objects. A Retention protects an object from deletion, while a Hold protects an object from modification.

- “cmis:item” Object Type
A new top-level data model type that is an extension point for repositories that need to expose other object types via CMIS that do not fit the CMIS model's definition for document, folder, relationship, or 
policy.

- “bulkUpdateProperties” Service
A method for supporting bulk property updates on a set of objects within a single service call.

- Append to a content stream
Support for appending to a content stream. Allow clients to break a very large upload of document content into many smaller calls.

- Browser Binding
A new optional binding specifically designed to support applications running in a web browser or other clients without the need for any additional client library. Notable among the differences in this binding are the use of JSON (Java Script Object Notation) instead of XML and the exclusive use of HTTP GET and POST for all operations.

CMIS V1.1 received Statements of Use from SAP AG, the Apache Chemistry OpenCMIS subproject and Alfresco Software Inc. [2]

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

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

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

Editable source: 
The CMIS TC generates PDF and HTML versions of the specification from TeX source. The editable TeX source files are availalbe at:
http://docs.oasis-open.org/cmis/CMIS/v1.1/cos01/tex/

Schemas and WSDL: 
http://docs.oasis-open.org/cmis/CMIS/v1.1/cos01/schema/

Examples: 
http://docs.oasis-open.org/cmis/CMIS/v1.1/cos01/examples/

Distribution ZIP files:

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/cmis/CMIS/v1.1/cos01/CMIS-v1.1-cos01.zip

-- Additional information -- 

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

TC Charter
https://www.oasis-open.org/committees/cmis/charter.php

[2] Statements of Use: 
SAP AG: 
http://lists.oasis-open.org/archives/cmis/201212/msg00011.html 

The Apache Chemistry OpenCMIS subproject 
https://lists.oasis-open.org/archives/cmis-comment/201212/msg00000.html 

Alfresco Software Inc.: 
http://lists.oasis-open.org/archives/cmis/201301/msg00005.html 

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393


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