W3C home > Mailing lists > Public > public-webappstore@w3.org > September 2012

Re: Early Prototype -- Web App Market

From: Scott Wilson <scott.bradley.wilson@gmail.com>
Date: Tue, 18 Sep 2012 10:07:02 +0100
Cc: "public-webappstore@w3.org" <public-webappstore@w3.org>
Message-Id: <3E528FF6-A3B3-4D38-8DC4-82199A7D29A6@gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
On 18 Sep 2012, at 09:58, Melvin Carvalho wrote:

> 
> 
> On 18 September 2012 08:14, Scott Wilson <scott.bradley.wilson@gmail.com> wrote:
> 
> On 17 Sep 2012, at 23:04, Melvin Carvalho wrote:
> 
>> 
>> 
>> On 29 August 2012 09:54, Scott Wilson <scott.bradley.wilson@gmail.com> wrote:
>> On 29 Aug 2012, at 08:30, Melvin Carvalho wrote:
>> 
>>> 
>>> 
>>> On 29 August 2012 08:32, 전종홍 <hollobit@etri.re.kr> wrote:
>>> Hi Melvin Carvalho,  
>>> 
>>>  
>>> 
>>> Web Application Store CG already have been formed in W3C.
>>> 
>>> I think it would be good to discuss together what is the future of open web application store.
>>> 
>>> 
>>> Thanks for the pointer, I joined the list!
>>> 
>>> Look forward to working with you on this. :)
>>> 
>>> As timbl pointed out in this weekend's keynote.  I think a starting point would be that apps need to have a URL, to be "on the Web".  Then we can collate the meta data of compliant apps, then build bridges to apps/widgets that use specific markup.
>> 
>> Welcome Melvin!
>> 
>> We also cover packaged web apps - that is web apps that are portable and can be hosted anywhere and so don't have a canonical URL. Packaged apps contain their own metadata in a manifest file, and a URI for an identifer. 
>> 
>> Thanks for the response.  I've had a bit more time to look at this, now.
>> 
>> Sure, it's possible to have data without a URI, but giving an app a URI elevates it to becoming a first class citizen of the Web.  We can handle both cases, but where it's possible to add a URI it makes life that much easier.  The reason is that you can share the link, bookmark it, search and index it, annotate it, add follow your nose discovery etc.
>>  
>> 
>> However, conceptually its the same thing - for a hosted app, you would probably interrogate the site for the metadata, whereas for a packaged app you read the included manifest when you install it locally. 
>> 
>> As long as the metadata is close enough semantically, you can do a reasonable job of putting both kinds of app in the store (hence the discussions on webapps about making sure the metadata in the Mozilla proposal for hosted app manifests is consistent with W3C packaged web apps (aka Widgets)).
>> 
>> There is also a bit of a grey area I keep coming across, which is apps that are normally considered hosted, such as OpenSocial apps, but don't have a canonical URL as they are also portable and can be rehosted. I've talked about this a bit with some OpenSocial folks - it may be a case of giving these kinds of gadgets a URI identifier, and/or packaging them us as W3C widgets for transport and installation.
>> 
>> I guess an easy start would be to know what kind of semantic market I need in order to start cataloging examples apps, so that I can showcase some of the existing ones we have in the RWW group.  Do we have a minimal list of fields to get started?
> 
> 
> We use W3C Widgets [1] as the starting point for the metadata; it also maps reasonably well onto other formats such as OpenSocial [2]. The data points we actually index in Solr are:
> 
> uri (widget.id in the case of W3C; the URL of gadgets.xml in the case of OpenSocial)
> title
> icon
> description
> license
> author
> 
> The bit we'd most like to see added is screenshots (there was a proposal for this on the list ages ago)
> 
> Thanks this is a great start ... just comparing with Mozilla's spec:
> 
> Fields we collect at submission:
> Name (autopopulated from manifest)
> Icon (autopopulated for apps)
> Summary (autopopulated from manifest)
> Support information
> Description
> URL slug (autopopulated from name)
> Homepage
> Categories
> Screenshots and Videos (videos are new)
> Compatibility (autopopulated for add-ons)
> 
> I guess the screenshot/video is going to be really useful.

I can't remember if screenshot was proposed on native-web-apps  or this list, but its something we can move back up the to-do list. 

> 
> Do you know what options there are for semantic markup?  Ideally I'd like to put some tags in the wordpress blog eg using an RDFa plugin.
> 
> I see in the widget spec they have 
> http://www.w3.org/ns/widgets
> I wonder is there a vocab that can go with this, maybe I should ask the widget guys?

I'm not aware of any, however I don't think anyone would object to using the Widgets NS and properties to create an RDFa or microdata schema.

>  
> 
> 
> [1] http://www.w3.org/TR/widgets/
> [2] http://docs.opensocial.org
> 
>>  
>> 
>> S
>> 
>>>  
>>> 
>>>  
>>> 
>>> Best Regards,
>>> 
>>>  
>>> 
>>> --- Jonathan Jeon
>>> 
>>>  
>>> 
>>> From: Kingsley Idehen [mailto:kidehen@openlinksw.com] 
>>> Sent: Wednesday, August 29, 2012 8:14 AM
>>> To: public-rww@w3.org
>>> Subject: Re: Early Prototype -- Web App Market
>>> 
>>>  
>>> 
>>> On 8/28/12 3:26 PM, Melvin Carvalho wrote:
>>> 
>>> Now that the RWW is starting to have social systems based on Web Standards (REST, HTTP, Linked Data) I thought it would be a good idea to have a place holder for apps that can be deployed to the Web.
>>> 
>>> The three advantages of this are:
>>> 
>>> Showcase some existing apps
>>> Allow users to add more functionality to their social experience
>>> Add payment technology so that authors can be incentivized more
>>> I've started an early prototype for these two which I'll be fleshing out over time.
>>> 
>>> http://webappmarket.org/
>>> 
>>> This is a non commercial open website, donated to the community.  It's based on wordpress to show a portfolio of apps.  And also the payswarm wordpress plugin as a proof of concept for payments.  Currently payments are working with the dev payswarm authority.
>>> 
>>> There are many app markets out there today,
>>> 
>>> Ubuntu app market
>>> IOS App market
>>> Android app market
>>> Microsoft app merkt
>>> Facebook app center
>>> OpenSocial
>>> Twitter apps
>>> app.net
>>> Chrome app store
>>> Mozilla app store
>>> 5apps
>>> To name a few.  The hope is to make, via HTML5 and the Open Web Platform a growing ecosystem which will be the intersection of app markets.
>>> 
>>> There should be no censorship, but spam and malware should be removed.
>>> 
>>> 
>>> Once you have Web-scale verifiable identity you kill off the effects of spam. Ditto malware. These irritations only exist today due to the Internet's identity flaw :-)
>>> 
>>> [SNIP]
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>>  
>>> Regards,
>>>  
>>> Kingsley Idehen       
>>> Founder & CEO 
>>> OpenLink Software     
>>> Company Web: http://www.openlinksw.com
>>> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
>>> Twitter/Identi.ca handle: @kidehen
>>> Google+ Profile: https://plus.google.com/112399767740508618350/about
>>> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>>>  
>>>  
>>>  
>>>  
>>> 
>> 
>> 
> 
> 
Received on Tuesday, 18 September 2012 09:07:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 18 September 2012 09:07:36 GMT