id
stringlengths 4
5
| content
stringlengths 35
470
| layer
stringclasses 3
values | summary
float64 |
|---|---|---|---|
SRS59 | SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
| Specification | null |
SRS60 | SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper | Specification | null |
SRS61 | SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI | Specification | null |
SRS62 | SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
| Specification | null |
SRS63 | SRS 63 - Libwarc and the bindings to its functionality shall enable the use of libwarc's iterators described in SRS 16-20 to be used within various dynamic languages and in Java v1.4 and earlier, using metaphors and paradigms familiar to those languages.
| Specification | null |
SRS64 | SRS 64 - Libwarc and the bindings to its functionality shall enable the use of libwarc's iterators described in SRS 16-20 to be used within Java v1.5 and and later, using Java's new container iterators, such as "for" and "foreach". | Specification | null |
SRS65 | SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
| Specification | null |
SRS66 | SRS 66 - It shall be possible for libwarc to be able to read, write and update WARC files at high speed, i.e. the design should focus on minimum memory footprint and performance.
| Specification | null |
SRS67 | SRS 67 - Libwarc shall be implemented to WARC v0.17.
| Specification | null |
SRS68 | SRS 68 - Major revisions to the WARC ISO standard may lead to revisions of libwarc, but these revisions should be isolated and not affect any tools developed incorporating libwarc
| Specification | null |
SRS69 | SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
| Specification | null |
SRS70 | SRS 70 - Libwarc shall be shipped with a manual and build scripts
| Specification | null |
SRS71 | SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
| Specification | null |
SRS72 | SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
| Specification | null |
SRS73 | SRS 73 - Libwarc shall be shipped with a number of ready-to-use command lines, for example, warcdump (to dump the contents of a WARC file), w-filter, etc. | Specification | null |
SRS74 | SRS 74 - Utility and application level functionality of WARC Tools shall be made available to end users as command line tools, extensions to existing tools, and simple web applications for accessing WARC content | Specification | null |
SRS75 | SRS 75 - Communication and support shall be provided to the open source community. This support must be provided for at least term of the project.
| Specification | null |
SRS76 | SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community | Specification | null |
SRS77 | SRS 77 - The code and documentation of libwarc shall be licensed to the community using an IIPC approved license, such as Apache 2.0 or BSD licence
| Specification | null |
SRS78 | SRS 78 - Libwarc and associated tools shall be shipped with installers to "mod_warc" for Apache (v2.X) and Lighttpd (v1.4.X) servers | Specification | null |
SRS79 | SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
| Specification | null |
SRS80 | SRS 80 - To ensure code portability on older computer architectures, Libwarc shall be compatible with any compiler conforming to the ANSI-C standard C89 revision.
| Specification | null |
SRS81 | SRS 81 - Command line tools incorporating libwarc shall be atomic - i.e. each tool performing a single function, performing it perfectly, and in the spirit of Unix command lines tools. These may be combined using pipes and redirection and scripting, to create more high level commands.
| Specification | null |
SRS82 | SRS 82 - Libwarc source code shall be released in the following archives: "libwarc-version.tar.gz", "libwarc-version.tar.bz2", "libwarc-version.zip" together with their corresponding digests. Developers may then adapt the build configuration files for best performance on their target machines. | Specification | null |
SRS83 | SRS 83 - Libwarc binary modules, ready to use binary commands and libraries (both static and shared), compiled with generic optimisation flags, shall be released also
| Specification | null |
SRS84 | SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
| Specification | null |
SRS85 | SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
| Specification | null |
SRS86 | SRS 86 - Libwarc shall not depend on a specific build tool in order to be built from source. However, makefiles for each target shall be included to simplify deployment.
| Specification | null |
SRS87 | SRS 87 - The default compiler used for all Unix systems to build libwarc will be gcc v.3.4.4 (or above). For Windows, the default compiler will be Microsoft Visual C++ 6.X (or above).
| Specification | null |
SRS88 | SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
| Specification | null |
SRS89 | SRS 89 - Assembly code and specific system features shall not be used in libwarc to ensure resulting code is widely portable across multiple target architectures
| Specification | null |
NFR01 | NFR 1 - The core functionality of WARC Tools, specifically the WARC writer/reader, shall be implemented as a comprehensive, standalone, general purpose software library - libwarc. | Non-Functional Requirement | null |
NFR02 | NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project. | Non-Functional Requirement | null |
NFR03 | NFR 3 - WARC Tools shall be highly portable, running on a range of Linux/Unix platforms and XP as a minimum, together with man pages, build and installation guides, developer guides, etc. | Non-Functional Requirement | null |
NFR04 | NFR 4 - Utility and application level functionality of WARC Tools shall be made available to end users as command line tools, extensions to existing tools, and simple web applications for accessing WARC content.
| Non-Functional Requirement | null |
NFR05 | NFR 5 - Communication and support shall be provided to the open source community. This support must be provided for at least term of the project. | Non-Functional Requirement | null |
NFR06 | NFR 6 - The library and each tool or extension shall be documented for developers and end users, using man pages and other common document forms. | Non-Functional Requirement | null |
NFR07 | NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms. | Non-Functional Requirement | null |
NFR08 | NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community. | Non-Functional Requirement | null |
NFR09 | NFR 9 - The code and documentation shall be licensed using an open source license. | Non-Functional Requirement | null |
NFR10 | NFR 10 - Installation scripts and/or instructions shall be made for the library and tools for each target platform, including Linux, Unix and Windows, as well as apache and lighttp installation scripts | Non-Functional Requirement | null |
NFR11 | NFR 11 - The WARC Tools shall be implemented as a C library | Non-Functional Requirement | null |
NFR12 | NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers. | Non-Functional Requirement | null |
NFR13 | NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2. | Non-Functional Requirement | null |
NFR14 | NFR 14 - Web server plug-ins shall conform to the Apache 'mod' API and shall operate correctly with both Apache and Lighttp servers and shall be compatible with appropriate web sever programming standards, such as WSGI in Python and the Servlet API in Java.
| Non-Functional Requirement | null |
NFR15 | NFR 15 - The deliverables shall be made available in source code, named as "libwarc-version.tar.gz", where version is the version of the library. A number of binary distributions may be made, including RPM, DEB and EXE. | Non-Functional Requirement | null |
NFR16 | NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows. | Non-Functional Requirement | null |
NFR17 | NFR 17 - The final WARC API shall be coded in C with minimum dependencies or external libraries (e.g. GZIP). It must not include any assembly code. | Non-Functional Requirement | null |
NFR18 | NFR 18 - The C library will be developed in such a way as to allow it to be used with the Simplified Wrapper and Interface Generator, or SWIG, (www.swig.org) in order to wrap the C code and allow it to be called natively in a wide variety of languages. | Non-Functional Requirement | null |
NFR19 | NFR 19 - An interface implementation may be made for Python to allow the library to be used natively by Python programmers requiring no knowledge of the internal implementation of libwarc or C. | Non-Functional Requirement | null |
NFR20 | NFR 20 - An interface implementation shall be made for Java to allow the library to be used natively by Java programmers requiring no knowledge of the internal implementation of libwarc or C. | Non-Functional Requirement | null |
NFR21 | NFR 21 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the specific implementation languages (C, Java, Python). | Non-Functional Requirement | null |