Let's Talk About Our Relationship

[Let's Talk About Our Relationship]

[Matt Bishop (@MattBishopL3)]

Links between resources and different APIs will drive the Network Effect.
Relationships are easy to identify--natural part of being alive.
Relationships are stable over time.
Location of relationships can change. My mom can move, but I still know what the name of our relationship is.
Can we standardize the relationship graph? Not the data at each resource, but the names of the resources and their links to other resources?
Semantic documents of prototype resources
Risk here is stifling innovation. People won't participate if they cannot innovate on the resources.
Maybe the names of the resources are really categories (like weather) that lead to specific providers (like weather.com).
Search for resource by facet. I want weather in a zip code, or I want long term forecasts for Madagascar
Dialects and L10N--can the resource provider support a resource dialect (certain sub-capabilities, like 10-day-forecast) in a particular Locale and present in a given language? This is about generating the right presentation data for the end consumer.
Search needs to provide comparable facets to do apple-to-apple comparisons, while letting the providers surface their innovations in the search results.
API needs to be browsable from there. HAL Browser is an example. Let the dev "poke around" in a sandbox would be great to see if they want to commit to binding to the resource provider. This means the media type is standardized to be browsable in the first place.

To get to mass adoption of APIs that will drive the network effect, we need to make it easy for amateurs to build an API.
Examples: A church, squash club, bowling league, bakery
Today these amateurs go to blogger, or maybe weebly
Do they know they need an API?
Do they even know they produce data?
RSS is similar to blogging, trick is capturing the event.
Internet of Things can capture the events and generate the data. Bowling scoring desk, internet-connected oven. User manipulates Thing, which generates event, which populates a DB.
@Include 'scores' in the website/blog page to draw the data into the presentation.
Hypermedia Controls standardize the way an API can change state
Form
Selector (checkbox, radio buttons)
Date/Time picker
Authentication