Re: Proposal – extension for Athletics

If we are going to discuss prizes, it would be worth making sure any new
type would be compatible with the general idea of awards, including
non-athletic awards.

- Vicki

On Fri, May 12, 2017 at 6:02 PM, Aaron Bradley <aaranged@gmail.com> wrote:

> @Aaron,
>> In your work with EA and eSports arenas, bookings, and planning... do
>> ya'll have any special Types yet that would fall in the "planning" category
>> that Martin mentions ? Could you ask some of those eSports event planners
>> and organizers if there are missing properties for our Event Type or
>> towards publishing in general ?
>>
>
>> You can capture all of these gaps under this extension and as time moves
>> forward, those Types and Properties that are useful for all Domains can be
>> pulled out and put into our Core for wider cross Domain usage.
>>
>
> For SportsEvent specifically the most notable additions are the property
> hasQualifier and its inverse property isQualifierFor (kind of analogous to
> OpenTrack's prevRound and nextRound), and hasPrize.
>
> With that wider cross-domain usage in mind, the types for hasQualifier and
> hasPrize, Qualification and Prize respectively, are both simply
> intangibles.  A Qualification might be, in sports, what qualifies you to
> participate in a sports event, but might also be what qualifies you to get
> into law school (obviously this is not far off OpenTracks
> QualificationCriteria).  A Prize in our context is a prize for a level of
> achievement in a sports event, but in other contexts might be prize for a
> contest.
>
> And yes, we're reaching out to those in the industry to help inform the
> development process (and would be grateful if anyone reading this forwards
> it to any parties they think might be interested in commenting or
> contributing to this effort).
>
>
>> Another tip from me:
>> Also, anything special about the publishing of results themselves ?  I
>> think most of that we have addressed already, but perhaps there are Machine
>> oriented properties or attributes of "ways to publish" or interprocess
>> properties that are missing that help with language translation of results
>> or specific publishing platform properties that we are missing...so also
>> think about those as well.  Don't just think about it in terms of  "its a
>> big Excel / CSV table of results".
>>
>> Think like a machine first....then apply your human brain. :)
>>
>
> Nothing special, just working out our approach.  We hope to fork the Git
> as per Richard's instructions
> <http://dataliberate.com/2016/02/10/evolving-schema-org-in-practice-pt1-the-bits-and-pieces/> (machines
> FTW:) but might publish something more lightweight (it's at least
> well-documented) to get the discussion started.
>
> Martin, looking forward getting that out and then hearing your feedback so
> we can, indeed, seek alignment.
>
>