emitted.schema.json

{
  "meta:license": [
    "Copyright 2017 Adobe Systems Incorporated. All rights reserved.",
    "This work is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license",
    "you may not use this file except in compliance with the License. You may obtain a copy",
    "of the License at https://creativecommons.org/licenses/by/4.0/"
  ],
  "$schema": "http://json-schema.org/draft-06/schema#",
  "$id": "https://ns.adobe.com/xdm/common/event/emitted",
  "type": "object",
  "title": "Emitted Event",
  "meta:extends": "https://ns.adobe.com/xdm/common/eventenvelope",
  "description":
    "The `emitted event` represents the activity of emitting a message or some `object`. This event type provides the capability to conform custom activities to the XDM Event Envelope. A custom activity is one where the system transporting the event isn't aware of what is in the event. A custom activity typically tends to be configured by a system's end user. Take, for example, custom OSGI events in AEM. One concern does arise regarding the `emitted event`, which is, its generic nature that allows for almost every activity to be modeled as 'message emitted' activity. This, however, is a trap that publishers of the XDM Event Envelope must steer away from.",
  "allOf": [
    {
      "$ref": "https://ns.adobe.com/xdm/common/eventenvelope"
    },
    {
      "properties": {
        "@type": {
          "type": "string",
          "const": "https://ns.adobe.com/xdm/common/event/emitted"
        }
      }
    }
  ],
  "meta:status": "experimental"
}