Under Review: Packt’s “Funambol Mobile Open Source”
I’m currently reading Packt’s “Funambol Mobile Open Source”. Written by the creator of the project, Stefano Fornari, this book covers a solution for the synchronization of data between multiple devices. A sample chapter is available.
Stay tuned.
On Knowledge-Based Representations for Actionable Data …
I bumped into a professional acquaintance last week. After describing briefly a presentation I was about to give, he offered to broker introductions to others who might have an interest in the work I’ve been doing. To initiate the introductions, I crafted a brief description of what I’ve been up to for the past 5 years in this area. I’ve also decided to share it here as follows:
As always, [name deleted], I enjoyed our conversation at the recent AGU meeting in Toronto. Below, I’ve tried to provide some context for the work I’ve been doing in the area of knowledge representations over the past few years. I’m deeply interested in any introductions you might be able to broker with others at York who might have an interest in applications of the same.
Since 2004, I’ve been interested in expressive representations of data. My investigations started with a representation of geophysical data in the eXtensible Markup Language (XML). Although this was successful, use of the approach underlined the importance of metadata (data about data) as an oversight. To address this oversight, a subsequent effort introduced a relationship-centric representation via the Resource Description Format (RDF). RDF, by the way, forms the underpinnings of the next-generation Web – variously known as the Semantic Web, Web 3.0, etc. In addition to taking care of issues around metadata, use of RDF paved the way for increasingly expressive representations of the same geophysical data. For example, to represent features in and of the geophysical data, an RDF-based scheme for annotation was introduced using XML Pointer Language (XPointer). Somewhere around this point in my research, I placed all of this into a framework.
A data-centric framework for knowledge representation.
In addition to applying my Semantic Framework to use cases in Internet Protocol (IP) networking, I’ve continued to tease out increasingly expressive representations of data. Most recently, these representations have been articulated in RDFS – i.e., RDF Schema. And although I have not reached the final objective of an ontological representation in the Web Ontology Language (OWL), I am indeed progressing in this direction. (Whereas schemas capture the vocabulary of an application domain in geophysics or IT, for example, ontologies allow for knowledge-centric conceptualizations of the same.)
From niche areas of geophysics to IP networking, the Semantic Framework is broadly applicable. As a workflow for systematically enhancing the expressivity of data, the Framework is based on open standards emerging largely from the World Wide Web Consortium (W3C). Because there is significant interest in this next-generation Web from numerous parties and angles, implementation platforms allow for increasingly expressive representations of data today. In making data actionable, the ultimate value of the Semantic Framework is in providing a means for integrating data from seemingly incongruous disciplines. For example, such representations are actually responsible for providing new results – derived by querying the representation through a ‘semantified’ version of the Structured Query Language (SQL) known as SPARQL.
I’ve spoken formally and informally about this research to audiences in the sciences, IT, and elsewhere. With York co-authors spanning academic and non-academic staff, I’ve also published four refereed journal papers on aspects of the Framework, and have an invited book chapter currently under review – interestingly, this chapter has been contributed to a book focusing on data management in the Semantic Web. Of course, I’d be pleased to share any of my publications and discuss aspects of this work with those finding it of interest.
With thanks in advance for any connections you’re able to facilitate, Ian.
If anything comes of this, I’m sure I’ll write about it here – eventually!
In the meantime, feedback is welcome.
Google Chrome for Linux on Bright Hub: Series Expanded
I recently posted on a new article series on Google Chrome for Linux that I’ve been developing over on Bright Hub. My exploration has turned out to be more engaging than I anticipated! At the moment, there are six articles in the series:
- Google Chrome for Linux: Building from Source
- Google Chrome for Linux: Testing and Contributing
- Google Chrome for Linux: The WebKit Web Browser Engine
- Google Chrome for Linux: The V8 JavaScript Engine
- Google Chrome for Linux: Why V8 Bests WebKit’s JavaScript Engine
- Google Chrome for Linux: Android Availability
I anticipate a few more …
It’s also important to share that Google Chrome for Linux does not yet exist as an end-user application. Under the auspices of the Chromium Project, however, there is a significant amount of work underway. And because this work is taking place out in the open (Chromiun is an Open Source Project), now is an excellent time to engage – especially for serious enthusiasts.
RDF-ization: Is That What I’ve Been Up To?
Recently, on his blog, Kingsley Idehen wrote:
RDF-ization is a term used by the Semantic Web community to describe the process of generating RDF from non RDF Data Sources such as (X)HTML, Weblogs, Shared Bookmark Collections, Photo Galleries, Calendars, Contact Managers, Feed Subscriptions, Wikis, and other information resource collections.
Although Idehen identifies a number of data sources, he does not explicitly identify two data sources I’ve been spending a fair amount of time with over the past few years:
- One source of data is that generated by scientific instruments. With various colleagues, the semantic framework I’ve built around this data source allows for RDF-ization of scientific data from semi-structured ASCII to XML (specifically ESML) to RDF via GRDDL. (Please see the illustration.) In principle, it should be possible to further transform the RDF representation into OWL thus resulting in what I’ve referred to elsewhere as an informal ontology. (According to Morville as well as Shadbolt et al., the RDF-ization of the data sources Idehen identifies result in folksonomies, rather than informal ontologies.) Again with various colleagues, I’ve also made use of RDF to annotate features inherent in the scientific data via XML Pointer Language (XPointer).
- Even more recently, with members of my Network Operations team at York University, I’ve been working with a relational database as a source of data on the topology of IP networks. (Please see the illustration.)
Of course, whether the motivation is personal/social-networking or scientific/IT related, the attention to RDF-ization is win-win for all stakeholders. Why? Anything that accelerates the RDF-ization of non-RDF data sources brings us that much closer to realizing the true value of the Semantic Web.
What You Will/Won’t Get with Stainless
Earlier today, I started to evaluate Stainless. In this post, it’s my intention to dig a little deeper by sharing more of what you will and won’t get with Stainless.
- Private Browsing – On selecting “File \ New Private Browsing Window”, the Stainless browser that appears makes use of WebKit‘s private browsing mode. In this mode, global history, page caching and storing of AutoFill information are disabled. Spawned tabs and windows inherit the private-browsing mode.
- Single-Point-of-Entry – Obviously you can type in a URL. However, you can also type in a text string (e.g., “Google Chrome”) to initiate a search via Google. In fact, via Stainless’ “Preferences”, you can choose to make use of Google, Yahoo!, Live Search, AOL or Ask.
- Process Management – I alluded to the multiprocess capability of Stainless in the previous post. I’ve just realized that by selecting “Window \ Process Manager” you can monitor and even terminate processes via a simple GUI. Very nice!
- Downloading Capability – I tried to download from a few sites … and all attempts FAILED!! I am shocked and amazed. I saw a Page loading error: Frame load interrupted message appear in the status bar each time … This is disappointing and will hopefully be fixed in version 0.2.
- History – Via Stainless’ “Back” button, there is some notion of history, but that’s it.
- URL Caching/Auto-Completion – URL caching and auto-completion are unavailable.
- An Open Source Version – There’s a significant Open Source aspect to Chrome. Based on proprietary technology developed by Mesa Dynamics for their Hypercube personal-widgetsphere offering, Stainless and Open Source seem unlikely to resonate.
- Cross-Platform Support – Stainless is available for Mac OS X Leopard. Will this offering will be broadened? Unknown.
- Extensibility – This killer functionality is a core competence of Mozilla Firefox. It appears that Chrome will sport something analogous. Stainless? Unknown?
- Offline Mode – I’m thinking of something along the lines of Google Gears … but I don’t see it arriving soon … I installed Gears for Safari. Unfortunately, Stainless gives me the impression that I have Gears support, but in reality (during an offline situation) it’s clear that I don’t. Misleading.
Despite the negatives, I expect to continue to make use of Stainless, and encourage you to do the same.
