Developers that embed structured data in their web pages can choose among a number of languages such as RDFa, Microformats and Microdata. Each of these structured data languages, while incompatible at the syntax level, can be easily mapped to Rdf. Json has proven to be a highly useful object serialization and messaging replacement for Soap.
In an attempt to harmonize the representation of Link Data in Json, this specification outlines a common Json representation format for Linked Data that can be used to represent objects specified via RDFa, Microformats and Microdata.

There is currently some discussion going on in the RDFa Community on this markup mechanism (start of thread).
A great amount of effort was made to ensure that the markup mechanism was compatible with Microformats.

Accounting: Fabrizio Scatena
Graphic design: Enrico Caputo [CaroselloLab] and Lorenzo De Tomasi
Information architecture and usability: Lorenzo De Tomasi and Ania Maslova
Development: Francesco D’Ambrosio and Lorenzo De Tomasi
Content management system: Drupal

Internet changed the music industry. At first, sharing systems like Napster allowed people to share any song they had on their computer with millions other people. That new reality changed the music industry’s landscape for good, and many juridical battles followed. However, a biggest change followed a couple of years later. Communities like MySpace started to appear. Strong of millions of regular users, such communities helped garage bands and obscure musicians to create their musical niche: the longtail of the music industry. This second change is more profound than the first one: now any musician has the possibility to reach their audience by sharing their work on the Web. In the mean time, a free database called MusicBrainz archiving million of between artists, albums and tracks appeared; music suggesting services like Pandora or Last.FM started to appear and Apple started to sell individual tracks at 1$ with iTunes.
At that point, the music industry of the eighties leaded by blockbusters was completely changed.

The Music Ontology is an attempt to provide a vocabulary for linking a wide range music-related information, and to provide a democratic mechanism for doing so. Anybody can publish Music Ontology data and link it with existing data, in order to help create a music-related web of data. For example, John Doe may publish some information about a performance he saw last night (like the fact that he was there, and a review). Mary Doe may publish the fact that she attended the same performance, that she recorded it using her cell-phone, and that the corresponding item is available in her podcast. The Music Ontology provides a vocabulary to express information ranging from this example to:

• In this performance was interpreted a particular arrangement of the Trout Quintet by Franz Schubert.
• This work was performed ten times, but only two of these performances were recorded.
• Ten takes of this particular track have been recorded, each of which with a particular microphone location.
• Come as You Are by Nirvana was released on a single and the Nevermind album.
• During this gig, the band played ten songs. During the last one (a cover of Eight days a week), the drummer from the support band joined them to play with them.

The Music Ontology is divided in three levels of expressiveness – from the simplest one to the more complex one. Everything is clustered around the following categories:

• Level 1: aims at providing a vocabulary for simple editorial information (tracks/artists/releases, etc.)
• Level 2: aims at providing a vocabulary for expressing the music creation workflow (composition, arrangement, performance, recording, etc.)
• Level 3: aims at providing a vocabulary for complex event decomposition, to express, for example, what happened during a particular performance, what is the melody line of a particular work, etc.

Links

• Music Ontology
• Music Ontology RDFa representation

Part of Sinapsi. A semantic WordPress project.

Simplified code for designers.

Version 2.8v1.0

License: Gnu-Gpl 3.0

Code: xhtml strict validated.

Tested with: WordPress 2.8.

Xhtml code and php adjustments by Lorenzo De Tomasi. The widget has been derived from Front page login by Hermescb. Thanks to Marco Buttarini for the php code for the “Remember me” checkbox.

If you need frequent and constant updates and upgrades for WordPress Login Widget, please sustain our work . We’ll release express updates compatible with latest versions of WordPress and qTranslate plugin. Feel free to ask for new features or to suggest a bug.

Download v. 2.8v1.0 (php single file zip compressed, 4Kb)

To do

• After login stays on current page (now always goes to the homepage);
• Full test on Internet Explorer 6;
• Full test on WordPress 2.8;
• Enable multiple widgets;
• Publish css file for default WordPress theme (Kubrik).

History

v. 2.8v1.0

• Username link bug corrected.
• Simplified php code

v. 2.7v1.1

• Custom widget title and abstract before the login form/infos
• Title bug corrected in widget setup options

Download v. 2.7v1.1 (php single file zip compressed, 4Kb)

v. 2.7v1.0

• Compatible with Wordpress 2.7: changed gettext values
• Added link to plugin page
• Added direct link to user profile
• Changed version rules: v. <Wordpress cms version>v<Plugin version>

Download v. 2.7v1.0 (php single file zip compressed, 4Kb)

v. 1.1.1

• Add "text" and "password" classes to input fields, for Internet Explorer 6 compatibility;
• Insert php code from wp-login.php instead of text, to activate automatic localization;
• Insert “Forgot your password?” link.

Download v. 1.1 (php single file, 4Kb)

www.madotto.com

If you need frequent and constant updates and upgrades for WordPress Login Widget, please sustain our work . We’ll release express updates compatible with latest versions of WordPress and qTranslate plugin. Feel free to ask for new features or to suggest a bug.

Download v. 2.7v1.1 (php single file zip compressed, 4Kb)

v. 2.7v1.0

• Compatible with Wordpress 2.7: changed gettext values
• Added link to plugin page
• Added direct link to user profile
• Changed version rules: v. <Wordpress cms version>v<Plugin version>

The project has been ideated by Lunaria and funded with support from the European Commission (Youth in action program).

Information architecture and interface design: Lorenzo De Tomasi
Content management system development: Marco Ridoni and  Lynx (released under a Gnu/Gpl license).

Everyone is invited to contribute new features and knowledge to Oryx. The project is hosted as a Google Code project under MIT license.

1. Open the page-template Page with category and save it from your browser (File > Save page as…).
2. Rename the file wp-page_category.txt in wp-page_category.php.
3. Open the template Navigate posts and save it from your browser (File > Save page as…).
4. Rename the file navigate_posts.txt in navigate_posts.php.
5. Using an free software ftp client (like Filezilla) copy both the files wp-page_category.php and navigate_posts.php into your wp-content/themes/<your theme folder>/.
6. Login at your website and write a new page.
7. Select the Page with category template as page-template.
8. Create a custom field with displayed_categories as Key and the numeric id of the category you want to display as Value.
9. Publish the page.
10. Visit the page you have just published.

License

©2008 by Lorenzo De Tomasi. Copyleft/Some rights reserved. The php code has been released under a Gnu/Gpl 3.0 license.

Future improvements

• Make the <!--more--> work. [Can you help to understand the problem? Thanks]
• Set the number of post listed for each page, using pagination buttons. If no value is set, display the default number of posts.
• Display more than one category at time (for example books and dvds), using comma separated numeric category-ids (131, 12, 36).
• Check if displayed_categories is set.
• Check if categories exist.