Informējam, ka Sistēma pielāgota darbam ar interneta pārlūkprogrammu Internet Explorer (8. un jaunākām versijām) un Mozilla Firefox (3.6 un jaunākām versijām).
Izmantojot citu interneta pārlūkprogrammu, brīdinām, ka Sistēmas funkcionalitāte var tikt traucēta.
<p>ISO 28500:2009 specifies the WARC file format:</p>
<ul>
<li>to store both the payload content and control information from mainstream Internet application layer protocols, such as the Hypertext Transfer Protocol (HTTP), Domain Name System (DNS), and File Transfer Protocol (FTP);</li>
<li>to store arbitrary metadata linked to other stored data (e.g. subject classifier, discovered language, encoding);</li>
<li>to support data compression and maintain data record integrity; </li>
<li>to store all control information from the harvesting protocol (e.g. request headers), not just response information;</li>
<li>to store the results of data transformations linked to other stored data; </li>
<li>to store a duplicate detection event linked to other stored data (to reduce storage in the presence of identical or substantially similar resources);</li>
<li>to be extended without disruption to existing functionality;</li>
<li>to support handling of overly long records by truncation or segmentation, where desired.</li>
</ul>
Reģistrācijas numurs (WIID)
44717
Darbības sfēra
<p>ISO 28500:2009 specifies the WARC file format:</p>
<ul>
<li>to store both the payload content and control information from mainstream Internet application layer protocols, such as the Hypertext Transfer Protocol (HTTP), Domain Name System (DNS), and File Transfer Protocol (FTP);</li>
<li>to store arbitrary metadata linked to other stored data (e.g. subject classifier, discovered language, encoding);</li>
<li>to support data compression and maintain data record integrity; </li>
<li>to store all control information from the harvesting protocol (e.g. request headers), not just response information;</li>
<li>to store the results of data transformations linked to other stored data; </li>
<li>to store a duplicate detection event linked to other stored data (to reduce storage in the presence of identical or substantially similar resources);</li>
<li>to be extended without disruption to existing functionality;</li>
<li>to support handling of overly long records by truncation or segmentation, where desired.</li>
</ul>
