Web of Things (WoT), Architecture, Thing Description, Scripting API | W3C

Documents

Web of Things (WoT) Architecture, 2017-09-14.

Summary
  1. WoT Thing Description
  2. WoT Scripting API
  3. WoT Binding Templates.

Web of Things (WoT) Thing Description, 2017-09-14.

Summary

Describes the metadata and interfaces of Things.

Web of Things (WoT) Scripting API, 2017-09-14.

Summary

Operates on Things characterized by Properties, Actions and Events.

Abstracts

Web of Things (WoT) Architecture

Abstract

The W3C Web of Things (WoT) is intended to enable interoperability across IoT Platforms and application domains. Primarily, it provides mechanisms to formally describe IoT interfaces to allow IoT devices and services to communicate with each other, independent of their underlying implementation, and across multiple networking protocols. Secondarily, it provides a standardized way to define and program IoT behavior.

This document describes the abstract architecture for the W3C Web of Things. It is derived from a set of use cases and can be mapped onto a variety of concrete deployment scenarios, several examples of which are given. This document is focused on the standardization scope of W3C WoT, which consists of three initial building blocks that are briefly introduced and their interplay explained.

The WoT Thing Description (TD) provides a formal mechanism to describe the network interface provided by IoT devices and services, independent of their implementation. Provision of a TD is the primary requirement for a device to participate in the Web of Things. In fact, defining a Thing Description for an existing device allows that device to participate in the Web of Things without having to make any modifications to the device itself. WoT Binding Templates define how a WoT device communicates using a concrete protocol. The WoT Scripting API—whose use is not mandatory—provides a convenient mechanism to discover, consume, and expose Things based on the WoT Thing Description.

Other non-normative architectural blocks and conditions underlying the Web of Things are also described in the context of deployment scenarios. In particular, recommendations for security and privacy are included, while the goal is to preserve and support existing device mechanisms and properties. In general, W3C WoT is designed to describe what exists rather than to prescribe what to implement.

Web of Things (WoT) Thing Description

Abstract

This document describes a formal model and common representation for a Web of Things (WoT) Thing Description. A Thing Description describes the metadata and interfaces of Things, where a Thing is an abstraction of a physical entity that provides interactions to and participates in the Web of Things. Thing Descriptions provide a narrow-waist set of interactions based on a small vocabulary that makes it possible both to integrate diverse devices and to allow diverse applications to interoperate. Thing Descriptions, by default, are encoded in JSON-LD. JSON-LD provides both a powerful foundation to represent knowledge about Things and simplicity, since it allows processing as a JSON document. In addition to physical entities, Things can also represent virtual entities. A Thing Description instance can be hosted by the Thing itself or hosted externally due to Thing’s resource restrictions (e.g. limited memory space) or when a Web of Things-compatible legacy device is retrofitted with a Thing Description.

Web of Things (WoT) Scripting API

Abstract

The Web of Things (WoT) provides layered interoperability between Things by using the WoT Interfaces.

This specification describes a programming interface representing the WoT Interface that allows scripts run on a Thing to discover and consume (retrieve) other Things and to expose Things characterized by properties, Actions and Events.

Scripting is an optional “convenience” building block in WoT and it is typically used in gateways that are able to run a WoT Runtime and script management, providing a convenient way to extend WoT support to new types of endpoints and implement WoT applications like Thing Directory.

Mentions

  • JSON-LD

Argot

The Suitcase Words
  • W3C Web of Things (WoT)
  • IoT Platforms
  • interfaces
  • devices
  • services
  • implementation
  • multiple networking protocols
  • standardized
  • behavior
  • abstract architecture
  • use cases
  • mapped
  • scenarios,
    deployment scenarios,
    concrete deployment scenarios
  • standardization scope
  • WoT Thing Description (TD),
    Thing Description (TD)
  • formal mechanism
  • network interface
  • independent of implementation
  • participate
  • WoT Binding Templates,
    Binding Templates. [no acronym]
  • WoT Scripting API,
    Scripting API.
  • blocks,
    blocks and conditions,
    architectural blocks and conditions,
    non-normative architectural blocks and conditions.
  • scenarios,
    deployment scenarios,
    the context of deployment scenarios,
    in the context of deployment scenarios.
  • Web of Things (WoT)
  • Thing Description
  • narrow-waist
    a narrow-waist set,
    a narrow-waist set of interactions,
    a narrow-waist set of interactions based on a small vocabulary,
    a narrow-waist set of interactions based on a small vocabulary that makes it possible both,
    a narrow-waist set of interactions based on a small vocabulary that makes it possible both to integrate diverse devices and to allow diverse applications to interoperate.
  • JSON-LD
  • foundation … knowledge
  • a Web of Things-compatible legacy device
  • layered interoperability
  • Things
  • WoT Interface
  • Actions
  • Events
  • gateways
  • WoT Runtime
  • script management
  • endpoints
  • Thing Directory

Previously filled.

Tech is Public Enemy #1. So Now What? | John Battelle

John Battelle; Tech Is Public Enemy #1. So Now What?; In His Blog, white-labeled as NewCo, centrally-hosted on Medium; 2017-09-10.
Teaser: If tech wants to reverse the crushing tide of negative public opinion, it must start creating public good commensurate with its extraction of private profit.

tl;dr → Agree, perhaps. But it’s not clear to what one is agreeing at all. Whereas the lede is buried; that being the promotion of Richard Florida’s book The New Urban Crisis.
and → Unto the hook of the title: For the sin, The Nostrum. To wit:

Nostrum
  • Enumerate.
  • Confess,
  • Repent,
  • Restitute, reparate.
  • Return.

Occasion

John Battelle interviewed Richard Florida towards a book promotion.

Book

Richard Florida The New Urban Crisis: How Our Cities Are Increasing Inequality, Deepening Segregation, and Failing the Middle Class—and What We Can Do About It 1st Edition ; Basic Books; 2017-04-11; 336 pages; ASIN:0465079741: Kindle: $18, paper: $12+SHT.

Mentions

  • Where “tech” is Apple, Amazon, Facebook, Google, and maybe Netflix (rly?).
  • And JB foresaw it in a vision of 2017-01; fair. he also “saw” it in 2011-12, had Microsoft in the cohort, and pitched “The Internet Big Five” as a gushing chronicle-of-the-times, only-time-will-tell honorific of boosterist veneration. indeed though, it’s okay to change one’s mind upon further reflection.
  • Richard Florida is granted 191 words at the end to speak as a threat.
    Whereas Richard Florida has a direct line to Congress.
    Unless his demands are met … something will happen
  • Google Apple Facebook Amazon (GAFA),
    Google Amazon Facebook Apple (GAFA)
  • Facebook Amazon Netflix Google (FANG),
    Facebook Apple Netflix Google (FANG)
  • No Wintel.  The PC Revolution is over O.V.E.R.
    • No Microsoft?
    • No Intel?
Definition: the “tech” is an enumeration
  • Apple → fabless. Purveyors of phones & some laptops.
  • Amazon → Retail reseller. Cloud (billed as a service).
  • Facebook → Entertainment. laid against advertising.
  • Google → Fabless, phone designs. Cloud (billed as a service), Advertising marketplaces.  And 25 other hobbies as “Alphabet.”
  • Netflix → Licensed video entertainment. An Amazon cloud customer.
    …can’t really seriously belong in the class of the first four can it?

Epithets

  • Uber — a company that proved a perfect exemplar of tech’s most sociopathic characteristics*.
  • <quote>The bro culture long parodied in popular culture proved to be virulently on display at the world’s most valuable startup — misogyny, tone deaf management, winning at all costs, ignorance of social and political consequence.</quote>
  • Everything Store
  • <quote>rapacious and robotic approach to platform capitalism</quote>
  • Amazon’s purchase of Whole Foods
  • Big Tech
  • fake news
  • Russian information ops
  • <quote>They’re extracting — but giving nothing back.</quote>

Rebuttal

New bogies for new panics, not the old bogies from old panics…

Missing

Anyone that actually makes things out of actual atoms. No one is afraid of companies that fabricate things out of atoms.

  • Industry (even so called “light industry”)
  • Big Defense (denizens of ‘I’ in Military-Industrial Complex)
  • Big Oil
  • Big Food
  • Big Finance, a.k.a. “Wall Street”
  • Big Auto
  • Big Semiconductor
  • Big Telecom
  • Big Blue, a.k.a. IBM
  • Big Mining
  • Big Ads, a.k.a. “Madison Avenue”
  • Big Media, a.k.a. major market television
  • Big Music, a.k.a. “the Record Labels”
  • Big Hollywood, a.k.a. “The Movie Studios”
  • Big Newspaper
  • Big Cable
  • The Diamond Cartel, e.g. de Beers
  • Railroad Trusts
  • Anyone on the Conference Board.
    Remember the “interlocking directorate” research of ‘ago?
  • The QSR, as a self-conscious class.
  • Disney
  • Microsoft
  • Walmart
  • McDonald’s

And

  • No Japanese conglomerates. Remember MITI-managed organized markets?
  • No European national champions. Remember the ’90s?

Referenced

In archaeological order, newer outbursts on top, older opinements below…

Previously

In His Blog

Related

The publishing pile-on exponentially increasing across 2015, 2016, 2017. There are many more than are presented here. Everyone is sayin’ it, doin’ it; walkin’ the walk, talkin’ the talk. Yet presented here in archaeological order, newer outbursts on top, older opinements below…

Previously filled.

AVOID: Intel Compute Stick

tl;dr => only runs software provided by Intel.  Will not boot anything but the software delivered with the unit.  This is crippled closed-source hardware.

<quote cite=”ref“> was able to load Ubuntu 14.04.02 64-bit using this method, as well as Ubuntu 15.04 64-bit. But WiFi didn’t work out of the box with either operating system.
Linux Mint 17.1 and Fedora 21 wouldn’t load at all.  was able to access the GRUB bootloader menu with these operating systems, but he couldn’t get the full OS to load.</quote>

Remediation

  • Full specs for all operating systems
  • Just sell the hardware; sell the bare machine (no installed OS).
  • No secret software drivers.
  • Must boot Fedora.
  • Must boot Ubuntu.
  • etc.

Concept

  • A Windows-only version
    • 2GB of RAM
    • 32GB of storage
    • $150
    • Available “now”
  • A Linux (Ubuntu-only) version
    • 1GB of RAM (only)
    • 8GB (only)
    • $110
    • Available “maybe June”

Source: Intel Compute Stick mini-computer (with Windows) review; ; In Liliputing; 2015-04-22.

Actualities

Intel Cloud Services Platform

Intel Cloud Services Platform, version 6.0, 2013-11-21

Release Notes

  • Intel Identity Services => FedID
  • Cultures
    • Android (2.2, Froyo onward)
    • iOS
    • JavaScript, HTML5
    • Windows
  • Baseline RESTful API
    • XML
    • JSON
  • Services
    • Analytics
    • Catalog,
    • Commerce
    • Curation,
    • Recommendation

Identity Services

  • Social Integration
    • Facebook API tokens
    • Yahoo! Social Login
  • Regulatory: COPPA
  • REST Developer’s Guide
  • Intel Identity Services REST API Reference
  • OAuth 2.0
    • ClientID + Client Secret
    • Access Token
    • https://api.intel.com/identityui/v2/auth
  • Concepts
    • Scopes
    • Redirect
    • Sync vs Async (urn:intel:identity:oauth:oob:async)
      • Web App Synchronous => http://localhost/callback.html
      • Mobile App Synchronous => (deep link) myapp://action
      • Web App Asynchronous => urn:intel:identity:
        oauth:oob:async
  • URN Support (i.e. deep links)
  • Badging




Analytics Services

  • Opt-Out
  • Session Tracking API
  • Custom Events API
  • Dashboards
  • Real-Time Analytics
  • User, device, session, and demographic Analysis

Commerce Services & API

  • Client ID
  • PayPal
  • Taxation computations
  • Subscription API
  • Cart & Order Management

Catalog Services

  • Datasets
  • Bulk Upload
  • POI Data
  • Schema Management

Context SDK

  • States
    • Location-based states:
      • Country,
      • City,
      • Semantic Place (Home/Work),
      • Nearby restaurants.
    • Time and date-based states:
      • Time zone,
      • Local time,
      • Weekday,
      • Part of day,
      • Holiday information in your location.
    • Device-based states:
      • Applications running,
      • Missed calls,
      • Battery level,
      • Music played.
  • Context states sensing
    • Environment weather.
    • Device terminal context.
    • Location semantic/geographic place.
    • Network connection.
    • Device contacts.
    • Device calendar.
    • Physical activity.
    • Audio classification.
    • Message (SMS).
    • Device information.
    • Installed applications.

Location-Based Services

  • Removed 2013-11-11

Miscellaneous

See Also

Genevieve Bell, Keynote Address; Intel IDF; 2013-09-12; 43 pages.

Via: backfill, backfill

User, device, session, and demographic Analysis