[ebxml-iic] Comments on Test Framework prior to vote

[Michael Kass <michael.kass@nist.gov>]

Title: minutes, and vote reminder

Jacques and all,

 

   I didn't see my previous message make it to the IIC reflector, so I am sending it again: Basically, the only issue I have is with the "Notification Message"

format.. which is not specified ( see line 568 of Test Framework 1.0 Specification ).  

 

Suggested Changes to Test Framework 1.0 Specification

 

Line#            Description                                                                                                                  

86                Change name of schema to “Service Related Message Schema”

172              Added references to Appendices D, E,F and G

188      All Glossary terms are supposed to be Italicized.. but they are not

235            Suggest removing any references to ebXML MS specs.. not generic

301      application code needs to be written?  Is this true?

336      Change spelling of  [ConfCertTestFrmk] reference

424      Change “PersistentMessage.xsd” to “MessageStore.xsd”

455            What does “bt” mean?

457      What does “bt” mean?

524      Does a Test Service name really need to be specified?  Can’t this be configurable?

568      Spec does not say what notification messages look like to the Test Driver for “Remote Operating Mode” .

598       ResponseURL – Don’t feel this is needed for local Test Driver ( scripted )  Configuration, is only applicable to remote configuration, so we should say so

599       NotificationURL – Don’t feel this is needed for local Test Driver ( scripted )  Configuration, is only applicable to remote configuration, so we should say so

625       The Action field is NOT irrelevant ( i.e. for Notifications .. or for message verification)

666       The word “somehow” sounds unsure/inclusive.. suggest removing it

669       Are we going to capitalize all Action names to remain consistent?

2053          Changed Message Store schema so that serviceInstanceId  is an optional attribute ( not available from Remote notifications)

2102     Change “Message Store should” to “Service-Specific Messages” MUST

4491          Change to “Test Service Message Schema” to “Service-Specific Message Schema”

 

Modified Appendices C and D to reflect changes in spec

 

 

NOTES***

 

Must specify what “Remote Reporting Mode” messages look like.  On option is to have the messages sent to the “ReportingURL” of the “hub” Test Driver.  But in that case.. Test Driver

“serviceInstanceID” is unknown…Test Driver serviceInstanceId should be “optional”... there is no way of  knowing if we are dealing with a remotely received message notification..  Also, no way of knowing if a remote notification is synchronous or asynchronous.

 

Normative schemas need real schemaLocations that match their namespaces ( i.e. on the OASIS web site)

 

----- Original Message -----

From: Jacques Durand

To: 'ebxml-iic@lists.oasis-open.org'

Sent: Friday, February 28, 2003 10:59 PM

Subject: [ebxml-iic] minutes, and vote reminder

All:

Minutes attached.

Remember that Monday 3rd we have our call (see previous mail), and
the email vote on Deployment Template and TestFramework end Monday evening 8pm.
(eligible voters, send me an email saying YES (approve), NO, or ABSTAIN for each of these specs.
They have been sent out on Wednesday.)

Regards,

Jacques

<<IIC_Feb_24_03_minutes.txt>>