"Blogs work differently. Instead of n-way authentication, there is only one-way authentication. Each author authenticates to a hosting service to post there. Each blog is bound to and emblematic of its author's identity. The popularity rankings that the blog indexers incessantly churn out are also measures of trust. As a longtime blogger, I've built trust that comes partly from speaking consistently over time with a credible voice and partly from peer validation expressed in the currency of links. Everyone can see that to violate that trust by spreading malicious code would be a self-destructive act.
If you're creating a Web service that you hope will have a disruptive impact, the lessons are clear. Support HTTP GET-style URLs. Design them carefully, matching de facto standards where they exist. Keep the URLs short, so people can easily understand, modify, and trade them. Establish a blog reputation. Use the blog network to promote the service and enable users of the service to self-organize. It all adds up to a recipe for recombinant growth."
The disruptive Web
Tuesday, January 07, 2003
True Lies
In Renmin Voice Joshua Allan defends the Semantic Web. Taking up another point in the argument, he says that whether statements are lies or not it's all knowledge. I'm not going to reiterate everything he's said. The initial points are well made. He then seems to be stretching as he makes such claims that XML and RDF are almost the same thing. His use of English is Bard-like in comparison to my own so it's garnered much more respect.
The Year of Linking Dangerously, Joshua Allen on the semantic web and Tracking all the lies are both positive and critical responses to Joshua's blog. I laughed at, "It's in the air. It's viral. It's contagious. Hold your breath or you'll catch it." and I thought I just had a cold.
Jonathon notes in Track all the lies that MoveableType can free you from the tyranny of Google (through the use of Trackback). I've wanted Trackback or pingback for a while. I agree that a link doesn't give you enough information. As Joshua is a Radio user there's no Trackback or Pingback which means hunting down all the responses.
The discussion continues and the tools get better.
The Year of Linking Dangerously, Joshua Allen on the semantic web and Tracking all the lies are both positive and critical responses to Joshua's blog. I laughed at, "It's in the air. It's viral. It's contagious. Hold your breath or you'll catch it." and I thought I just had a cold.
Jonathon notes in Track all the lies that MoveableType can free you from the tyranny of Google (through the use of Trackback). I've wanted Trackback or pingback for a while. I agree that a link doesn't give you enough information. As Joshua is a Radio user there's no Trackback or Pingback which means hunting down all the responses.
The discussion continues and the tools get better.
Monday, January 06, 2003
Pick Returns
Maverick is an open-source version of a Pick-like MultiValue database written in Java. I've seen old Pick systems but never could work out whether it was an alternative to an OS or an alternative to SQL databases.
""You can think in a relational manner, you can program it like a relational database, but it doesn't [have] all the relational constraints," Youngman said. For example, programming in SQL requires tables for each line on an invoice, while Pick needs just a single record per invoice that can be viewed relationally, he said." Open-source Pick-like database being developed
It currently backends onto some existing relational databases like MySQL.
""You can think in a relational manner, you can program it like a relational database, but it doesn't [have] all the relational constraints," Youngman said. For example, programming in SQL requires tables for each line on an invoice, while Pick needs just a single record per invoice that can be viewed relationally, he said." Open-source Pick-like database being developed
It currently backends onto some existing relational databases like MySQL.
Semantic Links
More than one way to link a cat "The move from document-centered hypertext systems to map-based hypertext systems had some unforeseen but far-reaching implications: relationships between nodes could be expressed in more than one way. Maps showed interconnectedness explicitly, usually in the form of a directed graph. But also node proximity came into play; relationships among different nodes or documents could be indicated simply on the basis of their relative location. The use of these map-based hypertext systems to author new information spaces uncovered an interesting phenomenon. Users avoided the explicit linking mechanisms in favor of the more implicit expression of relationships through spatial proximity and visual attributes [14]. Further analysis showed that the use of these spatial and visual cues to imply relationships applied not only to map-based hypertext systems, but also to traditional hypertext systems and in the physical arrangement of paper and notecards [15]."
Spatial Hypertext: An Alternative to Navigational and Semantic Links
Spatial Hypertext: An Alternative to Navigational and Semantic Links
Sunday, January 05, 2003
Go TKS
It seems that TKS will go into Practical RDF. iTQL isn't mentioned but given the time constraints it's pretty good anyway. There's even a chapter with XUL and RDF in Mozilla.
It looks like it will be a good book. However there were a couple of things that I thought were missing:
* P2P and RDF - like Edutella.
* Annotation - like Annotea.
* Document management - like DSpace.
* IRIs - Can't really tell though from just the TOC.
* CC/PP.
* FIPA.
It looks like it will be a good book. However there were a couple of things that I thought were missing:
* P2P and RDF - like Edutella.
* Annotation - like Annotea.
* Document management - like DSpace.
* IRIs - Can't really tell though from just the TOC.
* CC/PP.
* FIPA.
Saturday, January 04, 2003
How to be a philosopher
"Begin by making a spurious distinction. Befuddle the reader with your analytic wizardry. The reader will enter a logical trance, from which she will be unable to recall the initial spurious distinction and will feel strangely compelled to accept your conclusions." Techniques 7 and 10 aren't all that bad either. :-)
http://www.philosophersnet.com/article.php?id=540
http://www.philosophersnet.com/article.php?id=540
Tools will Save Us (again)
Tools Will Save Us "The person being scolded failed to realize why his post was so ironic and deserving of the scolding he got from Mark. I can't believe he failed to realize that the point Mark was making was that if we (i.e. he) can't even create properly machine readable versions of documents for simple formats like HTML and RSS, yet believs that we will somehow magically do this with more complex and confusing technologies like RDF/XML, DAML+OIL, OWL, etc. "
I haven't failed to understand that complexity will cause problems writing tools. In my original response, I linked to something I said in September, "It's a cop out to say that you should only use tools; until the machines write the tools that is."
The barrier to web publishing has never been lower than it is now, this is because of tools overcoming complexity.
Google is the obvious example of a tool overcoming massive complexity. Even Google doesn't always work. But then I end up using Vivisimo which lets me discriminate between the same lexical term by picking the correct semantic term.
Blogger is a bad tool, therefore tools can't save us. Engineers write tools, therefore engineers can't save us. These are very bad arguments, actually they're stupid and dangerous arguments. If that's the only argument that people have against the Semantic Web then please let me sell you some rocks to protect you from tigers. Things still work because of tolerance.
When I say we can categorize lies I was saying that this categorization does not have to depend on AI. All I was saying was that if you don't want to believe a person, site or data between the meta tag then that's what you can do. Maybe you don't need RDF but you'll need something that looks an awful lot like it.
I actually agree mostly with Mark if not the way he's argued his points. What is needed is semantics from the ground up and using HTML is a simple way of doing it, you need semantic applications for everyone indeed this is what the semantic web challenge is about.
Take a look at the TAP demos, like the Eric Miller example. This TAP KB is broad and shallow. However, it could be used to bootstrap a larger shared vocabulary. As Eric has said, "It's not artificial, and it's not intelligent...The conceptual models behind RDF are predicated on work in the digital library community. You can think of this as a common framework that supports thesaurus, taxonomies and classification schemes."
I don't like ad hominem arguments, and this isn't one, but I just had to wonder about the author of metacrap. That article always struck me as satire and made me laugh when I read it. Section 3 is even positive towards the latent semantics used by Google. So I dug around and I came across the author's FOAF which is an RDF vocabulary. He also co-founded OpenCola which is coming close to the every man's semantic web application. His "Disreputable Conduct in a Reputation Network OpenCola Versus the Demons of the Popular Imagination" talks about the kind of categorization and filtering that works and can be applied to the Semantic Web (he even talks about automated bots).
I haven't failed to understand that complexity will cause problems writing tools. In my original response, I linked to something I said in September, "It's a cop out to say that you should only use tools; until the machines write the tools that is."
The barrier to web publishing has never been lower than it is now, this is because of tools overcoming complexity.
Google is the obvious example of a tool overcoming massive complexity. Even Google doesn't always work. But then I end up using Vivisimo which lets me discriminate between the same lexical term by picking the correct semantic term.
Blogger is a bad tool, therefore tools can't save us. Engineers write tools, therefore engineers can't save us. These are very bad arguments, actually they're stupid and dangerous arguments. If that's the only argument that people have against the Semantic Web then please let me sell you some rocks to protect you from tigers. Things still work because of tolerance.
When I say we can categorize lies I was saying that this categorization does not have to depend on AI. All I was saying was that if you don't want to believe a person, site or data between the meta tag then that's what you can do. Maybe you don't need RDF but you'll need something that looks an awful lot like it.
I actually agree mostly with Mark if not the way he's argued his points. What is needed is semantics from the ground up and using HTML is a simple way of doing it, you need semantic applications for everyone indeed this is what the semantic web challenge is about.
Take a look at the TAP demos, like the Eric Miller example. This TAP KB is broad and shallow. However, it could be used to bootstrap a larger shared vocabulary. As Eric has said, "It's not artificial, and it's not intelligent...The conceptual models behind RDF are predicated on work in the digital library community. You can think of this as a common framework that supports thesaurus, taxonomies and classification schemes."
I don't like ad hominem arguments, and this isn't one, but I just had to wonder about the author of metacrap. That article always struck me as satire and made me laugh when I read it. Section 3 is even positive towards the latent semantics used by Google. So I dug around and I came across the author's FOAF which is an RDF vocabulary. He also co-founded OpenCola which is coming close to the every man's semantic web application. His "Disreputable Conduct in a Reputation Network OpenCola Versus the Demons of the Popular Imagination" talks about the kind of categorization and filtering that works and can be applied to the Semantic Web (he even talks about automated bots).
Predictions for 2003
Most of the predictions for 2003 seem to focus on web services, mobile phones, J2EE, .Net, Microsoft, Apple, Sun, etc. I liked Bill de hÓra's predictions for 2003, here's some of them:
Semantic Web:
* Ontologies are not as useful and more difficult to design than first expected; the upfront costs of creation become a concern.
* Specialized metadata formats continue to be favoured over RDF.
* RDF is used for systems integration.
* Machine learning comes to the semantic web.
XML:
* Users of of W3C Schema make all the same mistakes OO users did 10 years ago.
* XSLT/XPath are forked.
* W3C Schema is subsetted.
* Use of entity references for characters becomes an antipattern.
Some could say that XPath is already forked with XPath NG.
Semantic Web:
* Ontologies are not as useful and more difficult to design than first expected; the upfront costs of creation become a concern.
* Specialized metadata formats continue to be favoured over RDF.
* RDF is used for systems integration.
* Machine learning comes to the semantic web.
XML:
* Users of of W3C Schema make all the same mistakes OO users did 10 years ago.
* XSLT/XPath are forked.
* W3C Schema is subsetted.
* Use of entity references for characters becomes an antipattern.
Some could say that XPath is already forked with XPath NG.
Friday, January 03, 2003
XML Class Warfare
"Strong data typing is mostly a false crutch that collapses very readily...I also received a handful of messages with no new insights, but just expressing support for the "bohemian" point of view and dismay at the layers of complexity the W3C appears to be molding over everything it produces lately." - More on XML class warfare. Largely that complexity stems from XML Schema.
"The gentry, however, would like more class consciousness from these workhorse technologies. They reason that if they have gone to the trouble of specifying in the schema that ''1.0'' represents a floating point number, the XPath and XSLT processors should make this information available, and the processor should use such type information far more broadly. The gentry take the view that such capabilities should be built into the foundations of XPath and XSLT...Not by coincidence, these specifications are several times larger and more complex than the 1.0 generation of specifications."
I would agree with the "bohemians" that as some of these specs get close to acceptance the W3C then adds one more layer of complexity. Uche seems to think that XML data types are all or nothing, especially with the new versions of XPath and XSLT. As everything is about RDF, I just have to note that even without a parser that understands RDF data types, the RDF is still useful and distinct. It's a shame though, that types in RDF was not just another property but is embedded in the syntax of RDF/XML. This kind of separation is also mentioned in one of xml-dev threads.
From the original article, "The bohemians insist that the next-generation XML technologies should not only learn from RELAX NG's isolation of class consciousness, but should avoid bias toward WXS, supporting RELAX NG and other alternatives as well. The battle rages on at present."
A Relax NG Schema for RDF/XML does exist but it is not part of the RDF specification.
"The gentry, however, would like more class consciousness from these workhorse technologies. They reason that if they have gone to the trouble of specifying in the schema that ''1.0'' represents a floating point number, the XPath and XSLT processors should make this information available, and the processor should use such type information far more broadly. The gentry take the view that such capabilities should be built into the foundations of XPath and XSLT...Not by coincidence, these specifications are several times larger and more complex than the 1.0 generation of specifications."
I would agree with the "bohemians" that as some of these specs get close to acceptance the W3C then adds one more layer of complexity. Uche seems to think that XML data types are all or nothing, especially with the new versions of XPath and XSLT. As everything is about RDF, I just have to note that even without a parser that understands RDF data types, the RDF is still useful and distinct. It's a shame though, that types in RDF was not just another property but is embedded in the syntax of RDF/XML. This kind of separation is also mentioned in one of xml-dev threads.
From the original article, "The bohemians insist that the next-generation XML technologies should not only learn from RELAX NG's isolation of class consciousness, but should avoid bias toward WXS, supporting RELAX NG and other alternatives as well. The battle rages on at present."
A Relax NG Schema for RDF/XML does exist but it is not part of the RDF specification.
JLense
This looks to be an Eclipse based framework that uses Swing instead of SWT.
"..the Eclipse plugin platform is the inspiration for JLense. JLense is a significant departure from Eclipse in some important ways, especially with regard to the UIWorks framework, but JLense also incorporates some parts of Eclipse unchanged."
"There was some speculation that the name of the Eclipse project was perhaps specifically meant to suggest eclipsing of the 'Sun'.
While looking for a name for this project I read about a phenomenon called gravitational microlensing. In short, gravitational microlensing is similar to an eclipse in that a large object passes between us and another star. But unlike an eclipse, which obscures the more distant star, gravitational microlensing will cause the more distant star to become more visible or brighter in appearance.
And that is what I hope JLense (the large object between the viewer and the star) will do for Swing (the star)."
http://jlense.sourceforge.net/
"..the Eclipse plugin platform is the inspiration for JLense. JLense is a significant departure from Eclipse in some important ways, especially with regard to the UIWorks framework, but JLense also incorporates some parts of Eclipse unchanged."
"There was some speculation that the name of the Eclipse project was perhaps specifically meant to suggest eclipsing of the 'Sun'.
While looking for a name for this project I read about a phenomenon called gravitational microlensing. In short, gravitational microlensing is similar to an eclipse in that a large object passes between us and another star. But unlike an eclipse, which obscures the more distant star, gravitational microlensing will cause the more distant star to become more visible or brighter in appearance.
And that is what I hope JLense (the large object between the viewer and the star) will do for Swing (the star)."
http://jlense.sourceforge.net/
Dynamic Class Loader Using OWL
Mindswap's OWL Class Loader allows you to load and persist Java classes to RDF and is used in RIC. "So now to "compile" the Agenda-RIC program from the RIC code, all I need to do is put the correct OWL in the config file and make sure that its marked active. No recompiling is needed. Modules can be upgraded without changing code, just tell the program what the new module is to load, and voila, the program uses the new and improved part, rather than the old one you replaced.". By itself, I'm not sure it has much advantage over storing everything in XML (as in JSX, JAXB, Castor or KOML). However, as part of a larger system I can see how the configuration and autodeployment might be interesting. Your configuration files could depend upon version, security or any other piece of metadata you could query.
The next step is to actually have the actual functionality described in RDF which is close to what I've seen with Adenine (which is more like Lisp but uses Java objects) and is part of the Haystack project that I've covered before.
The next step is to actually have the actual functionality described in RDF which is close to what I've seen with Adenine (which is more like Lisp but uses Java objects) and is part of the Haystack project that I've covered before.
Thursday, January 02, 2003
J2EE Client Provisioning Servers
JSR 188 - "To enable interoperability between web servers and access mechanisms, and to facilitate development of device independent web applications, this specification will define a set of APIs for processing CC/PP information...This specification will depend on CC/PP [2] which uses RDF [4] (a framework for processing metadata) which uses XML [5]. This specification will not define a generalized API for RDF." Expert group includes HP, Nokia, Oracle, IBM, BT, and others.
Restina
Semantic Web Calendaring Agent "The Retsina Semantic Web Calendar Agent provides interoperability between RDF based calendar descriptions on the web, and Personal Information Manager (PIM) Systems such as Microsoft's Outlook. Schedules and events can be described on the web in RDF, using existing ontologies such as the Hybrid iCal-like RDF Schema or the Dublin Core ontology, and linked to individual's contact information described, for example, at their home page."
Machine Learning Software in Java
Weka and Kea - these are useful for anyone wanting to have a look at some examples of extracting keyphrases from the text of a document and other data mining activitives (data pre-processing, classification, regression, clustering, association rules, and visualization). Also, take a look at the book.
Tools will Save You
My points are invalid because my RSS, HTML and email link are broken. Condemn me for my argument not my broken tools! At least you didn't comment on my appearance, spelling or grammar. Anyway, unless you parsed them yourself you used tools to see that my RSS and HTML were invalid. But is HTML or RSS flawed because my RSS and HTML are flawed? These can be fixed and will. I'm sorry you missed the point.
Specifically:
- I've written about RDF's failure with RSS before, its great tragedy (this one references a previous Dive Into Mark), and a simple way to convert between the various formats. I also think that the RDF/XML syntax is a mess and is an obstacle to good tool writing.
- An example where competition and truth can work together is with Semantic Web Services. There's also the more indepth paper "The Web Service Modeling Framework (WSMF)" (which covers mediated P2P as a way to get around the schema problems in a P2P environment).
- Blogger annoys me a lot, the ampersand problem is just one of many, it mangles ampersands in links. I really want to stop using it but I have to worry about not only moving to something else but taking this content with me. Again, a problem for a tool.
Specifically:
- I've written about RDF's failure with RSS before, its great tragedy (this one references a previous Dive Into Mark), and a simple way to convert between the various formats. I also think that the RDF/XML syntax is a mess and is an obstacle to good tool writing.
- An example where competition and truth can work together is with Semantic Web Services. There's also the more indepth paper "The Web Service Modeling Framework (WSMF)" (which covers mediated P2P as a way to get around the schema problems in a P2P environment).
- Blogger annoys me a lot, the ampersand problem is just one of many, it mangles ampersands in links. I really want to stop using it but I have to worry about not only moving to something else but taking this content with me. Again, a problem for a tool.
Wednesday, January 01, 2003
Tag Soup
In Tag Soup TNG Mark Pilgrim writes that the Semantic Web will never succeed because people lie. He also says that it's machine readable only which is just not so. As Tim Berners-Lee wrote in Nature: "The Web was designed as an information space, with the goal that it should be useful not only for human-human communication, but also that machines would be able to participate and help users communicate with each other." It's extra to the Web not a replacement.
In the Semantic Web, as in life, you don't have to believe everything everybody says forever. If you are deeply cynical, then don't believe what anyone says. Still, the Semantic Web technologies could be of use. You could use your own text mining tool to extract metadata (unlike the document's own data in the meta tag). You can then combine this with other document's metadata and create your own ontology. You can use ontologies to further classify other documents or sets of documents.
If you can trust other people and their metadata extraction then things get even better or even exponentially better as you trust more (people, groups, companies, etc.) and/or use more tools (Semantic Web enabled P2P clients or Google, etc.).
RDF lets you create statements that the document/author made, that you or anyone else has made. The lies can be categorized and pruned to your or anyone elses whim.
I really hope no one or at least very few, will ever have to manually produce RDF/XML. If you're a programmer use a library, if you're not use an application. If you want to write it yourself it's just like code or English - if it doesn't parse it can't be understood.
The schema problem does not seem that hard either. People do it now for XML or database schemas. The conversion tools can either be as general or as specific as you want and can include as much or as little human intervention as you want. The OntoShare paper addresses some of these problems such as how do you evolve a shared ontology and the use of tools (in their case ViewSum) to consistently extract key concepts. Semantic Gossiping outlines the problems involved in doing this in a peer-to-peer environment.
In the Semantic Web, as in life, you don't have to believe everything everybody says forever. If you are deeply cynical, then don't believe what anyone says. Still, the Semantic Web technologies could be of use. You could use your own text mining tool to extract metadata (unlike the document's own data in the meta tag). You can then combine this with other document's metadata and create your own ontology. You can use ontologies to further classify other documents or sets of documents.
If you can trust other people and their metadata extraction then things get even better or even exponentially better as you trust more (people, groups, companies, etc.) and/or use more tools (Semantic Web enabled P2P clients or Google, etc.).
RDF lets you create statements that the document/author made, that you or anyone else has made. The lies can be categorized and pruned to your or anyone elses whim.
I really hope no one or at least very few, will ever have to manually produce RDF/XML. If you're a programmer use a library, if you're not use an application. If you want to write it yourself it's just like code or English - if it doesn't parse it can't be understood.
The schema problem does not seem that hard either. People do it now for XML or database schemas. The conversion tools can either be as general or as specific as you want and can include as much or as little human intervention as you want. The OntoShare paper addresses some of these problems such as how do you evolve a shared ontology and the use of tools (in their case ViewSum) to consistently extract key concepts. Semantic Gossiping outlines the problems involved in doing this in a peer-to-peer environment.
XXL
XXL provides a powerful collection of easy-to-use index-structures, query operators and algorithms facilitating the performance evaluation of new query processing developments. Query algorithms in XXL use the same set of basic classes, like I/O routines and improved (de)serialization methods. Index structures include B-trees, R-trees, M-trees, AVL-trees, Red-Black-trees and bulk-loading-algorithms. Also includes VisualXXL which is a graphical query engine. Requires Java 3D.
JX
JX - The JX system architecture consists of a set of Java components executing on the JX core that is responsible for system initialization, CPU context switching and low-level domain management. The Java code is organized in components which are loaded into domains, verified, and translated to native code.
Subscribe to:
Posts (Atom)