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

Comments

Projects
None yet
8 participants
@danbri
Contributor

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

This comment has been minimized.

Show comment
Hide comment
@vholland

vholland Sep 22, 2015

Contributor

+1

Contributor

vholland commented Sep 22, 2015

+1

@pmika

This comment has been minimized.

Show comment
Hide comment
@pmika

pmika Sep 23, 2015

Collaborator

+1

Collaborator

pmika commented Sep 23, 2015

+1

@thiagomgd

This comment has been minimized.

Show comment
Hide comment
@thiagomgd

thiagomgd commented Sep 23, 2015

+1

@ajax-als

This comment has been minimized.

Show comment
Hide comment
@ajax-als

ajax-als 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)
.

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

This comment has been minimized.

Show comment
Hide comment
@sballesteros

sballesteros Sep 23, 2015

+1 we are currently misusing encodingFormat for that.

sballesteros commented Sep 23, 2015

+1 we are currently misusing encodingFormat for that.

@shankarnat

This comment has been minimized.

Show comment
Hide comment
@shankarnat

shankarnat commented Sep 24, 2015

+1

@mfhepp

This comment has been minimized.

Show comment
Hide comment
@mfhepp

mfhepp Sep 24, 2015

Contributor

+1

Contributor

mfhepp commented Sep 24, 2015

+1

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Sep 24, 2015

Contributor

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

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@danbri
Contributor

danbri commented Nov 6, 2015

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