- From: Dan Scott <denials@gmail.com>
- Date: Fri, 6 Dec 2013 09:29:04 -0500
- To: Antoine Isaac <aisaac@few.vu.nl>
- Cc: "public-schemabibex@w3.org" <public-schemabibex@w3.org>
Hi Antoine: On Fri, Dec 6, 2013 at 4:11 AM, Antoine Isaac <aisaac@few.vu.nl> wrote: > Hi Dan, > > Thanks for all this work! > >>> Note that on the new proposal (which seems otherwise quite good at first >>> glance!) I'm surprised by the sub-class definition "Periodical > >>> PeriodicalVolume" . Why would every volume be a periodical? >> >> Good question. I had inherited from Periodical because I wanted most >> of the properties (startDate, endDate, hasPeriodicalIssue) but it's >> cleaner to just expand the domain of those properties than to suggest >> that a volume is a kind of Periodical. > > Yes, it's much better this way! > startDate and endDate would look awkward defined for Periodical-related > classes anyway. I guess their scope is much wider. And am a bit surprised > they don't exist yet in schema.org. I'm confused: startDate and endDate do already exist in schema.org; that's where I took their range and definitions from. Do you mean that you don't think there should be startDate / endDate on Periodical and PeriodicalVolume? I think there are use cases for having these properties on both types. For example, for "dead" periodicals (per PRESSoo) being able to make some assertions about "XYZ Journal, published by ABC Inc from 1863 through 1995" seems like it could be handy. In an ideal world, of course, you'll also provide a url for XYZ Journal that then links to a list of all volumes, issues, and articles published in that journal, but we know that's not always going to happen. > OK, starting the research: Hey, I've been combing through http://schema.org/docs/schema_org_rdfa.html as I've been putting this together, believe it or not :) > - there's startDate and endDate on (separately!) http://schema.org/Season > and http://schema.org/Series, http://schema.org/Event > - there's startTime and endTime on http://schema.org/Action Right, when it came time to produce the actual RDFS, I planned to just add a domainIncludes of Periodical and PeriodicalVolume to startDate and endDate. I'm not sure how startTime and endTime are relevant to Periodicals or Comics. > Perhaps some homogeneization could help (though I suspect it's hard to > change names on established classes). Hmm, I guess I don't understand what you want to homogenize, or what needs help. Could you clarify? And would that be something that could be separated from nailing down a workable Periodicals & Comics extension? Thanks, Dan
Received on Friday, 6 December 2013 14:29:36 UTC