PUBLIC MARKS from decembre with tag microformat

The URI microformat takes advantage of OpenURL and existing link resolver solution.It defines a convention of plugging URI metadata in HTML page. If it is adopted and widely used,now a microformat-aware application (be a greasemonkey script, or a web service) can grab the identifier and point to your local OpenURL resolver, you immediately get the copy from local library. It is very similar to COINS, but it's much simpler and cleaner, anyone can understand and use it, and its aplication can be beyond traditional research library. e.g. in a public library, you can use amazon as catalog and immediately check if it's available in local collection. COinS provides a great number of additional capabilities that URI microformat can't support. Since COinS can't be dismissed for this reason, it doesn't make sense to me to create yet another standard that does the same thing with so little savings.I will grant that the COinS is less intuitive.....

test Libx pour bobigny....

To embed citation metadata into html in such a way that processing agents can discover, process and make use of the metadata. Since an important use of this metadata will be to allow processing agents to make OpenURL hyperlinks for users in libraries (latent OpenURL), the method must allow the metadata to be placed any where in HTML that a link might appear. In the absence of some metadata-aware agent, the embedded metadata must be invisible to the user and innocuous with respect to HTML markup. To meet these requirements, the span element was selected. The NISO OpenURL ContextObject is selected as the specific metadata package. The resulting specification is named "ContextObject in SPAN" or COinS for short. A COinS Generator site is available - See : COinS Processors Alf Eaton's Greasemonkey script for processing COinSVirginia Tech's

Operator demonstrates the usefulness of semantic information on the Web, in real world scenarios.Here are some examples of things you can do with this release of Operator, and with the Web as it exists today : Yahoo! Local and Your Address Book. With Operator you can send the phone number of your favorite pizza place from Yahoo! Local to your address book, without having to type anything..... Operator requires information on the Web to be encoded using microformats, and since this method for semantically encoding information is relatively new, not all sites are using microformats yet. However, Operator works great with any blog that uses rel-tag, and the sites Yahoo! Local, Flickr, and Upcoming.org, all of which contain millions of pieces of information expressed using microformats. As more sites begin to semantically encode data with microformats, Operator will automatically work with them as well.

Il y a eu récemment beaucoup de très bonnes idées d'interfaces-utilisateurs et des suggestions pour travailler sur les microformats. Cette page sert à rassembler et documenter de façon à ce que nous puissions être inspirés et informés sur les travaux des autres.

hCalendar est un format simple, ouvert, distribué pour le calendrier et les événements, fondé sur le standard iCalendar (RFC2445 (http://www.ietf.org/rfc/rfc2445.txt)), adaptable pour l'embarquement dans HTML ou XHTML, Atom, RSS et le XML arbitraire. hCalendar est l'un des nombreux standards ouverts microformat. Vous voulez démarrer par écrire un événement hCalendar ? Utilisez le hCalendar creator (http://microformats.org/code/hcalendar/creator) pour écrire un événement et le publier, ou suivez les trucs de publication hCalendar pour ajouter de la syntaxe hCalendar à votre page d'évènements à venir ou des événements que vous mentionnez dans vos billets de blogs, wikis, etc.

Nouvelle technologie qui n'a pas encore fait ses preuves et qui n'est pas non-plus idiote sur le principe. C'est pourquoi je vais essayer d'adopter une démarche scientifique, formuler des hypothèses, faire des expériences et progresser en même temps q