I've been slowly adding the historical results of baseball's world series, and in thinking about the 1994 world series, I hit upon a bit of a hurdle: this world series didn't occur.
As a piece of information, this fact seems relevant to me. However, in terms of integrating the "non-event" into the site, it really doesn't fit at all with the structure of all the other world series results, namely, "winner, loser, score", etc.
I guess that my question, then, is how is one to deal with non-events that are nevertheless relevant precisely because of their exceptionalism? The expectation of a world series in 1994, given the pattern set both before and after the cancelled season, separates this instance from all others in its class. However, since the actual event never occurred, I’m not sure if representing it in the current schema is either (i) possible or (ii) desirable.
There are other examples of this kind of expected-but-never-occurred event, notably in sports, and I was wondering if there are any ideas/suggestions on how to represent this type of information.
Thanks
Non-events
-
-
-
That's a good point. Just because an event doesn't appear in Freebase doesn't mean you can assume that it didn't occur.
I would model this by co-typing the 1994 World Series topic with a Canceled Event type and then maybe add a property to say why it was canceled.
-
Ditto what Shawn said; a new type seems the best way to handle this. I would also strongly recommend bringing up this discussion on the data-modeling mailing list.
-
cool, thanks for the feedback. I will definitely bring this up on the list.
-
