W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2004

RE: Cocoon

From: Steven Dale <sdale@stevendale.com>
Date: Thu, 24 Jun 2004 00:28:37 -0400 (EDT)
Message-ID: <4523.68.232.129.182.1088051317.squirrel@www.stevendale.com>
To: <gdeering@acslink.net.au>
Cc: <sdale@stevendale.com>, <w3c-wai-ig@w3.org>

I will be gone until Sunday but when I get back I will get the latest and
start playing again.  I am interested in delivering content to specific
ability.  I think that is the real power of Cocoon.  A universally
accessible website.  Delivering content suited for the device, at, user
preferences etc.  For instance, restructuring the layout for tiny screens
like phones.  Sending alt and long descriptions instead of pictures to
screen readers.  Sending pictorial based information for cognitive
impaired users such as using PECS symbols.  You name it, content could be
the same and by changing the templates, you have radically different
sites.  I think using the CC/PP type of information from the DIWG and User
Profiles that the users can themselves tailor, it is possible.  I think if
we work together, we could make something great.  I have a domain that
could host it.

-Steve

>>
>> I am getting ready to play around with Cocoon with an eye towards
>> Accessiblity.  I believe it would be a great tool if we can get it
>> working in a best practices type of way.  Have you played with it?   I
>> was involved a couple years ago when developing web content for both
>> the PCs and WAP phones.  I think it would be great to tailor the page
>> output based upon the user's preferences.
>>
>> -Steve
>>
>
> I intend to do much the same, but for me not only does the application
> framework need to work properly, as well as the CMS, but there needs to
> be ways that the CMS can collect enough metadata to extract from the
> source xml for the transformed documents to be semantically rich and
> populate the various attribute/elements with metadata that enrich them
> to user agents addressing accessibility.
>
> Not one commercial CMS collects metadata correctly, if at all.
> Interwoven/Teamsite is the only one that allows a few fields for
> metadata, but it is an EXTREMELY primitive approach.  It seems to me,
> very few architects have seen how important this is to the whole CMS
> workflow.  It astounds me.  Anyone who does this, immediately has huge
> advantages over the rest, and it is not just in the ability to produce
> semantically rich content, but to bring detailed workflow analysis.
>
> This is also a problem working with MS Office and the discipline of
> putting the right metadata in properties and using this meta repository.
>  The custom fields in MS Office cannot be read on the scripting side,
> last time I wrote anything to extract these fields.  I haven't tried it
> with Open Office, but at least that developer community is open to
> feedback.
>
> The other thing I love about the Cocoon architecture is the use of TCN
> (transparent content negotiation), something that is SADLY underused in
> web content delivery.  That is the other area I want to focus on in
> using Cocoon.
>
> I'd also like to get on the back of user agent developers and try and
> fix the http header accuracy as far as the "Accept" headers are concern,
> so that TCN can become a more viable option.  It has improved, since the
> Netscape 2 debacle that wrecked it, but it is still inconsistently
> supported (last time I looked).
>
> Geoff
Received on Thursday, 24 June 2004 00:29:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:33 UTC