Commits

Anonymous committed c58edc8

initial readme

  • Participants

Comments (0)

Files changed (1)

+iodeflib
+========
+
+a python library to create, parse and edit cyber incident reports using the
+IODEF XML format (RFC 5070).
+
+Project website: http://www.decalage.info/python/iodeflib
+
+Usage
+-----
+
+How to parse IODEF data
+~~~~~~~~~~~~~~~~~~~~~~~
+
+How to create IODEF data
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+How to edit IODEF data
+~~~~~~~~~~~~~~~~~~~~~~
+
+
+How to contribute
+-----------------
+
+Either send an e-mail to the author, or use the fork / pull request features of
+Bitbucket to propose improvements to the code.
+
+How to report bugs
+------------------
+
+You may create an issue ticket on https://bitbucket.org/decalage/iodeflib/issues
+
+Please provide enough information to reproduce the bug: which version you use,
+which operating system and version of Python, etc. Please also provide sample
+code and data files to reproduce the bug.
+
+License
+-------
+
+Copyright (c) 2011-2012, Philippe Lagadec (http://www.decalage.info)
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.