Add Schema.org Claim

specs/botframework-activity/botframework-activity.md

@@ -1477,6 +1477,9 @@ The `error` field contains the reason the original [command activity](#command-a
 
 # Appendix I - Changes
 
+## 2023-09-22 - hawo@microsoft.com
+* Added [Schema.org Claim](#schema-org-claim) type definition
+
 ## 2020-07-07 - contact.me@nlchar.rocks
 * Fix the broken link to the Bot Framework Manifest Spec in the References section
 
@@ -1571,6 +1574,7 @@ Activity [entities](#entity) communicate extra metadata about the activity, such
 | string         | N/A                                     | String                    |
 | number         | N/A                                     | Number                    |
 | clientInfo     | N/A                                     | Skype client info         |
+| Claim          | https://schema.org/Claim                | Schema.org Claim          |
 
 ### string and number
 
@@ -1616,6 +1620,26 @@ Note that on channels with a persistent chat feed, `platform` is typically usefu
 
 `A9230`: Bots SHOULD NOT use the `platform` field to control how response data is formatted unless they have specific knowledge that the content they are sending may only ever be seen on the device in question.
 
+#### Schema.org Claim
+
+A response may sometimes contains references to other work to support facts claimed in the message. These references provide transparency to human users. Human users may use these references to understand system's intended uses, interpret relevant system behavior effectively, and remain aware of the possible tendency of over-relying on outputs produced by the system.
+
+When a reference is not fully accessible by the user, the bot can use [Schema.org Claim](https://schema.org/Claim) to include full or partial text from the original work. The claim is an extension to the activity and must not be cross-referenced from another activity.
+
+Channels decide how the referenced content can be displayed in their user experience. In most cases, contents should be shown in a separate pane, popover, or dialog. In cases where the channel has limited capability to display the content, the channel may use an alternative channel (e.g. a link to a website, or sending the content via email).
+
+`A9240`: The entity MUST include a `type` field, with value of `https://schema.org/Claim`.
+
+`A9241`: The entity MUST include an `@context` field, with value of `https://schema.org`.
+
+`A9242`: The entity MUST include an `@type` field, with value of `Claim`.
+
+`A9243`: The entity SHOULD include an `@id` field, with value of type IRI unique to the activity and referenced in the message `text` field.
+
+`A9244`: The entity MUST include a `text` field of type string, containing full, excerpted, or summarized text from the original work.
+
+`A9245`: The entity MAY include a `name` field of type string.
+
 # Appendix III - Protocols using the Invoke activity
 
 The [invoke activity](#invoke-activity) is designed for use only within protocols supported by Bot Framework channels (i.e., it is not a generic extensibility mechanism). This appendix contains a list of all Bot Framework protocols using this activity.
@@ -1722,4 +1746,3 @@ Here is an example of a command result indicating that the command was not suppo
 
 ### Channel rejecting commands
 Some channels may may not support the command protocol or not allow for application customization of commands. In this case, the channel can reject commands with a transport-level response codes to allow a sender to detect the command activity was rejected. Example: When the transport is HTTP, 200 indicates acceptance and 400 indicates that the Activity name is not supported.
-