- From: Jarno van Driel <jarno@quantumspork.nl>
- Date: Sat, 22 Jun 2013 13:28:01 +0200
- To: public-vocabs@w3.org
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?) 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. 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.
Received on Saturday, 22 June 2013 11:28:33 UTC