<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>OpenDocument's feed | Diigo Group</title>
    <link>http://groups.diigo.com/opendocument/bookmark/tag/wicd</link>
    <description>Bookmarks from OpenDocument tagged by wicd</description>
    <pubDate>Tue, 27 May 2008 07:43:44 -0000</pubDate>
    <item>
      <title>Putting Andy Updegrove to Bed (without his supper) | Universal Interoperability Council</title>
      <link>http://www.universal-interop-council.org/node/4</link>
      <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;by &lt;a href=&quot;http://www.universal-interop-council.org/glossary/term/32&quot; class=&quot;glossary-term&quot;&gt;&lt;acronym title=&quot;OASIS: Organization for the Advancement of Structured Information Standards. A software industry consortium based in the U.S. that develops data format voluntary standards. See About OASIS web page.&quot;&gt;OASIS&lt;/acronym&gt;&lt;/a&gt; attorney Andy Updegrove claimed that &lt;a href=&quot;http://www.w3.org/2004/CDF/&quot;&gt;&lt;/a&gt;&lt;a href=&quot;http://www.universal-interop-council.org/glossary/term/6&quot; class=&quot;glossary-term&quot;&gt;&lt;acronym title=&quot;CDF: Compound Document Formats. A set of World-Wide Web Consortium candidate recommendations (standards) for generating and rendering compound documents. It includes a markup language-neutral interoperability framework (CDRF + CDIF) and WICDprofiles for different combinations of XML-derived markup languages. See How Does Compound Document Framework Benefit Us? and W3C CDF Working Group public home page.&quot;&gt;W3C Compound Document Formats&lt;/acronym&gt;&lt;/a&gt;: [i] are non-editable formats; [ii] are not designed for conversions to other formats; and [iii] are therefore unsuitable as office formats. Updegrove could not have been more wrong.&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;Shorn to essentials, Updegrove in effect argues for the existence of some sort of immaculately conceived data, that data cannot be generated by software editing tools if a &lt;em&gt;homo sapiens&lt;/em&gt; operating a keyboard is somehow involved.&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;&lt;strong&gt;Conversions — &lt;/strong&gt;Updegrove hedged somewhat on this issue, attributing a statement to Lilly that the &quot;CDF working group was not &lt;em&gt;chartered&lt;/em&gt; to achieve conversion between formats.&quot; But one might as well argue that because claw hammers were designed to drive and pull nails they can not be used to hit anything else.&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;To suggest that only W3C WICD profiles can be used with the Framework either flows from or is an appeal to ignorance. There is no wiggle room between those two conclusions.&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;&lt;p&gt;While the Framework specification does require that markup languages combined to create conforming documents be profiled following strict rules, there is no requirement that the profiles thus used superset one or more of the WICD profiles. It may be preferable to do so for purposes of &lt;a href=&quot;http://www.universal-interop-council.org/glossary/term/10&quot; class=&quot;glossary-term&quot;&gt;&lt;acronym title=&quot;compatibility: In the information technology context, the qualitative degree to which one information technology system can properly process information provided by another IT system. Compatibility involves consideration of  fidelity  and is not a synonym for interoperability.&quot;&gt;compatibility&lt;/acronym&gt;&lt;/a&gt; and interoperability with web applications, but to repeat, that is not required.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;p&gt;In fact, virtually any plain text-based markup language that can be profiled can be used within the structure of the Framework. But more importantly, a combination of cutting edge W3C markup language versions such as XHTML 2.0, CSS 3.0, XForms, SVG, etc. can, with only trivial extensions, serve as the full-featured metalanguage superset every expert who has spoken to the subject agrees is necessary to convert between ODF and OOXML with high &lt;a href=&quot;http://www.universal-interop-council.org/glossary/term/18&quot; class=&quot;glossary-term&quot;&gt;&lt;acronym title=&quot;fidelity: A key measure of interoperability and compatibility, the quality of document content, presentation and metadata preserved on exchange between applications. Fidelity is an objective measure, usually the percentage extent to which data and metadata can be properly mapped from one format to the other without being lost or garbled in the conversion process.&quot;&gt;fidelity&lt;/acronym&gt;&lt;/a&gt;.&lt;/p&gt;&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;ODF and OOXML are designed for apps from the &lt;a href=&quot;http://en.wikipedia.org/wiki/Sneaker_net&quot;&gt;sneaker net&lt;/a&gt; era. Do we choose formats designed for the dinosaurs or formats designed for tomorrow's needs? ODF and OOXML are about the past; CDF is about the future. And yes, there are fully interoperable editors in that future.&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/cdf&quot;&gt;cdf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/foundation&quot;&gt;foundation&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/updegrove&quot;&gt;updegrove&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/w3c&quot;&gt;w3c&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/wicd&quot;&gt;wicd&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/marbux&quot;&gt;marbux&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Tue, 27 May 2008 07:43:44 -0000</pubDate>
    </item>
    <item>
      <title>CDI WICD 2.0</title>
      <link>http://www.w3.org/2004/CDF/specs/CDI/cdi-wicd/Overview.html</link>
      <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;&lt;p&gt;This document defines a generic language-independent processing model
   for combining arbitrary document formats.&lt;/p&gt;

  &lt;p class=&quot;note&quot;&gt;The Compound Document Framework is language-independent.
   While it is clearly meant to serve as the basis for integrating W3C's
   family of XML formats within its Interaction Domain (e.g., MathML, SMIL,
   SVG, VoiceXML, XForms, XHTML, XSL) with each other, together with CSS and
   the DOM; it can also be used to integrate non-W3C formats with W3C formats
   or integrate non-W3C formats with other non-W3C formats.&lt;/p&gt;

  &lt;h3 id=&quot;conformance&quot;&gt;&lt;span class=&quot;secno&quot;&gt;1.1. &lt;/span&gt;Conformance&lt;/h3&gt;

  &lt;p&gt;Everying in this specification is normative except for diagrams,
   examples, notes and sections marked non-normative.&lt;/p&gt;

  &lt;p&gt;The key words &lt;em class=&quot;ct&quot;&gt;must&lt;/em&gt;, &lt;em class=&quot;ct&quot;&gt;must not&lt;/em&gt;,
   &lt;em class=&quot;ct&quot;&gt;required&lt;/em&gt;, &lt;em class=&quot;ct&quot;&gt;shall&lt;/em&gt;, &lt;em class=&quot;ct&quot;&gt;shall not&lt;/em&gt;, &lt;em class=&quot;ct&quot;&gt;should&lt;/em&gt;, &lt;em class=&quot;ct&quot;&gt;should not&lt;/em&gt;, &lt;em class=&quot;ct&quot;&gt;recommended&lt;/em&gt;, &lt;em class=&quot;ct&quot;&gt;may&lt;/em&gt; and &lt;em class=&quot;ct&quot;&gt;optional&lt;/em&gt; in this document are
   to be interpreted as described in RFC 2119 [&lt;cite&gt;&lt;a href=&quot;#RFC2119&quot;&gt;RFC2119&lt;/a&gt;&lt;/cite&gt;].&lt;/p&gt;

  &lt;p&gt;This specification defines the following classes of products:&lt;/p&gt;

  &lt;dl&gt;
   &lt;dt&gt;&lt;dfn id=&quot;conforming&quot;&gt;conforming implementation&lt;/dfn&gt;&lt;/dt&gt;

   &lt;dd&gt;A user agent that implements all interfaces described in this
    specification and follows all &lt;em class=&quot;ct&quot;&gt;must&lt;/em&gt;-, &lt;em class=&quot;ct&quot;&gt;required&lt;/em&gt;- and &lt;em class=&quot;ct&quot;&gt;shall&lt;/em&gt;-level of critera
    in this specification.&lt;/dd&gt;

   &lt;dt&gt;&lt;dfn id=&quot;conforming0&quot;&gt;conforming document&lt;/dfn&gt;&lt;/dt&gt;

   &lt;dd&gt;A document that follows all &lt;em class=&quot;ct&quot;&gt;must&lt;/em&gt;-, &lt;em class=&quot;ct&quot;&gt;required&lt;/em&gt;- and &lt;em class=&quot;ct&quot;&gt;shall&lt;/em&gt;-level of critera
    in this specification that apply to document authors.&lt;/dd&gt;

   &lt;dt&gt;&lt;dfn id=&quot;conforming1&quot;&gt;conforming authoring tool&lt;/dfn&gt;&lt;/dt&gt;

   &lt;dd&gt;One that produces conforming documents.&lt;/dd&gt;&lt;/dl&gt;&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/cdf&quot;&gt;cdf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/css&quot;&gt;css&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/svg&quot;&gt;svg&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/w3c&quot;&gt;w3c&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/wicd&quot;&gt;wicd&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/xforms&quot;&gt;xforms&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/xhtml&quot;&gt;xhtml&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Sun, 20 Jan 2008 23:52:44 -0000</pubDate>
    </item>
    <item>
      <title>The Future is CDF | Metaphorical Web - Kurt Cagle</title>
      <link>http://metaphoricalweb.blogspot.com</link>
      <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;As editing increasingly moves onto the web, its safe to say that the document of choice will be neither ODF nor OOXML, both of which gain their power on the basis of supporting legacy word processing systems. Instead, what seems to be emerging from the W3C is something that is not an office suite because it didn’t evolve from one, but that nonetheless is capable of most if not all of the same functions that office suite documents pose.&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/cdf&quot;&gt;cdf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/ms-ooxml&quot;&gt;ms-ooxml&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/odf&quot;&gt;odf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/officeopenxml&quot;&gt;officeopenxml&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/opendocument&quot;&gt;opendocument&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/wicd&quot;&gt;wicd&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Mon, 03 Dec 2007 20:27:17 -0000</pubDate>
    </item>
    <item>
      <title>Play the tape!!! The W3C eMails to the Foundation tell a differenct story | OpenDocument Format community steadfast despite theatrics of now impotent 'Foundation' | TalkBack on ZDNet - Flock</title>
      <link>http://talkback.zdnet.com/5208-10741-0.html?forumID=1&amp;threadID=41562&amp;messageID=770813&amp;start=-1</link>
      <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Comments:&lt;/strong&gt;&lt;ul&gt;&lt;li&gt;&lt;font face=&quot;Tahoma&quot; size=&quot;3&quot;&gt;The W3C's Doug Schepers joins the discussion claiming that the Foundation misunderstood his eMail messages.&amp;nbsp;&amp;nbsp; We say otherwise!&lt;br /&gt;&lt;br /&gt;There is of course one way to settle this: PLAY THE TAPE!&lt;br /&gt;&lt;br /&gt;So here it is.&lt;br /&gt;&lt;br /&gt;~ge~&lt;/font&gt;&lt;br /&gt;&lt;br /&gt; &lt;small&gt;posted by &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/small&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;&lt;dt&gt;An honest misunderstanding?  Hardly!  Play the tape!&lt;/dt&gt;
	
	&lt;dd&gt;
	
	
	&lt;p&gt;Instead of arguing about who said what when, let's just go to the record and see exactly what the W3C's Doug Schepers said to us in an eMail introducing himself.  Keep in mind that we did not contact the W3C or Mr. Schepers.  The following eMail was most welcome, but entirely unsolicited.&lt;/p&gt;&lt;/dd&gt;&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/cdf&quot;&gt;cdf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/ms-ooxml&quot;&gt;ms-ooxml&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/odf&quot;&gt;odf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/schepers&quot;&gt;schepers&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/w3c&quot;&gt;w3c&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/wicd&quot;&gt;wicd&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Mon, 03 Dec 2007 09:47:37 -0000</pubDate>
    </item>
    <item>
      <title>Blake Matheny : OpenDocument Foundation to Drop ODF for W3C CDF WICD | Blogging success</title>
      <link>http://blogging.compendiumblog.com/blog.php/blogging-success/0/0/opendocument-foundation-to-drop-odf</link>
      <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Comments:&lt;/strong&gt;&lt;ul&gt;&lt;li&gt;&lt;font face=&quot;Tahoma&quot; size=&quot;3&quot;&gt;Wow!&amp;nbsp; Does Blake Matheny ever get it!&amp;nbsp; Maybe it's time for the W3C CDF Community to speak up? &amp;nbsp;  &lt;/font&gt;&lt;br /&gt; &lt;small&gt;posted by &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/small&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;&lt;p&gt;
Now, Sam Hiser, VP of the ODF, has said that he sees the W3C standard CDF (Compound Document Format) as a more viable universal format than ODF. He stated simply that, &quot;ODF is not the open format with the open process we thought it was&quot;. Why is this significant?
&lt;/p&gt;
&lt;p&gt;
First, I think it speaks to how important the W3C is and has become over the past several years. The number of web standards in particular that have been formalized by the W3C is remarkable, whether they have been successful or not. Second, it (CDF) addresses an issue that I see on a daily basis in my role here at Compendium Blogware.&lt;/p&gt;&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/cdf&quot;&gt;cdf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/foundation&quot;&gt;foundation&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/odf&quot;&gt;odf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/ooxml&quot;&gt;ooxml&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/w3c&quot;&gt;w3c&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/wicd&quot;&gt;wicd&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Mon, 19 Nov 2007 08:38:30 -0000</pubDate>
    </item>
    <item>
      <title>OpenDocument Foundation folds; will Microsoft benefit? - Mary Jo ZDNet</title>
      <link>http://talkback.zdnet.com/5206-12558-0.html?forumID=1&amp;threadID=40984</link>
      <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;&lt;h2&gt;&lt;a href=&quot;http://talkback.zdnet.com/5208-12558-0.html?forumID=1&amp;amp;threadID=40984&amp;amp;messageID=760682&quot;&gt;+1
&lt;/a&gt;&lt;/h2&gt;
&lt;span&gt;&lt;strong&gt;gary.edwards&lt;/strong&gt; - 11/16/07&lt;/span&gt;
&lt;p&gt;Thanks for the consideration Anton.  You might want to follow an emerging discussion now taking place at the OpenDocument Fellowship:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://lists.opendocumentfellowship.com/pipermail/odf-discuss/2007-November/003170.html&quot;&gt;Interop between multiple standards and multiple applications&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Check on the follow up post and understand that this is the same problem the da Vinci group tried to overcome in Massachusetts, when ODF hung by a thread in the summer of 2006; with the sole hope being a plug-in conversion process capable of very high &quot;round trip&quot; fidelity.&lt;/p&gt;

&lt;p&gt; To assist Massachusetts and the da Vinci Group, the OpenDocument Foundation introduced to the OASIS ODF TC a series of discussions and proposals collectively known as the &lt;b&gt;&lt;i&gt;ODF iX interoperability enhancements&lt;/i&gt;&lt;/b&gt;.&lt;/p&gt;

&lt;p&gt;A total of six comprehensive iX enhancements were introduced between July of 2006 and March of 2007.  The first three sets of iX enhancements were signed off on by CIO Louis Gutierrez, with the full knowledge and awareness of IBM (they participated directly in those discussions and i do have the emails and conference schedules to verify this &lt;img class=&quot;jive-emoticon&quot; src=&quot;http://www.cnet.com/i/mb/emoticons/happy.gif&quot; border=&quot;0&quot; alt=&quot;:)&quot; /&gt;.

&lt;/p&gt;&lt;p&gt;Also, if you're interested in other issues surrounding the da Vinci groups use of CDF WICD Full as an in-process conversion target for MSOffice documents, there is a series of recent responses posted in the comments section of &lt;a href=&quot;http://fussnotes.typepad.com/plexnex/2007/11/going-to-bed-wi.html&quot;&gt;this blog, &quot;Going to Bed (without my supper)&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;One last note; I do have a response to AlphaDog sitting in the blog que, where i try to put the MSOffice to CDF WICD Full conversion, and the OpenOffice ODF to CDF WICD Full conversion into the larger context of the web platform and universal interoperability. This post will also briefly explain the events immediately preceding the decision to shut the Foundation down.&lt;/p&gt;

&lt;p&gt;Hope this helps,&lt;/p&gt;
&lt;p&gt;~ge~&lt;/p&gt;&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/cdf&quot;&gt;cdf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/odf&quot;&gt;odf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/ooxml&quot;&gt;ooxml&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/w3c&quot;&gt;w3c&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/wicd&quot;&gt;wicd&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Sat, 17 Nov 2007 08:33:28 -0000</pubDate>
    </item>
    <item>
      <title>WICD Full 1.0 - CDF Desktop Profile</title>
      <link>http://www.w3.org/TR/WICDFull</link>
      <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Comments:&lt;/strong&gt;&lt;ul&gt;&lt;li&gt;Now this is interesting.&amp;nbsp; I wonder if IBM and the OASIS Lawyer have seen this page?&lt;br /&gt; &lt;small&gt;posted by &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/small&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;WICD Full 1.0 is targeted at desktop agents&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;
        The WICD Full 1.0 profile is designed to enable 
        rich multimedia content on desktop and high capability handheld agents.
        &lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;
        The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, 
        &quot;SHALL NOT&quot;, &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;may&quot;,
        and &quot;OPTIONAL&quot; in this document are to be interpreted as 
        described in RFC&amp;nbsp;2119 (see http://www.ietf.org/rfc/rfc2119.txt). 
        However, for readability, 
        these words do not appear in all uppercase letters in this 
        specification.&lt;/div&gt;&lt;ul&gt;&lt;li&gt;This will make marbux happy! &lt;small&gt;posted by &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/small&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/cdf&quot;&gt;cdf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/odf&quot;&gt;odf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/ooxml&quot;&gt;ooxml&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/w3c&quot;&gt;w3c&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/wicd&quot;&gt;wicd&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Tue, 13 Nov 2007 06:49:53 -0000</pubDate>
    </item>
    <item>
      <title>CDF and WICD FAQ - Flock</title>
      <link>http://www.w3.org/2004/CDF/cdf-faq.html</link>
      <description>&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Comments:&lt;/strong&gt;&lt;ul&gt;&lt;li&gt;Thanks to the CDF Workgroup!&amp;nbsp; &lt;br /&gt; &lt;small&gt;posted by &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/small&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Highlights and Sticky Notes:&lt;/strong&gt;&lt;p&gt;&lt;div class=&quot;content&quot;&gt;&lt;dt id=&quot;odf-ooxml&quot;&gt;What is CDF's relationship with ODF and OOXML?&lt;/dt&gt;
      &lt;dd&gt;They occupy different spaces.  ODF and OOXML are office applications formats, while &lt;a href=&quot;http://www.w3.org/#cdf&quot;&gt;CDF&lt;/a&gt; is a W3C Working Group defining a framework for extensibility on the Web.  Compound Documents such as WICD may be appropriate as ODF/OOXML export formats for Web presentation.&lt;/dd&gt;&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/cdf&quot;&gt;cdf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/odf&quot;&gt;odf&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/ooxml&quot;&gt;ooxml&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/w3c&quot;&gt;w3c&lt;/a&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/tag/wicd&quot;&gt;wicd&lt;/a&gt; &lt;/p&gt;&lt;p&gt;&lt;strong&gt;Posted by:&lt;/strong&gt; &lt;a href=&quot;http://groups.diigo.com/opendocument/bookmark/garyedwards&quot;&gt;garyedwards&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Tue, 13 Nov 2007 06:47:54 -0000</pubDate>
    </item>
  </channel>
</rss>