transition from MDX v1 to v3 for Docusaurus v3 upgrade.

Author: sivaprasadanakarla

docs/agent-bridging/spec.md

@@ -10,7 +10,7 @@ Desktop Agent Bridging is an experimental feature added to FDC3 in 2.1, hence, i
 
 :::
 
-<!-- ## TODO list
+\<!-- ## TODO list
 
 * Expand on how the DAB should create the JWT token (and its claims, which must change to avoid replay attacks) which it sends out in the `hello` message for DAs to validate.
 * Link to BackPlane project somewhere 

docs/api/ref/DesktopAgent.md

@@ -1476,7 +1476,7 @@ Not implemented
 </TabItem>
 </Tabs>
 
-Adds a listener for incoming context broadcasts from the Desktop Agent. Provided for backwards compatibility with versions FDC3 standard <2.0.
+Adds a listener for incoming context broadcasts from the Desktop Agent. Provided for backwards compatibility with versions FDC3 standard\<2.0.
 
 **See also:**
 
@@ -1550,7 +1550,7 @@ Not implemented
 </TabItem>
 </Tabs>
 
-Version of `open` that launches an app by name rather than `AppIdentifier`. Provided for backwards compatibility with versions of the FDC3 Standard <2.0.
+Version of `open` that launches an app by name rather than `AppIdentifier`. Provided for backwards compatibility with versions of the FDC3 Standard\<2.0.
 
 **See also:**
 
@@ -1575,7 +1575,7 @@ Not implemented
 </TabItem>
 </Tabs>
 
-Version of `raiseIntent` that targets an app by name rather than `AppIdentifier`. Provided for backwards compatibility with versions of the FDC3 Standard <2.0.
+Version of `raiseIntent` that targets an app by name rather than `AppIdentifier`. Provided for backwards compatibility with versions of the FDC3 Standard\<2.0.
 
 **See also:**
 
@@ -1600,7 +1600,7 @@ Not implemented
 </TabItem>
 </Tabs>
 
-Version of `raiseIntentForContext` that targets an app by name rather than `AppIdentifier`. Provided for backwards compatibility with versions of the FDC3 Standard <2.0.
+Version of `raiseIntentForContext` that targets an app by name rather than `AppIdentifier`. Provided for backwards compatibility with versions of the FDC3 Standard\<2.0.
 
 **See also:**
 

docs/api/ref/Metadata.md

