Re: Scores for head to head events

Here’s the SportsML vocab for event status, as promised:

pre-event
mid-event
post-event
postponed
suspended
halted
forfeited
rescheduled
delayed
canceled
intermission
if-necessary
discarded

Here’s the IPTC knowledge file that has definitions for these:
> On Mar 7, 2016, at 9:08 AM, Eleni Mikroyannidi <Eleni.Mikroyannidi@bbc.co.uk> wrote:
> 
> 
> Bringing this up again to discuss next actions,
> 
> Cheers,
> Eleni
> On 26/11/2015 10:10, "Steve Potts" <freeballoon@gmail.com> wrote:
> 
>> Thank you for bringing cricket into the discussion Richard, and also the scenario of a half-time status.
>> To this end, I'd like to tease out the progression of the score (or "measurement") through the event. 
>> 
>> Taking the example of cricket, we should be able to describe the following:
>>  • first period measurement (e.g. home team's first innings),
>>  • second period measurement (e.g. away team's first innings),
>>  • third period measurement (e.g. home team's second innings),
>>  • fourth period measurement (e.g. away team's second innings),
>> And for football:
>>  • half-time: home team goals + away team goals (plus overtime)
>>  • full-time: home team goals + away team goals (plus overtime)
>>  • extra-time half-time: home team  goals + away team goals (plus overtime)
>>  • extra-time full-time: home team goals + away team goals (plus overtime)
>>  • shootout: home team goals + away team goals 
>> Similarly for Baseball (multiple innings), Tennis (sets), Rugby (multiple measurement types) etc.
>> 
>> Although I don't have a proposed answer right now, I'm happy to pose the question.
>> 
>> 
>> 
>> On 25 November 2015 at 19:41, Richard Wallis <richard.wallis@dataliberate.com> wrote:
>>> Eleni,
>>> 
>>> I agree with you about modelling and inference, which is up to the consumer.
>>> 
>>> Taking a look at what Jonathan proposed I decided to test it a little with an extreme case - cricket.  Being English and having a couple of hours to fill at an airport gate.  If what is proposed can handle cricket scores, it can handle most anything!
>>> 
>>> The examples previously handle the Schedules/Cancelled/Postponed/Rescheduled cases well.
>>> 
>>> See from below, I think there is justification for EventInProgress, EventDelayed, and in addition EventPaused.
>>> 
>>> ~Richard.
>>> 
>>> Example 1.  Football at half-time:
>>> <script type="application/ld+json">
>>> {
>>>   "@context":"http://schema.org",
>>>   "@type":"SportsEvent",
>>>   “name": "Barclays Premier League Liverpool v Crystal Palace",
>>>   “eventStatus”:{
>>>       “@type”: “EventPaused”,
>>>       “description”: “Halftime break”
>>>    },
>>>   "competitor": [ 
>>>     {
>>>       "@type": "SportsTeam",
>>>       "name": "Liverpool",
>>>       "alignment": "home",
>>>       "measurement": {
>>>         "@type": "Measurement",
>>>         "measurementUnits": "Goals",
>>>         “measuredValue": "0"
>>>       }
>>>     },
>>>     {
>>>       "@type": "SportsTeam",
>>>       "name": "Crystal Palace",
>>>       "alignment": "away",
>>>       "measurement": {
>>>         "@type": "Measurement",
>>>         "measurementUnits": "Goals",
>>>         “measuredValue": "0"
>>>       }
>>>     },
>>>   ]
>>> }
>>> </script>
>>> Example 2. Cricket - in progress (day2)
>>> <script type="application/ld+json">
>>> {
>>>   "@context":"http://schema.org",
>>>   "@type":"SportsEvent",
>>>   “name”: “England Australia Ashes Test“,
>>>   “eventStatus”:{
>>>       “@type”: “EventInProgress”,
>>>       “description”: “Day 2 - Morning”
>>>    },
>>>   "competitor": [ 
>>>     {
>>>       "@type": "SportsTeam",
>>>       “name": "England",
>>>       "alignment": "home",
>>>       “measurement": [
>>>            {
>>>               “@type": "Measurement",
>>>               “name”: “First innings”,
>>>               “measurementUnits": "Runs",
>>>               “measuredValue”: "152"
>>>           },
>>>            {
>>>               "@type": "Measurement",
>>>               “name”: “First innings”,
>>>               “measurementUnits”: "Wickets",
>>>               “measuredValue”: “3"
>>>           },
>>>               "@type": "Measurement",
>>>               “name”: “First innings”,
>>>               “measurementUnits”: “Innings",
>>>               “measuredValue”: “1”
>>>           }
>>>        ]
>>>     },
>>>     {
>>>       "@type": "SportsTeam",
>>>       “name": "Australia",
>>>       "alignment": "away",
>>>       “measurement": {
>>>          “@type": "Measurement",
>>>          “name”: “First innings total”,
>>>          “measurementUnits": "Runs",
>>>          “measuredValue”: “210"
>>>        }
>>>     }
>>>   ]
>>> }
>>> </script>
>>> 
>>> Example 3. Cricket - paused (day 4)
>>> <script type="application/ld+json">
>>> {
>>>   "@context":"http://schema.org",
>>>   "@type":"SportsEvent",
>>>   “name”: “England Australia Ashes Test“,
>>>   “eventStatus”:{
>>>       “@type”: “EventPaused”,
>>>       “description”: “Day 4 - Rain stopped play”
>>>    },
>>>   "competitor": [ 
>>>     {
>>>       "@type": "SportsTeam",
>>>       “name": "England",
>>>       "alignment": "home",
>>>       “measurement": [
>>>            {
>>>               "@type": "Measurement",
>>>               “name”: “First innings total”,
>>>               “measurementUnits": "Runs",
>>>               “measuredValue”: “457"
>>>           },
>>>           {
>>>               "@type": "Measurement",
>>>               “name”: “Second innings”,
>>>               “measurementUnits": "Runs",
>>>               “measuredValue”: “87”
>>>           },
>>>            {
>>>               "@type": "Measurement",
>>>               “name”: “Second innings”,
>>>               “measurementUnits”: "Wickets",
>>>               “measuredValue”: “5”
>>>           },
>>>               "@type": "Measurement",
>>>               “measurementUnits”: “Innings",
>>>               “measuredValue”: “2”
>>>           }
>>>        ]
>>>     },
>>>     {
>>>       "@type": "SportsTeam",
>>>       “name": "Australia",
>>>       "alignment": "away",
>>>       “measurement": [
>>>            {
>>>               “@type": "Measurement",
>>>               “name”: “First innings total”,
>>>               “measurementUnits": "Runs",
>>>               “measuredValue”: “210"
>>>           },
>>>            {
>>>               “@type": "Measurement",
>>>               “name”: “Second innings total”,
>>>               “measurementUnits": "Runs",
>>>               “measuredValue”: “602”
>>>           },
>>>        ]
>>>     }
>>>   ]
>>> }
>>> </script>
>>> 
>>> 

Received on Monday, 7 March 2016 18:27:52 UTC