Top_bar_btn_squeeze

Data.gov

In giving evidence before the - Victorian Parliament - Economic Development and Infrastructure Committee’s  Inquiry into Improving Access to Victorian Public Sector Information and Data my sister Professor Anne Fitzgerald quoted a passage from an article published in the Yale Journal of Law and Technology which addressed the role that the US federal government should have in modernising its internet infrastructure:

In order for public data to benefit from the same innovation and dynamism that characterize private parties’ use of the Internet, the federal government must reimagine its role as an information provider. Rather than struggling, as it currently does, to design sites that meet each enduser need, it should focus on creating a simple, reliable and publicly accessible infrastructure that “exposes” the underlying data. Private actors, either nonprofit or commercial, are better suited to deliver government information to citizens and can constantly create and reshape the tools individuals use to find and leverage public data. The best way to ensure that the government allows private parties to compete on equal terms in the provision of government data is to require that federal websites themselves use the same open systems for accessing the underlying data as they make available to the public at large. 328 (David Robinson, Harlan Yu, William Zeller, Edward Felten, ‘Government data and the invisible hand’, Yale Journal of Law and Technology, vol. 11, no. Fall 2008).

The Economic Development and Infrastructure Committee’s report quoted this evidence (at page 109)

The establishment of the Data.gov website in the US embodies this philosophy. (See as background President Obama’s Memorandum for the Heads of Executive Departments and Agencies : Transparency and Open Government (January 2009))

The Data.gov website explains its role as follows:

About

The purpose of Data.gov is to increase public access to high value, machine readable datasets generated by the Executive Branch of the Federal Government.

As a priority Open Government Initiative for President Obama’s administration, Data.gov increases the ability of the public to easily find, download, and use datasets that are generated and held by the Federal Government. Data.gov provides descriptions of the Federal datasets (metadata), information about how to access the datasets, and tools that leverage government datasets. The data catalogs will continue to grow as datasets are added. Federal, Executive Branch data are included in the first version of Data.gov.

Participatory Democracy

Public participation and collaboration will be one of the keys to the success of Data.gov. Data.gov enables the public to participate in government by providing downloadable Federal datasets to build applications, conduct analyses, and perform research. Data.gov will continue to improve based on feedback, comments, and recommendations from the public and therefore we encourage individuals to suggest datasets they’d like to see, rate and comment on current datasets, and suggest ways to improve the site.

Goal

A primary goal of Data.gov is to improve access to Federal data and expand creative use of those data beyond the walls of government by encouraging innovative ideas (e.g., web applications). Data.gov strives to make government more transparent and is committed to creating an unprecedented level of openness in Government. The openness derived from Data.gov will strengthen our Nation’s democracy and promote efficiency and effectiveness in Government.

For some interesting examples of what can be done see Rewired State (UK)

It’s a mere two weeks til the Freebase Hack Day and Unconference on July 11th in San Francisco. If you haven’t yet signed up, you should!

Plans are coming together. We’re starting to organise some projects to hack on and hunt down people to run sessions in the unconference. If you’ve got a project or a subject area you’d like covered, let us know! So far, some of the exciting topics that will be part of Hack Day include:

  • We’ll be launching Acre 1.0 just a few days before Hack Day. Jason Douglas will be showing off the features of our hosted app development platform, including the ability to share and clone apps, connect to other APIs with our keystore and OAuth, and build queries and templated web pages based on Freebase data more easily than ever before. Acre’s come a long way since our last Hack Day, so don’t miss this. (Read more about Acre.)
  • The MQL Boot Camp will be run this year by Bryan Culbertson. Learn how to query against Freebase’s structured data about almost 6 million topics, and see the new features of our query editor, including tab-completion for syntax and schema. (Read more about MQL and the query editor).
  • Learn how to use Freebase to enhance your website with structured data, like the Wall Street Journal, or build entire apps and websites on Acre, like Tippify.
  • Hack on apps like our Games With A Purpose, a TV program schedule mashup, and more. If you have a project and you’re looking for partners, technical help, or ideas, bring it with you! We’re also working on having a handful of projects ready for people to hack on who haven’t brought one of their own.)
  • Find out about how Freebase’s part in the Linked Open Data world, and how to use Semantic Web techniques and tools to work with Freebase data.

