: Nesting Microdata vs. independent Items I've been reading about Microdata and its implementation, however the examples are quite simple and I'm yet to find a website that thoroughly implements

@Ann8826881

[Updated: I suggest nesting types/elements when mark-up appears to require it. The reason is simple. You never know how the data will be used and where nesting is appropriate, nesting will give a clearer picture of the data you are marking-up.

Nesting does not always seem possible when you try and stitch mark-up into your HTML. It can be a real struggle sometimes. This is an important challenge to conquer. In this case, you may need to use id and then itemref to refer to parts of your schema definition to create relationships. The more data that you try and mark-up, the more difficult it will become to juggle all of the types/elements and therefore some compromises may need to be made- but never compromise on nesting types and elements and never break them up. The reason is simple. Nesting allows types and elements to have relationships. Breaking up types/elements and not properly nesting them will break the relationships between types/elements and make the mark-up less effective.]

I also strongly warn anyone to pay attention to nesting. Your mark-up may appear correct but not work while a simple nesting issue exists. I have seen this several times on this site. It can be confusing using mark-up and anyone can go cross-eyed very quickly.

Vote Up Vote Down