Defining the data model of HTTP messages, not just the format
summary
Proposes a concrete extension to HTTP: an Accept-Profile header (IETF draft + W3C docs) that lets clients request resources by data model rather than just media type, enforces profile-before-format precedence, and returns an alternate-representations listing via Link headers or a JSON resource. Demonstrations include JSON/Link-based examples with GeoJSON/GeoSPARQL profiles and a small tool that composes validators (a checker validator aggregator) to validate inherited profile hierarchies; the prototype negotiates and validates profiles successfully.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker intro
- 1:35Talk positioning and outline
- 3:04Content negotiation refresher
- 8:42Content format blends and profiles
- 10:27Content negotiation by profile proposal
- 11:51What is a profile?
- 13:43Organizations using formal profiles
- 15:26Alternative methods for profile negotiation
- 17:33Format profile precedence rules
- 19:39Alternate representations data model
- 22:13HTTP as one implementation model
- 27:33Defining data models in profiles
- 31:04Profiles vs XML Schema and other tools
- 34:08Profiles vocabulary and tooling
- 35:58Profile validation tools
- 37:45Future adoption and impact