Same as last time, we’ll have three meeting rooms available for presentations, discussions, and other unconference programming, while our main lunch room area and lounge will be available for general hacking and chat. Come prepared to talk about what interests you, share your ideas, and collaborate!

This event is completely free, but places are limited.


Coffee, lunch, and snacks will be provided, including vegetarian options. Unfortunately we can’t offer childcare or kids’ activities at this time, but parents of babies are welcome to bring them.

Please help us spread the word. Link to this blog post, or to http://freebasehackday.eventbrite.com/, tweet about the event, or just tell your friends and colleagues. It’s going to be a great event!

If you are a movie fan, you might have noticed that The Wall Street Journal recently joined the Freebase developer community, integrating Freebase content into film reviews on WSJ.com.

Most noticeably, each review now features a widget on the right-hand side (called “Films Mentioned In This Article”) that provides the reader with useful information about all of the films that are reviewed on that page. It includes the film name, image, director, and cast, along with links to useful third party sites like Netflix and Rotten Tomatoes, and links to related film reviews on WSJ.com:

wsj widget

All of this is powered by the free data, images, relationships, and third party identifiers stored in Freebase.

At the top of this widget, there is also a search box powered by Freebase Suggest. This allows visitors to WSJ.com to easily search the WSJ film review archives and discover similar films they might not have known about. Because the search box uses Freebase Suggest, it takes advantage of our handy autocomplete feature, shows previews of each entry, and limits the results set specifically to films that appear in the WSJ index. Pretty cool!

wsj search

Behind the scenes, the app users other publisher-friendly features, like an editorial tool that allows the WSJ team to review all changes made to the data before it goes live on WSJ.com.

We’re excited to see open data from Freebase being integrated into more sites across the Web and to have sites like the Wall Street Journal contributing back to Freebase. If you are interested in having similar content integrated into your site, please let us know! It’s all powered by Acre and Freebase Suggest, so the same tools can be cloned and reused anywhere else on the Web.

This is not strictly PHP, but it is about scalability, and every PHP programmer *ought* to be thinking about this stuff. Theo Schlossnagle of OmniTI (where I work as a web architect) has this slide deck posted about Scalable Internet Architecture: Scalable Internet Architecture View more presentations from postwait. via http://www.slideshare.net/postwait/scalable-internet-architecture (Aside: I joke that at OmniTI, my reporting chain [...]

A recent article by Tim Berners-Lee, “Putting Government Data online“, has  attracted significant interest to the  datasets published at the US data.gov website.  As Berners-Lee discusses the Semantic Web techniques that can be used to get those data into RDF space (something we are now working on), we would like to share our initial investigation of the contents of these government datasets.

I. Translate dataset into RDF

The catalog of the datasets in data.gov,http://www.data.gov/details/92,  is published in CSV format as part of data.gov. We  converted it into RDF using simple CSV parsing. We kept the translation minimal: (i) the properties are directly created from thecolumn names; (ii) each table row is mapped to an instance of pmlp:Dataset; (iii) all non-header cells are mapped to a literal - we don’t create new URIs at this point. The output of our work is published on tw website at:

http://data-gov.tw.rpi.edu/raw/92/catalog.rdf

(We are now starting to do more  integration work, extracting multiple objects from single tables, linking into the linked open data  cloud, etc.  and will publish new version when that is done - the purpose of this first work was simply to make the catalog more available to the RDF community)

II. Browse and query the RDF graph

As an example, we can browse the dataset in tabulator, and then use a SPARQL webservice to query the dataset. For example, we use a sparql query to list datasets published in CSV format:

