Clause model - solution proposals

[Jason Harrop <jharrop@speedlegal.com>]

In our last teleconf, we accepted the clause model requirements doc and 
agreed to follow a process (cut and pasted below for convenience) to 
develop a clause model.

Step (a) of that process invites "interested TC members to forward 
proposals to the mailing list which satisfying [sic] all or part of the 
requirements (a 3 week period concluding 9 July). Such proposals could 
be complete solutions, or contribute partial or point solutions, 
intended to be used as part of a complete solution."

The purpose of this post is to try to offer some guidance about what 
would be the best way to frame a proposal so it is most useful as input 
to the process.

My thoughts on what should appear in a proposal:

1. some introductory text summmarising the proposal, and explaining the 
philosophy behind the approach.

2. material organised in the same order as the 11 "Specific 
requirements" appear in the requirements document, commenting on how 
well the proposal addresses each requirement, and summarising with 
"meets" or "does not meet".

3. (if applicable) a DTD (in a separate file) implementing the proposal. 
  (If your proposal can't be represented using a DTD, please explain 
why, and use your preferred alternative)

4. well-formed XML (in a separate file) which shows how the proposal 
would apply to the Clause structure example which is to be found in 
Attachment 1 of the requirements document.  State whether this XML is 
valid against item 3 above or not.

Have i missed anything?  As always, comments welcome.

kind regards,


Jason





The requirements doc:

http://www.oasis-open.org/apps/org/workgroup/legalxml-econtracts/download.php/2390/ClauseModel-Requirements-1.pdf


--------------------

3.2.2. that the TC develop a Clause Model addressing those requirements, 
according to the following process:

(a) interested TC members to forward proposals to the mailing list which 
satisfying all or part of the requirements (a 3 week period concluding 9 
July).

Such proposals could be complete solutions, or contribute partial or 
point solutions, intended to be used as part of a complete solution.

(b) Jason Harrop to prepare a report to the TC recommending a clause 
model which takes those contributions in to account. The report is to 
include the clause model and a summary of the contributions received.
(it is expected this report could be completed in 4 weeks from 9 July, 
namely 6 August).

(c) draft report to be circulated to TC members who had contributed 
proposals as input to that work, for comment and fine tuning, before 
surfacing on the mailing list

(d) mailing list and teleconference discussion, and possible further 
fine tuning

(e) TC to vote to accept the report.