s_text,s_id,t_text,t_id,label
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 40 - A Java interface shall be implemented,FR40,1
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,1
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,1
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 39 - A Python interface shall be implemented
",FR39,1
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,1
"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.
",SRS63,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,1
"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"".",SRS64,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,1
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,1
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,1
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,1
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,1
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,1
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,1
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,1
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,1
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,1
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,1
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,1
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,1
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 23 - WARC Browser shall support a proxy-style interface,FR23,1
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,1
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,1
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,1
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,1
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,1
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,1
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,1
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,1
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,1
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,1
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,1
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,1
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,1
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 22 - WARC Browser shall support a rewriting interface,FR22,1
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,1
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,1
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,1
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,1
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,1
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,1
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,1
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,1
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,1
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,1
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,1
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,1
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,1
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,1
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,1
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 15 - Libwarc shall use disk-based working memory
",FR15,1
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,1
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,1
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,1
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,1
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,1
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,1
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,1
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,1
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,1
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,1
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,1
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,1
"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
",SRS68,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,1
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,1
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,1
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,1
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,1
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,1
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,1
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,1
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,1
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,1
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,1
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,1
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 39 - A Python interface shall be implemented
",FR39,1
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,1
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,1
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,1
"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.",NFR06,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,1
"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.",NFR06,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,1
"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.",NFR06,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,1
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,1
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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.
",SRS63,1
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,1
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,1
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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.
",SRS80,1
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,1
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.,NFR05,"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.
",SRS75,1
"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.
",NFR04,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,1
"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.
",NFR04,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,1
"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.
",NFR04,"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",SRS74,1
"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.
",NFR04,"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.",SRS73,1
"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.
",NFR04,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,1
"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.
",NFR04,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,1
"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.
",NFR04,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,1
"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.
",NFR04,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,1
"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.
",NFR04,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,1
"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",NFR10,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,1
"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",NFR10,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,1
"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.
",NFR14,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,1
"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.
",NFR14,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,1
"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.",NFR01,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,1
"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.",NFR15,"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
",SRS83,1
"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.",NFR15,"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.",SRS82,1
"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.",NFR15,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,1
"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.",NFR03,"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
",SRS89,1
"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.",NFR03,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,1
"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.",NFR03,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,1
"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.",NFR03,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,1
"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.",NFR03,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,1
"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.",NFR03,"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.
",SRS80,1
"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.",NFR03,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,1
"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.",NFR03,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,1
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.,NFR17,"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
",SRS89,1
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.,NFR17,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,1
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.,NFR17,"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.
",SRS80,1
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,1
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,1
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,1
"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.",NFR18,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,1
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.,NFR19,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,1
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.,NFR19,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,1
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.,NFR19,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,1
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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
",SRS77,1
"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).",NFR21,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,1
"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).",NFR21,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,1
"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).",NFR21,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,1
"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).",NFR21,"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.
",SRS63,1
"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).",NFR21,"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"".",SRS64,1
"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).",NFR21,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,1
"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).",NFR21,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,1
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.,NFR20,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,1
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.,NFR20,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,1
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.,NFR20,"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.
",SRS63,1
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.,NFR20,"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"".",SRS64,1
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,1
"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",NFR10,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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
",SRS77,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"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.
",SRS66,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.
",NFR14,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"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).",NFR21,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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
",SRS83,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
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.,NFR05,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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.
",SRS86,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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).
",SRS87,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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).",NFR21,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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
",SRS83,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.",NFR01,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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.",SRS73,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",NFR15,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"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.
",NFR04,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR18,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",SRS82,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.
",SRS81,FR 40 - A Java interface shall be implemented,FR40,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"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",NFR10,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",NFR18,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"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.
",SRS75,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.
",NFR14,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 19 - Libwarc shall manage all write and read access,FR19,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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.
",SRS86,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.
",NFR04,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"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.
",SRS63,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR06,"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.
",SRS81,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
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.,NFR19,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"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.
",NFR14,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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).",NFR21,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 40 - A Java interface shall be implemented,FR40,0
"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.",NFR18,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.",NFR06,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
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.,NFR17,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR03,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.
",NFR04,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"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",NFR10,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS86,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",NFR18,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
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.,NFR05,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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
",SRS77,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 40 - A Java interface shall be implemented,FR40,0
"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.",NFR01,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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
",SRS83,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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",NFR10,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.
",SRS63,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.",NFR01,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
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.,NFR20,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"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
",SRS83,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
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.,NFR05,"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
",SRS89,0
"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.",NFR03,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR15,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"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.
",SRS80,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",SRS66,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.",NFR06,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"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.
",NFR14,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"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.
",SRS63,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",NFR06,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"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.",NFR06,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"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.",NFR18,"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.
",SRS66,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR18,"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).
",SRS87,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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
",SRS89,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.
",SRS81,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",SRS80,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.
",SRS63,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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
",SRS89,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.
",SRS75,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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).
",SRS87,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
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.,NFR20,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
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.,NFR20,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",NFR01,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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
",SRS83,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR15,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"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.
",SRS81,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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
",SRS89,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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.
",SRS63,0
"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.",NFR01,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"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
",SRS83,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 19 - Libwarc shall manage all write and read access,FR19,0
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.,NFR17,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR18,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"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",NFR10,"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.
",SRS66,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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"".",SRS64,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",NFR14,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"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",NFR10,"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.
",SRS80,0
"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.",NFR03,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"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.",SRS82,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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).",NFR21,"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",SRS74,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.
",NFR14,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.",SRS82,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.
",SRS63,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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
",SRS89,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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
",SRS68,0
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.,NFR19,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
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.,NFR17,"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.
",SRS81,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 40 - A Java interface shall be implemented,FR40,0
"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.
",SRS86,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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.
",SRS86,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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",NFR10,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
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.,NFR05,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"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.
",SRS75,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
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.,NFR19,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
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.,NFR20,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",SRS66,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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",NFR10,"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.
",SRS75,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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.
",NFR14,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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).
",SRS87,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
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.,NFR05,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"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.",NFR03,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"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.",NFR15,"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
",SRS89,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
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.,NFR17,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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).",NFR21,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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
",SRS77,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.
",SRS63,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",NFR04,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 39 - A Python interface shall be implemented
",FR39,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"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",NFR10,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR03,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.",NFR03,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"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.
",NFR04,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"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.
",SRS66,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.",NFR03,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.
",SRS81,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 40 - A Java interface shall be implemented,FR40,0
"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.
",NFR04,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"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.
",SRS86,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"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
",SRS83,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"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"".",SRS64,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
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.,NFR20,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",NFR14,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.",NFR01,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"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.",NFR15,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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",SRS74,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"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.",SRS73,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
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.,NFR19,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",NFR14,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
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.,NFR20,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
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.,NFR05,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS75,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
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.,NFR20,"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.
",SRS75,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 40 - A Java interface shall be implemented,FR40,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"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.",NFR03,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
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.,NFR20,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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"".",SRS64,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
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.,NFR19,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
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.,NFR05,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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.
",SRS75,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 40 - A Java interface shall be implemented,FR40,0
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.,NFR19,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"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.",NFR15,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.
",NFR04,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
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.,NFR19,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
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.,NFR05,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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
",SRS68,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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
",SRS68,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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",NFR10,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"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.",NFR15,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
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.,NFR20,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.
",SRS75,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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.",SRS73,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",NFR14,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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
",SRS83,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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",SRS74,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
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.,NFR20,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"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
",SRS68,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
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.,NFR19,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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).",NFR21,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",NFR18,"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.
",SRS81,0
"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
",SRS68,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
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.,NFR17,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.",NFR06,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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",SRS74,FR 40 - A Java interface shall be implemented,FR40,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"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.",NFR18,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.
",SRS75,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.",NFR15,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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.
",SRS86,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"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
",SRS89,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR03,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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).",NFR21,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.
",SRS63,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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",SRS74,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",NFR04,"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.
",SRS86,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"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
",SRS89,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"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
",SRS83,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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.
",SRS75,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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",NFR10,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"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.
",NFR14,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"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.",NFR15,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
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.,NFR17,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"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"".",SRS64,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
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.,NFR20,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"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
",SRS83,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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"".",SRS64,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.",NFR06,"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"".",SRS64,0
"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.
",NFR04,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"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.",NFR15,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
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.,NFR05,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"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",NFR10,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"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
",SRS83,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 39 - A Python interface shall be implemented
",FR39,0
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.,NFR19,"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.",SRS82,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",NFR14,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
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.,NFR20,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 40 - A Java interface shall be implemented,FR40,0
"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",NFR10,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"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",NFR10,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.
",NFR14,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"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.
",SRS66,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
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.,NFR17,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR06,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.
",SRS80,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
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.,NFR05,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",SRS63,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.",NFR15,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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.
",SRS63,0
"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.",SRS82,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
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.,NFR20,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 40 - A Java interface shall be implemented,FR40,0
"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
",SRS83,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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
",SRS68,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 40 - A Java interface shall be implemented,FR40,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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).
",SRS87,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"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).",NFR21,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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).",NFR21,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
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.,NFR05,"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.
",SRS63,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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).
",SRS87,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.",NFR06,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 40 - A Java interface shall be implemented,FR40,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.",NFR03,"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"".",SRS64,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
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.,NFR20,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
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.,NFR05,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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
",SRS77,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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.",SRS82,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.",NFR01,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"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.
",SRS81,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.",NFR15,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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.",NFR15,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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"".",SRS64,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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"".",SRS64,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"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.
",SRS81,"FR 39 - A Python interface shall be implemented
",FR39,0
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.,NFR17,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",NFR01,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"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.",NFR15,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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",NFR10,"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.
",SRS81,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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).",NFR21,"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.
",SRS66,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.",NFR06,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"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.
",SRS75,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.",NFR06,"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
",SRS83,0
"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.",SRS73,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR06,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"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",SRS74,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 40 - A Java interface shall be implemented,FR40,0
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.,NFR19,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.
",SRS80,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.",SRS73,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR01,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
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.,NFR19,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
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.,NFR19,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.",NFR15,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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
",SRS77,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",NFR06,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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",SRS74,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
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.,NFR19,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"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.",NFR01,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"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.",NFR15,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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
",SRS68,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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"".",SRS64,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.",SRS73,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.
",SRS66,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
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.,NFR19,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
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.,NFR17,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.",NFR03,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.",NFR18,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 39 - A Python interface shall be implemented
",FR39,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"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",NFR10,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.
",SRS66,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.",NFR03,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR06,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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
",SRS68,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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",NFR10,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"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.",NFR06,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"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.
",SRS75,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR06,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",NFR01,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
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.,NFR20,"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.",SRS73,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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.
",SRS66,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
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.,NFR19,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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.
",SRS86,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.",NFR18,"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",SRS74,0
"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.",NFR15,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
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.,NFR05,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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
",SRS89,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR06,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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
",SRS89,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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.",NFR18,"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
",SRS89,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.
",SRS63,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",NFR01,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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.",NFR15,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR03,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR06,"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).
",SRS87,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
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.,NFR19,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
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.,NFR20,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR18,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"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.",NFR06,"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.
",SRS63,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 39 - A Python interface shall be implemented
",FR39,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 40 - A Java interface shall be implemented,FR40,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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.",SRS73,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",NFR14,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
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.,NFR20,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"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).
",SRS87,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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",NFR10,"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.
",SRS86,0
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.,NFR20,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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
",SRS77,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
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.,NFR20,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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.
",SRS80,0
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.,NFR17,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.
",SRS86,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
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.,NFR05,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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.
",SRS86,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR05,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"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
",SRS83,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
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.,NFR20,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"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.",SRS82,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"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
",SRS77,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.",NFR06,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"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.",NFR15,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR18,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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
",SRS68,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR06,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"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
",SRS68,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",NFR04,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
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.,NFR05,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"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.",NFR03,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"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.
",SRS81,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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",SRS74,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.
",SRS80,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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"".",SRS64,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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
",SRS89,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.",SRS82,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.",NFR18,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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.",NFR18,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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.
",SRS81,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
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.,NFR20,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"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.",NFR15,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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.",NFR15,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.",SRS82,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR18,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
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.,NFR19,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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).",NFR21,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"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",NFR10,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"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.
",SRS81,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.
",NFR14,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
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.,NFR20,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.",NFR15,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
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.,NFR20,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"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.",NFR03,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"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.",NFR15,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"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.
",SRS63,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.",NFR18,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"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.",NFR06,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",NFR01,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
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.,NFR20,"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
",SRS83,0
"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.",NFR15,"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.
",SRS66,0
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.,NFR17,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",NFR04,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"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).",NFR21,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"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.",NFR01,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"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.",NFR03,"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
",SRS77,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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).
",SRS87,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.
",SRS86,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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"".",SRS64,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.
",NFR14,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
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.,NFR05,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"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.
",SRS75,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",NFR01,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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",NFR10,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"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.
",NFR14,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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",NFR10,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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.
",SRS66,0
"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.
",SRS81,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR03,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"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.
",SRS86,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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",NFR10,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"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.",NFR18,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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
",SRS83,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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",SRS74,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR06,"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.
",SRS86,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.
",NFR04,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
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.,NFR20,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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.
",SRS86,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR01,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
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.,NFR17,"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
",SRS83,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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.
",SRS75,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.",NFR06,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
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.,NFR05,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
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.,NFR17,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.",NFR06,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"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.
",NFR14,"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.",SRS73,0
"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"".",SRS64,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.
",SRS86,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",SRS73,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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.
",SRS80,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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",SRS74,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.",NFR18,"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
",SRS83,0
"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.",NFR18,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"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
",SRS77,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.",NFR03,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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
",SRS83,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",NFR06,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"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.",SRS73,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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).
",SRS87,0
"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.
",SRS66,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.
",SRS75,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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
",SRS89,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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).",NFR21,"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.
",SRS75,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.
",SRS75,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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).",NFR21,"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
",SRS83,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.
",NFR04,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"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",NFR10,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",SRS75,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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.
",SRS81,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"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.
",NFR14,"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.",SRS82,0
"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
",SRS89,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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
",SRS89,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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",NFR10,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.",SRS73,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
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.,NFR19,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"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.
",NFR04,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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.
",NFR14,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"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).",NFR21,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.
",SRS63,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.",NFR01,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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.",NFR18,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"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.
",NFR14,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",NFR04,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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).
",SRS87,0
"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
",SRS83,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.",NFR15,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",NFR04,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR17,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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.
",NFR14,"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.
",SRS80,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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).
",SRS87,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.
",SRS66,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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).",NFR21,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
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.,NFR20,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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.",NFR18,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"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.
",SRS66,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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
",SRS68,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.",NFR06,"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.
",SRS66,0
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.,NFR20,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"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).",NFR21,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.",NFR18,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"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).",NFR21,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"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.
",SRS80,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.",SRS82,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.",NFR01,"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.",SRS73,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS86,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 39 - A Python interface shall be implemented
",FR39,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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.",SRS73,0
"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
",SRS83,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
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.,NFR05,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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.
",SRS80,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",NFR14,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.
",SRS75,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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",NFR10,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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",NFR10,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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).
",SRS87,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"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.
",NFR14,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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",NFR10,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"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.",NFR15,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
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.,NFR19,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",NFR04,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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
",SRS77,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
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.,NFR05,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
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.,NFR17,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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",SRS74,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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).",NFR21,"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
",SRS77,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR18,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"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.",NFR15,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 39 - A Python interface shall be implemented
",FR39,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"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",NFR10,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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).",NFR21,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
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.,NFR17,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR01,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 40 - A Java interface shall be implemented,FR40,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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",NFR10,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
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.,NFR05,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 40 - A Java interface shall be implemented,FR40,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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",SRS74,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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.",NFR18,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
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.,NFR17,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"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).",NFR21,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"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.",NFR18,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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
",SRS77,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.
",NFR14,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"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.",NFR06,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.
",NFR14,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
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.,NFR19,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
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.,NFR19,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"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.",NFR15,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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
",SRS77,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.",NFR18,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.
",SRS66,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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"".",SRS64,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"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.",NFR01,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"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.
",SRS66,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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).
",SRS87,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
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.,NFR19,"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).
",SRS87,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",NFR15,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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
",SRS89,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",SRS81,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR15,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"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.
",SRS80,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"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.",NFR15,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
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.,NFR05,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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).
",SRS87,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.",NFR18,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"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.
",SRS66,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",SRS73,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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).
",SRS87,0
"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",NFR10,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR20,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",SRS73,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",SRS82,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
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.,NFR05,"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).
",SRS87,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"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.",NFR01,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"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.",NFR06,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"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
",SRS89,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.",SRS73,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"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.",NFR15,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"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.
",SRS75,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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
",SRS89,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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
",SRS68,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 40 - A Java interface shall be implemented,FR40,0
"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.",NFR06,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"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.",NFR18,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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",SRS74,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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).",NFR21,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"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.
",NFR04,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.",NFR06,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",SRS81,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS75,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.
",NFR14,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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
",SRS68,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",NFR14,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
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.,NFR19,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",SRS66,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.
",SRS86,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
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.,NFR19,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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.
",SRS80,0
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.,NFR19,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 40 - A Java interface shall be implemented,FR40,0
"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.",NFR15,"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.
",SRS63,0
"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.
",NFR04,"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.",SRS82,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR03,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.",NFR15,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"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.",NFR18,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"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.
",SRS75,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.",SRS73,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR20,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
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.,NFR05,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.
",SRS86,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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
",SRS68,0
"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.",NFR01,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
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.,NFR20,"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",SRS74,0
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.,NFR05,"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",SRS74,0
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.,NFR19,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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",SRS74,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.
",SRS75,FR 40 - A Java interface shall be implemented,FR40,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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.
",SRS66,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.
",NFR14,"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.
",SRS86,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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.
",SRS63,0
"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.
",SRS81,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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.",NFR06,"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
",SRS68,0
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.,NFR20,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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"".",SRS64,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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).
",SRS87,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"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
",SRS77,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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
",SRS83,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
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.,NFR19,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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
",SRS89,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
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.,NFR20,"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
",SRS89,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.
",SRS81,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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).",NFR21,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
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.,NFR20,"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.",SRS82,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.",NFR01,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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",SRS74,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.
",NFR14,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"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.
",SRS80,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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).",NFR21,"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
",SRS68,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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).",NFR21,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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).",NFR21,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 40 - A Java interface shall be implemented,FR40,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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).",NFR21,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"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.",NFR18,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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).
",SRS87,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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",SRS74,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR20,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR06,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.",NFR06,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",NFR04,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"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.
",NFR04,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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.
",SRS66,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.
",SRS63,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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",NFR10,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.",NFR18,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.
",SRS81,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
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.,NFR17,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.",NFR03,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"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.",NFR01,"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
",SRS83,0
"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.",NFR15,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 19 - Libwarc shall manage all write and read access,FR19,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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.
",SRS63,0
"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.
",SRS63,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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.
",SRS75,0
"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.",SRS82,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.
",SRS86,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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
",SRS68,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.",NFR06,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",NFR04,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"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.",NFR06,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.
",NFR14,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"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.",NFR18,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"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.",NFR03,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.",NFR01,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
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.,NFR17,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"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.",NFR01,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"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.
",SRS75,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR01,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.
",SRS66,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"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.
",SRS63,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.
",NFR14,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",SRS82,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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
",SRS83,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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.",NFR15,"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.
",SRS75,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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.
",SRS66,0
"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.",NFR01,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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
",SRS77,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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"".",SRS64,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
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.,NFR19,"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
",SRS68,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",NFR14,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"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).",NFR21,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
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.,NFR17,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR06,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"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).",NFR21,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"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.
",NFR14,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 40 - A Java interface shall be implemented,FR40,0
"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.
",SRS81,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
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.,NFR17,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"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.",NFR06,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
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.,NFR17,"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
",SRS68,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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).",NFR21,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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.
",SRS66,0
"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.",NFR18,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
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.,NFR19,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.",NFR01,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
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.,NFR20,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR01,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"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.",NFR01,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",SRS73,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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
",SRS68,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"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.",NFR18,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"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.",SRS82,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",SRS81,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.",NFR03,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"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.
",NFR14,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",SRS80,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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).
",SRS87,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.
",SRS86,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.
",SRS86,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",NFR14,"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"".",SRS64,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.
",SRS66,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR05,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"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.",NFR18,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR06,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
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.,NFR17,"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.",SRS82,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.
",SRS75,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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.
",SRS63,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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
",SRS83,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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",NFR10,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
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.,NFR05,"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.
",SRS86,0
"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",NFR10,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
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.,NFR19,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"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.
",SRS81,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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",NFR10,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"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.
",NFR04,"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
",SRS68,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",SRS63,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.",NFR15,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.",SRS73,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.
",SRS80,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
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.,NFR20,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
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.,NFR20,"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.
",SRS80,0
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.,NFR17,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"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.",NFR01,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR19,"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.
",SRS66,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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
",SRS83,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
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.,NFR17,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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
",SRS68,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR06,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"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.
",NFR04,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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.",NFR06,"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.
",SRS80,0
"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.
",NFR14,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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
",SRS77,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"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.
",SRS63,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR20,"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).
",SRS87,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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",NFR10,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"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.",NFR18,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.",NFR18,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.",NFR18,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"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.
",NFR04,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"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
",SRS77,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"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.",NFR06,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"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.
",NFR04,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.
",NFR04,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.
",SRS63,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"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.
",NFR04,"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"".",SRS64,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
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.,NFR05,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"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.",NFR01,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"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.",NFR03,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
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.,NFR20,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",NFR03,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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",NFR10,"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
",SRS83,0
"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.
",NFR04,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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
",SRS77,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 39 - A Python interface shall be implemented
",FR39,0
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.,NFR19,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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
",SRS89,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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).",NFR21,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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
",SRS83,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.",SRS73,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
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.,NFR05,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"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
",SRS68,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",SRS75,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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",SRS74,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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).
",SRS87,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.
",SRS63,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",SRS73,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",SRS82,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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
",SRS68,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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.
",SRS81,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",NFR03,"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.",SRS73,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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.
",SRS81,0
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.,NFR19,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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).",NFR21,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
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.,NFR19,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"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
",SRS89,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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"".",SRS64,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
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.,NFR05,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR01,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"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",NFR10,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
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.,NFR17,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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",NFR10,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.
",NFR04,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR01,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
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.,NFR19,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"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.
",SRS81,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
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.,NFR17,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.",NFR01,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.",NFR15,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.
",NFR04,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.",NFR01,"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"".",SRS64,0
"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
",SRS68,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.
",SRS86,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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
",SRS89,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.
",NFR04,"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.
",SRS80,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
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.,NFR20,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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
",SRS89,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.",NFR06,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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
",SRS77,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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",NFR10,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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",NFR10,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"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.
",SRS75,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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.",SRS82,0
"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.",NFR01,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR15,"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"".",SRS64,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.",SRS82,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
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.,NFR05,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",SRS73,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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).",NFR21,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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",NFR10,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
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.,NFR05,"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.",SRS73,0
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.,NFR17,"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
",SRS77,0
"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.",NFR15,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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.",NFR01,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
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.,NFR19,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"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.
",SRS86,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 39 - A Python interface shall be implemented
",FR39,0
"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",NFR10,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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
",SRS77,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 40 - A Java interface shall be implemented,FR40,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
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.,NFR17,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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"".",SRS64,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.
",NFR14,"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
",SRS89,0
"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
",SRS89,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",NFR14,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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).",NFR21,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",NFR14,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"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.",NFR18,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"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.",SRS82,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
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.,NFR17,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"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.
",SRS81,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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"".",SRS64,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",NFR18,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR01,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
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.,NFR17,"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).
",SRS87,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR01,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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.
",SRS75,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR15,"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
",SRS77,0
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.,NFR19,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR03,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",NFR18,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"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"".",SRS64,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.
",SRS81,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
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.,NFR20,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",NFR04,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"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.",NFR18,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
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.,NFR17,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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
",SRS89,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",SRS66,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.
",SRS86,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.
",SRS66,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.
",SRS75,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"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.",NFR03,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"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).",NFR21,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"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.
",SRS81,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",NFR06,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
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.,NFR19,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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.
",SRS75,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.
",NFR04,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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.
",SRS81,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"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",SRS74,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
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.,NFR20,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.
",NFR14,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.
",SRS63,FR 40 - A Java interface shall be implemented,FR40,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.",NFR18,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR20,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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.",NFR03,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",NFR04,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
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.,NFR20,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"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).",NFR21,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"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.
",NFR04,"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
",SRS83,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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.
",SRS63,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"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
",SRS77,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.",SRS82,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.",NFR18,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"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.
",SRS86,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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
",SRS83,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
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.,NFR19,"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.
",SRS75,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"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.",NFR03,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR01,"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.",SRS82,0
"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.
",SRS63,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.",SRS73,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
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.,NFR20,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"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.",NFR03,"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.
",SRS66,0
"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.",NFR03,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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).",NFR21,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"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.",NFR03,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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",NFR10,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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
",SRS83,0
"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.",NFR18,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",NFR14,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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
",SRS77,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS86,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 40 - A Java interface shall be implemented,FR40,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
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.,NFR19,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",SRS66,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.
",NFR04,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"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.",NFR15,"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
",SRS68,0
"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).",NFR21,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"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
",SRS68,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
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.,NFR19,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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).",NFR21,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.
",SRS80,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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.",NFR01,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
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.,NFR19,"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
",SRS83,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.
",SRS80,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR18,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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",NFR10,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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
",SRS83,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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
",SRS77,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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",NFR10,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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
",SRS83,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.
",SRS66,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR15,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
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.,NFR17,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
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.,NFR05,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.
",SRS80,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",SRS80,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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.
",SRS66,0
"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.
",SRS66,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
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.,NFR20,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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
",SRS77,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
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.,NFR05,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
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.,NFR19,"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.",SRS73,0
"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.",NFR06,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.",NFR15,"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).
",SRS87,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 40 - A Java interface shall be implemented,FR40,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR15,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"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
",SRS68,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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).",NFR21,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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.
",SRS81,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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.
",SRS75,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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
",SRS77,0
"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.",NFR06,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.
",SRS75,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR18,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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.",NFR01,"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.
",SRS86,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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
",SRS89,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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
",SRS68,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"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.",NFR06,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"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.
",NFR14,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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",SRS74,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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.
",SRS80,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.
",NFR14,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.
",NFR04,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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.
",SRS80,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",NFR18,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"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"".",SRS64,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.
",SRS81,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",NFR15,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR03,"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.
",SRS63,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"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.",NFR03,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"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.",NFR18,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.
",SRS80,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.
",SRS86,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.
",SRS86,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 40 - A Java interface shall be implemented,FR40,0
"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"".",SRS64,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.",NFR03,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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",SRS74,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",NFR04,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"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
",SRS89,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
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.,NFR05,"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
",SRS68,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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).
",SRS87,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",SRS73,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.
",NFR14,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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
",SRS83,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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",NFR10,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
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.,NFR17,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"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
",SRS68,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.
",SRS80,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
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.,NFR19,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 19 - Libwarc shall manage all write and read access,FR19,0
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.,NFR05,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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",NFR10,"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
",SRS89,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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",NFR10,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"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.
",SRS66,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.",NFR06,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"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",SRS74,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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
",SRS89,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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",SRS74,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.
",SRS81,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.",NFR06,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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.
",SRS81,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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).
",SRS87,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 40 - A Java interface shall be implemented,FR40,0
"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.
",NFR04,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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"".",SRS64,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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
",SRS68,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",NFR04,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
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.,NFR20,"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
",SRS68,0
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.,NFR19,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
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.,NFR17,"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",SRS74,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",SRS82,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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
",SRS77,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.
",NFR04,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"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).",NFR21,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
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.,NFR17,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"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
",SRS68,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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",SRS74,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.
",SRS80,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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).",NFR21,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"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
",SRS68,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR18,"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.
",SRS86,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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).",NFR21,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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).",NFR21,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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.
",SRS81,0
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.,NFR05,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
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.,NFR05,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
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.,NFR05,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
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.,NFR05,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"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.",NFR06,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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
",SRS77,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 39 - A Python interface shall be implemented
",FR39,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.
",NFR14,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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",NFR10,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR17,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",SRS80,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.",NFR06,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"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",NFR10,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"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.",NFR06,"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
",SRS89,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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",NFR10,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.
",SRS80,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"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.
",NFR04,"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.
",SRS63,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR06,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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
",SRS77,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR18,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
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.,NFR19,"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.
",SRS80,0
"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.",NFR18,"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.
",SRS63,0
"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.",NFR06,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
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.,NFR17,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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
",SRS77,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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",SRS74,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",SRS73,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
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.,NFR20,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 19 - Libwarc shall manage all write and read access,FR19,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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.",SRS82,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.",NFR03,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
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.,NFR19,"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.
",SRS86,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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"".",SRS64,FR 19 - Libwarc shall manage all write and read access,FR19,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"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.
",NFR04,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.",NFR18,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"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.
",SRS86,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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
",SRS83,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
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.,NFR17,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"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",NFR10,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR03,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"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.
",SRS75,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
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.,NFR17,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",SRS82,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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).",NFR21,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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
",SRS77,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
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.,NFR05,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.
",SRS63,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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).",NFR21,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
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.,NFR20,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"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
",SRS68,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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",SRS74,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.
",SRS75,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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",NFR10,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
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.,NFR05,"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
",SRS83,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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).",NFR21,"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.",SRS82,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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"".",SRS64,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"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"".",SRS64,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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
",SRS77,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",NFR14,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR03,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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
",SRS89,0
"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
",SRS77,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 40 - A Java interface shall be implemented,FR40,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 40 - A Java interface shall be implemented,FR40,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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
",SRS89,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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).
",SRS87,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"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).",NFR21,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
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.,NFR19,"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
",SRS89,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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"".",SRS64,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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
",SRS89,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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.
",NFR14,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"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",NFR10,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"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.
",NFR14,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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.
",SRS63,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"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.",NFR15,"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.
",SRS80,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"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.",SRS82,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.",NFR18,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"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.
",SRS80,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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.
",SRS81,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.
",SRS80,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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",NFR10,"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",SRS74,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"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.",SRS73,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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).",NFR21,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"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).
",SRS87,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"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.
",SRS75,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 40 - A Java interface shall be implemented,FR40,0
"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
",SRS83,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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).
",SRS87,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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",SRS74,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"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.
",NFR04,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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.
",SRS66,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"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.",NFR15,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",NFR15,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
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.,NFR19,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"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.
",SRS75,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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",NFR10,"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.",SRS82,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
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.,NFR17,"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.
",SRS75,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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).
",SRS87,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
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.,NFR17,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
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.,NFR05,"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.
",SRS81,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
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.,NFR05,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.",NFR18,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"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.",NFR01,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",NFR15,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR06,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR01,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"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.",SRS73,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.",NFR03,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
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.,NFR17,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.",NFR03,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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"".",SRS64,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR06,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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.",SRS82,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.
",SRS86,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
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.,NFR05,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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
",SRS83,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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
",SRS89,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
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.,NFR19,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
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.,NFR20,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
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.,NFR19,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"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"".",SRS64,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",SRS82,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR05,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
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.,NFR17,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.
",NFR14,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.",NFR03,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR15,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
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.,NFR20,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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
",SRS68,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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).
",SRS87,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.",NFR18,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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"".",SRS64,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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
",SRS77,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR18,"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
",SRS77,0
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.,NFR05,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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
",SRS77,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.",NFR06,"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.",SRS82,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",SRS66,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
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.,NFR20,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.
",NFR04,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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",SRS74,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.",NFR15,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"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).",NFR21,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",NFR01,"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
",SRS68,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",SRS82,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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
",SRS77,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.
",NFR14,"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.
",SRS63,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR03,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"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.
",SRS63,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",NFR06,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
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.,NFR19,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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",SRS74,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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.",NFR03,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"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.",NFR06,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"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.",NFR01,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"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).",NFR21,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.
",SRS86,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
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.,NFR20,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"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",NFR10,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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).",NFR21,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
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.,NFR19,"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.
",SRS81,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
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.,NFR19,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"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.
",NFR04,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"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.",NFR03,"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.
",SRS75,0
"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.",NFR01,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"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.",NFR15,"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.
",SRS86,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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.
",SRS86,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"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.",NFR03,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"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.
",NFR14,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"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.
",SRS80,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.",NFR18,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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"".",SRS64,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
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.,NFR17,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"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.
",NFR14,"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.
",SRS81,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",NFR03,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.",NFR06,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
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.,NFR05,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 39 - A Python interface shall be implemented
",FR39,0
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.,NFR19,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"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.",NFR18,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",NFR18,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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"".",SRS64,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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).",NFR21,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR18,"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.
",SRS75,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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"".",SRS64,0
"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.
",SRS86,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
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.,NFR19,"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.
",SRS63,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",SRS82,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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
",SRS77,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
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.,NFR19,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"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.",NFR03,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
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.,NFR05,"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"".",SRS64,0
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.,NFR05,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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
",SRS77,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"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.",NFR06,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"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).",NFR21,"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).
",SRS87,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
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.,NFR17,"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.
",SRS66,0
"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.",NFR15,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"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.
",NFR04,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"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"".",SRS64,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"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.",NFR15,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"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
",SRS68,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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",SRS74,0
"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
",SRS68,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.
",NFR14,"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
",SRS68,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 19 - Libwarc shall manage all write and read access,FR19,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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.",NFR06,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"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",SRS74,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR15,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
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.,NFR19,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"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.",NFR01,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"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.",NFR03,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"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.
",SRS66,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR20,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 40 - A Java interface shall be implemented,FR40,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.",SRS73,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS75,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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
",SRS89,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.",NFR15,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"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).
",SRS87,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.
",NFR04,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.
",SRS81,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.
",SRS80,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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
",SRS83,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR19,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"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.
",SRS86,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",SRS82,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
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.,NFR19,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"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.",SRS73,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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
",SRS89,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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).
",SRS87,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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
",SRS77,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",NFR18,"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"".",SRS64,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
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.,NFR19,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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
",SRS83,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",NFR03,"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",SRS74,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR18,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.",SRS82,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS80,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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.
",SRS86,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.
",SRS75,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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
",SRS68,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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
",SRS68,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR03,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"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.",NFR03,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"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.",NFR03,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"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.
",SRS63,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.",SRS73,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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",SRS74,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"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).
",SRS87,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.
",SRS63,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",SRS63,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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).",NFR21,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
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.,NFR20,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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).
",SRS87,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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).",NFR21,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"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"".",SRS64,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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
",SRS68,0
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.,NFR20,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"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.
",NFR04,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
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.,NFR05,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"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.
",SRS86,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",SRS73,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
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.,NFR19,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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.
",SRS81,0
"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.
",SRS75,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",SRS82,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.",SRS82,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",SRS63,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.
",NFR04,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"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.
",SRS63,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 40 - A Java interface shall be implemented,FR40,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"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).",NFR21,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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",NFR10,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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",SRS74,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.
",NFR04,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
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.,NFR19,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.
",SRS63,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
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.,NFR05,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"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.",NFR15,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR06,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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.",SRS82,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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",SRS74,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",NFR14,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"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
",SRS68,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.
",SRS75,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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).",NFR21,"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.
",SRS81,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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
",SRS68,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",NFR14,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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",SRS74,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
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.,NFR20,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
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.,NFR17,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.",NFR15,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
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.,NFR20,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR19,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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).",NFR21,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR03,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"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.
",SRS80,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
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.,NFR05,"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
",SRS77,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.",NFR15,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 40 - A Java interface shall be implemented,FR40,0
"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.",NFR03,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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",SRS74,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.",NFR18,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR15,"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.
",SRS81,0
"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.",SRS73,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"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
",SRS89,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 40 - A Java interface shall be implemented,FR40,0
"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.
",SRS80,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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.",SRS73,0
"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.",NFR15,"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.",SRS73,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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"".",SRS64,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",NFR04,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"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.",NFR18,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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
",SRS89,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.",NFR01,"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).
",SRS87,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
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.,NFR05,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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).
",SRS87,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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).",NFR21,"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.
",SRS86,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR06,"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.
",SRS75,0
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.,NFR19,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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).",NFR21,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
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.,NFR17,"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.
",SRS63,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.",NFR03,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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",NFR10,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"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.
",SRS86,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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
",SRS77,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 39 - A Python interface shall be implemented
",FR39,0
"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",NFR10,"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.",SRS73,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",SRS81,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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
",SRS89,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",NFR04,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"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.
",SRS75,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
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.,NFR17,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
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.,NFR17,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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",NFR10,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"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
",SRS83,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 40 - A Java interface shall be implemented,FR40,0
"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
",SRS68,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.
",NFR04,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.
",SRS80,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",NFR14,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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.
",NFR04,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
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.,NFR17,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"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.
",SRS66,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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",NFR10,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.
",SRS66,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.",NFR06,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",NFR01,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"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.",NFR01,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
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.,NFR05,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",NFR04,"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.
",SRS66,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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.",NFR03,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
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.,NFR19,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
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.,NFR20,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.",NFR01,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
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.,NFR20,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"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.",SRS73,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",SRS82,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.
",NFR14,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
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.,NFR20,"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
",SRS77,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"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.",NFR15,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
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.,NFR20,"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.
",SRS81,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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).
",SRS87,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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
",SRS89,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
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.,NFR17,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.",NFR01,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.
",NFR04,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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
",SRS89,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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.
",SRS80,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.
",SRS63,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
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.,NFR17,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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
",SRS68,FR 19 - Libwarc shall manage all write and read access,FR19,0
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.,NFR05,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"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.",NFR06,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"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.",NFR03,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"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.
",SRS63,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",NFR15,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR03,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"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).
",SRS87,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 40 - A Java interface shall be implemented,FR40,0
"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.",SRS82,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.
",SRS63,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 40 - A Java interface shall be implemented,FR40,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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.",SRS73,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR01,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"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.",NFR18,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
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.,NFR20,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR19,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"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",NFR10,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 19 - Libwarc shall manage all write and read access,FR19,0
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.,NFR17,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",NFR01,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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.
",SRS81,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
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.,NFR05,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",NFR18,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"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
",SRS83,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
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.,NFR05,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"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.",NFR15,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.
",NFR04,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"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).",NFR21,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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.",SRS73,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 19 - Libwarc shall manage all write and read access,FR19,0
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.,NFR05,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"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).
",SRS87,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",NFR01,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"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.",NFR18,"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.",SRS73,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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"".",SRS64,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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
",SRS83,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR18,"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.
",SRS80,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",NFR01,"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.
",SRS63,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.",NFR15,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",SRS82,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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
",SRS89,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR03,"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.
",SRS86,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.",NFR06,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"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.",NFR01,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"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.
",SRS75,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
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.,NFR19,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 39 - A Python interface shall be implemented
",FR39,0
"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).
",SRS87,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR01,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
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.,NFR19,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"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.
",SRS80,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
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.,NFR19,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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).
",SRS87,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
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.,NFR19,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
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.,NFR05,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"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.
",SRS66,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.
",NFR04,"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.
",SRS81,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR15,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"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.
",NFR14,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"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"".",SRS64,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.
",SRS86,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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",SRS74,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 40 - A Java interface shall be implemented,FR40,0
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.,NFR17,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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
",SRS89,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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",SRS74,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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).",NFR21,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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
",SRS83,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.",NFR15,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"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).
",SRS87,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
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.,NFR05,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.
",SRS75,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
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.,NFR17,"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"".",SRS64,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.
",SRS86,FR 19 - Libwarc shall manage all write and read access,FR19,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR03,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.",NFR06,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"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.",NFR15,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"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).
",SRS87,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR03,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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
",SRS83,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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).",NFR21,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"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).
",SRS87,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.",NFR18,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
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.,NFR20,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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",NFR10,"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
",SRS77,0
"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.
",SRS81,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.
",NFR04,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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.
",SRS63,0
"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.",NFR01,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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"".",SRS64,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
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.,NFR17,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"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",SRS74,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.
",NFR04,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.",NFR03,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"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.
",SRS63,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
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.,NFR19,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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"".",SRS64,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"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.
",SRS86,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
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.,NFR19,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.",NFR06,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
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.,NFR17,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"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.
",NFR14,"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).
",SRS87,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",NFR06,"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",SRS74,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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",NFR10,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
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.,NFR19,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
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.,NFR05,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
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.,NFR17,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"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.
",NFR14,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"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.
",NFR14,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 39 - A Python interface shall be implemented
",FR39,0
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.,NFR17,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
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.,NFR19,"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",SRS74,0
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.,NFR19,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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.",SRS82,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
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.,NFR20,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
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.,NFR05,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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"".",SRS64,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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
",SRS89,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 39 - A Python interface shall be implemented
",FR39,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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.
",SRS86,0
"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.
",NFR14,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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.",SRS73,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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
",SRS83,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",NFR15,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
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.,NFR20,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"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
",SRS77,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"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"".",SRS64,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
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.,NFR19,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"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.",SRS73,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"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.",NFR03,"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
",SRS83,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
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.,NFR17,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"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.",NFR01,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"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",NFR10,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",SRS73,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"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).",NFR21,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"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.
",NFR14,"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.
",SRS66,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"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.
",NFR14,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.
",SRS63,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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",NFR10,"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.
",SRS63,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 39 - A Python interface shall be implemented
",FR39,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
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.,NFR17,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"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.",SRS82,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",NFR03,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"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.",SRS82,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.
",SRS80,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.
",NFR14,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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
",SRS83,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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",NFR10,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.",NFR06,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.",NFR06,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",NFR01,"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.
",SRS81,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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).",NFR21,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"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.",NFR03,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"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.
",SRS86,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
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.,NFR17,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"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).
",SRS87,0
"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
",SRS89,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
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.,NFR17,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
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.,NFR17,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR06,"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.",SRS73,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 39 - A Python interface shall be implemented
",FR39,0
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.,NFR17,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
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.,NFR17,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 19 - Libwarc shall manage all write and read access,FR19,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",NFR01,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"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.
",SRS80,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
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.,NFR20,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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",SRS74,0
"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.
",NFR14,"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
",SRS77,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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).
",SRS87,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",SRS86,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
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.,NFR17,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
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.,NFR17,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 40 - A Java interface shall be implemented,FR40,0
"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",SRS74,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 40 - A Java interface shall be implemented,FR40,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.
",NFR14,"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",SRS74,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR05,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
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.,NFR17,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR01,"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.
",SRS66,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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"".",SRS64,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
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.,NFR20,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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
",SRS68,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.
",SRS81,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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",NFR10,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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
",SRS83,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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
",SRS83,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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).
",SRS87,FR 40 - A Java interface shall be implemented,FR40,0
"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.
",SRS63,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",NFR15,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"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
",SRS83,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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).",NFR21,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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.
",SRS75,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",NFR04,"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
",SRS77,0
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.,NFR17,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
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.,NFR20,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"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.",NFR06,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"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.",NFR01,"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.
",SRS80,0
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.,NFR05,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 40 - A Java interface shall be implemented,FR40,0
"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.
",SRS80,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.
",SRS86,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
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.,NFR05,"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.",SRS82,0
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.,NFR17,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"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.",SRS73,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
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.,NFR05,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.
",SRS81,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.
",NFR14,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 39 - A Python interface shall be implemented
",FR39,0
"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",NFR10,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"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.",SRS73,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",NFR14,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"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.
",SRS75,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.",NFR01,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"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).",NFR21,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"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).",NFR21,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
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.,NFR05,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 40 - A Java interface shall be implemented,FR40,0
"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.",NFR01,"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
",SRS89,0
"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.
",SRS75,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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).
",SRS87,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",SRS86,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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
",SRS77,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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",SRS74,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.",NFR03,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",NFR01,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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",NFR10,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
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.,NFR05,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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
",SRS89,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.",NFR06,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
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.,NFR19,"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"".",SRS64,0
"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.",NFR15,"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",SRS74,0
"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).
",SRS87,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
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.,NFR17,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"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.
",SRS75,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.
",SRS63,FR 19 - Libwarc shall manage all write and read access,FR19,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"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.
",SRS81,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
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.,NFR20,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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",NFR10,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.",SRS73,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"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.",NFR18,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
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.,NFR20,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"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.",NFR03,"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
",SRS68,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.",NFR15,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"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.",NFR01,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR18,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",SRS66,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",NFR06,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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"".",SRS64,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.",NFR15,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.
",NFR14,"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,0
"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.",NFR06,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"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",SRS74,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.
",SRS81,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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
",SRS68,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",NFR01,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"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.",NFR03,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR20,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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",NFR10,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"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.",NFR18,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS75,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",SRS63,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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
",SRS68,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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.",NFR03,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
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.,NFR05,"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.
",SRS66,0
"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.",NFR18,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 39 - A Python interface shall be implemented
",FR39,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"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).
",SRS87,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.
",SRS66,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",NFR14,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.
",NFR14,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
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.,NFR05,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.
",SRS86,"FR 39 - A Python interface shall be implemented
",FR39,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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",NFR10,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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",NFR10,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"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.
",SRS63,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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.
",SRS80,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"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.
",SRS66,"FR 39 - A Python interface shall be implemented
",FR39,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",NFR01,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.",SRS73,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.
",NFR04,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
"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).
",SRS87,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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",SRS74,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",SRS80,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
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.,NFR20,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.
",NFR14,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"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"".",SRS64,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.",NFR01,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
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.,NFR20,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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
",SRS89,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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).
",SRS87,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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.",NFR01,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
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.,NFR05,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
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.,NFR05,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",NFR01,"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.
",SRS75,0
"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.",SRS82,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.
",SRS81,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.
",SRS80,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"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.",NFR01,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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.
",NFR04,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.",SRS82,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
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.,NFR20,SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
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.,NFR05,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"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.",NFR06,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"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"".",SRS64,FR 40 - A Java interface shall be implemented,FR40,0
"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).",NFR21,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
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.,NFR20,"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.
",SRS66,0
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.,NFR19,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"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
",SRS89,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.",NFR15,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"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.
",NFR04,"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.
",SRS75,0
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.,NFR17,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"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
",SRS77,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
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.,NFR20,"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.
",SRS86,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",NFR01,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"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.",SRS82,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
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.,NFR20,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.
",NFR14,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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
",SRS77,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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).",NFR21,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",SRS81,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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",SRS74,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR03,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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
",SRS68,0
"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.",SRS82,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",SRS82,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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).",NFR21,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR03,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.
",SRS66,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.",SRS73,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
"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
",SRS77,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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).",NFR21,"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.
",SRS80,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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
",SRS68,0
"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.
",SRS66,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
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.,NFR20,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"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
",SRS83,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.
",SRS86,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.",NFR03,"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.
",SRS81,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",SRS81,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.
",SRS80,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
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.,NFR17,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"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.",NFR01,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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",SRS74,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,0
"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
",SRS68,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,"FR 39 - A Python interface shall be implemented
",FR39,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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",NFR10,"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"".",SRS64,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
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.,NFR17,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
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.,NFR05,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"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
",SRS77,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"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.",NFR06,"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
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.,NFR19,"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
",SRS77,0
"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.
",SRS66,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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
",SRS89,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"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.",NFR03,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",NFR18,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",SRS63,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.",NFR15,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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",NFR10,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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
",SRS89,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.
",NFR04,"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"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",SRS74,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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).",NFR21,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"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.",NFR01,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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.
",NFR14,"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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.",SRS82,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
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.,NFR17,"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.",NFR01,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"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.
",SRS81,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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
",SRS89,"FR 39 - A Python interface shall be implemented
",FR39,0
"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",SRS74,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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.",SRS82,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.
",NFR14,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.",NFR06,"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
",SRS77,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
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.,NFR20,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.",NFR15,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"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
",SRS83,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
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.,NFR17,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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
",SRS83,0
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.,NFR20,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",SRS66,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",SRS66,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"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.
",NFR04,"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).
",SRS87,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"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.",NFR18,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
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.,NFR17,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR15,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
SRS 30 - It shall not be possible to use more than one compression schema (including noncompression) within a single WARC file. (i.e. it is not possible to mix compression schemes within a single WARC file).,SRS30,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.",NFR03,"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.",SRS82,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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.",SRS82,0
"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.
",SRS86,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.
",NFR04,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",NFR06,SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,0
"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).",NFR21,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.",SRS82,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.",NFR15,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
"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.
",SRS81,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.",NFR15,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"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
",SRS89,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",SRS75,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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.",SRS73,0
"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.",SRS82,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.
",SRS66,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR18,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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
",SRS68,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.",NFR15,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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.
",SRS86,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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).
",SRS87,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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.
",SRS80,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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
",SRS89,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.
",SRS75,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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).
",SRS87,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.
",SRS80,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.
",NFR04,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"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.
",SRS81,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",NFR14,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
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.,NFR05,"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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.
",SRS66,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",NFR03,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.",SRS73,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
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.,NFR19,"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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.
",SRS81,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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.",NFR18,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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"".",SRS64,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.",NFR01,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"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
",SRS68,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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).",NFR21,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"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.
",NFR14,"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.
",SRS75,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
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.,NFR05,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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"".",SRS64,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 58 - Void, duplicate of SRS 79
",SRS58,0
"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.",NFR15,"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"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.
",SRS80,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
NFR 11 - The WARC Tools shall be implemented as a C library,NFR11,"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.
",SRS75,0
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.,NFR05,"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.
",SRS80,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 7 - The universal header ""warc.h"" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records, based on the definition in the ""ISO TC 46/SC 4 N 595"" standards document. The interfaces shall be made available to create WARC records of the following types:
- ""warinfo""
- ""response""
- ""request""
- ""metadata""
- ""revisit""
- ""conversion""
- ""continuation""
- ""resource""
",SRS07,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.
",NFR14,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"SRS 58 - Void, duplicate of SRS 79
",SRS58,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
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.,NFR19,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"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
",SRS68,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
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.,NFR17,"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.",SRS73,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.
",SRS66,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",NFR14,"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,0
"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.",NFR01,"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",SRS74,0
"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.
",SRS66,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.",NFR01,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"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.",SRS82,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.
",SRS80,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
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.,NFR05,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
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.,NFR05,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
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.,NFR17,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
"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.
",NFR04,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"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.
",NFR14,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
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.,NFR17,"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.
",SRS86,0
"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).",NFR21,"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.",SRS73,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 55 - The WARC validator tool specified in SRS 31-32 shall be extended to optionally make use of the Jhove command line API to identify and validate WARC files, i.e. given a specific WARC file, this command shall be able to identify the file as a WARC file, validate the level of compliance with a given standard in terms of well-formedness and validity, and finally to characterise the file by extracting and displaying significant properties contained in the file.
",SRS55,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 40 - A Java interface shall be implemented,FR40,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"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
",SRS77,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,0
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.,NFR05,"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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",NFR10,"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).
",SRS87,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.
",SRS81,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
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.,NFR05,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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
",SRS77,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
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.,NFR17,SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
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.,NFR05,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
"SRS 41 - A command line tool ""arc2warc"" incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
",SRS41,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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.
",SRS86,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",NFR01,"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
",SRS77,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,0
"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.",NFR03,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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.
",NFR04,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
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.,NFR17,"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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
",SRS83,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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.",NFR18,"SRS 71 - Libwarc shall be shipped with installation guides for Fedora, Debian, FreeBSD, Mac OS X 10.5 and Windows XP.
",SRS71,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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.
",SRS80,0
"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.",NFR06,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"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.",NFR06,"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 56 - WarcMdoule and WarcHandler plugin modules shall be implemented for Jhove Plugin layer to enable identification and validation of WARC files.
",SRS56,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 17 - Libwarc shall provide a WARC-record MIME-type iterator
",SRS17,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 53 - Helper documentation for libwarc functionality shall be made available within the ""HTTrack"", ""wget"" and ""curl"" commands.",SRS53,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.
",NFR04,"SRS 51 - Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
",SRS51,0
"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.",SRS82,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.
",NFR14,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR18,"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
",SRS68,0
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.,NFR05,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,0
"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.
",SRS63,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 10 - Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.",SRS10,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 59 - Libwarc shall provide interfaces to SWIG wrappers to allow dynamic language bindings (Python, Ruby, Perl, Lua ...)
",SRS59,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"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
",SRS77,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,0
"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.",SRS73,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",NFR14,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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).",NFR21,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
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.,NFR20,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"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.",SRS82,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.
",NFR04,"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,0
"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.
",SRS86,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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.",SRS73,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",SRS73,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"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"".",SRS64,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"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",NFR10,"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,FR 40 - A Java interface shall be implemented,FR40,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"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).
",SRS87,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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.
",NFR04,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"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.",NFR18,SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.
",SRS63,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"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).",NFR21,"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
",SRS89,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,FR 19 - Libwarc shall manage all write and read access,FR19,0
SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.",SRS73,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"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.",NFR18,"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.",SRS82,0
"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.
",SRS66,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 52 - Extensions to ""HTTrack"", ""wget"" and ""curl"" incorporating libwarc shall be provided as patches to recent and specific versions of each tool, to enable users of the tool to access functionality of libwarc
",SRS52,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
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.,NFR19,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"SRS 2 - The ""libwarc"" headers shall be structured in a hierarchical manner. The universal header ""warc.h"" will include all of them.
",SRS02,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
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.,NFR05,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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.
",NFR04,"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
",SRS89,0
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.,NFR17,"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,0
"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
",SRS77,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 12 - Libwarc shall provide an abstract interface for iterators, to enable custom iterators",FR12,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
"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.",NFR18,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,FR 9 - Libwarc shall provide a records iterator to handle WARC-type records,FR09,0
NFR 8 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community.,NFR08,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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",SRS74,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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
",SRS77,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",NFR01,"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,0
"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",NFR10,"SRS 19 - Libwarc's generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
",SRS19,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
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.,NFR20,"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,0
"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",SRS74,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,0
"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",NFR10,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 19 - Libwarc shall manage all write and read access,FR19,0
"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.",NFR03,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"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).",NFR21,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
"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.",NFR01,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 36 - A Jhove plugin module and an output handler shall be made available for WARC files
",FR36,0
"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"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.",NFR15,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
"NFR 7 - Patches implemented for third party projects shall be documented for developers and end users, using man pages and other common document forms.",NFR07,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"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
",SRS68,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"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
",SRS77,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
SRS 14 - Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.,SRS14,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.
",NFR04,"SRS 70 - Libwarc shall be shipped with a manual and build scripts
",SRS70,0
"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"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",NFR10,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,SRS 38 -A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface and thereby ensure all content is delivered from the archive and not from the live web.,SRS38,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 24 - Libwarc shall allocate minimum memory heap to store WARC-record metadata.
",SRS24,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"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.",NFR03,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
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.,NFR05,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.",NFR18,"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 38 - The C library shall be implemented to be compatible with the Simplified Wrapper and Interface Generator (SWIG, http://www.swig.org) - a wrapper for libwarc C code to allow it to be called natively in a wide variety of languages.
",FR38,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,"FR 39 - A Python interface shall be implemented
",FR39,0
"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.
",NFR04,"SRS 28 - The default compression format shall be Gzip
",SRS28,0
"SRS 88 - Only essential external libraries shall be used in libwarc, such as Gzip compression and wide characters encoding libraries.
",SRS88,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
"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.",NFR03,"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).
",SRS87,0
NFR 9 - The code and documentation shall be licensed using an open source license.,NFR09,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
SRS 15 -Libwarc shall include ADT objects to handle read operations on ARC-records,SRS15,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
"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.",NFR18,"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,0
"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.",NFR18,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
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.,NFR20,"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 62 - An independent Java implementation of libwarc may be implemented subject to review of deliverables satisfying SRS 61
",SRS62,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"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.
",NFR04,"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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",NFR10,SRS 76 - Patches implemented for third party projects shall be contributed and distributed to the appropriate community,SRS76,0
SRS 57 - WARC files in various test-states shall be provided that test the Jhove deliverables,SRS57,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 3 - It shall be possible for developers to access, modify and manipulate of all aspects of the WARC file format by including this single header file.",SRS03,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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).",NFR21,"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"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.
",NFR04,"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,0
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.,NFR05,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"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.",NFR15,"SRS 16 - Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARCrecords and create an abstract WARC-document as a simple container
",SRS16,0
"SRS 11 - Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data. The data types shall be abstract (abstract data types - ADT), to ensure independence of concrete implementations.
",SRS11,"FR 39 - A Python interface shall be implemented
",FR39,0
"SRS 37 - WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links being delivered alongside archived content. This is based on the principles implemented in the Wayback Machine.
",SRS37,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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.",NFR03,SRS 20 - Libwarc's iterators may be combined into composite iterators to enable the developer to more than one search field,SRS20,0
"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",NFR10,"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 24 - An Apache and Lighttp plug-in shall provide access to the libwarc API and WARC Browser over http,FR24,0
"SRS 50 - The command line tools and API in SRS 50 will not include any links extraction features.
",SRS50,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
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.,NFR19,"SRS 6 - The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.",SRS06,0
"SRS 28 - The default compression format shall be Gzip
",SRS28,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 45 - A set of command line tools incorporating libwarc shall perform migration of ""HTTrack"" archives to WARC-records.",SRS45,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 3 - Libwarc shall provide a range of functions through a universal interface for creating each type of valid WARC-record, thus ensuring the resulting WARC files conform to the prevailing WARC standard
",FR03,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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
",SRS68,0
"SRS 46 - The HTTrack archive file format and link strategy may vary from version to version of HTTrack, therefore it shall be possible to adapt the migration scripts to deal with these changes.
",SRS46,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"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",NFR10,"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,0
"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.
",SRS66,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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
",SRS83,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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.",NFR06,"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,0
"SRS 1 - There shall be a single entry point to libwarc, called ""warc.h"".
",SRS01,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 35 - For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
",SRS35,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"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.",NFR06,"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,0
"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.
",SRS75,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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).",NFR21,SRS 40 - Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.,SRS40,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"SRS 69 - Libwarc shall be developed on GNU/Linux, Fedora 7
",SRS69,"FR 20 - WARC files shall be validated using a command line tool, ""w-validator"", which will enable validation or rejection of WARC files.",FR20,0
"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.",SRS73,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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
",SRS83,0
"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"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).
",SRS87,FR 6 - Libwarc shall provide a stable Application Programme Interface (API) to handle WARCrecords as abstract objects (ADT),FR06,0
"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,FR 19 - Libwarc shall manage all write and read access,FR19,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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"".",SRS64,0
"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.",NFR01,"SRS 25 - The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
",SRS25,0
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.,NFR05,"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,0
"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"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.
",SRS80,FR 16 - Dynamic memory management shall be hidden inside libwarc,FR16,0
"SRS 18 - Libwarc shall provide a WARC-record-type iterator
",SRS18,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
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.,NFR19,"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,0
"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
"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",SRS74,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 39 - Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache.
",SRS39,0
"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
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.,NFR19,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,0
"SRS 54 - A magic number for WARC shall be created and incorporated in the ""file"" mime-type database, enabling the simple identification of WARC files via the Unix ""file"" command",SRS54,"FR 27 - It shall be possible to collect HTTrack data from the directories output by HTTrack and write the data to WARC files
",FR27,0
"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
",SRS83,"FR 34 - It shall be possible to identify WARC files using the unix ""file"" command",FR34,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 33 - WARC extensions help content will be provided each of the commands ""curl"", ""wget"", and ""httrack""",FR33,0
"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
",SRS89,FR 40 - A Java interface shall be implemented,FR40,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 17 - Libwarc shall use gzip as the default compression format
",FR17,0
NFR 12 - Library functionality shall have APIs and dynamic language bindings to be made available as software libraries for developers.,NFR12,"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.",SRS73,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 14 - Libwarc shall be memory safe and manage dynamic memory internally
",FR14,0
"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,"FR 13 - Libwarc shall enable combinations of iterators to be used, i.e. composite iterators",FR13,0
"SRS 67 - Libwarc shall be implemented to WARC v0.17.
",SRS67,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"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",SRS74,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 31 - A Python script shall be made available to enable rapid development of WARC based solutions,FR31,0
SRS 36 - WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope.,SRS36,FR 1 - Any software tool or application based on libwarc shall require just a single header file.,FR01,0
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.,NFR17,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 43 - ""arc2warc"" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
",SRS43,0
"SRS 72 - Libwarc shall be shipped with a developer guide and useful examples.
",SRS72,"FR 21 - WARC Browser shall provide an API that allows browsing of WARC files and associated CDX files via an HTTP server
",FR21,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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.
",SRS81,0
"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
",SRS83,"FR 10 - Libwarc shall provide a MIMES iterator to handle MIME-types payloads
",FR10,0
NFR 2 - WARC v0.17 shall be the baseline version of the WARC standard used in this project.,NFR02,"SRS 29 - Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.",SRS29,0
"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,"FR 25 - It shall be possible to convert ARC files to WARC files using a command-line tool called ""arc2warc""
",FR25,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR03,"SRS 26 - Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.",SRS26,0
"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
",SRS89,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"SRS 12 - It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
",SRS12,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
"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.
",NFR14,"SRS 23 - Libwarc shall use dynamic heap memory for its internal usage.
",SRS23,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 4 - For each type of WARC-record, a set of functions shall be made available to create/modify the records properties.",FR04,0
"SRS 44 - It shall be possible to specify non-default operations of ""arc2warc"" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.",SRS44,FR 37 - WARC files in various test-states shall be provided that test the Jhove deliverables,FR37,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 22 - Developers using libwarc shall not be required to allocate/release memory directly, instead the developer shall use libwarc's object constructor and destructor functions.
",SRS22,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"NFR 16 - The deliverables shall be ported to the following platforms: Linux, FreeBSD, Mac OS X 10.5 and Windows.",NFR16,"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"".",SRS64,0
"SRS 84 - Libwarc shall be made available as a binary for at least GNU/Linux, FreeBSD, Mac OS X and Windows XP.
",SRS84,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
"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.
",NFR14,"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,0
"SRS 78 - Libwarc and associated tools shall be shipped with installers to ""mod_warc"" for Apache (v2.X) and Lighttpd (v1.4.X) servers",SRS78,FR 26 - ARC to WARC conversions made by arc2warc shall be carried out according to a specification in a configuration file,FR26,0
"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.
",NFR14,"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
",SRS83,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
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.,NFR20,"SRS 13 - It shall be possible to release the WARC-record using a destructor.
",SRS13,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 41 - An independent Java implementation of libwarc may be implemented
",FR41,0
"SRS 42 - The default operation of ""arc2warc"" shall carry out a one-to-one mapping of record fields, by converting each ARC-record to a corresponding ""response"" WARC-record and ""metadata"" WARCrecord, which shall include information about the conversion process.
",SRS42,FR 7 - Libwarc shall provide ARC-record reader functionality Libwarc reader will thereby make read operations as simple as possible.,FR07,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 5 - Libwarc shall provide a range of functions through a universal interface for reading a range of valid WARC-records
",FR05,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 27 - Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
",SRS27,"FR 35 - It shall be possible to identify and validate WARC files using ""Jhove""",FR35,0
NFR 13 - The functionality of the API shall enable the appropriate functionality in the library scriptable1 and programmable2.,NFR13,"SRS 34 - It shall be possible to perform read operations (read from offset, filters, etc.) on WARCrecords from a remote location via http.
",SRS34,0
SRS 61 - A Java interface to libwarc shall be implemented using the SWIG wrapper and/or JNI,SRS61,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"SRS 49 - A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records.",SRS49,"FR 18 - Libwarc shall provide a plug-in interface to enable use of alternative compression libraries, such as ""gzip2"", ""7zip"", etc.
",FR18,0
"SRS 65 - It shall be possible for libwarc to be able to handle WARC file of any size, with minimal memory usage.
",SRS65,"FR 30 - It shall be possible to collect arbitrary web content, such as html files, images etc. (for example from a web server document root directory), and write the data to WARC files
",FR30,0
"SRS 48 - A set of command line tools incorporating libwarc shall perform migration of ""curl"" archives to WARC-records.
",SRS48,FR 11 - Iterators can use exact pattern search or regex expressions,FR11,0
"SRS 21 - Libwarc shall encapsulate and handle all memory management when processing WARCrecords.
",SRS21,"FR 28 - It shall be possible to walk a wget mirror and write the data to WARC files
",FR28,0
"SRS 8 - Each WARC-record shall be accessible via a peer C class of the same name.
",SRS08,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"SRS 47 - A set of command line tools incorporating libwarc shall perform migration of ""wget"" archives to WARC-records.
",SRS47,"FR 32 - WARC extensions shall be released as a patch to each of the commands ""curl"", ""wget"", and ""httrack"" projects",FR32,0
"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",NFR10,"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
",SRS68,0
"SRS 9 - The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
",SRS09,"FR 15 - Libwarc shall use disk-based working memory
",FR15,0
"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.",NFR15,"SRS 33 - Libwarc shall provide a set of classes to enable remote management of WARC-records
",SRS33,0
"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",NFR10,"SRS 79 - Libwarc shall be implemented in C and shall conform to ANSI-C standard C99 revision.
",SRS79,0
"SRS 5 - The universal header ""warc.h"" shall ensure that deprecated function calls and changes to the library are notified at compile time.
",SRS05,FR 8 - Libwarc shall provide a default iterator as a built-in function,FR08,0
"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.
",SRS80,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0
"SRS 32 - The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.",SRS32,FR 22 - WARC Browser shall support a rewriting interface,FR22,0
"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.",NFR06,"SRS 4 - The universal header ""warc.h"" shall ensure compatibility between all versions of libwarc.",SRS04,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,"FR 29 - It shall be possible to walk a curl directory and write the data to WARC files
",FR29,0
"SRS 85 - Libwarc shall compile and run under Solaris, AIX, MingW or other Unix compliant system and may compile and run under Windows XP.
",SRS85,FR 42 - The functionality of the library shall be exposed in such a way as to fit the metaphors and paradigms of the implementation language,FR42,0
SRS 31 - A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.,SRS31,FR 23 - WARC Browser shall support a proxy-style interface,FR23,0
"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.",NFR15,SRS 60 - A Python interface to libwarc shall be implemented using the SWIG wrapper,SRS60,0
"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.
",SRS66,"FR 2 - The libwarc interfaces shall fully encapsulate and internal functionality, isolating by abstraction any tool or application based on libwarc from changes in the internal implementation.
",FR02,0