http://onto.rpi.edu/sw4j/sparql?queryURL=http://data-gov.tw.rpi.edu/sparql/select-csv-dataset.sparql

III. Observations on the RDF graph

Using this service we can answer some basic questions about the data.gov datatsets:

1. How many datasets are published, and how many among them can be easily converted into RDF?

There are 332 datasets which can be partitioned by  type:  raw data catalog(301);  tool catalog (31).

Not all of the datasets have a link to downloadable data because some offer only browseable data via their own websites,  Others  publish datasets in multiple formats. As of today, the online static files associated with the datasets are distributed as  follows:  204 datasets offer a CSV format dump, 10 datasets offer an XML format dump, and 21 datasets offer an XLS format dump.

2. How are the datasets categorized?

Category number of datasets
Geography and Environment 227
Labor Force, Employment, and Earnings 30
Social Insurance and Human Services 30
Health and Nutrition 11
Law Enforcement, Courts, and Prisons 7
Population 4
Other 3
Prices 3
Business Enterprise 2
Education 2
Energy and Utilities 2
Federal Government Finances and Employment 2
Income, Expenditures, Poverty, and Wealth 2
Science and Technology 2
Transportation 2
Construction and Housing 1
International Statistics 1
National Security and Veterans Affairs 1

3. What are some of the key items in the dataset?

4. What are the  sources of the datasets?

The majority of the datasets are published by the EPA, and they contain environmental data partitioned by the states of the US in three individual years.  Others come from other govt agencies - the distribution is as follows:

IV. Getting Datasets linked

Although the datasets are not explicily linked, we see a number of opportunities for connecting these datasets to others (and into the Linked Open Data datasets):

  • A large percentage of files have some sort of geo-tagging, thus they can be linked to DBpedia or Geo-names (and then presented via Map services).
  • Some datasets are subsets of other datasets, e.g. EPA data “2005 Toxics Release Inventory data for the state of Georgia” is a subset of  “2005 Toxics Release Inventory National data file of all US States and Territories” making for easier “internal” linking of the datasets.
  • A number of the datasets contain temporal information, e.g. IRS’s “Tax Year 1992 Private Foundations Study”,…”Tax Year 2005 Private Foundations Study” which provides an opportunity for mashups using timelines and such.

V. Conclusions

We are committed to getting more of the data.gov data online soon (in RDF), and then investigating data integration and knowledge discovery. In order to get our datasets linked to the linked data cloud, we will use SPARQL for extracting entities and our Semantic Mediawiki as a platform to capture the owl:sameAs mappings.  Scalable dataset publishing is also challenging as some of these are very large datasets, e.g. “2005-2007 American Community Survey Three-Year PUMS Population File” has a 1.1 g zipped csv file.  Moreover, some datasets are not directly available in one file but via a web service.  Our current plan is to produce RDF documents available for download soon, and to work on bringing more of these datasets into live, SPARQLable forms as we can.

Li Ding, Dominic DiFranzo and Jim Hendler

It almost happened, but it didn't for now. Originally we planned to release today. But again a few issues came up, even with Johannes deciding that sleep is for the weak, it just seemed unwise to announce the release today. So we pushed things back a few days, so the new date is June 30th (meaning it will be a Tuesday release). This also gives the documentation team, who have been expanding the 5.3 docs like crazy, a few more days to beef things up even more. Now is really high time to ensure that you have a PHP 5.3 compatible release of your software ..

Via reddit: The goto documentation got an xkcd overhaul. :)

Australia now has a government 2.0 taskforce.

AUD $2.45 million of funding to web 2.0-ify the Australian government.

Here's some ideas, to get you started:

CrimeTweet - A twitter like application, based on identi.ca, Google Maps API, and Zemanta.

Our local police force has someone publishing crimes on the front page of their website, which is also fed out to newspapers.

Why not provide an identi.ca client which lets you tweet about crimes?
Use a tool like Zemanta to linkify keywords, and google maps API to add an approximate geolocation (say, street level accurate). You add in structured data (RDFa?) too.

