Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

App Directory Discussion group - Monday 16th May 2022 #718

Closed
15 of 26 tasks
kriswest opened this issue May 16, 2022 · 12 comments
Closed
15 of 26 tasks

App Directory Discussion group - Monday 16th May 2022 #718

kriswest opened this issue May 16, 2022 · 12 comments
Labels
app-directory help wanted Extra attention is needed indexed When a meeting attendance is being tracked meeting

Comments

@kriswest
Copy link
Contributor

kriswest commented May 16, 2022 •
edited
Loading

Group overview

Discussion group to develop proposals for the improvement of the App Directory as part of the FDC3 standard. The group will examine the role/value/necessity of the AppD as part of the FDC3 specification and a compliance requirement for use of the FDC3 API, in addition to working on proposals to improve the description and functionality of the App Directory.

Relevant tags

Current open issues and PRs that relate to the above concepts with the label:
image

A github discussion is also available for this group (may be used to arrange meetings, agenda ask questions etc.)

Meeting Date

Thursday 16 May 2022 - 9am EST / 2pm GMT

WebEx info

More ways to join

  • Join by video system:
  • Join by phone
    • +1-415-655-0003 US Toll
    • +44-20319-88141 UK Toll
  • Access code: 2551 735 2618

Meeting notices

  • FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

  • All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

  • FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

  • FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

  • A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard. As such, participation in a Discussion group is not required for contributing to any particular issue or FDC 2.0 as a whole.

Agenda

Minutes

  • An overview of the consolidated PR so far was provided by @kriswest: AppD consolidated update PR #668
  • A reminder of the timeline for FDC3 2.0 was requested:
    • PRs to be presented to SWG by next meeting (Thurs 26th May)
    • Vote on adoption of 2.0 draft at the subsequent meeting (Thurs 23rd June).
  • 562 AppD vendor agnostic native apps #671
    • The proposed changes were discussed (including the surprising lack of a launch url field in the existing standard versions) and it was agreed that the approach (type, details and hostManifest fields) is reasonable.
      • A question was raised regarding whether the keys for the hostManifest field need to be standardized
        • @nkolba pointed out that you might need to vary these for different versions of desktop agents (e.g. because they support different FDC3 versions)
        • @kriswest It should probably be the responsibility of individual vendors to document what strings they look for, rather than the Standard. However, we can update the example provided (on request) to show it is for a particular product.
    • (silent) consensus was sought and received to merge the PR into the consolidated appD update PR
  • 566 remove appd create application endpoint #695
    • It was commented by several participants that administration systems for appD's will vary and there is no real need to standardize how they do that nor require that the expose this endpoint
    • Removing the endpoint from the standard does not prevent an implementation from using it
      • Add a comment to the appD spec that makes it clear that implementations MAY extend the standard endpoints
    • (silent) consensus was sought and received to merge the PR into the consolidated appD update PR
  • 370 remove appD search application endpoint #696
    • @kriswest review some of the discussion on the topic of improving the search endpoint that resulted in a PR to remove it
    • see Improve the AppD's search function and documentation #370
      • Current API makes it hard to implement a fairly standard keyword search or browse/filter by category
      • Combining results from different appD's would require a far more detailed specification of result weighting
        • The only way to do it well is to retrieve all the entries and implement the search and any necessary filtering client-side
      • There is one current use-case: to perform intent resolution for a Desktop Agent - however several participants commented that this was inefficient and is/would be better handled client-side
      • removing the endpoint from the standard does not prevent an implementation from using it (for example to support a built-in UI) - but does ensure that Desktop Agent implementations or UIs for browsing App Directories won't rely on it
    • (silent) consensus was sought and received to merge the PR into the consolidated appD update PR
  • 247 appd use of interop #697
    • @nkolba expressed a preference for dropping the interopUse element and moving the contents up to the top-level as siblings of the existing intents element
    • @nkolba queried the purpose of the raisesContexts element, @kriswest clarified that it was to represent contexts that raiseIntentForContext is called with and that other ways to handled it were to standardize a 'magic string' to represent any context type, or to rename the element using the API call (i.e. change the elements toraiseIntent and raiseIntentForContext)
    • The discussion was curtailed by the end of the meeting, it was resolved to continue the discussion on the issue.
    • @kriswest to update PR with suggested changes

Action Items

Untracked attendees

Full name Affiliation GitHub username
@kriswest kriswest added help wanted Extra attention is needed app-directory meeting labels May 16, 2022
@robmoffat
Copy link
Member

Rob / FINOS

@kriswest
Copy link
Contributor Author

Kris / Cosaic 🚀

@tpina
Copy link
Contributor

tpina commented May 16, 2022

Tiago Pina / Cosaic

@nkolba
Copy link
Contributor

nkolba commented May 16, 2022

Nick Kolba

@sarahaislinnstone
Copy link

Sarah Stone / Cosaic

@Qiana-Citi
Copy link

Qiana / Citi

@chedzoir
Copy link

Malcolm Chedzoy / Citi

@nicopreto
Copy link

Nico Pretorius / Scott Logic

@dimiter-georgiev
Copy link

Dimiter / Symphony

@kriswest
Copy link
Contributor Author

Minutes have been posted and a preview of the consolidated PR is now available at here

Please provide any further feedback on the draft proposal and add your review at:

@kriswest kriswest mentioned this issue May 16, 2022
Closed
@robmoffat
Copy link
Member

can I close this now?

@kriswest
Copy link
Contributor Author

can I close this now?

Usually not closed until next meeting. I will however go and close the last meeting, thanks for reminding me!

@github-actions github-actions bot added the indexed When a meeting attendance is being tracked label Jul 28, 2022
@kriswest kriswest mentioned this issue Jul 28, 2022
Closed
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
app-directory help wanted Extra attention is needed indexed When a meeting attendance is being tracked meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@robmoffat @nkolba @kriswest @tpina @chedzoir @dimiter-georgiev @sarahaislinnstone @Qiana-Citi @nicopreto