Compliance

["Pascal Coupet" <pascal.coupet@temis.com>]

We had a discussion during the last TC conf call about what will mean
UIMA compliance and what should be enforced if any. 

I had a quick look to different OASIS standard and get different methods
related to compliance, from very strict to relaxed ones. 


Test suites:
============

A first way to provide some compliance level is to provide test suites,
like Java does. See by example the OGC page dedicated to this method 
http://xml.coverpages.org/OGC-ComplianceTests.html
A test suite can be a validation (must pass the test) or produce a level
of compliance with some mandatory tests and others optional, providing a
compliance score. 
Test suites are organized by domain in large projects

In UIMA context (example)
A test suite will contain an annotator to be deployed (and wrapped if
needed if the framework use a different communication protocol), a set
of documents, and the expected results. 
Different suites can test different parts of the specification. 
We may dedicate some test suites form samples and examples from the
Apache delivery. 

Reference implementation: 
=========================

On the same page from OGC you can see a second method which is to
provide a reference implementation. Not exactly a measure of compliance
but guidance and a reference.

In UIMA context (example)
We may issue a recommendation that it is expected that a future version
of Apache UIMA will be compliant with the specification  

Formal Grammar/description:
===========================

This is more for document format and eventually exchanges through XML
format. 
 
Test Application: 
=================

An available application is capable to test several functions of an
implementation.



In general, We can imagine compliance at different levels in UIMA.
Probably the most important is to be able to deploy annotators, sources
and consumers without too much pain. This is booth a need for people who
want to develop one of these components and for people who want to
develop a framework to manage them. It will be interesting to have a
test suite covering these cases. 


An interesting link on compliance in general:
http://www.consortiuminfo.org/cb/


Pascal








Pascal Coupet
Chief Technology Officer & Co-founder

TEMIS INC
1518 Walnut Street, suite 1702, Philadelphia, PA 19102, USA
 Tel:   +1 215 732 2549 ext 112 
Mob:   +1 215 609 2514
Fax:   +1 215 732 0490 
www.temis.com
 

Strictly Personal and Confidential
This message may contain confidential and proprietary material for the
sole use of the intended recipient. Any review or distribution by or to
others is strictly prohibited. If you are not the intended recipient,
please contact the sender and delete all copies.

-----Original Message-----
From: ehn@cs.cmu.edu [mailto:ehn@cs.cmu.edu] 
Sent: Friday, March 14, 2008 4:55 PM
To: uima@lists.oasis-open.org
Subject: [uima] Groups - UIMA TC Meeting Minutes of Mar 15 2008
(minutes20080315.txt) uploaded

The document named UIMA TC Meeting Minutes of Mar 15 2008
(minutes20080315.txt) has been submitted by Eric Nyberg, 3rd to the
OASIS
Unstructured Information Management Architecture (UIMA) TC document
repository.

Document Description:


View Document Details:
http://www.oasis-open.org/apps/org/workgroup/uima/document.php?document_
id=27588

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/uima/download.php/27588/min
utes20080315.txt


PLEASE NOTE:  If the above links do not work for you, your email
application
may be breaking the link into two pieces.  You may be able to copy and
paste
the entire link address into the address field of your web browser.

-OASIS Open Administration