Hi Alan,

Yes, you are correct – the info in WS-* workshop invitations are public, so they are definitely quotable in your article.

If you wish to point to an online reference, this info is posted on MSDN for public consumption:

http://msdn.microsoft.com/webservices/community/workshops/composability042005.aspx

I realize you probably know this already, but just to repeat for the record, the following is public data:

            - Contents of workshop invitations

            - A general summary of workshop meetings

- Which companies participated in each workshop meeting

Pretty much the only thing that you can’t quote publicly is the _specific_ results of individual companies.
The reason is simply that we want to have an environment that respects that companies may bring pre-release code to these workshops, so their results at that time may not necessarily bear any relation to the code they eventually ship to market.

Also, should you wish to provide some background links in your article about the WS-* Workshop process, there’s an article on MSDN with an Overview of the WS-* Workshop Process which you are welcome to link to.

http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnwebsrv/html/wkshopprocess.asp

Let me know if you need any additional info, or if you would like an extra pair of eyes to review your article before submission.

Best regards,

Jorgen

I am writing an article on the interop testing of two sets of specs:
1] WS-RM'g and WS Secure Conversation
2] WS-Reliability and WS Security

Are there any problems with publishing the following (this is taken
from the workshop announcement mail sent by Jurgen):

BEA Systems Inc, International Business Machines, Microsoft
Corporation and TIBCO Software Inc., co-developers of the WS-Reliable
Messaging specification, are hosting a two day Composability Interop
Workshop on April 13 and 14, 2005 at Microsoft's Silicon Valley
Campus in Mountain View.  The two day interop workshop is an ad-hoc,
open forum for companies who have WS-Reliable Messaging and WS-Secure
Conversation  implementations, and who want to test their
implementations with other companies' implementations. Attendees
bring their own laptops, their implementations and any other tools
they feel would be needed; testing among all attendees will occur
throughout the day.  As with previous WS-* workshops, these events
are open to anyone who desires to participate and who can bring an
implementation based on the specifications listed above.
A revised test scenario document for use in the Interop Workshop was
recently made available to interop participants.
Footnote:
1.   Web Services Secure Conversation Language (WS-
SecureConversation):
This specification defines extensions that build on [WS-Security] and
[WS-Trust] to provide secure communication across one or more
messages. Specifically, this specification defines mechanisms for
establishing and sharing security contexts, and deriving keys from
established security contexts (or any shared secret).

If not, I will include the above in the article, which I will submit
to gridtoday.com and web services pipelines (where I have previously
published.

Thanks

alan Weissberger