[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [legalxml-enotary] Consultant tasks
Rough Prefatory note: With regard to the 5 items that are listed below all deal with the five signature profiles. Items 1 and 2 deal with binary or dumb documents, and 3, 4 and 5 with smart documents. In the process of developing 3, 4 or 5 while there may be certain changes needed to be made to 1 and 2, it is expected they will build upon 1 and 2. In all cases, all the five signature profiles are intended to be developed and no additional profiles are expected. > -------- Original Message -------- > From: John Messing <jmessing@law-on-line.com> > Date: Wed, October 17, 2007 12:19 pm > To: legalxml-enotary@lists.oasis-open.org > > > FWIW > > Proposed Tasks > > 1. 30 days -Consultant will provide a draft schema to the TC within > 60 days consistent with the Use Case document version 0.9 to implement > the Binary File MarkUp for eNotarization TC, first rough draft, revision > 2. > 2. 90 days -Consultant will provide an Enotary Specification for > binary file markup for all other use cases as outlined in the face to > face meeting minutes of July 2007, building upon the schema in number 1 > and making such changes and modifications thereto as directed by the TC > and incorporating the other TC use cases. > > 3. 180 days -Consultant will provide a complete draft EN 1.0 > Specification including a compliant with for structure and semantics, > and consistent with current PRIA and MISMO and the National Information > Exchange Model (NIEM) 2.0 releases, the TC use case document, and the > existing signature profiles. > > 4. 240 days -Consultant will provide a near final EN 1.0 Core > Specification with such draft Profile Specifications as may be > practically required to achieve interoperable applications. > > 5. 360-450 days -Consultant will finalize all specifications in > light of comments. > > Schedule B > > Rate Sheet > > Consultant will provide the following staff to perform the services > listed in Schedule A at the standard hourly rates listed below. The > total cost of the project, including both professional services and > expenses, will not exceed $50,000. Consultant will bill OASIS $15,000 > upon delivery and acceptance of deliverables 1-2 to the TC, $20,000 upon > delivery and acceptance of deliverables 3-4 to the TC, and the remainder > at the conclusion of the project. > > I think this is a good starting basis. > ----- Original Message ----- > From: John Messing > To: Arshad Noor > Cc: Rolly Chambers ; Mark Ladd > Sent: Thursday, October 11, 2007 9:43 AM > Subject: RE: Update > > > According to Patrick Gannon, there is a form of contract that has two > appendices. The TC and the consultant need to reach agreement on the > appendices. The first principally includes these topics: tasks and > deliverables, and a rate sheet. The rest is pretty much standard. > > What follows is an example drawn from the Electronic Court Filing TC > contract of this year: > > Tasks > > 1. Consultant will provide the ECF 3.1 Core Specification including > a > complete Information Exchange Package Documentation (IEPD) compliant > with the Global Justice XML Data Model (GJXDM) 3.0.3. ECF 3.1 will > include the following additions/modifications to the 3.0 specification: > a. Add bar number > b. Add person identifier (id/idref) > c. Add transactional case identifiers > d. Add policy enhancements for hierarchies and context > e. Add support for multiple filing parties > f. Add a timestamp > g. Add support for demand and judgement amounts > h. Add support for multiple versions of the same document > i. Add child support elements > j. Add additional instances > k. Add description of architectural principles > l. Add description of approach for self represented litigants > m. Add description of version changes > n. Change mappings/definitions to reconcile with GJXDM > o. Change fee query to return itemized filing related fees > p. Change DocumentType to not require CaseCourtEvent > q. Change CourtEvent to support multiple documents > r. Change schemas as needed to fix validation issues > s. Change references to externally defined schemas > > 2. Consultant will provide the ECF 3.1 Web Service SIP > Specification > including the following additions/modifications to the 3.0 > specification: > a. Change web services SIP to use MTOM > > 3. Consultant will provide the ECF 4.0 Core Specification including > a > complete Information Exchange Package Documentation (IEPD) compliant > with the National Information Exchange Model (NIEM) "Harmony" release. > ECF 4.0 will include the following additions/modifications to the 3.1 > specification: > a. Add appellate courts case types > b. Add lower courts (traffic, etc.) case types > c. Add description of version changes > d. Change party attorney relationships > e. Change core specification to conform to NIEM > f. Change service schemas as needed > > 4. Consultant will provide the ECF 4.0 Web Service SIP > Specification > which will include the following additions/modifications to the 3.1 > specification: > a. Add support for bulk filings to web services SIP > b. Add support for chunking to web services SIP > > With regard to rates, with confidential information removed, this is > what the contract provided: > > Schedule B > > Rate Sheet > > Consultant will provide the following staff to perform the services > listed in Schedule A at the standard hourly rates listed below. The > total cost of the project, including both professional services and > expenses, will not exceed $25,800. Consultant will bill OASIS $10,000 > upon delivery of deliverables 1-2 to the TC and the remainder at the > conclusion of the project. > > I think this is a good starting basis. > > > -------- Original Message -------- > > From: Arshad Noor <arshad.noor@strongauth.com> > > Date: Thu, October 11, 2007 8:56 am > > To: John Messing <jmessing@law-on-line.com> > > > > > > What do you need from me as a next step, John, to be in > > the running for this? Thanks. > > > > Arshad > > > > John Messing wrote: > > > The Steering Committee today approved the additional eNotary budgetary > > > consulting funds for 2008. The TC intends to enter a consulting contract > > > at the earliest possible time. > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]