Motion made to approve minutes by Frank; seconded by Rob. Not dissenting votes cast and minutes approved

The launch of FDC3 1.0 was described. 

• appd-poc now points to right API specification
  
  
• Updated specification to replace company related copyright headers to Apache 2.0.  This was approved and committed this week. 

• A question was asked about how to get support in getting the reference implementation up and running (e.g. appd-poc), esp. if as problems are encountered in getting the reference implementation up and running. 
  • Guidance was to send a note with the technical question to the AppD mailing list or google groups
    
    
• Examples folder has been added (See screen shot):  Should we use this folder for reference implementations? Question for next session. 
  
• Reference implementation will allow different stubs to be generated (e.g., for java, typescript/angular, etc.)
  
  
  • Frank: Raised the question of releasing FDC3 1.0 client bindings and stubs to maven central?  Will be raised to PMC for guidance. 

Frank proposed the following changes to the existing search method in the specification.  The changes are focused on adding optional search parameters that reflect the defined attributes of the Application component/model.  

Questions:

Do we make the parameter values substring search based or exact match? What is the default? Is it optional?

Discussion:

• Agreed we should add a "search_type" to the parameter list (optional) with two required values supported sub/exact.  Substring search will be default if search_type is not provided. Implementers could extend the type values to include other search types (<> version..etc). 
• Action: Frank will add "search_type" to parameters as optional, with default being substring. 

To search on nested Intent attributes, parameters were added that are prefixed with intent_(attribute).  This removes the need to send nested objects to the search API (POST (Application) vs GET (parameters)).    Need more discussion around this.