- From: Jarno van Driel <jarno@quantumspork.nl>
- Date: Tue, 11 Jun 2013 23:07:48 +0200
- To: public-vocabs@w3.org
Let me be clear by saying that 'my' ordered breadcrumb markup isn't mine, though. I mentioned 'the breadcrumb proposal' in my opening and maybe I should have been clearer in mentioning the source - Egor/Yandex- as mentioned by Gregg Kellogg. I took his markup as a base and only tried to clarify that a nested breadcrumb -imho- could do without a breadcrumb type. The way I see it is that we only need a new property -child- to make it work. Now there might be a multitude of reasons (RDFa/schema.org wise) why my statement is wrong but that could be because my level of theoretical knowledge could do with an upgrade. If somebody can confirm/deny my way of thinking in this -by all means- please do so. I'm very much open to learn something new. The only problem I see with the nested breadcrumb is getting it to be implemented/used by big CMS's and eCommerce platforms (Drupal, Wordpress, Magento) and developers. The markup maybe doesn't look very spectacular but having developed for mentioned platforms I know what a pain it is to get an ordered breadcrumb -with data-vocabulary.org markup- to be generated according to specs. If there is decided that a nested breadcrumb will be the standard I foresee serious implementation problems. Maybe not for all but at least for many low- and mid-level developers out there. Semantically it may be the nicest option but for practicality reasons it sure isn't. That's why I also pointed out the ordered breadcrumb -data-vocabulary.org - http://support.google.com/webmasters/bin/answer.py?hl=en&answer=185417. Which maybe has the poorer markup but, for the same practicality reasons, is a lot more feasible and likely to be successfully adopted by developers. I feel this is a very valid point that shouldn't be overlooked in this discussion.
Received on Tuesday, 11 June 2013 21:08:15 UTC