Re: markup for a community meeting?

Ah! I understand - you want to broaden the subject of "seeks" from an agent (Person or Organization) to an event.

Hmm. One one hand, it dilutes the basic GoodRelations Agent-Promise-Object-Compensation principle.

See also

We could solve this by either multi-typing the event so that it represents both the event and the group of organizers, or make the organizer a properly declared entity. 

Alternatively, we could add a new property "contributionsNeeded", "seeksContribution", etc. Since seeks is a rather fundamental property, I am hesitant towards overloading it with a new meaning in this special case. 

On the other hand, it would not break a lot in terms of data at this point, but still, what we gain in markup brevity, we may loose in terms of explaining the core model.

BTW, I am now working on the GoodRelations User's Guide, which will explain the e-commerce model in in more detail. The given URI is one of the pages that are already quite final, and it may be of generic interest, so please feel free to share the URI.


martin hepp
e-business & web science research group
universitaet der bundeswehr muenchen

phone:   +49-(0)89-6004-4217
fax:     +49-(0)89-6004-4620
www: (group) (personal)
skype:   mfhepp 
twitter: mfhepp

Check out GoodRelations for E-Commerce on the Web of Linked Data!
* Project Main Page:

On 26 Jun 2014, at 15:03, ☮ elf Pavlik ☮ <> wrote:

> On 06/26/2014 12:39 PM, 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": "",
>    "pto": ""
>  },
>  "@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:30:59 UTC