W3C home > Mailing lists > Public > public-vocabs@w3.org > March 2012

Re: Last Call for Comments ... Re: proposal for updates to http://schema.org/Event

From: Danny Ayers <danny.ayers@gmail.com>
Date: Mon, 5 Mar 2012 12:17:19 +0100
Message-ID: <CAM=Pv=TY0TN+uLz4ZoWT5fc2Qe0T=9Ne6AgwYpy_QOqDwT74Yg@mail.gmail.com>
To: Adrian Giurca <giurca@tu-cottbus.de>
Cc: public-vocabs@w3.org, Dan Brickley <danbri@danbri.org>
On 5 March 2012 09:26, Adrian Giurca <giurca@tu-cottbus.de> wrote:
> I would say Schema.org does not define any required property.  By
> consequence interpreting a missing @location in http://schema.org/Event as
> null is a bit forced.

Event is defined as "An event happening at a certain time at a certain
location.". Ok, referring to a "null" place might not be the best
choice of words, but by definition it *does* have a place even if
@location is missing in the data.

One may define an http://schema.org/Event just by
> using one of properties such as:
>
> @startDate - then if nothing else is known, a processor would say this is a
> continuous event after @startDate

Ok, but then why bother with "Event" at all? If a "Thing" has a
@startDate then a processor can say this is a continuous event after
@startDate etc.

I agree that not requiring properties is the way to go for schema.org
("missing isn't broken"), but also think there's an advantage in using
typed items which have commonly associated properties. On the one hand
it's fairly close to how we as humans describe things, on the other it
simplifies management/processing of the data in the computer.

I just believe tweaking this particular definition to make it a little
more granular (making the space-time dimensions independent :) would
simplify reuse of Event and reduce the potential for confusion.

The location property can still be used to associate the Event with a
Place (or PostalAddress).

Cheers,
Danny.

-- 
http://dannyayers.com

http://webbeep.it  - text to tones and back again
Received on Monday, 5 March 2012 11:17:51 GMT

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