Tim Berners-Lee
The purpose of this blog is the discussion of the Architecture of the World Wide Web.
As a foundation for discussion, the W3C Recommendation of 15 December 2004 is used as follows:
Table of Contents
1. Introduction
1.1. About this Document
1.1.1. Audience of this Document
1.1.2. Scope of this Document
1.1.3. Principles, Constraints, and Good Practice Notes
2. Identification
2.1. Benefits of URIs
2.2. URI/Resource Relationships
2.2.1. URI collision
2.2.2. URI allocation
2.2.3. Indirect Identification
2.3. URI Comparisons
2.3.1. URI aliases
2.3.2. Representation reuse
2.4. URI Schemes
2.4.1. URI Scheme Registration
2.5. URI Opacity
2.6. Fragment Identifiers
2.7. Future Directions for Identifiers
2.7.1. Internationalized identifiers
2.7.2. Assertion that two URIs identify the same resource
3. Interaction
3.1. Using a URI to Access a Resource
3.1.1. Details of retrieving a representation
3.2. Representation Types and Internet Media Types
3.2.1. Representation types and fragment identifier semantics
3.2.2. Fragment identifiers and content negotiation
3.3. Inconsistencies between Representation Data and Metadata
3.4. Safe Interactions
3.4.1. Unsafe interactions and accountability
3.5. Representation Management
3.5.1. URI persistence
3.5.2. Linking and access control
3.5.3. Supporting Navigation
3.6. Future Directions for Interaction
4. Data Formats
4.1. Binary and Textual Data Formats
4.2. Versioning and Extensibility
4.2.1. Versioning
4.2.2. Versioning and XML namespace policy
4.2.3. Extensibility
4.2.4. Composition of data formats
4.3. Separation of Content, Presentation, and Interaction
4.4. Hypertext
4.4.1. URI references
4.5. XML-Based Data Formats
4.5.1. When to use an XML-based format
4.5.2. Links in XML
4.5.3. XML namespaces
4.5.4. Namespace documents
4.5.5. QNames in XML
4.5.6. XML ID semantics
4.5.7. Media types for XML
4.5.8. Fragment identifiers in XML
4.6. Future Directions for Data Formats
5. General Architecture Principles
5.1. Orthogonal Specifications
5.2. Extensibility
5.3. Error Handling
5.4. Protocol-based Interoperability
6. Glossary
7. References
7.1. Architectural Specifications
8. Acknowledgments
Please use the above numeration to refer to specific issues. The original document may be found at the w3c home.
As a foundation for discussion, the W3C Recommendation of 15 December 2004 is used as follows:
Table of Contents
1. Introduction
1.1. About this Document
1.1.1. Audience of this Document
1.1.2. Scope of this Document
1.1.3. Principles, Constraints, and Good Practice Notes
2. Identification
2.1. Benefits of URIs
2.2. URI/Resource Relationships
2.2.1. URI collision
2.2.2. URI allocation
2.2.3. Indirect Identification
2.3. URI Comparisons
2.3.1. URI aliases
2.3.2. Representation reuse
2.4. URI Schemes
2.4.1. URI Scheme Registration
2.5. URI Opacity
2.6. Fragment Identifiers
2.7. Future Directions for Identifiers
2.7.1. Internationalized identifiers
2.7.2. Assertion that two URIs identify the same resource
3. Interaction
3.1. Using a URI to Access a Resource
3.1.1. Details of retrieving a representation
3.2. Representation Types and Internet Media Types
3.2.1. Representation types and fragment identifier semantics
3.2.2. Fragment identifiers and content negotiation
3.3. Inconsistencies between Representation Data and Metadata
3.4. Safe Interactions
3.4.1. Unsafe interactions and accountability
3.5. Representation Management
3.5.1. URI persistence
3.5.2. Linking and access control
3.5.3. Supporting Navigation
3.6. Future Directions for Interaction
4. Data Formats
4.1. Binary and Textual Data Formats
4.2. Versioning and Extensibility
4.2.1. Versioning
4.2.2. Versioning and XML namespace policy
4.2.3. Extensibility
4.2.4. Composition of data formats
4.3. Separation of Content, Presentation, and Interaction
4.4. Hypertext
4.4.1. URI references
4.5. XML-Based Data Formats
4.5.1. When to use an XML-based format
4.5.2. Links in XML
4.5.3. XML namespaces
4.5.4. Namespace documents
4.5.5. QNames in XML
4.5.6. XML ID semantics
4.5.7. Media types for XML
4.5.8. Fragment identifiers in XML
4.6. Future Directions for Data Formats
5. General Architecture Principles
5.1. Orthogonal Specifications
5.2. Extensibility
5.3. Error Handling
5.4. Protocol-based Interoperability
6. Glossary
7. References
7.1. Architectural Specifications
8. Acknowledgments
Please use the above numeration to refer to specific issues. The original document may be found at the w3c home.
