- From: Karen Coyle <kcoyle@kcoyle.net>
- Date: Fri, 06 Dec 2013 06:57:32 -0800
- To: Dan Scott <denials@gmail.com>, "Olson, Peter" <polson@marvel.com>
- CC: "public-schemabibex@w3.org" <public-schemabibex@w3.org>, Henry Andrews <hha1@cornell.edu>
On 12/5/13 9:54 PM, Dan Scott wrote: >> Another example - over the years we published a series of Comic Series in which the titles changed but the numbering was continuous: X-Men -> New X-Men -> X-Men -> X-Men Legacy -> X-Men (again see the talk, which lists out a few more examples). Under the definition in the proposal each distinct title would be a distinct Comic, correct? > > Fascinating! Yes, I think each title would be a distinct Comic in that > case. Maybe we'll need some sort of relatedWork mechanism sooner > rather than later after all. From http://docs.comics.org/wiki/Tracking > it looks like "Continues from" / "Continues in" covers the > relationships that comics.org cares about, although it carries series > name, publisher, and date with each relationship. For many years libraries used the rule that if a periodical changed title it became a "new" or "different" periodical for purposes of cataloging, even if the numbering was continuous. The reason for that was that it was assumed that users would look under a specific title and therefore expected to find that title in the catalog. This is being re-thought (finally) because periodicals tend to change titles for purposes of marketing even when the subject matter does not change. (Sound familiar? :-)). Such title changes were so annoying that the serials catalogers named their own professional journal "Title Varies." I hope we haven't veered away from mark-up and into cataloging. Markup should mark up what is on the page, however the page creator wishes it. I would place any *decisions* about description of things outside of schema.org. Flexibility is what is needed. kc > > How would that have been handled in the original proposal: separate > ComicSeries for each title change, I guess? > >> Comic Stories - because stories can be and are reprinted, the original comic issue in which they appeared should probably be identified in the schema. For example, the Spider-Man origin story has been reprinted hundreds of times, but it's always "from" Amazing Fantasy #15. > > That sounds very reasonable; so something like an > "originallyPublishedIn" property that should only be used if there are > more than one "partOfComicIssue" / "partOfPeriodicalIssue" properties, > to identify the ur-comic (or periodical, as that could be useful for > non-comic articles as well)? > >> It might be worthwhile looking at the comics.org schema as well: http://docs.comics.org/wiki/Current_Schema > > As someone who cut his first-career teeth developing a relational > database for 8 years, *yes*, it's always worthwhile looking at > database schemas (I will pretend that I'm not seeing the "recalculated > by code on data updates" statements) :) > > Hey, there is a "Story" table in the schema. That makes me feel better > about having a ComicStory type, then! > > Many thanks again for your contributions, Peter! > > Dan > > -- Karen Coyle kcoyle@kcoyle.net http://kcoyle.net m: 1-510-435-8234 skype: kcoylenet
Received on Friday, 6 December 2013 14:57:59 UTC