Andre Schaaff presented progress report on VO-WS-Basic profile

Version 2.1 doc is on wiki



Items from previous meetings.



    WS-I WebService Interoperability

        List of deliverables



    WS-I documents

        Clarifications on how to use the specifications correctly



    VO WebServices Basic Profile

        Introduced in Pune



--



Work to do (from Pune)

    Integrate IVOA specifications

    Take WS-I Attachment Profile into account

    Develop testing tools



Remarks from previous meetings



    Boston InterOp

        WS-I Basic Profile 1.0 final version.

    Pune InterOp

        WS-I Basic Profile had reached 1.1 but testing tools were still at 1.0.

        WS-I Basic Profile - binding and attachment moved to other documents.



    WS-I philosophy, partial conformance is allowed.



--



WS-I Attachment Profile 1.0



    Defines a MIME multipart structure for attachments.

    Means it can't be mandatory if we want to use DIME etc.

    Asked who uses which formats ?



Alasdair Allan :

    DIME is Microsoft specification but not a standard.

    However, it has several implementations including Perl and Java.



Wil O'Mullane :

    New version of .Net hides the underlying format, so could have changed to be MIME, developer does not see the details.



Guy Rixon :

    What is the current IVOA recomendation ?



Wil O'Mullane :

    DIME at the moment



Andre Schaaff :

    Suggest we change it to 'DIME is allowed, but MIME should be the minimum'.

    Problem with recomending DIME is that we may exclude other languages/platforms that do not have support for it.



Guy Rixon :

    Suggest we change it to

        If you use MIME, it must conform to the specification.

        If you use other format, then you must declare what version.



Wil O'Mullane :

    Current WS-I says MIME is minimum.



Andre Schaaff :

    No longer in BasicProfile, has been moved to external recommendation.



Guy Rixon :

    Suggested

        Not to make it mandatory yet.

        Use of MIME is optional at this stage.



----



Proposal



Publish a suite of profiles



    VO WS BasicProfile - Core document

    plus

    Extensions

        Other IVOA recommendations

        WS-I Simple SOAP Binding

        WS-I Attachment Profile



A VO service can claim (in VOService registry entry)

    Conformance to core document

    plus

    Additional extensions implemented



Note 'Additional extensions' is not in VOService registry schema yet.

Need to work with registry team to get this added.



----



Rules

Suggestion that we adopt a similar format to the WS-I rules.

Brief description of the format for WS-I rules, and the assertions document.



Assertions document used to configure test tools.

    <testAssertion id="WSI1003"

        ....

        <reference profileID="BP1">R1012</reference>

        <reference profileID="BP1">R1018</reference>

    </testAssertion>



Testing tools use this to run tests.

e.g. 

    Rule requires HTTP 1.1

    Test checks for HTTP 1.1

    Test results output to another document.



Test tools act as man-in-middle, checking messages passed between the services.



----



Example rules document



    R0001 an IVOA Web Service MUST be compliant to the WS- I Basic Profile 1. 1

    ....

    R0100 All VO services should implement the "getRegistration" interface.



Note :

General consensus at the meeting to adopt the suggested format for rules and assertions.



----



WS-I Basic Profile 1.1 contains Discovery based on UDDI.

We don't use UDDI, so should we create our own IVOA Discovery Profile based on our Registry ? 



Andre Schaaff :

    Note that WS-I Basic Profile 1.1 does not require UDDI, just constrains how you use it.

    We can skip these tests by commenting out the assertions in the test config doc.



Guy Rixon :

    If not mandatory, just ignore it.



----



Conclusion and roadmap



WS-I recommendations

    Use WS-I BP 1.1 in VO WS Basic Profile

    Include other WS-I recommends later or use as extensions (e.g. attachments).



All :

    Generally accepted.



VO WS Basic Profile

    Rules are ok.

    Assertion format to be defined.

    First testing tools to be provided soon.



Asking for people to experiment first beta release.



Guy Rixon :

    Are people here happy with using this ?



Wil O'Mullane :

    Fine with the proposal, need to see the tools and find the problems before we can comment in more detail.



Andre Schaaff :

    Note that we are not testing 'quality' of the service, just testing conformance.



Noel Winstanley :

    Once we have tested a few services, we should create a HOW-TO document for fixing common failures.



All :

    General consensus on accepting the proposal.



Wil O'Mullane :

    If this can run on any WebService, can we make this automagical in Registry ?

    i.e. Automatically test conformance when a service is registered ?



All :

    Nice idea, but a bit ambitious for now :-)




---559023410-758783491-1116555252=:9455--