W3C home > Mailing lists > Public > public-vocabs@w3.org > November 2013

Re: [proposal] Property: organizer (for Event) || Property: host ?

From: Thad Guidry <thadguidry@gmail.com>
Date: Mon, 18 Nov 2013 09:55:39 -0600
Message-ID: <CAChbWaOJjTz35aacbn6ADz-8hT0hcd9eBDhsKjaCjZzSJ83U7A@mail.gmail.com>
To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
Cc: "public-vocabs@w3.org" <public-vocabs@w3.org>
Sponsor is also a useful property as well for some events, by the way.  And
sometimes the Sponsor and Organizer are one in the same.

In Freebase, we added several "x Sponser" properties in the Conferences,
Film Festivals, Exhibitions, etc domains.

But in general, a Sponsorship mediator is best... to account for reuse.  It
would hold the "Sponsored Recipient" and the "Sponsored By"  ... something
like this:


On Mon, Nov 18, 2013 at 8:49 AM, ☮ elf Pavlik ☮ <
perpetual-tripper@wwelves.org> wrote:

> Hello,
> I started coding simple open source app for organizing events, focusing at
> this moment on Crisis Camps and activities related to ongoing #hack4good
> virtual hackathon. So far I use Event, Place and Person to model this
> domain.
> In Event i can already use Property: attendee and Property: performer but
> for most events i find useful to distinguish people who organize it. What
> do you think about introducing: Property: organizer
> For very common tech (user-group) meetups, one could use:
> organizer - people who co-organize
> performer - people who present
> attendee - people who show up
> I can add it to http://www.w3.org/wiki/WebSchemas/SchemaDotOrgProposalsif few more people find it useful.
> Possibly relevent, in meetup.com events I see use of terms *organizer*
> and *host*: http://www.meetup.com/opentechschool-berlin/
> Cheers!

+ThadGuidry <https://www.google.com/+ThadGuidry>
Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>
Received on Monday, 18 November 2013 15:56:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:49:16 UTC