Again as someone already mentioned the naming of wave wasn't exactly ideal. Almost all of the google products I can think of give clue of what it is about in the name. Chrome and Wave and exceptions, although you could say the "chrome" alludes somewhat to the nature of the product, especially at the time is was released. Also there is a track record about naming browsers that is somewhat different to other products.
FedOne, whilst not perfect is certainly in the ball park. I think it certainly should have "federated" in there. That is an important thing to mention. It is probably going to end up as an initialism of some sort. I think that is most appropriate for the audience, who should be using it eventually for their own services and brand appropriately. >From a developer point of view we know the technology as wave, but you also need to encourage developers not to use a obscure subcultures in naming for future wave products. I say lead by example. I think if "wave" is going to be in there at all it should be something like "wave like", e.g. Wave Like Federated Sever. Live Collaborative Federated Server (LCFS), etc. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
