In the previous section, I argued in favor of creating content based on structured types with semantic associations and a computer-readable representation of hierarchy and relationships.
If we break our content out of an arbitrary container and structure it semantically, we have what appears to be a problem but is in reality an opportunity. There is no predefined way of displaying this content, no default rendering.
This is a Good Thing™.
When content exists in the abstract, the presentation playing field is leveled. No preeminence is given to web or mobile or print output. All forms are equal. ...