- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Thu, 26 Jun 2014 15:03:08 +0200
- To: "martin.hepp@ebusiness-unibw.org" <martin.hepp@ebusiness-unibw.org>
- CC: W3C Web Schemas Task Force <public-vocabs@w3.org>
On 06/26/2014 12:39 PM, martin.hepp@ebusiness-unibw.org wrote: > Note that you cannot directly seek or makesOffer an Event, because the range of those is a bundle of rights on something. Unless you sell the event itself, you have to create an offer with the business function "attend". The principle is shown in the GoodRelations extension for tickets at With schema:seek I would like to express what people organizing this event request *for this event* (food, projector, wifi, etc.), so schema:Demand -> schema:Product pattern would still apply. In case where multiple organizations collaborate on given event, I thinks it would require to create dedicated schema:Organization with multiple parents maybe related with inverse of schema:subOrganization I guess just adding host/organizer for event would work if system implements easy creation of new organizations. It still feels more intuitive to me if I could just use. { "@context": { "@vocab": "http://schema.org/", "pto": "http://www.productontology.org/id/" }, "@id": "/events/banana-matera-karaoke", "@type": "Event", "seeks": [ { "@id": "/listing/231231", "@type": "Demand", "itemOffered": { "@type": ["Product", "pto:Projector"] } }, { "@id": "/listing/243212", "@type": "Demand", "itemOffered": { "@type": ["Product", "pto:Banana"] } } ]
Received on Thursday, 26 June 2014 13:05:40 UTC