W3C home > Mailing lists > Public > public-vocabs@w3.org > September 2014

Re: ItemList proposal

From: Jarno van Driel <jarnovandriel@gmail.com>
Date: Mon, 8 Sep 2014 15:31:21 +0200
Message-ID: <CADK2AU0C=6oxmZ5_u_pODWg2_Z3T74W2fwZBBNnpT9NLPkc=WQ@mail.gmail.com>
To: "martin.hepp@ebusiness-unibw.org" <martin.hepp@ebusiness-unibw.org>
Cc: Vicki Tardif Holland <vtardif@google.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
I looked up the original thread (
http://lists.w3.org/Archives/Public/public-vocabs/2013Sep/0127.html) and
Martin's and Dan are correct indeed. So never mind me bringing up the MTE
route again, closed subject.

*Jarno van Driel*
Digital Marketing Technologist

Tel: +31 652 847 608
Google+: https://plus.google.com/u/0/+JarnovanDriel
Linkedin: linkedin.com/pub/jarno-van-driel/75/470/36a/

2014-09-08 14:16 GMT+02:00 martin.hepp@ebusiness-unibw.org <
martin.hepp@ebusiness-unibw.org>:

> I think the proposal is fine and addresses what we discussed in the
> earlier threads.
>
> However, we need to improve the documentation strings:
>
> First, for ItemList, let us indicate when to use a Thing, Text, or
> ListItem:
>
> e.g. "For the itemListElement" values, you can use simple strings (e.g.
> "Peter", "Paul, "Mary"), existing entities, or ListItem nodes. Text values
> are best if the elements in the list are plain strings. Existing entities
> are best for a simple, unordered list of existing things in your data.
> ListItem nodes are recommended for ordered lists and when you want to
> provide additional context about the element in that list. Note: The order
> of elements in your mark-up is not sufficient for indicating the order or
> elements. Use ItemList with itemPosition in such cases."
>
> Second, for ListItem, indicate when to use itemPosition and when next vs.
> previous.
>
> e.g. "An list item, e.g. a step in a checklist or how-to description.
> There are two possible ways of indicating the order in the list (if any):
> With itemPositing, you can give a simple numerical or textual value (e.g.
> 1, 2, 3 or  a,b,c). With previous(Item) and next(Item) you can represent
> the order as a chain of relationships between elements. Using either
> itemPosition OR previous(Item)/next(Item) is sufficient and recommended."
>
> Also, I suggest renaming next and previous to nextItem and previousItem,
> because we may need a similar term in future versions of schema.org for
> other uses.
>
>
> Best wishes / Mit freundlichen Grüßen
>
> Martin Hepp
>
> -------------------------------------------------------
> martin hepp
> e-business & web science research group
> universitaet der bundeswehr muenchen
>
> e-mail:  martin.hepp@unibw.de
> 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/
>
>
>
>
> On 05 Sep 2014, at 19:49, Vicki Tardif Holland <vtardif@google.com> wrote:
>
> > After taking people's feedback, we have put together a simpler ItemList
> proposal.
> >
> > http://sdo-itemlist.appspot.com/ItemList
> > http://sdo-itemlist.appspot.com/ListItem
> >
> > Details:
> >
> > To allow for expressing "just a list", ItemList is now moved from being
> a subclass of CreativeWork to a subclass of Intangible. To support existing
> uses of ItemList as a CreativeWork, ItemList now contains the following
> properties:
> >
> > - about
> > - author
> > - datePublished
> >
> > Feedback is welcome.
> >
> > - Vicki
> >
> >
> > Vicki Tardif Holland | Ontologist | vtardif@google.com
> >
>
>
>
Received on Monday, 8 September 2014 13:31:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:44 UTC