Difference between revisions of "Activities"

From AMTech WikiDocs
Jump to: navigation, search
(Notification types)
(Notification types)
Line 10: Line 10:
 
== Notification types ==
 
== Notification types ==
  
*Notifications are defined as types in the same way that things and observations are.
+
* Notifications are defined as types in the same way that things and observations are.
*A notification type contains well-known supported properties, such as subject and body.
+
* A notification type contains well-known supported properties, such as subject and body.
*Notifications types can be used in actor's policies to define access to the instances of the notifications types
+
* Notifications types can be used in actor's policies to define access to the instances of the notifications types
 
* Instances of a notification type can be generated using an action notify in a reasoner
 
* Instances of a notification type can be generated using an action notify in a reasoner
  

Revision as of 22:02, 4 April 2016

Activity

Observers

Link to observer's help

Actors

Thing types

Notification types

  • Notifications are defined as types in the same way that things and observations are.
  • A notification type contains well-known supported properties, such as subject and body.
  • Notifications types can be used in actor's policies to define access to the instances of the notifications types
  • Instances of a notification type can be generated using an action notify in a reasoner

Reasoners

example

Types of reasoners

Actions

See Actions

Observation production configuration

  • Placeholders
  • Relation with entities observation production configuration

Validation for publication

In order to be published, an activity must be a valid json resource according to its metadata. All resources contained in the activity must also be valid for their metadata. The follower specific validations are also performed on the activity (some generate warning, others generate errors that will not allow publication)

  • Types involved in reasoners, observers and actors must be published
    • If there is an unpublished type that is used, and it is owned by the activity owner, a warning is generated
    • If the unpublished type is owned by another user, an error is generated
  • Types used in actors are involved in reasoners or observers (if not, a warning is generated)
  • Actors must not contain policies for notifications of a different activity

Publication