W3C home > Mailing lists > Public > public-vocabs@w3.org > September 2014

Re: Move schema:fileSize & schema:fileFormat to schema:CreativeWork

From: Dan Scott <dan@coffeecode.net>
Date: Thu, 4 Sep 2014 11:36:58 -0400
To: Wes Turner <wes.turner@gmail.com>
Cc: Adrian Pohl <ad.pohl@gmail.com>, "public-vocabs@w3.org" <public-vocabs@w3.org>
Message-ID: <20140904153657.GA32701@denials>
On Thu, Sep 04, 2014 at 09:54:31AM -0500, Wes Turner wrote:
>It would be useful to have these properties with the type CreativeWork.

Hmm. I would have preferred to see them go on something a bit more
specific like MediaObject, but "embedded in a web page" is a pretty
restrictive definition (and image/video/audio doesn't capture some of
the formats like PDF / ODT that Adrian listed). Maybe it's time to
broaden that type?

>Is there a distinction between a CreativeWork and *renderings* of said

Yes, there can be, using the associatedMedia / audio / image / video
properties of CreativeWork, or...

>How can we express that there is a PDF and an ODT of the same document?

... thanks to the workExample / exampleOfWork properties that were
recently added to schema.org, you can express those relationships. See
https://github.com/rvguha/schemaorg/pull/108 for a request to add
examples for those properties to schema.org (where we express that there
are both book editions and movie adaptations of a given novel).

>Wes Turner
>On Thu, Sep 4, 2014 at 9:30 AM, Adrian Pohl <ad.pohl@gmail.com> wrote:
>> Hello,
>> we started working on draft recommendations for publishing metadata
>> for open educational resources within a German-speaking KIM-DINI
>> working group (KIM = Competence Centre Interoperable Metadata), see
>> [1] (in German). For each metadata element we would like to recommend
>> a rdf property at best from schema.org/LRMI. The bulk of the elements
>> are already covered by schema.org.
>> Anyhow, for indicating the size and format of a learning resource
>> (this could be anything from a zip file, to odt, jpg, pdf, ppt etc.) I
>> could't find other properties than schema:fileSize and
>> schema:fileFormat. Currently, these properties are placed in the
>> schema.org hierarchy at the type SoftwareApplication.
>> As it would be very useful to have more generic properties to describe
>> files, I suggest moving these properties up in the schema.org
>> hierarchy to the type CreativeWork. What do you think?
>> (For file size, there is another property schema:contentSize which is
>> also too specific as it is associated with resources of type
>> schema:MediaObject.)
>> All the best
>> Adrian
>> [1] https://wiki.dnb.de/x/hq_kBQ
Received on Thursday, 4 September 2014 15:37:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:44 UTC