W3C home > Mailing lists > Public > public-schemaorg@w3.org > February 2016

RE: FRBR and schema.org

From: Young,Jeff (OR) <jyoung@oclc.org>
Date: Thu, 25 Feb 2016 17:33:00 +0000
To: Richard Wallis <richard.wallis@dataliberate.com>, Thomas Francart <thomas.francart@sparna.fr>
CC: schema.org Mailing List <public-schemaorg@w3.org>
Message-ID: <CY1PR0601MB1536BFB7076021C5E72211BFADA60@CY1PR0601MB1536.namprd06.prod.outlook.com>
It seems like schema:contentUrl would be the best choice to point at the actual URL of a media object that is being described: http://schema.org/contentUrl. Here’s the description:

Actual bytes of the media object, for example the image file or video file.

You have to stare closely at the domain and range to see the difference from schema:associatedMedia. They probably get mixed up in practice.


From: Richard Wallis [mailto:richard.wallis@dataliberate.com]
Sent: Thursday, February 25, 2016 12:07 PM
To: Thomas Francart <thomas.francart@sparna.fr>
Cc: schema.org Mailing List <public-schemaorg@w3.org>
Subject: Re: FRBR and schema.org

On 25 February 2016 at 13:32, Thomas Francart <thomas.francart@sparna.fr<mailto:thomas.francart@sparna.fr>> wrote:

What about using schema:MediaObject+schema:associatedMedia to describe PDF/HTML/XML Manifestations ?

I would

As MediaObject is a subtype of CreativeWork you have the properties you need to use either associtedMedia or workExampleto relate to the manifestation description.

Received on Thursday, 25 February 2016 17:33:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:23 UTC