Re: markup for a community meeting?

On 06/25/2014 02:51 PM, Justin Boyan wrote:
> I think adding a 'host' or 'organizer' property alongside attendee and
> performer on <> would make
> sense. I also think adding a new subtype, say,
> <>, is a no-brainer. The accessibility and
> amenities issues should be considered more broadly - and perhaps they go
> with the Place rather than the Event. Finally, IMO, issuesToAddress is
> unlikely to be used consistently as a structured field so that data
> should probably just be part of the event description.
I agree that accessibility and amenities Place fits better.
Also already while ago I suggested adding host/organizer property for

> On Thu, Jun 19, 2014, 5:31 AM, Albert Willis <
> <>> wrote:
>     Working on a project and I need to markup meetings of community
>     members of a city or neighborhood to address a civic issue and
>     nothing in fits.
>     Ideally, I’d like a version of Event with the following changes:
>       * instead of a performer, it would be a convener (or host) which
>         would be a Person or Organization
>       * instead of workPerformed, it would be issuesToAddress (something
>         that’s not a CreativeWork)
>       * markup to indicate if an RSVP is required
>       * a contactPoint for the meeting (like we see in
> for RSVPs or additional information
>       * markup for amenities offered (food, child care) to make it more
>         convenient for people to attend
>       * should be able to specify whether the location has affordances
>         for people in wheelchairs, etc.
>       * should be able to indicate if there will be translation
>         available for non-native speakers
>       * should be able to indicate whether sign language for deaf people
>         will be available
>     Most of the meetings I attend are hosted by ad hoc or temporary
>     entities (committees, working groups, etc.) that aren’t formal
>     Organizations, so the markup doesn’t
>     work well for that either, but that’s another issue.
>     In the short term, any suggestions for a combination of markup I
>     could use to indicate some of these attributes?
>     Longer term, I’m happy to participate in a process for new
> <> vocabulary to address these issues.
>     Thanks.
>       — Al
>     ---
>     Al Willis
> <>

Received on Wednesday, 25 June 2014 13:12:45 UTC