Specification mime types

[pwalsh]

Data Package

Commonly implemented as datapackage.json

• descriptor datapackage
• default serialisation: .json
• mime type: application/datapackage+json

JSON Table Schema

Commonly implemented as tableschema.json

• descriptor tableschema
• default serialisation: .json
• mime type: application/tableschema+json

Suggestion: Rename to Table Schema.

Resource

Commonly implemented as dataresource.json

• descriptor dataresource
• default serialisation: .json
• mime type: application/dataresource+json

[pwalsh]

Considering these together highlights some important points. So I'm merging in #245 #289 to this issue, and also working on a dataresource.json mime type.

[pwalsh]

From #245

@rufuspollock suggested

The MediaType [RFC4288] for Data Package JSON SHOULD be application/vnd.datapackage

I'm suggesting

The MediaType [RFC4288] for Data Package as JSON SHOULD be application/datapackage+json

There is no need to vendor, and we should make a distinction between the thing (datapackage), and the serialisation of it (json)

[pwalsh]

From #289

I'm suggesting

The MediaType [RFC4288] for Table Schema as JSON SHOULD be application/tableschema+json

[rufuspollock]

@pwalsh I'm +1 on all of these.

Is next step is to start the submission process to register these?

[pwalsh]

@rufuspollock yes, I started researching it now. I need to understand a few things the form requires before I can submit.

[pwalsh]

Registration with IANA happens here and is according to this RFC

[pwalsh]

note: all media types will be submitted to the vendor tree - submitting to the standards tree requires a formal publication by a recognised standards body (so, after our RFC to IETF, we could apply for the standards tree).

So:

• application/vnd.tableschema+json
• application/vnd.datapackage+json
• application/vnd.dataresource+json

[pwalsh]

The form(s) as submitted:

• Type name: application
• Subtype name: vendor tree
• Required parameters: not applicable.
• Optional parameters: not applicable.
• Encoding considerations: 8bit text
• Security considerations: not applicable.
• Interoperability considerations: Interoperability is enabled via JSON support in the platform.
• Published specification: http://specs.frictionlessdata.io/data-packages/ (and the others for each submission)
• Applications that use this media type: Applications which use this media type handle raw, often text-based data sources, and require additional metadata on those data sources. The payload accompanying this media type is a descriptor for that metadata and data.
• Fragment identifier considerations: not applicable.
• Restrictions on Usage
• Provisional Registrations: not applicable.
• Additional information: not applicable.
• Deprecated alias names for this type: not applicable.
• Magic number(s): not applicable.
• File extension(s): json
• Macintosh file type code(s): not applicable.
• Intended usage: "Common"; To transport data and metadata.
• Person & email address to contact for further information: Paul Walsh paul.walsh@okfn.org

[pwalsh]

Submitted to IANA. Now need to do PR on the specs.

[pwalsh]

• Media type add to Data Package and JSON Table Schema in [WIP] Stablize specifications to version 1 #330
• Media type added to Data Resource in [WIP] Data Resource spec; new DRY way to write a spec #335

Closing this issue.