[legalxml-courtfiling-repository] FW: Kick-off discussion: TrustedSpecification Repository Subcommittee Concept/requirements

["Lewis, Diane" <Diane.Lewis@usdoj.gov>]

second try.... diane

 -----Original Message-----
From: 	Lewis, Diane  
Sent:	Monday, July 29, 2002 11:21 AM
To:	'legalxml-courtfiling-repository@lists.oasis-open.org'
Subject:	Kick-off discussion: Trusted Specification Repository Subcommittee Concept/requirements

Greetings!
During the time period August 1- 16th i would like to receive your thoughts on the definition of a trusted specification repository (LegalXML network point of view; LegalXML Court Filing; Court Document points of view) via this list.  Karl tells me that we have 8-10 members so i look forward to lively discussions and detailed input based on everyone's experiences, expertise and knowledge of available resources.  appreciate your interest in this topic! 

The starting point of course is part 5 of Roger Winters Proposed Process for Specifications:

"V. Final Posting of Recommended Specification -- The Editor, WebMaster, and others who may be responsible for document mangaement for the TC, would finalize the specification (not altering the substance) for posting and entry into the TC's "Trusted Repository." ( subcommittee working on that). Changes and enhancements would be managed as new versions, updates, etc., applying the TC's standard methods for document management and version control."

As the TC's Editor finalizes the processing steps for TC specs.... August 12th...  we can identify a repository concept and list of requirement to support that process.

Items for feedback:

1. Definition of use and by whom?
 what is the most effective, efficient utilization of a trusted repository by the LegalXML Court Filing TC?

Community of interest for content... who are they??
likelihood of document exchange  (only publication via OASIS)???
scope of content in the repository???

Proposed Objectives of a Trusted repository:

a. provide an electronic document repository for only final versions of proposed specifications and approved specifications produced by  LegalXML ECF TC and subcommittees?

b. implement a security model that is "trusted by all TC members and community of interest"
	including back-up and recovery capability

c. open architecture whereby all TC members have desktop access to the repository on demand

d. implement a scalable solution that meets the repository content requirements and potential growth

e. content in the repository will be XML documents or components which are validated prior to entry into the repository

f. interface to the repository will provide simple index schema or limited search capability or only click/view or save doc to desk top.


2. physical location of a trusted repository...  what are the requirements?

a. Karl has told me that OASIS can currently offer a direction on the web/ ftp access to document via new legalxml web page.. to be created as the trusted repository link/page.

impact:  TC Editor; TC webmaster

b. TC member sponsorship of repository with publication of completed specifications for review or approval... published via OASIS resources.

identified issues:  
how to provide TC wide access?
how best to implement governance and management  (need for low maintenance solution?) of repository to gain the trust of TC members?

3. architecture of a trusted repository

search capability?  index, table of contents
interfaces and linkages?

granularity:  storage of data elements, namespaces, schemas, or just specification documents as unstructured documents

4.  other concerns, issues or thoughts on the topic of building a trusted specification repository?

look forward to reading replies   thanks diane lewis Trusted repository subcommittee chair