Comments on: ODF: Twenty Patterns of Use http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html?utm_source=rss&utm_medium=rss&utm_campaign=odf-twenty-patterns-of-use Thinking the unthinkable, pondering the imponderable, effing the ineffable and scruting the inscrutable Tue, 07 Feb 2012 11:20:47 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Alexandre Tornice http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-8770 Alexandre Tornice Tue, 01 Feb 2011 17:40:18 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-8770 ODF as a set of patterns I'm interested in developing and even in the utilization of software-related items 18, 19 and 20. Especially when trying relational searches. I see a way to make this possible would be the union of the existing standard formats. I highly recommend the utilization of MusicXML, besides the already used MathML. I wonder if anyone has more information on how to walk in that direction. Thank you very much! ODF as a set of patterns

I’m interested in developing and even in the utilization of software-related items 18, 19 and 20. Especially when trying relational searches. I see a way to make this possible would be the union of the existing standard formats. I highly recommend the utilization of MusicXML, besides the already used MathML. I wonder if anyone has more information on how to walk in that direction. Thank you very much!

]]> By: Introducing: the Simple Java API for ODF http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-3552 Introducing: the Simple Java API for ODF Mon, 01 Nov 2010 19:51:21 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-3552 [...] to manipulation using common, high level tools. I made a list of the top 2o document-based “patterns of use“, but the key ones are in the following [...] [...] to manipulation using common, high level tools. I made a list of the top 2o document-based “patterns of use“, but the key ones are in the following [...]

]]> By: In Dublin’s Fair City http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-3551 In Dublin’s Fair City Mon, 01 Nov 2010 18:18:49 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-3551 [...] experience with ODF, and enable ODF innovation beyond the editors, along the lines of the 20 patterns of use I outlined earlier. Microsoft is well-known for their commitment to developer tools and [...] [...] experience with ODF, and enable ODF innovation beyond the editors, along the lines of the 20 patterns of use I outlined earlier. Microsoft is well-known for their commitment to developer tools and [...]

]]> By: KDE wydało nową wersję darmowego pakietu biurowego | thecamels.org http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-3387 KDE wydało nową wersję darmowego pakietu biurowego | thecamels.org Sun, 27 Jun 2010 19:12:43 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-3387 [...] KOffice 1.6 wraz z zaimplementowaniem skryptów w KSpread, Krita i Kexi, stawia obsługę skryptów na zupełnie nowym poziomie. Jest to realizowane poprzez użycie modułu Kross, który umożliwia dodawanie skryptów napisanych w Pythonie lub Ruby, a w przyszłości także w Javascript i Java. W bieżącym wydaniu KOffice umożliwia także tworzenie skryptów bez interfejsu graficznego, np. dane w arkuszu kalkulacyjnym mogą być automatycznie zmieniane poprzez skrypty, co daje wiele nowych możliwości. [...] [...] KOffice 1.6 wraz z zaimplementowaniem skryptów w KSpread, Krita i Kexi, stawia obsługę skryptów na zupełnie nowym poziomie. Jest to realizowane poprzez użycie modułu Kross, który umożliwia dodawanie skryptów napisanych w Pythonie lub Ruby, a w przyszłości także w Javascript i Java. W bieżącym wydaniu KOffice umożliwia także tworzenie skryptów bez interfejsu graficznego, np. dane w arkuszu kalkulacyjnym mogą być automatycznie zmieniane poprzez skrypty, co daje wiele nowych możliwości. [...]

]]> By: The 21st ODF Toolkit Scenario http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-2639 The 21st ODF Toolkit Scenario Wed, 06 Jan 2010 02:05:36 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-2639 [...] Back in 2006 I gave a short in talk at a KDE conference in Dublin on the topic of “A Standard ODF Object Model”, essentially laying out my thoughts on why we needed an “ODF Toolkit”. As part of that presentation I listed “20 Prototypical App Dev Scenarios”, my attempt to enumerate all the fundamental patterns of use for ODF. I did a blog post on this list later that year. [...] [...] Back in 2006 I gave a short in talk at a KDE conference in Dublin on the topic of “A Standard ODF Object Model”, essentially laying out my thoughts on why we needed an “ODF Toolkit”. As part of that presentation I listed “20 Prototypical App Dev Scenarios”, my attempt to enumerate all the fundamental patterns of use for ODF. I did a blog post on this list later that year. [...]

]]> By: Rob http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-152 Rob Wed, 25 Oct 2006 14:24:00 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-152 #8 validation -- an example might be accessibility proofing. So, today checking things like all images must have alt text is easy to do. But what if we want to verify that no chart relies on color alone to impart meaning? You might want to check this to ensure that the a chart is readable by the color-blind user. This is something that can easily be expressed as a schema constraint.<br/><br/>Another example would be a journal's style guidelines with regards to figures, citation style, etc. It is not something you would want to mandate as the document schema per se, since each publisher is different. But it is something you might want to layer on as an additional set of pluggable constraints which can be evaluated when that particular output is targetted. My main point is validation is more than schema validation. <br/><br/>As to your second point, certainly these scenarios are possible with any well-written, platform and application neutral XML document format. That said, my reading of Microsoft's OOXML does not leave me optimistic in that regard. #8 validation — an example might be accessibility proofing. So, today checking things like all images must have alt text is easy to do. But what if we want to verify that no chart relies on color alone to impart meaning? You might want to check this to ensure that the a chart is readable by the color-blind user. This is something that can easily be expressed as a schema constraint.

Another example would be a journal’s style guidelines with regards to figures, citation style, etc. It is not something you would want to mandate as the document schema per se, since each publisher is different. But it is something you might want to layer on as an additional set of pluggable constraints which can be evaluated when that particular output is targetted. My main point is validation is more than schema validation.

As to your second point, certainly these scenarios are possible with any well-written, platform and application neutral XML document format. That said, my reading of Microsoft’s OOXML does not leave me optimistic in that regard.

]]> By: Anonymous http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-150 Anonymous Wed, 25 Oct 2006 02:45:00 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-150 How is #8 (Validation of document) possible?<br/><br/>Also, a minor nitpick. Pretty much all of these are available with Microsoft software. But since ODF reuses free specs and is free, these are now available without vendor lock-in. :-) How is #8 (Validation of document) possible?

Also, a minor nitpick. Pretty much all of these are available with Microsoft software. But since ODF reuses free specs and is free, these are now available without vendor lock-in. :-)

]]> By: Anonymous http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-93 Anonymous Sat, 30 Sep 2006 12:11:00 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-93 Good to see that you are none the worse for wear, or Dublin weir, Rob, your presentation at the KDE event was very interesting. Regarding your 20 patterns it would be useful to know, from a lay viewpoint, what each of these would entail in terms of development Good to see that you are none the worse for wear, or Dublin weir, Rob, your presentation at the KDE event was very interesting. Regarding your 20 patterns it would be useful to know, from a lay viewpoint, what each of these would entail in terms of development

]]> By: cliff http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-92 cliff Fri, 29 Sep 2006 03:01:00 +0000 http://www.robweir.com/blog/2006/09/odf-twenty-patterns-of-use.html#comment-92 Besides Google Spreadsheets, <a HREF="http://www.editgrid.com" REL="nofollow" rel="nofollow">EditGrid</a> is another online spreadsheet support open document, with its <a HREF="http://www.editgrid.com/tnc/cliff/Charts_Demo" REL="nofollow" rel="nofollow">charting function</a> which Google Spreadsheets lacking as it taken taken the light apps approach, I invite you to give it a try. Besides Google Spreadsheets, EditGrid is another online spreadsheet support open document, with its charting function which Google Spreadsheets lacking as it taken taken the light apps approach, I invite you to give it a try.

]]>