- From: Stéphane Corlosquet <scorlosquet@gmail.com>
- Date: Sat, 22 Jun 2013 07:58:52 -0400
- To: Jarno van Driel <jarno@quantumspork.nl>
- Cc: public-vocabs@w3.org
- Message-ID: <CAGR+nnEcAFNQME8yhiKpp4ixbrT5bzDsm+457cDpLFyy+qxz3g@mail.gmail.com>
On Sat, Jun 22, 2013 at 7:28 AM, Jarno van Driel <jarno@quantumspork.nl>wrote: > Thanks for the explanation, nice to know. I'm new in getting a bit > involved like this, so I just thought I'd put up the question. > > As for your question: 'Is nesting the markup an additional level with > each breadcrumb link one of those things that publishers often get > wrong? > > I don't know if in many cases it's the publishers that get it wrong > but in my experience it's more that people are bound to the CMS they > use. Unfortunately it often takes the big CMS's a long time to > implement features like schema.org correctly?) FYI, we're integrating schema.org in Drupal 8 (to be released end of the year or beginning of 2014). > and writing your own > modules simply isn't part of the skill-set of the majority of folks. > >From a semantic standpoint I'd prefer the nested breadcrumb. I think > it's the most correct. But... > Making it a nested breadcrumb makes it difficult to implement on > current CMS's because their breadcrumb systems mostly are based on an > ordered structure. > > Now if we somehow could get the right people at the big platforms > (Drupal, WordPress, Magento and such) involved maybe they could give > some useful input. > I'm a Drupal developer. Breadcrumbs are rendered as a flat list by default in Drupal, and I agree that's easier than nested breadcrumbs from a markup standpoint. > > In the end I'd like to get a 100% semantical correct breadcrumb but if > we'd need to settle for a 80% correct breadcrumb, because that way it > can be easier implemented on current systems, I'd be more than happy > to except that as well if it means we can move ahead and finally can > get it implemented. > > -- Steph.
Received on Saturday, 22 June 2013 12:04:33 UTC