[mashup-dev] Web Service Mashup Server positioning and buzz.

[Paul Fremantle]

I think having the mashup posting site is going to be key. I think we 
should think clearly about how we make this seem "independent" and 
"open". In other words, what standards do we publish around the APIs and 
how do we encourage people to know they are posting their mashups to an 
open site.

So for example we could register open-mashup.org (which is available) 
and brand it as an open site (sponsored or hosted by WSO2).

I know this isn't exactly the branding direction we've taken so far, but 
I personally am not sure how interested I'd be in posting my mashup to a 
"vendor" website.

Paul

BTW Sun's John Crupi has registered openmashups.org





James Clark wrote:
>>> If I've understood our approach to mashups, a strength is it's recursive
>>> nature: whenever you create a mashup, it in turn becomes something that
>>> can be mashed.  Do other approaches have that?  If not, I think that
>>> could be a very killer feature in terms of driving the number of mashups
>>> out there (which is one of the keys to success).
>> +1. This is, in effect, achieved by separating the UI from the mashup. 
>> However, putting it in terms of "if you do it our way your mashup can be 
>> mashed up by others too" would be a much better sell than saying "content 
>> and style separation" ;).
> 
> The other point about this is that it enables us to create a
> self-reinforcing dynamic for adoption.  I think that is one of the keys
> to getting really widespread adoption.
> 
> James
> 
> 
> _______________________________________________
> Mashup-dev mailing list
> Mashup-dev at wso2.org
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
> 

-- 
Paul Fremantle
VP/Technology and Partnerships, WSO2
OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
paul at wso2.com
(646) 290 8050

"Oxygenating the Web Service Platform", www.wso2.com