Align intent and application definition between schemas

Fixes #19 and #156

Author: rikoe

src/api/interface.ts

@@ -22,7 +22,10 @@ enum ResolveError {
 * Intent descriptor
 */
 interface IntentMetadata {
+  /** The unique name of the intent that can be invoked by the raiseIntent call */
   name: string;
+
+  /** A friendly display name for the intent that should be used to render UI elements */
   displayName: string;
 }
 
@@ -35,10 +38,27 @@ interface AppIntent {
 }
 
 /**
- * App metadata is Desktop Agent specific - but should support a name property.
+ * App definition as provided by the application directory
  */
 interface AppMetadata {
+
+  /** The unique app name that can be used with the open and raiseIntent calls. */
   name: string;
+
+  /** A more user-friendly application title that can be used to render UI elements  */
+  title?: string;
+
+  /**  A tooltip for the application that can be used to render UI elements */
+  tooltip?: string;
+
+  /** A longer, multi-paragraph description for the application that could include markup */
+  description?: string;
+
+  /** A list of icon URLs for the application that can be used to render UI elements */
+  icons?: Array<string>;
+
+  /** A list of image URLs for the application that can be used to render UI elements */
+  images?: Array<string>;
 }
 
 /**

src/intents/Intent.yaml

@@ -22,7 +22,7 @@ Intent:
         type: string
       description: The contexts the intent accepts. This will
         typically be a set of namespaced context types, e.g. 
-        "org.symphony.contact"
+        "fdc3.contact"
     customConfig:
         type: object
         description: Custom configuration for the intent