Preview release of RDFaCE special edition for Schema.org

During the last weeks I was working hard on the next release of RDFaCE . RDFaCE implements the WYSIWYM (What You See Is What You Mean) concept in order to facilitate the process of semantic content authoring.RDFaCE

The new version of RDFaCE is focused on Schema.org . You can create RDFa or Microdata annotations based on the schemas defined by schema.org. It will help to improve the SEO of your Website.

The main features of this new version include*:

Links:

*Of course it is only a preview release and might have some bugs.Please report the possible bugs using our issue tracker. As our next step, we will integrate the functionality of previous versions of RDFaCE with support for schema.org.

Advertisements

RDFaCE– Put a Smile on the Face of Semantic Content Authoring

In his influential paper “The Computer for the 21st Century” Mark Weiser talks about making machines fit the human environment instead of forcing humans to enter the machine’s environment. He notes, “The most profound technologies are those that disappear. They weave themselves into the fabric of everyday life until they are indistinguishable from it.”

When it comes to semantic content authoring the main question is how to  facilitate this process by removing the gap between content creation and content annotation. There are a lot of tools available for embedding semantic annotations within the Web content but one of the main obstacles  seen in promoting semantic content is the lack of intuitive and user-friendly semantic authoring tools.

  RDFaCE  (RDFa Content Editor ) is an online text editor based on TinyMCE. It supports authoring of RDFa content. In addition to two classical views for text authoring (WYSIWYG and Source Code view) , RDFaCE  supports two novel views for semantic content authoring namely WYSIWYM (What You See Is What You Mean) and Triple view (aka. Fact View). WYSIWYM view aims at displaying semantic annotaions on top of classical WYSIWYG view which is ubiqutous among people on the Web. It uses dynamic CSS stylesheets to distinguish semantic content from normal content. Triple view is another semantic view which only shows the facts (triples) stated in the text. RDFaCE provides a syncronizatiion between these four views so that changing in one view causes to change in the other views. Another feature supported in RDFaCE which empowers it in comparing to existing semantic editors is combining the results of multiple NLP APIs to facilitate semantic authoring process. This feature provides an initial set of annotations for users that can be modified and extended by them. a demo version of RDFaCE is available at http://rdface.aksw.org. For more informatiion you can visit here.

Schema.org : where business and academia could meet!

Recently Bing, Google and Yahoo! made an agreement to rely on a standard markup to improve the display of their search results, thereby making it easier for people to find the right web pages. They chose Microdata as annotation format to embed the types and properties of the content within the web pages. Microdata  is a new feature supported in HTML 5 which provides a mechanism to allow machine-readable data to be embedded in HTML documents in an easy-to-write manner, with an unambiguous parsing model. Schema.org aims at providing  a shared collection of schemas that webmasters can use for their Microdata markup.

That sounds a great news. It can be considered as a step towards realizing the semantic web. Then, what is the problem?!

There has been a long discussion in semantic web mailing list about this new announcement. Some people do agree on it as a progress to promote the semantic web efforts and some people criticize it  as a new revenue model for the web monsters. In this post I wanted to publish my thoughts about Schema.org approach.

The first question which comes to my mind in this context is: Why Microdata? Why not RDFa or either Microformat?

It looks great that three frontier companies on the web have come to a consensus. I really like and appreciate it. It is a moment that rarely can be seen on a tough competition unless there is  a win-win benefit out of it. But I believe doing a job well is better than doing just a good job when there is an opportunity. About choosing Microdata not RDFa or microformats, they mention:

“Focusing on microdata was a pragmatic decision. Supporting multiple syntaxes makes documentation for webmasters more complex and introduces more overhead in terms of defining new formats. Microformats are concise and easy to understand, but they don’t offer an open extensibility mechanism and the reuse of the class tag can cause conflicts with website CSS. RDFa is extensible and very expressive, but the substantial complexity of the language has contributed to slower adoption. Microdata is the most recent well-known standard, created along with HTML5. It strikes a balance between extensibility and simplicity, and is most suitable for building the schema.org. Google and Yahoo! have in the past supported both microformats and RDFa for certain schemas and will continue to support these syntaxes for those schemas. We will also be monitoring the web for RDFa and microformats adoption and if they pick up, we will look into supporting these syntaxes.”

I don’t think it is a good reasoning for a pragmatic decision. Simple is not always the better! As Samuel says, while there are a number of technical merits that speak in favor of RDFa over Microformats and Microdata (fully qualified vocabulary terms, prefix short-hand via CURIEs, accessibility-friendly, unified processing rules, etc. please take a look at this to see that RDFa is not really so complicated!), the main point is realizing of centralized innovation vs. distributed innovation. The web has always relied on distributed innovation and RDFa allows that sort of innovation to continue by solving the tenable problem of a semantics expression mechanism. Microdata has no such general purpose solution. Although it can facilitate one specific problem like searching data, it is not well scalable with the vision of semantic web. Schema.org as a centralized solution for web of data is really in conflict with the vision of making benefit out of distributed information islands. I wish they could make a better decision to speed up realizing a web of knowledge!