[wsas-java-dev] Re: [esb-java-dev] Product Names

[Chatra Nakkawita]

I'm sorry but I don't think this will work. -1 from me. We have to be
clear to the user on what implementation we are talking about, let it be
a project home page, downloads page, tutorial, article etc

I think the same theory on this mail applies to WSO2 products with
multiple implementations . See
https://www-lk.wso2.com/mailarchive/oxygentank/2007-February/001391.html

If we are having multiple implementations then we have to give equal
status to all the implementations. IMO we need ti figure out now how we
are going to call ESB Java implementation and ESB C implementation.
These two will stand side by side, and the distinguishing factor will be
the implementation language. How we are going to name multiple
implementations of the same product will be a good topic for Jim and the
business dev team to deal with as well. I think we can get some good
feedback from Jim on this if we put this up to him at the upcoming
meetings.

Ok...don't get mad for quoting this- "Codehaus XFire is a
next-generation java SOAP framework", so in this case we know when you
say "Codehaus XFire" we know it is a Java framework and nothing else. If
WSAS is not going to have any other implementations, then we can do the
same with it. But it's important we mention the implementation eg.,
'WSO2 WSAS is an integrated Java Web services Platform' or something
like that. So by default if you refer to WSAS you know it's Java

What do you think?

Thanks,
Chatra




Afkham Azeez wrote:

>Sanjiva Weerawarana wrote:
>  
>
>>+1 from me too. So how about:
>>
>>WSAS
>>ESB
>>WSF/Java etc.
>>
>>When we do a C impl of ESB, we'll figure out what to call it .. maybe
>>"ESB, C Edition".
>>    
>>
>
>++1
>
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Esb-java-dev mailing list
>Esb-java-dev at wso2.org
>http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
>  
>