<p>ISO 28500:2017 specifies the WARC file format:</p>
<p>- to store both the payload content and control information from mainstream Internet application layer protocols, such as the HTTP, DNS, and FTP;</p>
<p>- to store arbitrary metadata linked to other stored data (e.g. subject classifier, discovered language, encoding);</p>
<p>- to support data compression and maintain data record integrity;</p>
<p>- to store all control information from the harvesting protocol (e.g. request headers), not just response information;</p>
<p>- to store the results of data transformations linked to other stored data;</p>
<p>- to store a duplicate detection event linked to other stored data (to reduce storage in the presence of identical or substantially similar resources);</p>
<p>- to be extended without disruption to existing functionality;</p>
<p>- to support handling of overly long records by truncation or segmentation, where desired.</p>
Registration number (WIID)
68004
Scope
<p>ISO 28500:2017 specifies the WARC file format:</p>
<p>- to store both the payload content and control information from mainstream Internet application layer protocols, such as the HTTP, DNS, and FTP;</p>
<p>- to store arbitrary metadata linked to other stored data (e.g. subject classifier, discovered language, encoding);</p>
<p>- to support data compression and maintain data record integrity;</p>
<p>- to store all control information from the harvesting protocol (e.g. request headers), not just response information;</p>
<p>- to store the results of data transformations linked to other stored data;</p>
<p>- to store a duplicate detection event linked to other stored data (to reduce storage in the presence of identical or substantially similar resources);</p>
<p>- to be extended without disruption to existing functionality;</p>
<p>- to support handling of overly long records by truncation or segmentation, where desired.</p>
