- From: Adrian Giurca <giurca@tu-cottbus.de>
- Date: Wed, 19 Dec 2012 10:08:07 +0100
- To: jeremy french <jeremy@jeremyfrench.co.uk>
- CC: public-vocabs@w3.org
- Message-ID: <50D183F7.6000401@tu-cottbus.de>
Dear Jeremy, I would say you should not use @location property because it refers to a Place of PostalAddress. As Schema.org does not define property cardinality you should just ignore this property. Myself I would use @url to define the web place where the webinar takes place i.e. the real time communication page. What is indeed missing is a way to declare your event as "WebinarEvent". Therefore I suggest http://schema.org/WebinarEvent as a subclass of http://schema.org/Event without defining any new property (the same as many other subclasses of http://schema.org/Event) I use "WebinarEvent" just to conform with the naming the other Event subclasses, otherwise I would just use "Webinar" Regards, Adrian Giurca On 12/18/2012 3:10 PM, jeremy french wrote: > I am trying to mark up a site with schema.org <http://schema.org> > markup and have come across something that I believe is an omission. > > We have a number of events some are conferences or meetups, but a lot > are webinars, the latter case causes two potential problems. > > 1: is that the location field is blank > 2: is that there isn't a clear way to mark the URI for the webinar. > > It would seem to me that a URI could be used for the location. Perhaps > with a specific event class VirtualEvent to indicate that the > location is not physical. Otherwise as I understand it the URI in > location could resolve to something which describes a location, which > could be confusing. > > Does this seem reasonable. Is there a better suggestion for marking up > non spacial events? > > Regards > Jeremy > > -- -Adrian Twitter <http://www.twitter.com/giurca> LinkedIn <http://www.linkedin.com/in/adriangiurca>
Received on Wednesday, 19 December 2012 09:09:08 UTC