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

 


Help: OASIS Mailing Lists Help | MarkMail Help

legalxml-courtfiling-policy message

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


Subject: [legalxml-courtfiling-policy] OASIS LegalXML ECF Court PolicyRequirements document


I believe this is my initial posting on this discussion group, so let me introduce myself first.  My name is Christopher Smith of the California Administrative Office of the Courts.  I am now the voting member for the California AOC.    
 
I have concerns regarding the inconsistent structure of the ECF Court Policy Requirements. There seems to be considerable confusion about how Court Policy, CDC, and Query-Response are interrelated. This document appears to define elements of CDC (it shouldn't), hypothesizes a <getPolicy> query that does not exist in the latest version of the Query and Response specification, and includes requirements for a publish-and-subscribe capability that isn't in any version of the EFM-CMS API requirements document. 
 
Additionally, there is insufficient narrative describing the intent of each requirement and many requirements are unclear or need further explanation.  Finally, these Requirements do not include anything substantive on conformance and interoperability test requirements, despite the proposal for such in Salt Lake City and the work of the Washington State contingent since then. 
 
As I have strong misgivings about the suitability of the document as the basis for a useful specification, I vote to not accept it in its current state.
 
Christopher Smith
Information Services Department
California Administrative Office of the Courts
 
 
 

Attachment: Comments, v2 - Court Policy Interface Requirement 2002_10_18.doc
Description: Comments, v2 - Court Policy Interface Requirement2002_10_18.doc



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


Powered by eList eXpress LLC