Specialization can have dramatic benefits for the development of
new document architectures.
Among the benefits:
No need to reinvent the base vocabulary - Create a module in 1/2 day with
10 lines vs. 6 months with 100s of lines; automatically pick up changes to
the base
No impact from other designs that customize for different purposes - Avoid
enormous, kitchen-sink vocabularies; Plug in the modules for your requirements
Interoperability at the base type - Guaranteed reversion from special
to base
Reusable type hierarchies - Share understanding of information across
groups, saving time and presenting a consistent picture to customers
Output tailored to customers and information - More specific search, filtering,
and reuse that is designed for your customers and information not just the
common denominator
Consistency - Both with base standards and within your information set
Learning support for new writers - Instead of learning standard markup
plus specific ways to apply the markup, writers get specific markup with guidelines
built in
Explicit support of different product architectural requirements
- Requirements of different products and architectures can be supported and
enforced, rather than suggested and monitored by editorial staff