@@ -65,7 +65,7 @@ For each intent, it reference the applications that support that intent.
 interface AppMetadata extends AppIdentifier {
   /**
    *  The 'friendly' app name. This field was used with the `open` and
-   *  `raiseIntent` calls in FDC3 <2.0, which now require an `AppIdentifier`
+   *  `raiseIntent` calls in FDC3\<2.0, which now require an `AppIdentifier`
    *  with `appId` set. 
    * 
    *  Note that for display purposes the `title` field should be used, if set,

docs/api/spec.md

@@ -7,7 +7,7 @@ title: API Overview (next)
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-The role of FDC3 API is to establish a baseline interface for interoperability between applications. Because FDC3 is largely an agreement between existing platforms and applications, standards should be optimized for ease of adoption rather than functional completeness. Functionality absent from a FDC3 specification is in no way a commentary on its importance.
+The role  of FDC3 API is to establish a baseline interface for interoperability between applications. Because FDC3 is largely an agreement between existing platforms and applications, standards should be optimized for ease of adoption rather than functional completeness. Functionality absent from a FDC3 specification is in no way a commentary on its importance.
 
 The following sections examine the API's use-cases and core concepts. The API is fully defined in both subsequent pages of this Part and a full set of TypeScript definitions in the [src](https://github.com/finos/FDC3/tree/main/src/api) directory of the [FDC3 GitHub repository](https://github.com/finos/FDC3/).
 

docs/app-directory/overview.md

@@ -138,7 +138,7 @@ A launcher can then easily construct a URI by:
 3. URI port is default `https/443`, but can be overridden by the launcher
 4. URI url is by default `/api/appd/(version)/apps` . Calls that are made without version MUST automatically default to latest, i.e. `/api/appd/apps/app1` should return the same result as `/api/appd/v2/apps/app1".
 
-The resulting URI to retrieve application data for `app1` would be <https://appd.foo.com/api/appd/v2/apps/[email protected]>  
+The resulting URI to retrieve application data for `app1` would be https://appd.foo.com/api/appd/v2/apps/[email protected] [https://appd.foo.com/api/appd/v2/apps/[email protected]](https://appd.foo.com/api/appd/v2/apps/[email protected])  
 
 ### DNS/SRV Records
 

docs/context/ref/Action.md

@@ -8,20 +8,36 @@ sidebar_label: Action
 
 A representation of an FDC3 Action (specified via a Context or Context & Intent) that can be inserted inside another object, for example a chat message.
 
-The action may be completed by calling `fdc3.raiseIntent()` with the specified Intent and Context, or, if only a context is specified, by calling `fdc3.raiseIntentForContext()` (which the Desktop Agent will resolve by presenting the user with a list of available Intents for the Context).
+The action may be completed by calling:
+- `fdc3.raiseIntent()` with the specified Intent and Context
+- `fdc3.raiseIntentForContext()` if only a context is specified, (which the Desktop Agent will resolve by presenting the user with a list of available Intents for the Context).
+- `channel.broadcast()` with the specified Context, if the `broadcast` action has been defined.
 
 Accepts an optional `app` parameter in order to specify a specific app.
 
 ## Schema
 
-<https://fdc3.finos.org/schemas/next/context/action.schema.json> ([github](https://github.com/finos/FDC3/tree/main/schemas/context/action.schema.json))
+[https://fdc3.finos.org/schemas/next/context/action.schema.json](https://fdc3.finos.org/schemas/next/context/action.schema.json) ([github](https://github.com/finos/FDC3/tree/main/schemas/context/action.schema.json))
 
 ## Type
 
 `fdc3.action`
 
 ## Properties
 
+<details>
+  <summary><code>action</code></summary>
+
+**type**: `string` with values:
+- `broadcast`,
+- `raiseIntent`
+
+The **action** field indicates the type of action:
+- **raiseIntent** :  If no action or `raiseIntent` is specified, then `fdc3.raiseIntent` or `fdc3.raiseIntentForContext` will be called with the specified context (and intent if given).
+- **broadcast** : If `broadcast` and a `channelId` are specified then `fdc3.getOrCreateChannel(channelId)` is called to retrieve the channel and broadcast the context to it with `channel.broadcast(context)`. If no `channelId` has been specified, the context should be broadcast to the current channel (`fdc3.broadcast()`)
+
+</details>
+
 <details>
   <summary><code>title</code> <strong>(required)</strong></summary>
 
@@ -50,20 +66,30 @@ A context object with which the action will be performed
 
 </details>
 
+<details>
+  <summary><code>channelId</code></summary>
+
+**type**: `string`
+
+Optional channel on which to broadcast the context. The `channelId` property is ignored unless the `action` is broadcast.
+
+</details>
+
 <details>
   <summary><code>app</code></summary>
 
 **type**: api/AppIdentifier
 
-An optional target application identifier that should perform the action
+An optional target application identifier that should perform the action. The `app` property is ignored unless the action is raiseIntent.
 
 </details>
 
-## Example
+## Examples
 
 ```json
 {
   "type": "fdc3.action",
+  "action": "raiseIntent",
   "title": "Click to view Chart",
   "intent": "ViewChart",
   "context": {
@@ -90,3 +116,29 @@ An optional target application identifier that should perform the action
 }
 ```
 
+```json
+{
+  "type": "fdc3.action",
+  "action": "broadcast",
+  "channelId": "Channel 1",
+  "title": "Click to view Chart",
+  "context": {
+    "type": "fdc3.chart",
+    "instruments": [
+      {
+        "type": "fdc3.instrument",
+        "id": {
+          "ticker": "EURUSD"
+        }
+      }
+    ],
+    "range": {
+      "type": "fdc3.dateRange",
+      "starttime": "2020-09-01T08:00:00.000Z",
+      "endtime": "2020-10-31T08:00:00.000Z"
+    },
+    "style": "candle"
+  }
+}
+```
+

docs/context/ref/BaseContext.md

@@ -8,7 +8,7 @@ sidebar_label: BaseContext
 
 ## Schema
 
-<https://github.com/finos/FDC3/tree/main/schemas/context/context.schema.json>
+https://github.com/finos/FDC3/tree/main/schemas/context/context.schema.json [https://github.com/finos/FDC3/tree/main/schemas/context/context.schema.json](https://github.com/finos/FDC3/tree/main/schemas/context/context.schema.json)
 
 ## Type
 

docs/context/ref/Chart.md

@@ -17,7 +17,7 @@ In addition to handling requests to plot charts, a charting application may use
 
 ## Schema
 
-<https://fdc3.finos.org/schemas/next/context/chart.schema.json> ([github](https://github.com/finos/FDC3/tree/main/schemas/context/chart.schema.json))
+[https://fdc3.finos.org/schemas/next/context/chart.schema.json](https://fdc3.finos.org/schemas/next/context/chart.schema.json) ([github](https://github.com/finos/FDC3/tree/main/schemas/context/chart.schema.json))
 
 ## Type
 

docs/context/ref/ChatInitSettings.md

@@ -10,7 +10,7 @@ A collection of settings to start a new chat conversation
 
 ## Schema
 
-<https://fdc3.finos.org/schemas/next/context/chatInitSettings.schema.json> ([github](https://github.com/finos/FDC3/tree/main/schemas/context/chatInitSettings.schema.json))
+[https://fdc3.finos.org/schemas/next/context/chatInitSettings.schema.json](https://fdc3.finos.org/schemas/next/context/chatInitSettings.schema.json) ([github](https://github.com/finos/FDC3/tree/main/schemas/context/chatInitSettings.schema.json))
 
 ## Type
 

docs/context/ref/ChatMessage.md

@@ -10,7 +10,7 @@ A context representing a chat message. Typically used to send the message or to
 
 ## Schema
 
-<https://fdc3.finos.org/schemas/next/context/chatMessage.schema.json> ([github](https://github.com/finos/FDC3/tree/main/schemas/context/chatMessage.schema.json))
+[https://fdc3.finos.org/schemas/next/context/chatMessage.schema.json](https://fdc3.finos.org/schemas/next/context/chatMessage.schema.json) ([github](https://github.com/finos/FDC3/tree/main/schemas/context/chatMessage.schema.json))
 
 ## Type