Effort? I'd peg it at 2 months to get it polished; and then it's a matter of getting police forces to use it.

Benefits: A much tighter integration with citizen police groups (neighbourhood watch), and the ability to do crime maps / analyze the data.


Idea 2: As above, but expand it out to neighbourhood watch people, give them easy tools to upload photos of minor crimes (ie, graffiti).


Idea 3: Stolen goods register, powered by Freebase.
You use a Freebase suggest control to help people tag consumer goods / get pictures of said goods, plus a bit of storage for serial numbers and descriptions.

You provide RSS feeds / emails to all local pawn shops, cash convertors, etc.

Reblog this post [with Zemanta]

Maurice Svay has a new blog post that includes a script he's developed to perform facial recognition (detect faces in images) with PHP without the need of the Open-CV library.

OpenCV seems to perform well but you need to be able to install it on your server. In my case, I wanted to have a pure PHP solution, so it can work with most hosts. So I started to think about implementing it myself. [...] I kept searching and finally found a canvas+javascript implementation of face detection at http://blog.kpicturebooth.com/?p=8. The code looked fairly compact and simple. Shouldn't be hard to port to PHP.

The class takes in the filename of an image (just JPG, but could easily be adapted) and a data file to use to run the image through the GD image library and output a JPG similar to this with the face highlighted by a red square.

Photos
title

CloCkWeRX posted a photo:

title

Today, at the longest day of the year at the summer solstice, I am making a bit change to my life. If you're following me on twitter you probably already know what I'm up to. For everybody else, I am going to say good bye to Skien in Norway, and move to London (the one in England, and not the one in Ontario). Norway has been my home for the past five years, and I've had a great time exploring the nature as well as working at our office in Skien. Skien is a nice place, but ... not the most interesting of cities in the world. From today I will be living in London to see what life will bring me there. I am both sad to leave Norway, but I am also excited to live in a cool new place like London. I'll have awesome house mates (Hi, Mr. Þorbjörnsson, Ms. Cherry and Mr. Ray!!), and something new to put my energy in. I will continue to work as project leader for eZ Components for eZ Systems and continue to make great software with Alexandru, Tobias, Kore and Sebastian. If you are about in London, let me know! We could go for a pint or something. See you there!

Ubuntu's next release will have one hundred paper cuts as a focus - fixing usability issues for users.

Here's my best pet peeves.

  1. On windows, if I paste in a URL in an "open file" box, windows will fetch it for me, write it somewhere temporary, and give me that temporary path. Gnome is inconsistent - I can put a URL into a the 'Run' dialog, but gedit doesn't let me open it. However, if I start gedit from the command line, it will open it - gedit https://edge.launchpad.net/hundredpapercuts/
  2. 'Choose another application' when opening a file from firefox gets me to try and look around for the path of an application. As a newer user to linux, I often have to fall back to the terminal, and use things like 'which gedit' to get the right path. If the run dialog can work out which application I want, why can't firefox.
  3. With gedit, if I open a file which does not exist, it does not let me create said file - it just errors at me.


https://bugs.edge.launchpad.net/hundredpapercuts/+bug/18995





Reblog this post [with Zemanta]
June is here, and things are beginning to pick up again.

We've welcomed Rodrigo Sampaio Primo, probably better known for his efforts with TikiWiki and elsewhere, Peter Bittner joined us to feed back some of his Open Document improvements, we've seen the feature and bugfix releases of Services_Amazon_SQS, Net_LDAP2, Console_Commandline, XML_Serializer, PHP_UML, Payment_DTA, Net_UserAgent_Detect, Net_DNS, Services_Facebook, Testing_DocTest and Net_Nmap.

Christian Weiske has been working on getting Open Document back into shape, Greg Beaver is once again helping us move forward to elect a new PEAR group, as well as getting the next version of the PEAR installer ready for testing.

