[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes: April 4th 2005
Roll Call: The meeting was quorate
Doug raised a procedural question regarding the ballots that had taken place.
Discussion covered lack of attendance, whether the votes were quorate, whether
missing the votes counted against the member and, if so, whether they counted
as one or two missed votes given that they started and finished on the same day.
A number of members had missed the votes as the notifications and votes had taken
place during a holiday period.
(http://www.oasis-open.org/committees/process.php#participation)
ACTION: Martin to check situation with Jamie.
Minutes from last meeting:
Motion to accept: Mark
Second: Tony
No discussion, no objections, approved.
Action Items:
Greg and Doug: solution to must understand
Doug: Sent views to Greg but has heard nothing back so far.
SUB-ACTION: Doug to send his views to the list.
Review of editorial draft:
Martin: Query regarding status of actions assigned to editors
Mark: All actions closed at the last f2f have been incorporated along with
a few recent editorial actions.
The latest document was sent to the mailing list 4th April and includes
change bars.
There are currently 11 outstanding actions with CF, all assigned or in
holding pattern.
ACTION: Mark to identify all action items closed by latest draft.
Martin: How many people have read the current draft?
Tony: skimmed it and seems to be heading in the right direction.
Open Issues: Context (15 open)
168 Activity Hierarchy
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=168
This has been agreed in principal that it is a graph and has been updated
in the text. Waiting on updated WSDL & Schema.
209 unknown-context-fault/context-identifier
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=209
Waiting on updated WSDL & Schema.
214 Correlation ID in AssertionType should be removed
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=214
Waiting on updated WSDL & Schema.
218 Remove AssertionType and AssertionWithProtocolURIType
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=218
Waiting on updated WSDL & Schema.
223 Consistency of specification approach
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=223
Martin: There are a number of issues relating to consistency of
style, should we be grouping them?
Down to the editors.
ACTION: Tony to reproduce table for current version of CF.
234 refresh context
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=234
In progress. Mark previously sent text to the mailing list to
start discussion on this issue.
235 Inaccurate text between Figures 1 and 2
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=235
Assigned to Greg.
236 Context and SOAP attributes
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=236
Greg and Doug are dealing with this issue.
238 add transient fault message
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=238
Mark: adding a transient fault message is easy but what is our
fault model?
ACTION: Resolve fault architecture issue.
241 mustUnderstand clarification (Anish 18)
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=241
This is related to 236. Will be clear once the mustUnderstand
usage has been specified.
243 timeout value (Anish 22)
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=243
Ballot Item.
244 mustUndersand query (Anish 27)
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=244
Related to mustUnderstand.
246 possible incorrect use of mustUnderstand (Anish 32)
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=246
Related to mustUnderstand.
247 lack of namespace (Anish 44)
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=247
Ballot Item.
249 fault queries (Anish 49)
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=249
b) is related to the fault architecture.
d) should be raised as a separate issue.
ACTION: Separate d) in 294 into its own issue.
Open Issues: Coordination Framework (10 open)
165 Protocol requirements
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=165
Editorial.
187 Wsdl, request/reply, fields
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=187
Editorial.
Mark: There is no point addressing these until the documentation
is closer to being finalised.
Martin: Would it not be better to start with a template? Can you
propose a template for wsdl/operations?
Mark: Yes, it can be done. All proposals welcome.
ACTION: Editors to propose template.
191 Type of status
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=191
Mark: Tony believes this can be closed.
192 Coordinator-reference
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=192
Waiting for an updated schema.
201 Beginning and ending of coordinated activity
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=201
Mark: In hand.
208 Conformance to this Coordination Framework specification
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=208
Martin: We should action someone to come up with a conformance statement.
211 Clarification in error propagation text
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=211
Relates to fault architecture.
215 Add diagrams showing the CAF architecture
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=215
Martin: Do we have a diagram?
Mark: Not for CF.
Tony: We should put architectural diagram into CF document or into primer.
Martin: We should have the diagram in the primer and copies in the other
specifications with the non relevant parts greyed out.
ACTION: Editors to come up with a diagram.
216 Add tables giving message parameters and types
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=216
Consistency of style, related to template.
217 Add message sequencing specification
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=217
Editorial.
Martin: There are four main areas that still need to be addressed.
mustUnderstand attribute
Fault architecture
Consistency of style
Conformance statement for Coordination Framework
Discussion of votes
243: 2/1/0 (Yes/No/Abstain)
247: 3/0/0 (Yes/No/Abstain)
Discussion of 243:
Martin: Neither votes were quorate and they need to be run again. We should
understand why 243 had one vote against before rerunning the vote.
Doug: Voted against 243 as proposed solution has the same name but with
different semantics. Other areas that use timeout specify seconds.
It would be acceptable if it was renamed.
Motion: Mark
With reference to http://www.w3.org/TR/xmlschema-2/#isoformats, the proposal is:
Timeout in context is renamed to expiresAt and the value is dateTime specified in UTC.
Second: Doug
No discussion, no objections, adopted.
ACTION: Mark/Doug To raise issues associated with Doug's comments.
Pete: Comments made by Doug are not visible
Martin: Will make sure all future ballots are always visible.
Discussion of 247:
Mark: Original format came from Fujitsu's submission.
Motion: Mark
With reference to http://www.w3.org/TR/xmlschema-2/#QName, the proposal is:
Make status a QName.
Second: Kevin
Tony: What is the disadvantage of the namespace attribute and making it required?
Mark: We would be reinventing QNames. Makes more sense to adopt what already exists.
Tony: It would be good to incorporate an example int he primer.
Mark: An issue should be raised against the primer.
No objections, adopted.
Martin: Will we get another version of the document before the f2f?
Mark: There will be another version of Context. Not sure about CF as
there are a number of issues to be resolved.
Martin: We could do with a new version of context but not CF.
Mark: Context should be out end of this week, beginning of next.
Discussion of f2f and who is attending.
Currently not attending:
Tony, Doug, John, Kevin
Doug can dial in for part.
Actions from the meeting
ACTION: Martin to check situation with Jamie.
SUB-ACTION: Doug to send his views to the list.
ACTION: Mark to identify all action items closed by latest draft.
ACTION: Tony to reproduce table for current version of CF.
ACTION: Resolve fault architecture issue.
ACTION: Separate d) in 294 into its own issue.
ACTION: Editors to propose template.
ACTION: Editors to come up with a diagram.
ACTION: Mark/Doug To raise issues associated with Doug's comments.
--
Kevin Conner
Arjuna Technologies Ltd.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]