- From: Anthony Moretti <anthony.moretti@gmail.com>
- Date: Tue, 19 Jun 2018 17:06:02 -0700
- To: Richard Wallis <richard.wallis@dataliberate.com>
- Cc: "Muri, Allison" <allison.muri@usask.ca>, Simon Cox <Simon.Cox@csiro.au>, Thad Guidry <thadguidry@gmail.com>, Vicki Tardif Holland <vtardif@google.com>, roger@ecstatic.com, "schema.org Mailing List" <public-schemaorg@w3.org>
- Message-ID: <CACusdfTkksoJKuGBiShZntOCjs7=qMJV2mj0fLE1b2_ZNpo3uQ@mail.gmail.com>
Look, I'm no temporal expert or anything, but maybe the problem is in English it could be a continuum from "event" to "period" as the interval of time being named gets longer, with no clear boundary. Mike's birthday party - an event The Middle Ages - a period Because from a data modeling point of view they're the same (at least as far as my modeling knowledge goes). So an unpopular solution I'm guessing would be to rename the type to *EventOrPeriod*. So your previous example: The Black Death superEventOrPeriod: The Middle Ages People's ideas? Anthony On Tue, Jun 19, 2018 at 4:10 PM Richard Wallis < richard.wallis@dataliberate.com> wrote: > Anthony, > > I’m not following your logic here. I don’t see a Period (of time from a > start time/date to an end date/time) as an event. > > ~Richard. > > Richard Wallis > Founder, Data Liberate > http://dataliberate.com > Linkedin: http://www.linkedin.com/in/richardwallis > Twitter: @rjw > > On 20 June 2018 at 00:05, Anthony Moretti <anthony.moretti@gmail.com> > wrote: > >> That definitely works, but only if some definition of Period was agreed >> on. >> >> The property periodEventOccurred would be a subproperty of superEvent in >> any case: >> >> superEvent >> >> periodEventOccurred >> >> >> So you could describe the same information using the existing term right? >> >> The Black Death >> >> superEvent: The Middle Ages >> >> >> Anthony >> >> >> On Tue, Jun 19, 2018 at 3:50 PM Richard Wallis < >> richard.wallis@dataliberate.com> wrote: >> >>> Using a Period Type I would suggest a cleaner alternative way of saying >>> an event occurred during a period would be like this: >>> >>> { >>> "@context": "http://schema.org", >>> "@type": "Event", >>> "name": "The Black Death", >>> "Description": "A pandemic that spread throughout Europe", >>> "periodEventOccured": { >>> "@type": "Period", >>> "name": "The Middle Ages", >>> "approximateStartDate": "400AD", >>> "approximateEndDate":"1500AD" >>> } >>> } >>> >>> On 19 June 2018 at 23:41, Anthony Moretti <anthony.moretti@gmail.com> >>> wrote: >>> >>>> I was referencing the development version of Schema, I should probably >>>> reference production, sorry Roger: >>>> >>>> - https://schema.org/subEvent >>>> - https://schema.org/superEvent >>>> >>>> To say some event happened during the Iron Age for example: >>>> >>>> Invention of iron plow >>>> superEvent: Iron Age >>>> >>>> >>>> Anthony >>>> >>>> On Tue, Jun 19, 2018 at 3:05 PM Muri, Allison <allison.muri@usask.ca> >>>> wrote: >>>> >>>>> The google Cloud host is really slow and I think the 404 is a result >>>>> of something loading too slowly. I could probably publish this more >>>>> reliably on my own website! I generally just wait a bit and reload the >>>>> page. Sorry about that. >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On Jun 19, 2018, at 3:58 PM, Roger Rohrbach <roger@ecstatic.com> >>>>> wrote: >>>>> >>>>> I get 404 Not Found for both of those pages. >>>>> >>>>> >>>>> On Jun 19, 2018, at 11:50 AM, Anthony Moretti < >>>>> anthony.moretti@gmail.com> wrote: >>>>> >>>>> Isn't it already modeled by these properties?: >>>>> >>>>> - https://webschemas.org/subEvent >>>>> - https://webschemas.org/superEvent >>>>> >>>>> Events can exist in part-whole hierarchies, aren't named periods just >>>>> events high in these hierarchies? >>>>> >>>>> Anthony >>>>> >>>>> >>>>> >>> >
Received on Wednesday, 20 June 2018 00:06:38 UTC