Atlas Ecosystem Tweets (V 1.0)


The tweets sent/received by an active thing/Vendor/App Developer in a smart space are formated (in JSON, XML) as follows ...

Click on each segment to learn more about the different attributes that describe each part of the tweet







The different Types of tweets a thing can broadcast (announce) in the smart space and captured by other things/App developers/Vendors/SmartSpace owners are:

    Identification - the Atlas thing ID attribute defined by the Smart Thing ID attribute under the "descriptive metadata" sub-section of IoT-DDL.

    Service - information about one service the thing can offer to the smart space according to the service description from the IoT-DDL.

    Relationship - information about one relationship the thing's service is related to another service (offered by another thing) or unbounded service (description to a future service).

    Actionable Keyword - information about potential input data/parameters for another thing's service.


The different Types of tweets a thing/App developer/Vendor/Smartspace owner can unicast (direct) in the smart space are:

    API Call - call by the thing/Application Developer to trigger an API for an offered service by another entity of the smart space (e.g., smart thing).

    API Call Result - result of the directed call to trigger an API for an offered service.

    Device Management Command - call by the User/vendor through the device management service/server to update/edit attributes of the uploaded thing IoT-DDL or reconfigure parts of the mounted architecture.

    Device Management Command Result - result of the directed call done by device management service/server.

    Actionable Keyword Binding - a service has matched with the data from an Actionable Keyword and asks the original thing to use it.



The sender of the tweet (and its the smart space) by the App developer/Vendor/Owner/Atlas thing should be identified through the following attributes

    Sender ID * : the App developer Name/the vendor Name/the Atlas thing ID attribute defined by the Smart Thing ID attribute under the "descriptive metadata" sub-section of IoT-DDL.

    Sender Name : the App developer Name/the vendor Name/the Atlas thing Name attribute defined by the Smart Thing Name attribute under the "descriptive metadata" sub-section of IoT-DDL.

    Sender Smart Space ID * : the ID of the smart space defined by the Smart Space ID attribute under the "descriptive metadata" sub-section of IoT-DDL.

    Sender Smart Space Info : the Smart space location information defined by the Smart Space Description + Smart Space Coordinates attributes under the "descriptive metadata" sub-section of IoT-DDL.

* means required attributes, while the other attributes are optional to be considered.

Regardless the type of the tweet, the tweet must hold the identification attributes of the sender smart thing.



The Receiver of the tweet (and its the smart space) by the App developer/Vendor/Owner/Atlas thing should be identified through the following attributes

    Receiver ID * : the App developer Name/the vendor Name/the Atlas thing ID attribute defined by the Smart Thing ID attribute under the "descriptive metadata" sub-section of IoT-DDL.

    Receiver Name : the App developer Name/the vendor Name/the Atlas thing Name attribute defined by the Smart Thing Name attribute under the "descriptive metadata" sub-section of IoT-DDL.

    Receiver Smart Space ID * : the ID of the smart space defined by the Smart Space ID attribute under the "descriptive metadata" sub-section of IoT-DDL.

    Receiver Smart Space Info : the Smart space location information defined by the Smart Space Description + Smart Space Coordinates attributes under the "descriptive metadata" sub-section of IoT-DDL.

* means required attributes, while the other attributes are optional to be considered.

For only the tweet type (API call/Result and Device-Management commands/Result), the tweet must hold the identification attributes of the receiver smart thing.



The attributes/parameters that describe the payload of the tweet differs w.r.t. the tweet type as follows

  Identification tweet
    thing vendor
    thing model
    thing description
    communication module
    communication protocol
    IP address


  Service Announcement tweet
    Service Name
    Service Type
    Descriptive Keywords
    Application Category
    Service Description
    Service API

    Output Type
    Output Name
    Output Description
    Output Range
    Input Type
    Input Name
    Input Description
    Input Range


  Relationship Announcement tweet (between bounded services)
    Relationship Name
    Relationship Type
    Relationship Category
    Relationship Establisher
    Relationship Description

    First Service ID
    First Service Space ID
    First Service Type

    Second Service ID
    Second Service Space ID
    Second Service Type


  Relationship Announcement tweet (between bounded and unbounded service)
    Relationship Name
    Relationship Type
    Relationship Category
    Relationship Establisher
    Relationship Description

    First Service ID
    First Service Space ID
    First Service Type

    Ubounded Service Name
    Ubounded Service Vendor
    Ubounded Service Type
    Ubounded Service Keywords
    Ubounded Service Match


  Relationship Announcement tweet (between unbounded and bounded service)
    Relationship Name
    Relationship Type
    Relationship Category
    Relationship Establisher
    Relationship Description

    Ubounded Service Name
    Ubounded Service Vendor
    Ubounded Service Type
    Ubounded Service Keywords
    Ubounded Service Match

    Second Service ID
    Second Service Space ID
    Second Service Type


  Actionable Keyword (AKW) Announcement tweet
    AKW Name
    Input Name
    Input Type
    Input Description
    Descriptive Keywords




JSON-formatted example for an Identification tweet announced by a smart lamp thing to the smart space

    {
      "Tweet Type": "Identification",

      "Sender ID": "AtlasThing475",
      "Sender Name": "Smart Lamp",
      "Sender Smart Space ID": "Atlas_SmartSpace3260127",
      "Sender Smart Space Info": "Living Room",

      "Vendor": "Philips Hue",
      "Model": "4100730U7",
      "Owner": "Philips Hue",
      "Release Date": "1/1/18",
      "Description": "Philips Hue for personal wireless lighting, White Ambiance Wellness Dimmable LED Smart Table Lamp",

      "Tweet TimeStamp": "9/2/19 - 06:09PM"
    }




JSON-formatted example for a service announced by the smart lamp thing to the smart space

    {
      "Tweet Type": "Service",

      "Sender ID": "AtlasThing475",
      "Sender Smart Space ID": "Atlas_SmartSpace3260127",

      "Service Name": "Turn on Light for Duration",
      "Service Type": "Action",
      "Service Keywords": "Light, Morning, ambiance",
      "Service API": "Turn_ON_Duration:{[Duration Value, Integer, [1-60]]}:[none, void, []]",
      "Input Type": "Integer",
      "Input Name": "Duration Value",
      "Input Unit": "Minute",
      "Input Range": "[1-60]",

      "Tweet TimeStamp": "9/2/19 - 06:09PM"
    }




JSON-formatted example for an Actionable Keyword announced by the smart lamp thing to the smart space

    {
      "Tweet Type": "Actionable Keyword",

      "Sender ID": "AtlasThing475",
      "Sender Smart Space ID": "Atlas_SmartSpace3260127",

      "AKW Name": "Lamp State",
      "Input Name": "IsOn",
      "Input Type": "Boolean",
      "Input Description": "A value representing whether the light is currently on",
      "Keywords": "lamp, light, status, on"

      "Tweet TimeStamp": "9/2/19 - 06:09PM"
   }


This is part of Atlas thing Ecosystem project [Read more about it]