- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Fri, 8 Aug 2014 10:22:06 +0200
- To: "'W3C Web Schemas Task Force'" <public-vocabs@w3.org>
On Friday, August 08, 2014 3:16 AM, Thad Guidry wrote: >> <div itemscope itemtype="http://schema.org/ItemList"> >> <meta itemprop="mainContentOfPage" content="true"/> >> <h2 itemprop="name">Top 10 laptops</h2><br> >> <meta itemprop="itemListOrder" content="Descending" /> >> **<div itemprop="list" itemscope>** >> <p>1. <span itemprop="itemListElement">HP Pavilion dv6-6013cl</span></p> >> <p>2. <span itemprop="itemListElement">Dell XPS 15 (Sandy >> Bridge)</span></p> >> <p>3. <span itemprop="itemListElement">Lenovo ThinkPad X220</span></p> >> </div> >> </div> >> >> [adapted from http://schema.org/ItemList - no clue how the examples there >> are supposed to be interpreted currently) > > I see your <p> and raise you a <ul> As noted above, I just adapted the example at http://schema.org/ItemList. > Ack ! (cough cough) ...that is just too verbose for something so .. > simple... I think I would just give into plain markup over structured > data (WHAT WOULD JARNO DO? is the new phrase, btw,if you > didn't know) and prefer my simple HTML structures of <li> list > item , <ul> unordered list , and <ol> ordered list. Right, but the purpose of the example above was not to write nice markup but to show how the existing model (example) could be enhanced with a Microdata-specific solution as it lacks support for lists at the syntax level. Both JSON-LD (@list) and RDFa (inlist) have that built-in. -- Markus Lanthaler @markuslanthaler
Received on Friday, 8 August 2014 08:22:37 UTC