W3C home > Mailing lists > Public > public-vocabs@w3.org > October 2011

Re: Use of ContentURL in the ImageObject example on schema.org

From: Jason Douglas <jasondouglas@google.com>
Date: Tue, 18 Oct 2011 10:22:45 -0700
Message-ID: <CAEiKvUCCgw7QHs066=hjsc27QyQgMJhHZ46S8Ftx03TP=H4NNQ@mail.gmail.com>
To: Aaron Bradley <aaranged@yahoo.com>
Cc: PublicVocabs <public-vocabs@w3.org>
On Tue, Oct 18, 2011 at 10:19 AM, Aaron Bradley <aaranged@yahoo.com> wrote:

> Excuse the repost.  My original email somehow encoded the message in an
> attachment.
>
> -----
>
> On the page detailing ImageObject:
> http://schema.org/ImageObject
>
> The following example is given:
> <img src="mexico-beach.jpg" itemprop="contentURL" />
>
> On MediaObject (http://schema.org/MediaObject) we have another example of
> contentURL use.
> <meta itemprop="contentURL" content="
> http://media.freesound.org/[snip]....preview.mp3" />
>
>
> The expected type of contentURL is "URL."  All fine and well.  Except that
> under the description field schema.org says:
> "Actual bytes of the media object, for example the image file or video
> file."
>

That's meant to differentiate the URL of the media file rather than the URL
of its landing page.  Clearly, the wording could be improved.


>
> Wouldn't one expect a number here, then?  Or is the description incorrect?
>
> Or am I missing something?  The reference to the "image file or video file"
> again seems to support URL as the type, but "bytes" does not.
>
> By-the-by I sometimes see more obvious errors on schema.org (thinks like
> typos); is this list the most effective way of communicating those?
>
>
>
Received on Tuesday, 18 October 2011 22:47:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 06:48:56 GMT