- From: Richard Wallis <richard.wallis@dataliberate.com>
- Date: Fri, 9 Oct 2015 16:17:37 +0100
- To: Henry Andrews <hha1@cornell.edu>
- Cc: "public-schemabibex@w3.org" <public-schemabibex@w3.org>
- Message-ID: <CAD47Kz5=6OwuZ3ZBH4RoxM-mZkJCvg+67MumDZGEqO=rjHL6jA@mail.gmail.com>
I would suggest that datePublished is probably the best place to put the date of publication: YYYY or YYY-MM etc. (2015 or 2015-04). As to cover date, my inclination is to see that more as a name or alternateName, or maybe even a short description, which handle all sorts of variations: "The Obscure Journal - Spring 2014 Issue", "The Obscure Journal: May-October 2012". As these would be described as PublicationIssue(s), perhaps with an exampleOfWork link to a Periodical description, such names would make sense. ~Richard. Richard Wallis Founder, Data Liberate http://dataliberate.com Linkedin: http://www.linkedin.com/in/richardwallis Twitter: @rjw On 7 October 2015 at 07:09, <hha1@cornell.edu> wrote: > Hi folks, > > Looking at the PublicationIssue and PublicationEvent, I'm confused as to > where to put the cover date and how to represent dates that don't map > directly to the ISO format. Quarterlies are the most obvious, but > bi-monthlies and semi-monthlies are other examples. I'm also confused as > to whether this should be in "datePublished" (as a date) or "publication" > (as a PublicationEvent, which could indicate a quarter by giving a > startDate and endDate of the relevant months, perhaps?). > > I don't see an example of anything other than a fully specified date- is > there a more comprehensive set of date examples somewhere? Defining a > PublicationEvent that spans the whole time designated by the cover date > seems to be the most flexible option, but perhaps that is stretching the > concept of "Event" too far. > > "releasedEvent" seems like the clear home for the actual release > date(s), which are easier as they are full dates. > > thanks, > -henry >
Received on Friday, 9 October 2015 15:18:05 UTC