You can edit directly in text if you like.
I agree we definitely need to cover the three points you mention,
especially the definition of the the wemi-type.
Cheers,
Peeter
On Wed, Dec 5, 2012 at 8:51 AM, Thomas Lund Sigdestad <> wrote:
> Great job of putting things together Peeter :-)
>
> I suggest we focus on and prepare for the following:
>
> - What is a wemi-type, and how does this affect the "content" part?
> - How do we provide the optimal paging support (links/map/includes etc)
> - Honing the use-cases
>
> Is it ok to edit directly in the text for suggestions/improvements, or should we do all through comments?
>
> Vennlig hilsen/Best regards
> Enonic AS
>
> Thomas Sigdestad
> CTO
> +47 98236011
>
> An Open Source Company
>
> ----- Original Message -----
> From: "Peeter Piegaze" <>
> To: "Cedric Huesler" <>,
> Sent: Tuesday, December 4, 2012 5:54:12 PM
> Subject: [wemi] Draft WEMI Spec
>
> Hi all,
>
> I have updated and cleaned up the WEMI spec document. We will use this
> as a basis for tomorrow's discussion.
>
> Cheers,
> Peeter
>
>
> WEMI Specification -
> https://docs.google.com/document/d/1npHRZK1Dsdxr81PnU6iXdXwuaFiqOOoDwqbH79nSgJA/edit
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
