(2) Summary
The Web is an amazingly robust and constantly evolving body of shared concepts. Most
developers today use APIs as a standard way of how capabilities are encapsulated and
exposed. For some popular APIs, SDKs may allow developers to conveniently ignore API
details. For API designers and users of less popular APIs, however, understanding
how Web APIs work helps a lot to become a better designer and user of them. [http://webconcepts.info/] captures many standards that can help to design better APIs, and to easier understand
well-designed APIs. In this presentation, Erik briefly explains the idea behind Web
Concepts. He also demos how the site can be forked and customized to cover and document
a "personalized Web API surface" that helps developers and organizations to better
understand which Web surface they are surfing, and which of their APIs expose certain Web concepts.
Web Concepts: The Basics
(9) Food Labels
(10) Safety Labels
(11) Web Concepts: [http://webconcepts.info/specs/]
- Specifications define values for existing concepts [Web Concepts: [http://webconcepts.info/concepts/] (1)]
- [http://webconcepts.info/specs/IETF/RFC/7234] defines new values for three existing Web Concepts:
- [http://webconcepts.info/concepts/http-cache-directive/]:
[http://webconcepts.info/concepts/http-cache-directive/max-age], [http://webconcepts.info/concepts/http-cache-directive/max-stale], [http://webconcepts.info/concepts/http-cache-directive/min-fresh], [http://webconcepts.info/concepts/http-cache-directive/must-revalidate], [http://webconcepts.info/concepts/http-cache-directive/no-cache], [http://webconcepts.info/concepts/http-cache-directive/no-store], [http://webconcepts.info/concepts/http-cache-directive/no-transform], [http://webconcepts.info/concepts/http-cache-directive/only-if-cached], [http://webconcepts.info/concepts/http-cache-directive/private], [http://webconcepts.info/concepts/http-cache-directive/proxy-revalidate], [http://webconcepts.info/concepts/http-cache-directive/public], [http://webconcepts.info/concepts/http-cache-directive/s-maxage]
- [http://webconcepts.info/concepts/http-header/]:
[http://webconcepts.info/concepts/http-header/Age], [http://webconcepts.info/concepts/http-header/Cache-Control], [http://webconcepts.info/concepts/http-header/Expires], [http://webconcepts.info/concepts/http-header/Pragma], [http://webconcepts.info/concepts/http-header/Warning]
- [http://webconcepts.info/concepts/http-warn-code/]:
[http://webconcepts.info/concepts/http-warn-code/110], [http://webconcepts.info/concepts/http-warn-code/111], [http://webconcepts.info/concepts/http-warn-code/112], [http://webconcepts.info/concepts/http-warn-code/113], [http://webconcepts.info/concepts/http-warn-code/199], [http://webconcepts.info/concepts/http-warn-code/214], [http://webconcepts.info/concepts/http-warn-code/299]
- Specifications add one or more values for one or more concepts
- [http://webconcepts.info/specs/IETF/] define naming patterns for automated processing
(12) Web Concepts: [http://webconcepts.info/concepts/]
- Concepts establish a namespace for sharing values with shared meanings
- [http://webconcepts.info/concepts/http-header/] are one concept with currently 192 distinct values
- The currently listed values all are defined in W3C/IETF specifications
- If required the list could be extended with de-facto standards as well
- [http://webconcepts.info/concepts/link-relation/] are an extensible and fuzzy concept
- 103 link relations have been established as registered values
- Hypermedia applications often will use
private
URI-identified relations
- It is possible that only registered link relations are good candidates for sharing
(13) Web Concepts Overview
(14) Specification Series
<primary id="IETF" href="http://www.ietf.org/">
<name short="IETF">Internet Engineering Task Force</name>
<secondary id="RFC">
<name short="RFC">Request for Comments</name>
<id-pattern>^(\d+)$</id-pattern>
<md-pattern>$1</md-pattern>
<name-pattern>RFC $1</name-pattern>
<uri-pattern>urn:ietf:rfc:$1</uri-pattern>
<url-pattern>http://tools.ietf.org/html/rfc$1</url-pattern>
</secondary>
<secondary id="I-D">
<name short="I-D">Internet Draft</name>
<id-pattern>^(.+)$</id-pattern>
<md-pattern>$1</md-pattern>
<name-pattern>Internet Draft $1</name-pattern>
<uri-pattern>urn:ietf:id:$1</uri-pattern>
<url-pattern>http://tools.ietf.org/html/draft-$1</url-pattern>
</secondary>
</primary>
(15) Concept Configuration
<concept id="http-header">
<title-singular>HTTP Header Field</title-singular>
<title-plural>HTTP Header Fields</title-plural>
<iana-registry>http://www.iana.org/assignments/message-headers/message-headers.xhtml</iana-registry>
</concept> <concept id="http-warn-code">
<title-singular>HTTP Warn Code</title-singular>
<title-plural>HTTP Warn Codes</title-plural>
<iana-registry>https://www.iana.org/assignments/http-warn-codes/http-warn-codes.xhtml</iana-registry>
</concept>
<concept id="http-cache-directive">
<title-singular>HTTP Cache Directive</title-singular>
<title-plural>HTTP Cache Directives</title-plural>
<iana-registry>http://www.iana.org/assignments/http-cache-directives/http-cache-directives.xhtml</iana-registry>
</concept>
[http://creativecommons.org/licenses/by/3.0/]
