Align AppMetadata and IntentMetadata with other FDC3 specifications

[rikoe]

The AppMetadata and IntentMetadata returned by findIntent and findIntentsByContext should be aligned with the App Directory Specification and Intents Specification, respectively.

[ColinEberhardt]

Currently it looks like the App Directory working group are defining HTTP REST APIs rather than TypeScript:

https://github.com/FDC3/appd-api/blob/master/specification/appd.yaml

[rikoe]

Current AppMetadata object:

interface AppMetadata {
  name: string;
}

Current App Directory specification (example):

{
  "appId": "string",
  "name": "string",
  "manifest": "string",
  "manifestType": "string",
  "version": "string",
  "title": "string",
  "tooltip": "string",
  "description": "string",
  "images": [
    {
      "url": "string"
    }
  ],
  "contactEmail": "string",
  "supportEmail": "string",
  "publisher": "string",
  "icons": [
    {
      "icon": "string"
    }
  ],
  "customConfig": [
    {
      "name": "string",
      "value": "string"
    }
  ],
  "intents": [
    {
      "name": "string",
      "displayName": "string",
      "contexts": [
        "string"
      ],
      "customConfig": {}
    }
  ]
}

Current App Directory specification (definition):

components:
  schemas:
    Application:
      required:
        - appId
        - name
        - manifest
        - manifestType
      properties:
        appId:
          type: string
        name:
          type: string
        manifest:
          type: string
        manifestType:
          type: string
        version:
          type: string
        title:
          type: string
        tooltip:
          type: string
        description:
          type: string
        images:
          type: array
          items:
            $ref: '#/components/schemas/AppImage'
        contactEmail:
          type: string
        supportEmail:
          type: string
        publisher:
          type: string
        icons:
          type: array
          items:
            $ref: '#/components/schemas/Icon'
        customConfig:
          type: array
          items:
            $ref: '#/components/schemas/NameValuePair'
        intents:
          type: array
          items:
            $ref: '#/components/schemas/Intent'

[rikoe]

Current IntentMetadata object:

interface IntentMetadata {
  name: string;
  displayName: string;
}

Current Intent specification (see https://github.com/FDC3/FDC3/tree/master/src/intents):

interface Intent {
    name:string;
    displayName? : string;
    contexts?: string[]
    customConfig?: Object; 
}

[nkolba]

The "contexts" field on the Intent interface for AppD is to provide metadata for routing intents for that specific App for the provided context. I.e. the app may fulfill the ViewNews intent if an instrument context is provided - but not for a contact context.