You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement a user interface for managing the (optional) theory assigned to a project:
uploading the theory (as a Clojure source file)
deleting the theory
replacing the theory by another theory.
Security problem: the Clojure source file needs to be somehow sandboxed, to be sure that it only uses functions provided by Carneades for defining theories.
Note: The Carneades Editor was configurable to use two theories, one defining argumentation schemes and the other defining rules for some application domain. In the web application, a single theory can be (optionally) assigned each project. No distinction is made between argumentation schemes and domain rules by the system, but since theories can now be organized into a hierarchy of sections (with subsections, subsubsections, etc) users can distinguish different kinds of schemes/rules by putting them in different sections.
The text was updated successfully, but these errors were encountered:
Implement a user interface for managing the (optional) theory assigned to a project:
Security problem: the Clojure source file needs to be somehow sandboxed, to be sure that it only uses functions provided by Carneades for defining theories.
Note: The Carneades Editor was configurable to use two theories, one defining argumentation schemes and the other defining rules for some application domain. In the web application, a single theory can be (optionally) assigned each project. No distinction is made between argumentation schemes and domain rules by the system, but since theories can now be organized into a hierarchy of sections (with subsections, subsubsections, etc) users can distinguish different kinds of schemes/rules by putting them in different sections.
The text was updated successfully, but these errors were encountered: