Skip to content

pinazo/chickadee

BranchesTags
 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

170 Commits
bin
bin
 
 
lib
lib
 
 
web
web
 
 
.gitignore
.gitignore
 
 
.jshintrc
.jshintrc
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
package.json
package.json
 
 

Repository files navigation

chickadee

A contextual associations store and API for the IoT

chickadee is a contextual associations store. Specifically, it associates wireless device identifiers with a URL and/or a tag. In other words it maintains, for instance, the link between your wireless device and your online stories so that Smart Spaces which detect your device can understand what you're sharing about yourself. It also allows logical groupings of devices to share a common tag such as "lounge", for instance, to represent the sensor devices in a lounge, and "friends", for instance, to represent the devices carried by a group of friends.

chickadee is also a contextual API for the IoT. It binds to an instance of barnacles which provides the current state. It supports queries regarding the context at or near either a device ID or a tag. Continuing with the example above, it supports queries such as what is the contextat the lounge, as well as what is the contextnear the friends.

In the scheme of Things (pun intended)

The barnowl, barnacles, barterer and chickadee packages all work together as a unit, conveniently bundled as hlc-server. Check out our developer page for more resources on reelyActive software and hardware.

chickadee logo

What's in a name?

The Cornell Lab of Ornithology explains: "The Black-Capped Chickadee hides seeds and other food items to eat later. Each item is placed in a different spot and the chickadee can remember thousands of hiding places." Not only does it have an outstanding associative memory, it is also "almost universally considered cute thanks to its oversized round head, tiny body, and curiosity about everything, including humans."

If you were entrusting a bird to associate your wireless device with your online stories you'd want it to be cute and friendly enough to eat out of your hand, right? We could have named this package Clark's Nutcracker, the bird with arguably the best associative memory, but the whole nut-cracking thing doesn't inspire the same level of friendliness now does it?

One more fun fact that we feel compelled to pass along: "Every autumn Black-capped Chickadees allow brain neurons containing old information to die, replacing them with new neurons so they can adapt to changes in their social flocks and environment even with their tiny brains." Wow, that's database efficiency that we can aspire to!

Installation

npm install chickadee

Hello chickadee, barnacles & barnowl

var chickadee = require('chickadee');
var barnacles = require('barnacles');
var barnowl = require('barnowl');

var associations = new chickadee();
var notifications = new barnacles();
var middleware = new barnowl();

middleware.bind( { protocol: 'test', path: 'default' } );
notifications.bind( { barnowl: middleware } );
associations.bind( { barnacles: notifications } );

When the above is run, you can query the contextat a given (receiving) device, and the contextnear a given (transmitting) device:

A test tag is provided by default for the four simulated test reelceivers, present when barnowl is bound to the test protocol, and can be queried at http://localhost:3004/contextat/tags/test.

RESTful interactions

Include Content-Type: application/json in the header of all interactions in which JSON is sent to chickadee.

GET /contextat/receiver/{device-id}

Retrieve the context at the given receiver device id. For example, the id 001bc50940800000 would be queried as GET /contextat/receiver/001bc50940800000 and might return:

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3004/contextat/receiver/001bc50940800000"
    }
  },
  "devices": {
    "001bc50940100000": {
      "url": "http://reelyactive.com/metadata/test.json",
      "nearest": [
        {
          "device": "001bc50940800000",
          "rssi": 144
        }
      ],
      "href": "http://localhost:3004/associations/001bc50940100000"
    },
    "001bc50940800000": {
      "url": "http://reelyactive.com/metadata/ra-rxxx.json",
      "href": "http://localhost:3004/associations/001bc50940800000"
    }
  }
}

GET /contextat/directory/{directory}

Retrieve the context at the given directory value. For example, the directory forest:tree would be queried as GET /contextat/directory/forest:tree and would return data with the same structure as the above.

GET /contextat/tags/{tags}

Retrieve the context at the given tags. For example, the tag test would be queried as GET /contextat/tags/test and would return data with the same structure as the above.

GET /contextnear/transmitter/{device-id}

