- From: Vicki Tardif Holland <vtardif@google.com>
- Date: Wed, 11 Sep 2013 13:46:43 -0400
- To: Justin Boyan <jaboyan@google.com>
- Cc: Martin Hepp <martin.hepp@ebusiness-unibw.org>, Jason Douglas <jasondouglas@google.com>, Jarno van Driel <jarno@quantumspork.nl>, Dan Brickley <danbri@google.com>, Guha Guha <guha@google.com>, TallyFy <hello@tallyfy.com>, PublicVocabs <public-vocabs@w3.org>, Sam Goto <goto@google.com>
- Message-ID: <CAOr1obHw9MO_kN9bNnBzr5GpftZBqRvi7O6HWcrUWyJ4DVT3_A@mail.gmail.com>
I prefer option 1 (modifying ItemListElement to allow for a structured value). A rank property in Thing lacks context. (Rank relative to what?) The ambiguity is an invitation for many localized interpretations. Vicki Vicki Tardif Holland | Metadata Analyst | vtardif@google.com | 978-613-9630 On Wed, Sep 11, 2013 at 11:51 AM, Justin Boyan <jaboyan@google.com> wrote: > The current proposal is ambiguous about whether the ListItem is the item > itself, or whether the ListItem.represents is the item. Here are two > options which I think would be clearer: > > Option 1. Make the range of itemListElement be Thing. Create a new > StructuredValue called NumberedItem which pairs a Number and a Thing. > > With this schema, representing a list without numbers can be done with a > flat model: > > { "@context" : "http://schema.org", > "@type" : "ItemList", > "itemListElement" : [ {"@type" : "Movie", "name" : "Jaws"}, {"@type" : > "Movie", "name" : "Bulworth"} ] } > > And the extra hierarchy only comes into play when numbers are required: > > { "@context" : "http://schema.org", > "@type" : "ItemList", > "itemListElement" : [ {"@type" : "NumberedItem", "number" : 1, "item" : > {"@type" : "Movie", "name" : "Jaws"}}, > {"@type" : "NumberedItem", "number" : 2, "item" : > {"@type" : "Movie", "name" : Bulworth"}} ] } > > > Option 2. Add a new property for the item position directly to > schema.org/Thing. Call it, say, "rank" -- maybe it finds some other > general applications besides item lists. > > { "@context" : "http://schema.org", > "@type" : "ItemList", > "itemListElement" : [{"@type" : "Movie", "rank" : 1, "name" : "Jaws"}, > {"@type" : "Movie", "rank": 2, "name" : "Bulworth"}] } > > > What do you think? I think I prefer Option 1. > > Justin > > > > > > On Wed, Sep 11, 2013 at 11:34 AM, Martin Hepp < > martin.hepp@ebusiness-unibw.org> wrote: > >> > >> > My question was about *numbered* unstructured steps... which I think is >> actually the use case that started the thread. >> > >> Then I ListItem.name should do the trick. >> >> > >> > >> > Martin >> > >> > >> > -------------------------------------------------------- >> > 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/ >> > >> > >> > >> > >> >> -------------------------------------------------------- >> 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/ >> >> >> >> >
Received on Wednesday, 11 September 2013 17:47:15 UTC