search

project-open-data / project-open-data.github.io

Open Data Policy — Managing Information as an Asset
https://project-open-data.cio.gov/
Other
1.34k stars 584 forks source link

Consider possibility of including character encoding in schema #464

Open philipashlock opened 9 years ago

philipashlock commented 9 years ago

DCAT doesn't provide a way to specify character encoding as noted in the INSPIRE profile of DCAT. Some, including examples from Chicago, have attempted to include the character encoding as part of the mediaType but this breaks validation. As the INSPIRE profile notes, perhaps this should be an additional field in the distribution such as characterEncoding

paultag commented 9 years ago

this sounds like a wonderful idea

On Wed, Apr 8, 2015 at 4:25 PM, Philip Ashlock notifications@github.com wrote:

DCAT doesn't provide a way to specify character encoding as noted in the INSPIRE profile of DCAT https://ies-svn.jrc.ec.europa.eu/projects/metadata/wiki/INSPIRE_profile_of_DCAT-AP_-_Reference#Character-encoding. Some, including examples from Chicago https://data.cityofchicago.org/data.json, have attempted to include the character encoding as part of the mediaType but this breaks validation. As the INSPIRE profile notes, perhaps this should be an additional field in the distribution such as characterEncoding

— Reply to this email directly or view it on GitHub https://github.com/project-open-data/project-open-data.github.io/issues/464 .

:wq

brownpl commented 6 years ago

+1 for this. I just fielded a request from an end user looking for this information. I also think it would be a great field to add.