WikiVisor (talk | contribs)
Created page with "== WikiDeal == The proposed project scope cannot be solely implemented on the MediaWiki platform. While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature,..."
 
WikiVisor (talk | contribs)
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
== WikiDeal ==
== WikiDeal ==
The proposed project scope cannot be solely implemented on the MediaWiki platform.  
The proposed project scope cannot be solely implemented on the MediaWiki platform.  


While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements of the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow unattainable.
While MediaWiki excels in collaborative text editing and knowledge creation, its design, geared towards openness, proves inadequate for handling electronic signatures, private data, and sensitive or confidential content. The platform lacks official support for splitting access to content on a per-page basis, making it insufficiently secure for documents of a legal nature, such as contracts. Storing personalized clauses globally in the central database would significantly escalate the requirements for the database server. It is imperative not to store personal data on the wiki, including actual values of sensitive contract variables or real contracts. The above factors render the signing workflow unattainable.


What we can do, however, is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder. This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.
What we can do, however, is utilize MediaWiki as a repository for clauses and contract models, with an integrated interactive contract prototype builder. This tool should enable users to pass variables, configure options, preload predefined sections and clauses, and select additional clauses from a designated "bank." Users should also be able to adjust the ordering of these components. The system will generate a dynamic preview of the contract, incorporating the selected clauses aligned with the contract model and substituting dynamic variables with values provided. It can be printed as is on the fly. The resulting text will not be stored or edited on the wiki.
Line 13: Line 14:


# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The wiki'''. Open to the community. Focused on creating contract model collections for different deals, countries, and use cases (and in multiple languages, maybe). Allows standard contract construction and printing. Even anonymously. It is already a considerable project.
# '''The X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required.
# '''The X app'''. Personal. Allows editing and storing personalized copies of contracts generated on WikiDeal. Can implement the peer-to-peer signing workflow. Not MediaWiki. Independent, no MediaWiki account is required. Can connect to different WikiDeal instances.


== MediaWiki ==
== MediaWiki ==
Line 46: Line 47:
:::* Available Clauses (dynamic)
:::* Available Clauses (dynamic)


; Workflows
=== Main Workflows ===
:* '''Management'''
;Management
::* Discussion
:* Discussion
::* Consensus
:* Consensus
::* Legal verification
:* Legal verification
::* Approval
:* Approval
:* Spam combating


:* '''Wiki Editing''
;Wiki Editing
::* Creation and improvement of Clauses
:* Creation and improvement of Clauses
::* Creation and improvement of Contract Models
:* Creation and improvement of Contract Models


:* '''Browsing Clauses'''
;Browsing Clauses
::* Filtering
:* Filtering
::* Personalized tagging
:* Personalized tagging
::* Voting
:* Voting


:* '''Contract Prototype Creation'''
;Contract Prototype Creation
::* Selecting a Contract Model
:* Selecting a Contract Model
::* Adjusting options and variables
:* Adjusting options and variables
::* Adjusting outline
:* Adjusting outline
::* Selecting Clauses
:* Selecting Clauses


:* '''Contract Creation '''
;Contract Creation
::* Wiki markup => Rendered HTML => ?Editable format (programmatically)
:* Wiki markup => Rendered HTML => ?Editable format (programmatically)


== X App ==
== X App ==


??
Can't say, I am too MediaWiki for this. I can help connecting the app to the MediaWiki API.