Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Section 8 in conflict with section 6 for warc-fields #50

Open
wumpus opened this issue Feb 2, 2019 · 1 comment
Open

Section 8 in conflict with section 6 for warc-fields #50

wumpus opened this issue Feb 2, 2019 · 1 comment

Comments

@wumpus
Copy link

wumpus commented Feb 2, 2019

In addition to these MIME types not being registered (#33), there is an inconsistency about whether the WARC-Type of warcinfo and metadata SHALL BE, MAY, or is recommended to be application/warc-fields (quoting from 1.1 standard)

 section 6.2 'warcinfo'
   The format of this descriptive record block may vary, though the use of the "application/warc-fields" content-type is recommended.
 section 6.6 'metadata'
   The "application/warc-fields" format may be used
 section 8
   The MIME type of warcinfo records, WARC metadata records, and potentially other records types in the future, shall be application/warc-fields.
@JustAnotherArchivist
Copy link

JustAnotherArchivist commented Aug 16, 2019

There exist at least two WARC-writing tools which use a different content type for warcinfo records: crocoite and qwarc both write JSON data with Content-Type: application/json; charset=utf-8.

The interpretation of warcinfo record contents is likely to be tool-dependent anyway since the fields are not really standardised (section 6.2 only gives some recommendations). Therefore, it doesn't make much sense to me to restrict the content type to the fairly inflexible WARC header field format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants