[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes / Actions from 18 Jun Editors' SC Call
Minutes / Actions from 18 Jun Editors’ SC Call In attendance: Krasimir; Dieter; Ralf; Ivana; Luc Find below my notes from Wed’s call. Please review. Thanks Luc Luc Clément Active
Endpoints, Inc +1.978.793.2162
| luc.clement@activevos.com Note to Dave Ings: please see comment below regarding
BP-16/17 Note to Vinkesh: please note that your check-in of BP
1, 3 and 7 did not take place – Ivana will be contacting you on this once
she completes her work to coordinate getting these re-introduced in the specs On Wed we allocated work on resolved items as follows in no
specific order. I’ve updated Jira accordingly (http://www.osoa.org/jira/secure/BrowseProject.jspa). Dieter ·
BP-22 Make
b4p:peopleAssignments optional Dieter
Koenig ·
BP-21 Precedence
of spec vs schema files Dieter
Koenig ·
BP-13 Merge
ws-humantask-context.xsd and ws-humantask-protocol.xsd into a single file Dieter
Koenig ·
BP-2 Defer
Activation Time is missing from HT protocol message Dieter
Koenig Krasimir ·
BP-18 Task
Priority is underspecified Krasimir Nedkov Ralf ·
BP-17 Define
Conformance Targets Ralf Mueller ·
BP-11 Initialization
of process generic human roles in b4p Ralf
Mueller Luc ·
BP-10 More
control needed for the propagation of attachments Luc
Clement Ivana ·
BP-9 ht:getTaskID()
is not defined Ivana Trickovic ·
BP-8 Are
string literals required for part, task, and LPG name in HT functions? Ivana
Trickovic ·
BP-5 Discrepancy
between spec and schema regarding LPG attribute Ivana
Trickovic ·
BP-4 Declaration
of imported LPG not mentioned in B4P spec Ivana
Trickovic Vinkesh (Also note that status
was prematurely marked as “Applied”) ·
BP-7 addAttachment API call is missing the
content type param Vinkesh Mehta ·
BP-3 Syntax for LPG in B4P spec missing
reference attribute Vinkesh Mehta ·
BP-1 Remove fault name from getFault HT API call
Vinkesh Mehta Status / Next steps 1.
Ivana will be doing a check-in shortly and coordinate
with Vinkesh to retrofit the work on items 1, 3, and 7. 2.
Dieter has the pen next 3.
We’ll coordinate over email the assignment of the
next editor Comments to Editors ·
Reminder: We agreed to update the “Revision
History” appendix providing a summary of changes when a change is applied Conformance Targets (BP-17) and RFC2119 Compliancy (BP-16) ·
We will start working through BP-17 on 2 July
during the regularly scheduled SC mtg ·
On the 25 Jun TC call the SC will propose to the
TC that it approve as “Resolved” BP-16 so that the Editors’
can take a first cut at changing the spec text. ·
Work on BP-16 and perhaps BP-17 (depending on
the result of our 2 July mtg) will start once we’ve submitted a version
of the specs to the TC for review of changes “Applied” to the spec.
This will be distributed to the TC as a marked up Word document. We then plan
to devote a review cycle to BP-16 and 17. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]