Effective XML: 50 Specific Ways to Improve Your XML - page 1
- 1
- 2
- Main Page
- Main Page
- Table of content
- Copyright
- Praise for Effective XML
- Effective Software Development Series
- Titles in the Series
- Preface
- Acknowledgments
- Introduction
- Element versus Tag
- Attribute versus Attribute Value
- Entity versus Entity Reference
- Entity Reference versus Character Reference
- Children versus Child Elements versus Content
- Text versus Character Data versus Markup
- Namespace versus Namespace Name versus Namespace URI
- XML Document versus XML File
- XML Application versus XML Software
- Well-Formed versus Valid
- DTD versus DOCTYPE
- XML Declaration versus Processing Instruction
- Character Set versus Character Encoding
- URI versus URI Reference versus IRI
- Schemas versus the W3C XML Schema Language
- Part 1: Syntax
- Item 1. Include an XML Declaration
- The version Info
- The encoding Declaration
- The standalone Declaration
- Item 2. Mark Up with ASCII if Possible
- Item 3. Stay with XML 1.0
- New Characters in XML Names
- C0 Control Characters
- C1 Control Characters
- NEL Used as a Line Break
- Unicode Normalization
- Undeclaring Namespace Prefixes
- Item 4. Use Standard Entity References
- Item 5. Comment DTDs Liberally
- The Header Comment
- Declarations
- Item 6. Name Elements with Camel Case
- Item 7. Parameterize DTDs
- Parameterizing Attributes
- Parameterizing Namespaces
- Full Parameterization
- Conditional Sections
- Item 8. Modularize DTDs
- Item 9. Distinguish Text from Markup
- Item 10. White Space Matters
- The xml:space Attribute
- Ignorable White Space
- Tags and White Space
- White Space in Attributes
- Schemas
- Part 2: Structure
- Item 11. Make Structure Explicit through Markup
- Tag Each Unit of Information
- Avoid Implicit Structure
- Where to Stop?
- Item 12. Store Metadata in Attributes
- Item 13. Remember Mixed Content
- Item 14. Allow All XML Syntax
- Item 15. Build on Top of Structures, Not Syntax
- Empty-Element Tags
- CDATA Sections
- Character and Entity References
- Item 16. Prefer URLs to Unparsed Entities and Notations
- Item 17. Use Processing Instructions for Process-Specific Content
- Style Location
- Overlapping Markup
- Page Formatting
- Out-of-Line Markup
- Misuse of Processing Instructions
- Item 18. Include All Information in the Instance Document
- Item 19. Encode Binary Data Using Quoted Printable andor Base64
- Quoted Printable
- Base64
- Item 20. Use Namespaces for Modularity and Extensibility
- 1
- 2
