-
Notifications
You must be signed in to change notification settings - Fork 590
Clarify that format refers to mediaType #272
Comments
I want to connect a discussion to this issue that's been going on between a number of us offline (@ddnebert, @rsignell-usgs, @amilan17, ...) about it would be good to get a consolidated list of formats (or mediaTypes as @philipashlock suggests) to be used in DCAT and through that hopefully upstream in agency catalogs and metadata practices. |
Here's an example of what it would look like: |
This is addressed in 6c376cf |
Changes that still need to be addressed are changes in structure and should we add usage notes additions here or no?: * Adds optional describedByType field at the dataset and distribution level (#291, #332) * Changes contactPoint field to an object that contains the name (fn) and email address (hasEmail) (#358) * Adds fn field as part of contactPoint replacing earlier use of contactPoint (#358) * Changes publisher field to an object that allows multiple levels of organizations (#296) * Changes accessURL field to represent indirect access and to exist only within distribution (#217, #335) * Changes format field to a human readable description and to exist only within distribution (#272, #293) * Adds optional description field for use within distribution (#248) * Adds optional title field for use within distribution (#248) * Changes accrualPeriodicity field to use ISO 8601 date syntax (#292) * Changes distribution field to become required-if-applicable and to always contain the accessURL or downloadURL fields (#217) * Changes license field to be a URL (#196)
Thank you for driving the conversation around this issue and helping to assemble the v1.1 metadata update. There appears to be strong consensus around this issue, which has been accepted in the v1.1 update and merged into Project Open Data. Project Open Data is a living project though. Please continue any conversations around how the schema can be improved with new issues and pull requests! It's important for government staff as well as the public to continue to collaborate to make the Open Data Policy ever better. Though the v1.1 update is a substantial update, future iterations do not have to be, so whatever your ideas - big or small - please continue to work with this community to improve how government manages and opens its data. |
While many of the fieldnames are derived from DCAT it looks like
format
andmediaType
were mixed up. The way thatformat
is used here is really whatmediaType
is meant for (referring to IANA, aka MIME type). The distinction is described here: http://www.w3.org/TR/vocab-dcat/#Property:distribution_media_typeAs a recommendation for a future iteration of the spec,
format
should be deprecated in favor ofmediaType
when referring to an IANA (aka MIME type) value as we're currently using it. Theformat
field could still be acceptable for a more human readable name for themediaType
as per http://www.w3.org/TR/vocab-dcat/#Property:distribution_formatIn related issues:
mediaType
should also be paired withdownloadURL
(#335) within thedistribution
array (#217)The text was updated successfully, but these errors were encountered: