Issue description
The HTTP interface needs to be documented. Since this documentation will mainly address developers, it would be ok to have the behavior noted *formally*. This formal description of what the interface does can be used as a test suite as well.
So here is the plan:
* Set up a Topincs Store to hold the information
* Think of an ontology for HTTP interface description
* Use that ontology to describe the Topincs Interface
* Write a minimal program *P* , that can be integrated in Ant to generate the runnable tests
* The runnable tests can use Rhino to create an request, HTTPUnit to issue it and Rhino to apply post-conditions to the response.
Since *P* does computation, it will assume that certain statements hold for the data it is fed. This brings in the problem of validation.
Created: 2007-10-14 10:20:11, Robert Cerny Modified: 2009-08-21 08:59:06, Robert Cerny
Link,
No reifier
Rejection comment
No need for that anymore.
Created: 2011-11-24 18:05:44, Robert Cerny Modified: 2011-11-24 18:05:44, Robert Cerny
Link,
No reifier
|
Reporting date2007-10-14 Created: 2007-10-14 10:30:33, Robert Cerny Modified: 2007-10-14 10:30:33, Robert Cerny
Link,
No reifier
Reported by
Robert Cerny
Created: 2007-10-14 10:30:33, Robert Cerny Modified: 2007-10-14 10:30:33, Robert Cerny
Link,
No reifier
Rejection date2011-11-24 Created: 2011-11-24 18:05:44, Robert Cerny Modified: 2011-11-24 18:05:44, Robert Cerny
Link,
No reifier
Rejected by
Robert Cerny
Created: 2011-11-24 18:05:44, Robert Cerny Modified: 2011-11-24 18:05:44, Robert Cerny
Link,
No reifier
|