What is the Open Web? I just arrived at O'Reilly's Sebastopol Campus where they're holding a *Camp event on the open web, eponymously named "Open Web Foo Camp". A few days ago I was speaking with Jim Dwyer of the New York Times about the Federated Indie Social Web vs. sharecropping and site death (more on that in another post), and he happened to ask me (probably because I mentioned it in passing), what is, or what do I mean by "the open web". At the time I didn't have a working definition, but apparently provided an answer good enough for a self-described non-technical journalist to "get" what is the open web. Here's roughly what I told Jim, off the top of my head: For me the Open Web is about the ability to openly do three kinds things: publish content and applications on the web in open standardscode and implement the web standards that that content/apps depend onaccess and use content / code / web-apps / implementations Each of these merit a bit of expansion.
Publishing content and applications Translations. Linked Data Patterns. XHTML+RDFa: chemical examples. Microdata: HTML5âs Best-Kept Secret | Webmonkey | Wired.com. Given the amount of industry noise about native video and scripted animations, you’d be forgiven if you had never heard of the new microdata specification included in HTML5. Similar to outside efforts like Microformats, HTML5′s microdata offers a way of extend HTML by adding custom vocabularies to your pages.
The easiest way to understand it is to consider a common use case. Let’s say you want list details about a business on your page — the name, address, telephone number and so on. To do that you’ll need to use some vocabulary in addition to HTML, since there is no <business> tag. Using microdata, you can create your own custom name/value pairs to define a vocabulary that describes a business listing. When a search engine spider comes along, it will know that not only is your data a business listing, but it can discover the address, the phone number, or even the precise geo-coordinates if you want to include them. Given that HTML5 is still a draft at this point, why bother? Microdata. HTML5 Microdata: Why isnât anyone talking about it? Written by Brian Cray on September 8th, 2010 Many big web design blogs are raving about HTML5, as they should be. But if you read many of them, [1, 2, 3], you'll be bombarded with an over-publicizing of header, article, footer, et. al tags, which reminds me of circa 2002 when we were all jumping onto the XHTML bandwagon.
But 8 years later where'd XHTML get us? Suddenly we're moving back to HTML. Why? XHTML provided no actual benefits. HTML5 on the other hand is bringing with it a ton of actually useful technologies, including much needed advances in HTML forms, native video support, and a vector API/canvas. But back to circa 2010/2002-wannabe. So my fellow web design bloggers: let's shift our focus to something that's a part of the HTML5 definition, changes the way we write tags, and has actual benefits: Microdata. A few web design blogs, including one of my favorites, NETTUTS, has covered Microdata briefly, and I want to add some more fuel to the conversation. What is HTML5 Microdata? FISE - Enhancement Engines. Annotation-ontology - Project Hosting on Google Code. Ciccarese P, Ocana M, Castro LJG, Das S, Clark, T. An Open Annotation Ontology for Science on Web 3.0. J Biomed Semantics 2011, 2(Suppl 2):S4 (17 May 2011) Please read this carefully: Specification is undergoing changes.
The Annotation Ontology specification is currently used as input for the activities of the W3C Open Annotation Community Group that works towards a common, RDF-based, specification for annotating digital resources. The Group effort starts by working towards a reconciliation of two proposals that have emerged over the past two years: the Annotation Ontology and the Open Annotation Model. AO: Annotation Ontology The Annotation Ontology is a vocabulary for performing several types of annotation - comment, entities annotation (or semantic tags), textual annotation (classic tags), notes, examples, erratum... - on any kind of electronic document (text, images, audio, tables...) and document parts. Author: Contact: paolo -dot- ciccarese -at- gmail -dot- com Contributors: Media Fragments URI 1.0. Representing Content in RDF 1.0. [contents] Abstract This document is a specification for a vocabulary to represent content in the Resource Description Framework (RDF).
This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by web quality assurance tools such as web accessibility evaluation tools to record a representation of the assessed web content, including text, images, or other types of formats. In many cases, it can be used together with HTTP Vocabulary in RDF 1.0, which allows quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. This is particularly useful for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). Status of this document This section describes the status of this document at the time of its publication.
Table of Contents <? Untitled. ISO 3166 RDF Representation. Latest version: This version: Previous version: Author: Scott Martin Copyright © 2005 Scott Martin. This work is licensed under a Creative Commons License. Abstract This resource acts as a simple representation of the ISO 3166 definitions of country names. Usage Following is an example of a simple RDF document, using WAIL and this vocabulary, referencing the United Kingdom. <rdf:RDF xmlns:dc = " xmlns:rdf = " xmlns:wail = " ><rdf:Description><dc:title>Something</dc:title><wail:locatedIn><wail:Country rdf:about=" /></wail:locatedIn></rdf:Description></rdf:RDF> Note the URI pointing to the fragment of the schema that represents the United Kingdom.
Defining schema name alpha_2 alpha_3 Changes since last version. Open Knowledge Foundation Blog. Southampton ECS Web Team › The Modeller. I’ve invented a new Batman villain. His name is “The Modeller” and his scheme is to model Gotham city entirely accurately in a way that is of no practical value to anybody. He has an OWL which sits on his shoulder which has the power to absorb huge amounts of time and energy. The Modeller In the first issue, “Batman vs the Modeller” the modeller gets away by confusing batman as to exactly which incarnation he currently is (Frank Miller, Golden age or Batman Begins) which forces Batman into an identity crisis where he registers different URIs and FOAF profiles for Batman and Bruce Wayne.
Over the 3 issues there’s a running subplot about the modelers master weapon, the FRBR, which everyone knows is very very powerful but when the citizens of Gotham talk about it none of them can quite agree on exactly what it does. While unpopular with the fans, issue two, “Batman vs the Protégé“, will later be hailed as a Kafkaesque masterpiece. I’m interested to see if I get any outraged comments. Welcome to Linked Open Data Around the Clock | Linked Open Data Around-The-Clock. Semantic Copyright. Introducing fise, the Open Source RESTful Semantic Engine, Nuxeo Developers Blog. Edit: fise is now known as the Stanbol Enhancer component of the Apache Stanbol incubating project. As a member of the IKS european project Nuxeo contributes to the development of an Open Source software project named fise whose goal is to help bring new and trendy semantic features to CMS by giving developers a stack of reusable HTTP semantic services to build upon.
As such concepts might be new to some readers, the first part of this blog post is presented as a Q&A. What is a Semantic Engine? A semantic engine is a software component that extracts the meaning of a electronic document to organize it as partially structured knowledge and not just as a piece of unstructured text content. Current semantic engines can typically: categorize documents (is this document written in English, Spanish, Chinese? During the last couple of years, many such engines have been made available through web-based API such as Open Calais, Zemanta and Evri just to name a few.
How to use fise? The engines endpoint. S foaf stories | the web, the world, us, you and them. Very raw, sometimes verbatim but doubtless flawed notes from Harry Wood‘s excellent talk at Open Data Institute in London. #odifridays Many thanks to Harry for a great talk and to ODI for putting together these lunchtime lectures. The ODI have also published slides and audio from the talk. “An introduction to OpenStreetMap, the UK born project to map the world as open data, and a look at how volunteer mappers helped with disaster response in the Philippines after Typhoon Haiyan, with Harry Wood . Harry is a developer at transportAPI.com, and is on the board of the Humanitarian OpenStreetMap Team.”
Note: this is un-checked, very raw notes that I typed while listening. Typhoons …phillipines area hammered during typhoon season. [shows video clip] More than 6000 died. Q: who has edited OSM? Maps … GIS / vector data will always be a bit complex, but we try to dumb it down. But the maps are a important aspect of disaster response. OSM editing -> appear on map can take ~ 10 mins. [end] A Quick demo. Code 4 Lib 2010 The Linked Library Data Cloud: Stop Talking and Start Doing. The Registry! :: home. The Fate of the Semantic Web. Overview Sir Tim Berners-Lee, the inventor of the World Wide Web, has worked along with many others in the internet community for more than a decade to achieve his next big dream: the semantic web.
His vision is a web that allows software agents to carry out sophisticated tasks for users, making meaningful connections between bits of information so that “computers can perform more of the tedious work involved in finding, combining, and acting upon information on the web.” Some 895 experts responded to the invitation of the Pew Research Center’s Internet & American Life Project and Elon University’s Imagining the Internet Center to predict the likely progress toward achieving the goals of the semantic web by the year 2020.
Asked to think about the likelihood that Berners-Lee and his allies will realize their vision, often called Web 3.0, these technology experts and stakeholders were divided and often contentious. Some 47% agreed with the statement: Also in this report: » Survey method. Semantic Web For Hack Days. Extending HTML5 — Microformats. While HTML5 has a bunch of semantic elements, including new ones like <article> and <nav>, sometimes there just isn’t an element with the right meaning. What we want are ways to extend what we’ve got, to add extra semantics that are machine-readable — data that a browser, script, or robot can use. Native ways to extend HTML There were five fundamental ways we could extend HTML 4: <meta> elementclass attributerel attributerev attributeprofile attribute In HTML5, rev has fallen by the wayside, becoming obsolete since hardly anyone used it correctly, and because it can be replaced by rel. profile is also obsolete, and there is no support for namespaces in HTML5.
However, <meta>, class, and rel are all in HTML5. In fact, <meta> now has spec-defined names and a way to submit new name values, and rel has several new link types defined in the HTML5 specification and a way to submit more too. Finally there are microformats. Introducing microformats Microformat specifications Published microformats. Tingle's Technology Notes (linked data -- good for authority control) I Have Yet to Metadata I Didn’t Like. At the SemTech conference earlier this summer there was a kind of vuvuzela-like buzzing in the background. And, like the World Cup games on television, in play at the same time as the conference, I found the droning to be just as irritating. That droning was a combination of the sense of righteousness in the superiority of linked data matched with a reprise of the “chicken-and-egg” argument that plagued the early years of semantic Web advocacy [1].
I think both of these premises are misplaced. So, while I have been a fan and explicator of linked data for some time, I do not worship at its altar [2]. My main points are not against linked data. Observation #1: What Problem Are We Solving? When I began this blog more than five years ago — and when I left my career in population genetics nearly three decades before that — I did so because of my belief in the value of information to confer adaptive advantage. Observation #2: The Problem is Not A Lack of Consumable Data. SKOS Simple Knowledge Organization System - home page. SKOS is an area of work developing specifications and standards to support the use of knowledge organization systems (KOS) such as thesauri, classification schemes, subject heading lists and taxonomies within the framework of the Semantic Web ... [read more] Alignment between SKOS and new ISO 25964 thesaurus standard (2012-12-13) ISO 25964-1, published in 2011, replaced the previous thesaurus standards ISO 2788 and ISO 5964 (both now withdrawn).
Members of the Working Group responsible for ISO 25964 have gone on to consider the implications for SKOS users. From Chaos, Order: SKOS Recommendation Helps Organize Knowledge (2009-08-18) Today W3C announces a new standard that builds a bridge between the world of knowledge organization systems - including thesauri, classifications, subject headings, taxonomies, and folksonomies - and the linked data community, bringing benefits to both. Call for Review: SKOS Reference Proposed Recommendation (2009-06-15) Semantic Web. All things cataloged. HTML5 Forums :: View topic - Microdata implementation. Freebase. Swirrl: Online Database Software.