Slightly worrying, we haven't heard much from Amir since the elections in Iran, and he hasn't been on IRC.

PHP 5.3 isn't far off, and I think it's fair to suggest that we've all got a subdued sense of excitement about it. That, and the consumption of a metric tonne of meat.



Reblog this post [with Zemanta]
A few hours ago, 11th release of PHP 5.2, 5.2.10 was released to the world. This, as most past 5.2.X releases has been largely focused on bug fixing with quite a few obscure crashes and memory leaks being addressed, in addition to a single security fix in the exif_read_data() function. All in all there are over 100 individual bug fixes in this release and most 5.2.X and definitely all 4.X users should consider upgrading to this version.

The sources and windows binaries for this release can be found at http://www.php.net/downloads.php and the detailed changelog itemizing all of the changes can be seen here.
I've always wondered if I had a part in spawning the firefox crop circle.

I posted to spreadfirefox.com back in 2004.

Amusing thought - Crop Circles
Posted by CloCkWeRX on Fri, 10/22/2004 - 16:42Firefox Marketing Ideas

:) Speaks for itself. Ties into the Nov. 9. mystery and ILoveBees ideas.

"Something is coming.
Something big.
Something alien to most of us...
Something that's from out of this world..."

First off, you need a field. Second, you need a manual. Third, you need a worried farmer.


Come 2006, they made the crop circle.

They give credit to some Mozilla folk.


Matt and John, Mozilla video interns, came up with the idea a few weeks beforehand. Fueled by the enthusiasm of Asa Dotzler at Mozilla, suddenly the crop circle was within reach. While at OSCON 2006 in Portland, the three of them ran into members of the OSLUG, and things really started to take shape.



Whoever really generated the idea, it gives me no end of pleasure that it's hitting back at the horrible Microsoft marketing campaign, bribing users to switch to IE8 while insulting the rest of us.




Reblog this post [with Zemanta]
I don't know about you, but i'm damn excited about the upcoming version of Ubuntu, so it better deliver! As usual, there will be tons of bug fixes, updated packages, tighter integration, as well as increased stability and usability. All talk so far. The One Hundred Paper Cuts campign looks promising on providing even more usability enhancements. Aside from a new Ubiquity slideshow for new users, what specific things are there to look forward to?

Before i start, i must give good mention to PlayDeb, which should be back up for Karmic! Gaming needs some leverage in Ubuntu. PlayDeb is a third-party repository you can add to Ubuntu for all of the latest games available that aren't included in the Ubuntu repos. I can easily install and play StepMania 4 and Yo Frankie! (even if it doesn't make it into Ubuntu).