Retrieve the context near the given transmitter device id. For example, the id 001bc50940100000 would be queried as GET /contextnear/transmitter/001bc50940100000 and might return:

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3004/contextnear/transmitter/001bc50940100000"
    }
  },
  "devices": {
    "001bc50940100000": {
      "url": "http://reelyactive.com/metadata/test.json",
      "nearest": [
        {
          "device": "001bc50940800000",
          "rssi": 133
        }
      ],
      "href": "http://localhost:3004/associations/001bc50940100000"
    },
    "001bc50940800000": {
      "url": "http://reelyactive.com/metadata/ra-rxxx.json",
      "href": "http://localhost:3004/associations/001bc50940800000"
    }
  }
}

GET /contextnear/tags/{tags}

Retrieve the context near the given tags. For example, the tag test would be queried as GET /contextnear/tags/test and would return data with the same structure as the above.

GET /associations/{device-id}

Retrieve the association for the device with the given id. For example the id 001bc50940800000 would be queried as GET /associations/001bc50940800000 and might return:

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3004/associations/001bc50940800000"
    }
  },
  "devices": {
    "001bc50940800000": {
      "url": "http://myjson.info/story/test",
      "directory": "forest:tree",
      "tags": [
        "birdnest"
      ],
      "href": "http://localhost:3004/associations/001bc50940800000"
    }
  }
}

PUT /associations/{device-id}

Update or create an association for the given device id. For example, to update a device with identifier 001bc50940800000, PUT /associations/001bc50940800000 and include the updated JSON, for example:

{ "url": "http://myjson.info/story/lonely",
  "directory": "forest:tree:branch",
  "tags": [ "birdnest", "home" ] }

A successful response might return:

{
  "_meta": {
    "message": "ok",
    "statusCode": 200
  },
  "_links": {
    "self": {
      "href": "http://localhost:3004/associations/001bc50940800000"
    }
  },
  "devices": {
    "001bc50940800000": {
      "url": "http://myjson.info/story/lonely",
      "directory": "forest:tree:branch",
      "tags": [
        "birdnest",
        "home"
      ],
      "href": "http://localhost:3004/associations/001bc50940800000"
    }
  }
}

If the device id does not already exist, it will be created.

DELETE /associations/{device-id}

Delete a given device association.

GET /associations/{device-id}/url

GET /associations/{device-id}/directory

GET /associations/{device-id}/tags

Identical to GET /associations/id except that only the url, directory or tags is returned, respectively.

PUT /associations/{device-id}/url

PUT /associations/{device-id}/directory

PUT /associations/{device-id}/tags

Identical to PUT /associations/id except that only the url, directory or tags is updated, respectively.

DELETE /associations/{device-id}/url

DELETE /associations/{device-id}/directory

DELETE /associations/{device-id}/tags

Identical to DELETE /associations/id except that only the url, directory or tags is deleted, respectively.

Implicit Associations

The following implicit associations are supported. In other words, the implicit url will be provided unless the device is already uniquely associated, via its identifier, with a url. If you're one of the manufacturers below and would like the URL to instead point to an API on your server please contact us.

Where to bind?

barnacles

barnacles provides the current state. In the absence of a barnacles binding, chickadee will always return a 404 Not Found status. chickadee can bind to a single instance of barnacles only.

associations.bind( { barnacles: notifications } );

Options

The following options are supported when instantiating chickadee (those shown are the defaults):

{
  httpPort: 3004,
  associationManager: null,
  persistentDataFolder: "data"
}

Notes:

  • persistentDataFolder specifies the path to the folder which contains the persistent database file (before v0.3.12 the default was "")

What's next?

This is an active work in progress. Expect regular changes and updates, as well as improved documentation! If you're developing with chickadee check out:

License

MIT License

Copyright (c) 2015 reelyActive

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

About

Contextual associations store and API. We believe in an open Internet of Things.

www.npmjs.com/package/chickadee

Resources

Readme

License

MIT license
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • JavaScript 86.9%
  • HTML 7.6%
  • CSS 5.5%