Add vendor-agnostic properties to the AppD application definition format for launching native apps

[kriswest]

Enhancement Request

Add vendor-agnostic properties to the AppD application definition format for launching native apps

FDC3 and the AppD are expected to support native and hybrid applications in addition to web apps. However, the appD app definition format currently requires a hostManifest (in an unstandardized, vendor-specific format) in order to support launching of native applications.

Since the merge of PR #437, the appD's application definition format includes a vendor agnostic details.url property that can be used to launch web applications. Consider the addition of further sub-properties of details that will support vendor-agnostic launching of native applications.

Use Case:

Vendors of native apps, and in-house native app development teams may wish to publish details of their apps for inclusion in app directories. Despite the fact that native apps may not be launchable without installation, there are several use-cases for inclusion in an appD:

• Providing configuration to customers that have installed the applications and wish to use them with FDC3 (i.e. to save the customer figuring an optimised configuration themselves).
• Native apps that do support launch without installation (e.g ClickOnce apps).
• In-house developed native apps that are already deployed.
• Supporting discovery of apps that could be installed to work with FDC3