Noz’s reference example of a content type is the new one. Everyone recognizes this type of content and its elements (semantic categories): title, signature, photo caption, etc. The consistent structure of this type of content allows people to create and consume news in familiar and predictable ways.
This consistency, coupled with semantic markup, also allows canada business email list machines to process news in powerful ways they otherwise couldn’t – for example, listing today’s news headlines or pulling leading paragraphs to create a overview set.
This report (which contains a grain of truth – Noz taught an adaptive content workshop in Redmond on May 18) contains the typical elements, or semantic categories, that belong to this type of content.
Content type 2: product description
Just like news, product descriptions have a typical set of elements (semantic categories): product overview, product name, model number, etc. If you’re part of a business that creates product descriptions, and if those descriptions use inconsistent tag structures or metadata, your business is missing out on opportunities to make those descriptions easier to create, use, and automate.
Even if you can’t read Vietnamese, you instantly recognize this type of content as a product description. The consistent structure allows users to “browse and scan”. When consistently structured content is semantically marked up, machines can understand it and act on it in powerful ways. (Image borrowed from Noz presentation )
Formalized content types, such as product Denmark Phone Number List descriptions, allow teams from different parts of an organization to work together. For example (as shown here) you can map elements of a product description to wireframes for different output types. You could say, for example, “We need to display the product name, model number, and tagline in that order everywhere, and we’ll never have two taglines.”
