- From: Thad Guidry <thadguidry@gmail.com>
- Date: Tue, 10 Apr 2012 13:56:21 -0500
- To: public-vocabs@w3.org
- Message-ID: <CAChbWaOZF2LLo8gx8M9or-55LSpg-O=vTjF+Jp9od_p4zwET9w@mail.gmail.com>
One example that I use to explain a web page is that of an encyclopedia itself, when it comes to "possible" structure. For instance.. Many folks consider that ALL the pages between the first volume's front binder cover <HEADER> and the last volume's rear binder cover <FOOTER> could be considered "content", in html terms <BODY> However we all know that there are many structured parts of what the "content" contains.... you have verso pages, you have appendixes sometimes on each volume, .... you get the idea. In looking at Danny's suggestions... I like the idea of "Item" being almost a superclass above all others. Item could potentially contain many Articles (where each one has a date), which all Articles are "content" having things AND all those Articles are in fact... Creative Works. So... the only Schema that could possibly apply appears at http://schema.org/ItemPage and http://schema.org/CollectionPage BUT both of which imply to the whole webpage itself. Where it gets fuzzy in Schema.org is WHAT class to use when you have many Items, and each Item has many Articles. More documentation is needed for CollectionPage ... it or something else could be the "collector" of all "content" that potentially could span multiple pages with multiple articles... I just dunno. On Tue, Apr 10, 2012 at 3:11 AM, François Daoust <francois@joshfire.com>wrote: > +1 as well, to 'content' and 'date' in particular. > I'm basically using CreativeWork when I need something above Article > but having an Item class to restrict this to content-oriented material > would be nice to have as well. > > Francois. > > On Mon, Apr 9, 2012 at 11:40 AM, Martin Hepp > <martin.hepp@ebusiness-unibw.org> wrote: > > Strong + 1 > > > > Martin > > > > On Apr 5, 2012, at 3:55 PM, Danny Ayers wrote: > > > >> In trying to map from some simple vaguely blog-like data I ran into > >> problems with the current vocab that would have been eased if the > >> following terms existed: > >> > >> Item (class) - any content-oriented material > >> a superclass of schema:Article etc. corresponding to rss:item, > >> atom:entry, foaf:Document, Information Resource > >> > >> date (property) - any date > >> a superproperty of datePublished etc. corresponding to dc:date > >> > >> content (property) - any content > >> placed alongside schema:description, corresponding to atom:content etc. > >> > >> I'd suggest that having broadly-defined classes/properties at the top > >> of the tree will simplify integration across the board. > >> > >> Background: > >> > http://dannyayers.com/2012/04/05/A-first-taste-of-the-schema.org-carbonated-soft-drink > >> > >> Cheers, > >> Danny. > >> > >> -- > >> http://dannyayers.com > >> > >> http://webbeep.it - text to tones and back again > >> > > > > -------------------------------------------------------- > > martin hepp > > e-business & web science research group > > universitaet der bundeswehr muenchen > > > > e-mail: hepp@ebusiness-unibw.org > > phone: +49-(0)89-6004-4217 > > fax: +49-(0)89-6004-4620 > > www: http://www.unibw.de/ebusiness/ (group) > > http://www.heppnetz.de/ (personal) > > skype: mfhepp > > twitter: mfhepp > > > > Check out GoodRelations for E-Commerce on the Web of Linked Data! > > ================================================================= > > * Project Main Page: http://purl.org/goodrelations/ > > > > > > > > > > -- -Thad http://www.freebase.com/view/en/thad_guidry
Received on Tuesday, 10 April 2012 18:56:50 UTC