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

broaden https://schema.org/fileFormat - useful for many CreativeWorks #790

Closed
danbri opened this issue Sep 22, 2015 · 9 comments
Closed

broaden https://schema.org/fileFormat - useful for many CreativeWorks #790

danbri opened this issue Sep 22, 2015 · 9 comments
Assignees

Comments

@danbri
Copy link
Contributor

@danbri danbri commented Sep 22, 2015

Currently https://schema.org/fileFormat "MIME format of the binary (e.g. application/zip)." is a text field associated only with the SoftwareApplication type.

I propose we broaden it to apply (potentially) to any CreativeWork. This would allow us for example to say that some particular Dataset is in application/ld+json format, or that an ImageObject was image/png.

Although the name of the property is a little inelegant (it should probably have been called "media type" initially), it does not seem a huge win to change that now. I suggest instead we write something like:

  • CreativeWork: fileformat(Text) - "Media type (MIME format) of the content e.g. application/zip of a SoftwareApplication binary. In cases where a CreativeWork has several media type representations, 'encoding' can be used to indicate each MediaObject alongside particular fileFormat information."

(and link to http://www.iana.org/assignments/media-types/media-types.xhtml - in the schema we should mark this as equivalent to dc:format)

/cc @rvguha @shankarnat @vholland @chaals @mfhepp @ajax-als @pmika @tilid @scor @mfhepp

I'd like to squeeze this into the upcoming http://sdo-phobos.appspot.com/docs/releases.html#sdo-phobos release (improves DataFeed), if I can get some +1s here...

@danbri danbri self-assigned this Sep 22, 2015
@vholland
Copy link
Contributor

@vholland vholland commented Sep 22, 2015

+1

2 similar comments
@pmika
Copy link
Collaborator

@pmika pmika commented Sep 23, 2015

+1

@thiagomgd
Copy link

@thiagomgd thiagomgd commented Sep 23, 2015

+1

@ajax-als
Copy link
Collaborator

@ajax-als ajax-als commented Sep 23, 2015

+1

On Wed, Sep 23, 2015 at 9:11 AM, Thiago Margarida notifications@github.com
wrote:

+1


Reply to this email directly or view it on GitHub
#790 (comment)
.

@sballesteros
Copy link

@sballesteros sballesteros commented Sep 23, 2015

+1 we are currently misusing encodingFormat for that.

@shankarnat
Copy link
Collaborator

@shankarnat shankarnat commented Sep 24, 2015

+1

1 similar comment
@mfhepp
Copy link
Contributor

@mfhepp mfhepp commented Sep 24, 2015

+1

@danbri
Copy link
Contributor Author

@danbri danbri commented Sep 24, 2015

Sounds like rough consensus (pinging @scor for steering group unanimity). I'll code it up for the next release under sdo-phobos.

@danbri
Copy link
Contributor Author

@danbri danbri commented Nov 6, 2015

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

Successfully merging a pull request may close this issue.

None yet
8 participants
You can’t perform that action at this time.