Sorry for the lack of pictures and a more detailed breakdown, but i'm sure you will see much of that will develop over the coming weeks. This list should hold you off until then:
  1. New Theme
  2. I list this first because we've been promised this for so long, and even though we were promised it was actually happening in Karmic, i'm just not so sure anymore. I hope to see it, but i won't set myself up to be crushed if we don't =]
  3. Flawless PulseAudio
  4. Oh yes, we've been waiting on this for all too long. Audio should finally be close to perfect. If you're like me, and haven't had any real problems with it, please move along to the next item.
  5. Firefox 3.5
  6. The wonderful new version of Mozilla Firefox that adds support for Ogg Theora/Vorbis, audio and video, respectively for HTML 5's Open Web Video (also supported in Midori using WebKit) should be a significant upgrade from the current version.
  7. Faster Boot Times
  8. This is a general thing that we should see improve a lot in Karmic and Karmic +1. Self-explanatory, move along now.
  9. Ext4 now Default
  10. Ext4 support was just added in 9.04, and now it will be the default for new installs of 9.10. If you don't know already, Ext4 brings a lot of nice changes, over Ext3, and will generally improve filesystem performance.
  11. GNU GRUB 2
  12. The boot loader for new installation will now be GNU GRUB 2, which is a complete rewrite of GRUB which make it faster, cleaner, safer, as well as more robust, portable, and powerful.
  13. Plymouth
  14. Goodbye, USpash! Plymouth will be making our graphical boot experiance cleaner with no more of that annoying flickering of the display at startup. It makes Ubuntu look more polished, or at least less unpolised. [Update, see  below]
  15. New Linux Kernel
  16. The newest Linux Kernel 2.6.31 will be included in which we can hope to see ATI kernel-based mode-setting (KMS) and memory managemnt support in. The current 2.6.30 Kernel will already be old by then.
  17. New Intel Drivers
  18. Again, this will solve major performance problems that Ubuntu Jaunty 9.04 had with Intel drivers. Gah, i hate Intel. Sorry, i had to throw that in there.
  19. New NVIDIA Drivers
  20. The new NVIDIA drivers add VDPAU and CUDA support resulting in, you guessed it-- more performance enhancements!
  21. GNOME 2.28 (and Testing GNOME 3)
  22. Not only will Ubuntu ship with all the enhancements of GNOME 2.28, but users will be able to test GNOME 3 in Karmic! Cool stuff.
  23. PackageKit
  24. Oh yes. It's a much nicer way to manage and update applications than Add/Remove and Update Manager that actually uses PolicyKit. This will certainly be quite a refreshing change.
  25. Empathy
  26. Lastly, the most controversial of the changes, Empathy will take the place of both Pidgin and Ekiga. I would like to take this opportunity to support this decision. Hopefully, even if you still prefer Pidgin for yourself, you can appreciate what Empathy brings for new users. It has been discussed for over half a year at UDS Jaunty and Karmic, and there are a number of reasons it should happen:
    New users: Pidgin has lots of features and plugins that may cater to some of us just better, but Empathy has a friendlier UI for new users. We want to make Ubuntu the best experience for those migrating to it. The rest of us have no trouble keeping Pidgin.
    Integration: Empathy integrates well into the GNOME desktop. A lot of cool stuff is possible with it. 'Nuff said (you can learn more on your own).
    Features: Empathy is mostly feature complete, and the lack of OTR is something that new users will not know or use. I agree it is important, but it is still available in Pidgin until Empathy implements it.
    Telepathy: Empathy uses the awesome Telepathy framework. It supports libpurple for all networks only currently in Pidgin.
    Voice/Video: Empathy already has VoIP support for audio and video chatting, which means it can replace both Pidgin and Ekiga.
    Feature Gap: Yes, Telepathy might be a tiny bit behind in a few places, but none of them are showstoppers, and it is far ahead in others. Including it in Karmic will mean that the feature gap between Empathy and Pidgin will close and reverse much sooner, not to mention we'd like Empathy to be awesome in Ubuntu Karmic +1 10.04 LTS.

P.S. Today is Empathy Hug Day! Let's all give it some love.

Update: My bad, Plymouth has been dropped to focus on making Ubuntu boot in under ten seconds which would make Plymouth worthless.

I am proud to announce the release the websites of two of our products to come: structWSF and conStruct. Both products will be available in open source under the Apache 2 license. Mike just unveiled and demoed the two projects in his talk at SemTech 2009.

As we describe them on Structured Dynamics‘ website:

structWSF

structWSF is a platform-independent Web services framework for accessing and exposing structured� RDF data. Its central organizing perspective is that of the dataset. These datasets contain instance records, with the structural relationships amongst the data and their attributes and concepts defined via ontologies (schema with accompanying vocabularies).

The structWSF middleware framework is fully RESTful in design and is based on HTTP and Web protocols and open standards. The initial structWSF framework comes packaged with a baseline set of about a dozen Web services in CRUD, browse, search and export and import.

All Web services are exposed via APIs and SPARQL endpoints. Each request to an individual Web service returns an HTTP status and optionally a document of resultsets. Each results document can be serialized in many ways, and may be expressed as either RDF or pure XML.

