F2F Meeting Minutes Sept 13 PM (2nd Half)

[David Snelling <David.Snelling@UK.Fujitsu.com>]

Folks,

Review of progress so far:

Need to finish BaseN and Brokered Open Issues.

Things still to do:

All details are in Issues list for - 4.2, "Pending changes", AI132, 
2.57-61.

[Peter is fighting with kavi again.]

2.57 - is OK.
2.58 - is OK.
2.59 is to be done from the minutes.
2.60 - is OK.
2.61 - is OK.

Next Steps:

    1) Editors finish work: Everything except 2.58 by Sept 13, 2005
    2) Editors to finish: 2.58 ASAP Sept 13, 2005 (later in the day)
    3) Verification done: Sept 23, 2005
    4) Call for PR2 ballot of call: Sept 26, 2005

Brokered Notification:

Issue 3.23: Destroy operation name to DestroyRegistration - is OK

Issue 3.24: Identifying a registered publisher - Make second EPR 
(Notification Consumer) required.
             Action Peter: Update the issues list
             Editor is then OK.

Issue 3.25: Use of Resource access pattern - Check through the list on 
the call. Use the same pattern as before on lines 609 and 535.
             Action Peter: To update Issues list
             Editor is ok

Issue 3.26: Editor is OK.

Issue 3.27: Interim version of WS-A namespace and Reference 
"Properties" to "Parameters" (line 505) - Editor - OK.

Issue 3.28: Inconsistent approach to PP optimality - see minutes from 
earlier today.
             Some details: Remove 342, 345, 410-413, 417-420.
                           The schema change is to remove the fault at 
984 - 990.
                           The WSDL change is to remove the PullPoint 
operations from the NotificationBroker PT (1242-153).
             Action Peter : Update Issue list accordingly.
             Editor is OK.

Next Steps:

    1) Update Issues list: Sept 13, 2005.
    2) Editors to finish: ASAP Sept 13, 2005 (later in the day)
    3) Verification done: Sept 23, 2005
    4) Call for PR2 ballot of call: Sept 26, 2005

General Policy Discussion:

Policies have two flavors: Part of the architecture (useRaw) and 
deployment policies (durableSubscription). Defining both types of 
policy can be independent of their advertisement. Requesting a given 
policy is by operation parameter as Subscribe. We could restrict the 
policy types we talk about to those policies that can appear in the 
policy parameter of subscribe.

New Issue: Number 2.62
Three problems: 1) Implies that NP must support both Notify and useRaw.
                 2) UseRaw is idempotent so one of the faults makes no 
sense.
                 3) Need a generic policy rejected fault.

            Fix text surrounding useRaw (line 689). Remove 627-628, 
688-689, and corresponding schema and WSDL.
            288-290 clean text to imply that if useRaw (or not) is 
accepted, then messages MUST be sent as requested.
            Add a UusupportedUseRawFault fault.
            Add a PolicyRejectedFault fault, with a "service MAY throw 
this fault" semantic.

Open issue still to discuss is 1). Options are Support Both, either, or 
Notify plus optionally raw.

Tomorrow: We do WS-Topics and verify starting at 11:30 with people on 
the phone.

-- 

Take care:

     Dr. David Snelling < David . Snelling . UK . Fujitsu . com >
     Fujitsu Laboratories of Europe
     Hayes Park Central
     Hayes End Road
     Hayes, Middlesex  UB4 8FE

     +44-208-606-4649 (Office)
     +44-208-606-4539 (Fax)
     +44-7768-807526  (Mobile)