Date: 2017-08-31 Chair: Anish Karmarkar Scribe: Anish Karmarkar Attendees: Oracle Anish Karmarkar Chair Oracle Gil Pilz Voting Member Oracle Martin Chapman Voting Member Outstanding AIs: Anish & Gil to update spec + metadata zip file Agenda: 1) Roll and minute taker appointment 2) Agenda bashing 3) Approval of 2017-08-24 minutes https://www.oasis-open.org/committees/document.php?document_id=61486&wg_abbrev=camp 4) AI review Martin to generate a proposal for CAMP-232 5) Implementation status update, JPMC OSS update 6) New issues https://issues.oasis-open.org/browse/CAMP-223?jql=project%20%3D%20CAMP%20AND%20status%20%3D%20New%20ORDER%20BY%20created%20DESC%2C%20priority%20DESC 223: suggest closing this as not an issue 230: suggest opening and resolving this w/ proposal in JIRA 224: suggest closing this as not an issue. 227: suggest opening and resolving this w/ proposal in JIRA 228: ?? 238: suggest opening and resolving this w/ proposal in JIRA 232: suggest opening and resolving this w/ proposal in JIRA (Martin) 225: suggest opening and resolving this w/ proposal in JIRA 7) Open issues https://issues.oasis-open.org/browse/CAMP-218?jql=project%20%3D%20CAMP%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC 222: suggest opening and resolving this w/ proposal in JIRA 8) Updating json metadata zip file 9) Straggler roll & AOB Topic: Roll quorate Topic: Agenda bashing agenda approved as posted Topic: Approval of minutes approval postponed till next call Topic: AI reivew All AIs done Topic: Issue 223 MOTION: m:Gil s:Martin to close issue 223 as not a bug, this was done intentionally to wait for best practices to emerge no disccussion motion approved u/n Topic: Issue 230 MOTION: m:Martin s:Gil to open and resolve issue 230 w/ proposal in JIRA to delete the phrase "As discussed previously' no discussion motion approved u/n Topic: issue 224 MOTION: m:Gil s:Martin to close issue 224 as not a bug, this was done intentionally as URI specific comparison is not relevant here in the sort no dicussion motion approved u/n Topic: Issue 227 MOTION: m:Martin s:Gil to open and resolve issue 227 w/ comment in JIRA(original text "Based on the binary comparison of the Unicode characters in the String." proposed resolution: replace text with "Based on unicode collation algorithm [ref]" ref is: http://www.unicode.org/reports/tr10/tr10-36.html no discussion motion approved u/n Topic: 228 Replace "characteristics: CharacteristicSpecification[] ?" with "characteristics: CharacteristicSpecification[]" in 4.3.6 MOTION: m:Gil s:Martin to open and resolve 228 by replacing "characteristics: CharacteristicSpecification[] ?" with "characteristics: CharacteristicSpecification[]" in 4.3.6 (fixing pseudo schema to align with text) no discussion motion approved u/n Topic: issue 238 MOTION: m:Martin s:Gil to open and resolve issue 238 w/ comment in JIRA (add quotes around type) no discussion motion approved u/n Topic: issue 232 MOTION: m:Martin s:Gil to open and resolve issue 232 with proposal from Martin in Jira no discussion motion approved u/n Topic: Issue 225 original text: "Note that the information presented in pseudo-schema is intended as a condensed guide and is subordinate to the textual descriptions of the nodes and objects that appear in those descriptions." fixed text: "Note that the information presented in pseudo-schema is not normative and is intended as a condensed guide for ease of understanding by the reader." MOTION: m:Gil s:Martin to open and resolve issue 225 by replacing the original text "Note that the information presented in pseudo-schema is intended as a condensed guide and is subordinate to the textual descriptions of the nodes and objects that appear in those descriptions." with "Note that the information presented in pseudo-schema is not normative and is intended as a condensed guide for ease of understanding by the reader." no discussion motion approved u/n Topic: issue 222 Replace: "The PDP (and the Plan file, see Section 4.2, Plan Overview) defines the formats for on-boarding new applications onto a CAMP-enabled Provider." With: "The Platform Deployment Package (PDP), and the Plan file (see Section 4.2, "Plan Overview") ensures portability across platforms. It can be created by a platform to export to another platform, which then imports it. It can also be created by an Application Development Environment running locally or deployed as Software as a Service in the cloud." gilbert.pilz: It can also be created by an Application Development Environment. "The Platform Deployment Package (PDP), and the Plan file (see Section 4.2, "Plan Overview") ensures portability across platforms. It can be created by a platform to export to another platform, which then imports it. It can also be created by an Application Development Environment." gilbert.pilz: It can also be created by an Application Development Environment or other tools such as Maven. "The Platform Deployment Package (PDP), and the Plan file (see Section 4.2, "Plan Overview") ensures portability across platforms. It can be created by a platform to export to another platform, which then imports it. It can also be created by an Application Development Environment and other tools." MOTION: m:Martin s:Gil to resolve issue 222 by replacing "The PDP (and the Plan file, see Section 4.2, Plan Overview) defines the formats for on-boarding new applications onto a CAMP-enabled Provider." with "The Platform Deployment Package (PDP), and the Plan file (see Section 4.2, "Plan Overview") ensures portability across platforms. It can be created by a platform to export to another platform, which then imports it. It can also be created by an Application Development Environment and other tools." no discussion motion approved u/n Topic: future calls All issues resolved; waiting for spec and metadata zip file to be updated. ACTION: Anish & Gil to update spec + metadata zip file NO calls till we have updated artifacts Next call is 21st Sept. 7th and 14th sept calls are canceled Meeting Adjourned