In initial release, structWSF has direct interfaces to the Virtuoso RDF triple store (via ODBC, and later HTTP) and the Solr faceted, full-text search engine (via HTTP). However, structWSF has been designed to be fully platform-independent. Support for additional datastores and engines is planned. The design also allows other specialized systems to be included, such as analysis or advanced inference engines.

The framework is open source (Apache 2 license) and designed for extensibility. structWSF and its extensions and enhancements are distributed and documented on the OpenStructs Web site.

conStruct

conStruct SCS is a structured content system that extends the basic Drupal content management framework. conStruct� enables structured data and its controlling vocabularies (ontologies) to drive applications and user interfaces.

Users and groups can flexibly access and manage any or all datasets exposed by the system depending on roles and permissions. Report and presentation templates are easily defined, styled or modified based on the underlying datasets and structure. Collaboration networks can readily be established across multiple installations and non-Drupal endpoints. Powerful linked data integration can be included to embrace data anywhere on the Web.

Depending on roles and permissions, a given user may or may not see specific datasets or tools within the Drupal interface. Search and browse results are similarly sequestered depending on access rights.

conStruct provides Drupal-level CRUD (create - read - update - delete), data display templating, faceted browsing, full-text search, and import and export over structured data stores based on RDF. It also provides a system for additional tools additions and expansions for this structured data. conStruct SCS is built on the platform-independent structWSF Web services framework.

Like Drupal and structWSF, conStruct is free and open source (GPL license). Versions of conStruct SCS are planned to adopt it to other content management systems (CMS).

Next

The alpha version of the code with all the proper documentation will be released later this summer. Everybody will be able to contribute to the project by enhancing/developing the core code or by extending it with new modules and web services. Stay tuned!

Photos
compliance_qs

CloCkWeRX posted a photo:

compliance_qs

I'm happy to announce CommonTag, a new RDFS vocabulary for Semantic Tagging, designed to bridge the gap between free-text tagging and Linked Data. In a similar way that what I've done in the past with MOAT, CommonTag allows one to create links between his tags (as simple keywords) and the concept they represent, defined as URIs of Semantic Web resources, from public knowledge bases such as Freebase or DBpedia.

What is especially relevant with regards to CommonTag is that the vocabulary aims to be simple to understand, easily accessible, and with an easy RDFa annotation process for end-users and Web developers. On the other hand, it features mappings with existing tagging vocabularies (the Tag Ontology, MOAT, SCOT, SIOC and SKOS) for those who want to go further or use their existing applications with this new model.

But most interestingly, as one can see when browsing the website, a key feature is that CommonTag is not an isolated initiative but supported by various companies involved in the Semantic Web and the Social Web -- and especially in both ! -- namely (for the initial nucleus and by alphabetical order, hope it will grow soon !) AdaptiveBlue, DERI (NUI Galway), Faviki, Freebase, Yahoo, Zemanta and ZigTag - and I must add that was a great experience to design this vocabulary together !

CommonTag is already supported in various applications as you can see on the website and on the following picture, from Zemanta to index your blog posts to Sindice to build applications on the top of it. And there is more to come soon, stay tuned ;-)

Pages:      1 2 3 ... 97 Next

recently listened to:
  • FROG THE DAWG – DMX vs. Rob Zombie
  • Pimpdaddysupreme – Thriller Shake (Thriller vs. Ying Yang Twins Feat. Pitbull)
  • The Dandy Warhols – Your Ghost
  • LCDremixed.com – Someone Great (Shokking Shokkaboy Remix)
  • DJ Morgoth – Black Metal Pogo (German Version) [Ascii.Disko vs. Planetakis]
  • Celldweller – The Last Firstborn
  • Celldweller – Stay With Me (Unlikely)
  • Celldweller – Switchback
  • The Wombats – Let's Dance to Joy Division
  • M.I.A. – Boyz
via last.fm
sponsor
time tracking harvest

Harvest - Simple time tracking, powerful reporting.

Suprss
(Subscribe to this page via RSS!)