| From | Sent On | Attachments |
|---|---|---|
| Peter Michalek | Dec 20, 2004 7:28 am | |
| Peter Michalek | Dec 20, 2004 9:58 am | |
| Peter Michalek | Jan 4, 2005 2:58 pm | |
| Ivan Ristic | Jan 5, 2005 5:12 am | |
| Peter Michalek | Jan 18, 2005 11:18 pm | |
| Peter Michalek | Feb 1, 2005 7:11 pm | |
| Peter Michalek | Feb 14, 2005 4:48 pm |
| Subject: | WAS Protect (or is it EVDL Protect now?) | |
|---|---|---|
| From: | Ivan Ristic (iva...@webkreator.com) | |
| Date: | Jan 5, 2005 5:12:01 am | |
| List: | org.oasis-open.lists.was | |
I have just released the fifth version of the Protect specification. It did not change much, I changed the syntax slightly and it now makes more sense. More importantly, the new release of the specification is accompanies by the full implementation in Java (the implementation is of near-beta quality). Find the documentation and the software here:
http://www.modsecurity.org/projects/wasprotect/
With regards to the specification, I am almost entirely satisfied with it. It is capable of doing all the things I want it to, and in a simple and understandable manner. Or so I think. Other opinions are welcome.
Consequently, there are very few outstanding issues:
1. Meta-data. I feel the schema needs a few fields for meta data and versioning. For example, version number, release data, etc.
2. The schema probably needs more work. I am no Schema expert and I doubt I'll have time to learn more about it. Help is more than welcome.
3. A proper specification - I will write it once the format is accepted and frozen.
-- Ivan Ristic (http://www.modsecurity.org)





