- From: jean delahousse <delahousse.jean@gmail.com>
- Date: Thu, 1 Mar 2012 15:21:19 +0100
- To: Adrian Giurca <giurca@tu-cottbus.de>
- Cc: Dan Brickley <danbri@danbri.org>, public-vocabs@w3.org
- Message-ID: <CAO+52yXgTOXXfHx5meV+9rO+w0B56webTvX9mRzR1Dh=qAM50g@mail.gmail.com>
For event : For information the work done by IPTC for event description is quite a good source of inspiration : see eventML http://www.iptc.org/site/News_Exchange_Formats/EventsML-G2/ 1) for URL to link to the web page of the event, I suggest we use the " contactPoints" already used for organization class, it will be convenient to give contact point of event organizer, or reservation office... For each contactpoint we will have an URL 2) for repetition, there is several cases : 2.1 a simple case is when the event as several occurrences in the same place, with exact same conditions like movie theater, then it is useful to describe several start/end dates 2.2 a other case is when the event happens several times, in various places at various dates... like a theater play which move from one town to the other, or Tour de France... then it is better to have several level of events. It enables to describe the main event (this theater-play with this casting, organizers, booking system..) and sub-events with a stard/end date and location - we have such type of relationship for organizations with "member" property 2.3 there is also the case of event that repeats themselves overtime, like "Festival de Cannes", "Olympic Summer Games", sportive events... You don't know the next dates, but you want to express this event appends each year, semester, 2 years..., or each sunday after eastern... 3) it can be useful to have the "duration" property, sometimes you wish to have startdate and duration of the event with no enddate. IPTC eventML uses a stadard to describe those durations 4) adding an eventcategory would be useful, but how does it interact with the event subclasses already defined BusinessEvent ChildrensEvent ComedyEvent DanceEvent EducationEvent Festival FoodEvent LiteraryEvent MusicEvent SaleEvent SocialEvent SportsEvent TheaterEvent UserInteraction VisualArtsEvent All the best, Jean 2012/3/1 Adrian Giurca <giurca@tu-cottbus.de> > 1. I find the markup for periodic events too verbose. I would propose a > property of class Event > periodicity:Number - the number of units as repetition period. > > The issue is with "unit" which can be any time unit such as second, > minute, hour, day, week, ... but I believe it should be in accordance with > startDate and endDate values. > > 2. eventCategory might be a http://schema.org/Enumeration This way it may > have expected type URL > > All the best, > - Adrian > > > On 2/29/2012 8:50 PM, Dan Brickley wrote: > >> On 24 February 2012 16:39, Dan Brickley<danbri@danbri.org> wrote: >> >>> I've just posted another draft proposal in the W3C wiki, >>> http://www.w3.org/wiki/**EventSchemaUpdate<http://www.w3.org/wiki/EventSchemaUpdate> >>> >>> From the wrapper text there, >>> >>> "The proposal comes from the Google teams working with the existing >>> Event markup, and has been checked by the other schema.org partners >>> prior to publication. See PDF for full details of the proposal." >>> >>> * "Proposes 3 new properties of Event: eventStatus, previousStartDate, >>> previousEndDate to support canceled or rescheduled events. >>> * Adds eventCategory to support categorised events. >>> * Supports recurring events by making startDate and endDate repeated. >>> * Encourages use of existing 'url' property (of Thing) to link to >>> associated Web pages." >>> >>> Feedback as ever welcomed here or in the Wiki. >>> >> OK, we didn't get a lot of discussion on this proposal. It has had >> some review elsewhere and is based on implementation feedback on the >> earlier deployed vocab so I suggest we wrap this one up quickly. >> >> Consider this a last call for comments on >> http://www.w3.org/wiki/**EventSchemaUpdate<http://www.w3.org/wiki/EventSchemaUpdate>, >> where btw the phrase 'Last >> Call' doesn't have the formality associated with official W3C >> standards. Rather it means, "hey, we're expecting to update schema.org >> based on this draft Real Soon Now and welcome your comments". Thanks >> for any feedback :) >> >> cheers, >> >> Dan >> >> >> > > -- -------------------------------------------------------------------------------------------------------- +33 6 01 22 48 55, delahousse.jean@gmail.com, skype: jean.delahousse @jdelahousse, http://jean-delahousse.info
Received on Thursday, 1 March 2012 14:21:48 UTC