OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wemi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wemi] WEMI follow up


Hi,

A list of last modified stuff is also very useful for users,
especially in wikis, to see "what's happened recently".

Florent

On Wed, Apr 18, 2012 at 3:33 PM, Thomas Lund Sigdestad <tsi@enonic.com> wrote:
> Hi Serge!
>
> Just some quick comments..
>
> The last modified case is useful for external data indexing, and is comparable to queries, but differs when it comes to deleted items I believe.
>
> In regards to sitemaps, I just want to make sure we look beyond data. Embeds (widgets++) and services (rest api's?) are indeed powerful things - and then we really enable web interoperability!
>
> mvh
> Thomas Sigdestad
> +47 98236011
>
> Den 18. apr. 2012 kl. 15:15 skrev Serge Huber <shuber@jahia.com>:
>
>> Hi all (too),
>>
>> I'd like to second Arje and Thomas to thank all of you for the opportunity to meet in person in Copenhagen.
>>
>> Thanks Thomas for proposing some use cases.
>>
>> On 18 avr. 2012, at 15:01, Thomas Lund Sigdestad wrote:
>>
>>> * Ability to get a list of "things" that have been modified since a given point in time for a site/web (including deletions)
>>
>> Although I find this interesting, I'm not sure what this would imply in terms of model, since this looks more like a sync protocol than anything else. Or maybe we could use queries for such a thing ?
>>
>>> * Ability ask any given site/application about what "services/embeds/data" it can provide, and where these can be located
>>
>> I think that's the global idea we were discussing when talking about site maps, no ?
>>
>>> * Define common ways to integrate "embeds/widgets" from any given system and rules for javascript/css
>>
>> Here this is definitely the use case I think we were including when we talked about exposing model objects using either JSON or HTML. Despite the lack of initial interest for HTML, I think that it can serve some aggregation use cases, for example on mobile devices.
>>
>> Regards,
>>  Serge Huber.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wemi-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: wemi-help@lists.oasis-open.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wemi-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wemi-help@lists.oasis-open.org
>



-- 
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com  ; http://www.nuxeo.org  ; +33 1 40 33 79 87


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]