Sky Bear Technical Standards - Home
Search
×
FR

Placeholder headline

This is just a placeholder headline

TEMA 2026 Edition – Online Subscription Only

$

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 15SIH, 2nd Edition: Installation and Handling of Spoolable Reinforced Plastic Line Pipe

$

158

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 754, 4th Edition: Process Safety Performance Indicators for the Refining and Petrochemical Industries

$

393

BUY NOW

Placeholder headline

This is just a placeholder headline

ASME B31.1-2020: Power Piping

$

668

BUY NOW

Placeholder headline

This is just a placeholder headline

ASME B31.1-2022: Power Piping

$

668

BUY NOW

ISO 28500:2017

ISO 28500:2017 Information and documentation – WARC file format

CDN $261.00

SKU: 4579e7ec0a27 Categories: ,

Description

ISO 28500:2017 specifies the WARC file format:

– to store both the payload content and control information from mainstream Internet application layer protocols, such as the HTTP, DNS, and FTP;

– to store arbitrary metadata linked to other stored data (e.g. subject classifier, discovered language, encoding);

– to support data compression and maintain data record integrity;

– to store all control information from the harvesting protocol (e.g. request headers), not just response information;

– to store the results of data transformations linked to other stored data;

– to store a duplicate detection event linked to other stored data (to reduce storage in the presence of identical or substantially similar resources);

– to be extended without disruption to existing functionality;

– to support handling of overly long records by truncation or segmentation, where desired.

Edition

2

Published Date

2017-08-14

Status

PUBLISHED

Pages

26

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

ISO 28500:2017 specifies the WARC file format:

- to store both the payload content and control information from mainstream Internet application layer protocols, such as the HTTP, DNS, and FTP;

- to store arbitrary metadata linked to other stored data (e.g. subject classifier, discovered language, encoding);

- to support data compression and maintain data record integrity;

- to store all control information from the harvesting protocol (e.g. request headers), not just response information;

- to store the results of data transformations linked to other stored data;

- to store a duplicate detection event linked to other stored data (to reduce storage in the presence of identical or substantially similar resources);

- to be extended without disruption to existing functionality;

- to support handling of overly long records by truncation or segmentation, where desired.

Previous Editions

Can’t find what you are looking for?

Please contact us at: