<p>There you go. The key "editors" today are MSOffice and OpenOffice, neither of which supports advanced W3C formats. Especially XHTML-CSS.</p>
<p>XHTML-CSS is a highly interoperable XML based structuring that effectively separates content and presentation layers. In particular, CSS is a highly portable "presentation" layer. Especially when compared to the wholly application speciifc "presentation" layers in MSOffice XML and OpenOffice OpenDocument XML.</p>
<p>The key is that MSOffice and OpenOffice are powerful desktop "editors" of much of the world's business rich compound documents. With the recent ISO approval of MSOffice XML, billlions of these business process rich "client/server" documents will now become Web Ready and useful to the emerging "client/Web-Stack/server models common to SOA, WOA and Cloud Computing initiatives.</p>
<p>The December 2007 MSOffice SDK contained an important conversion component for the easy conversion of MSOffice XML <> XAML. "fixed/flow". XAML is part of the proprietary WPF (Windows Presentation Foundation) set of technologies which inlcude XAML, Silverlight, Smart Tags and LINQ.</p>
<p>The proprietary WPF technologies are alternatives for W3C XHTML-CSS, CDF, SVG, XForms, RDF and SparQL.</p>
<p>Neither desktop "editors" produce advanced W3C XHTML-CSS, SVG, Xforms, RDF, SparQL ready docuemtns. OpenOffice OpenDocument is capable of producing application specific supersets of W3C technologies, but does not fully implement interoperable instances. MSOffice is of course in a world owned entirely by Microsoft and the Microsoft Web-Stack.</p>
<p>No surpirses there. A W3C compliant OpenOffice would not doubt change the world. But then, so would a W3C compliant plug-in for MSSOffice!!!!!! Hello WikiWORED!</p>
This link has been bookmarked by 22 people . It was first bookmarked on 05 Mar 2008, by enricosmaps.
-
18 Jun 09
-
17 Sep 08
-
29 Apr 08
Gary Edwardspodcast with Sir Tim discusses the "linked Data Project" and the Semantic Web contrast to Web 2.0 Social Stovepipe Systems
-
“Web 2.0 is a stovepipe system. It’s a set of stovepipes where each site has got its data and it’s not sharing it. What people are sometimes calling a Web 3.0 vision where you’ve got lots of different data out there on the Web and you’ve got lots of different applications, but they’re independent. A given application can use different data. An application can run on a desktop or in my browser, it’s my agent. It can access all the data, which I can use and everything’s much more seamless and much more powerful because you get this integration. The same application has access to data from all over the place.”
-
Add Sticky Note
-
-
-
16 Apr 08
-
21 Mar 08
-
14 Mar 08
-
09 Mar 08
-
06 Mar 08
-
05 Mar 08
-
Asked about an important article in Scientific American from 2001, Berners-Lee was quick to move past the grand vision outlined there, and to stress the importance of simple yet empowering steps;
“In fact, the gain from the Semantic Web comes much before that. So maybe we should have written about enterprise and intra-enterprise data integration and scientific data integration. So, I think, data integration is the name of the game. That’s happening, it’s showing benefits. Public data as well; public data is happening and it is providing the fodder for all kinds of mashups.
What we should realize is that the return on investment will come much earlier when we just have got this interoperable data that we can query over.”
-
data holders will gain benefits
-
‘oh, the Semantic Web is going to involve us all going to our HTML pages and marking them up to put semantics in them.’ Now, there’s an important thread there, but to my mind, it’s actually a very minor part of it. Because I’m not going to hold my breath while other people put semantics in by hand… So, where is the data going to come from? It’s already there. It’s in databases…”
-
So, some data is scraped from HTML pages, some of it is pulled out of databases, some of it comes from projects which have been in XML.
-
growth in the availability of data from less philanthropic sources, there is a clear need for greater clarity with respect to the ‘proper’ use and reuse of data
-
to those sites receiving such criticism for their rather different perspective at the moment, the social networks.
-
they hoard this data. The business model appears to be, ‘We get the users to give us data and we reuse it to our benefit. We get the extra value.’”
…
-
Web 2.0 is a stovepipe system. It’s a set of stovepipes where each site has got its data and it’s not sharing it.
-
“People can indeed choose not to go to that site [if it does not open access to their data]”
In other words, in a market such as the one in which we operate, there is always scope for new entrants
-
-
29 Feb 08
gabriela ortizmichella entrevista (esperaría) y comentarios del entrevistador de la reseña que acabo de marcar (lleva horas cargándose) ((desarrollo de la red social, por otro quién es dueño de los datos como las ligas, las líneas, las relaciones))
comunidadesvirtuales entrevista resenIa informacion legalSI onWeb2.0 socialNetworks socialsoftware sociedadinfo webSemantica dedelicious
-
28 Feb 08
-
27 Feb 08
Public Stiky Notes
There you go. The key "editors" today are MSOffice and OpenOffice, neither of which supports advanced W3C formats. Especially XHTML-CSS.
XHTML-CSS is a highly interoperable XML based structuring that effectively separates content and presentation layers. In particular, CSS is a highly portable "presentation" layer. Especially when compared to the wholly application speciifc "presentation" layers in MSOffice XML and OpenOffice OpenDocument XML.
The key is that MSOffice and OpenOffice are powerful desktop "editors" of much of the world's business rich compound documents. With the recent ISO approval of MSOffice XML, billlions of these business process rich "client/server" documents will now become Web Ready and useful to the emerging "client/Web-Stack/server models common to SOA, WOA and Cloud Computing initiatives.
The December 2007 MSOffice SDK contained an important conversion component for the easy conversion of MSOffice XML <> XAML. "fixed/flow". XAML is part of the proprietary WPF (Windows Presentation Foundation) set of technologies which inlcude XAML, Silverlight, Smart Tags and LINQ.
The proprietary WPF technologies are alternatives for W3C XHTML-CSS, CDF, SVG, XForms, RDF and SparQL.
Neither desktop "editors" produce advanced W3C XHTML-CSS, SVG, Xforms, RDF, SparQL ready docuemtns. OpenOffice OpenDocument is capable of producing application specific supersets of W3C technologies, but does not fully implement interoperable instances. MSOffice is of course in a world owned entirely by Microsoft and the Microsoft Web-Stack.
No surpirses there. A W3C compliant OpenOffice would not doubt change the world. But then, so would a W3C compliant plug-in for MSSOffice!!!!!! Hello WikiWORED!
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.