background preloader

Xml

Facebook Twitter

Rdf

The Atom Publishing Protocol. History of blogging APIs Basic operation of the Atom Publishing Protocol Applications to areas outside weblogs One of the earliest weblog updating protocols. Uses 'application/x-www-form-urlencoded' encoded data sent to the server. The response is encoded as a series of key/value pairs separated by newlines. Called The LiveJournal Flat Client/Server Protocol POST /interface/flat HTTP/1.0 Host: www.livejournal.com Content-type: application/x-www-form-urlencoded Content-length: 34 mode=login&user=test&password=test HTTP/1.1 200 OK Date: Sat, 23 Oct 1999 21:32:35 GMT Server: Apache/1.3.4 (Unix) Connection: close Content-Type: text/plain name Mr.

Test Account success OK message Hello Test Account! Create a new log entry. There are other capabilities relating to 'friend' management. While not a major protocol today it set the pattern. Everything is done through HTTP POST Everything goes through one URI Does not use HTTP Authentication HTTP has other methods: GET PUT DELETE <? Internationalization. DocBook to WordML. Guide. The DocBook Project.

RestWiki. The Beauty of REST. March 17, 2004 I've just been to SXSW to speak on a panel called Streetwise Librarians and the Revolution in Libraries. My own small contribution to that revolution, and the reason for my visit to SXSW, is the LibraryLookup project I launched 16 months ago. I'll admit that "project" is a lofty term for what is, basically, just a bunch of variations on a simple JavaScript bookmarklet. But for thousands of patrons of hundreds of libraries, that snippet of JavaScript -- which extracts the ISBN from an Amazon (or other ISBN-bearing) URL and checks for the book's availability in your local library -- has been an eye-opener.

Rekindled interest in local libraries is part of LibraryLookup's charm. There are a handful of major OPAC (online public access catalog) systems, and dozens of minor ones. The use of POST rather than GET is a minor obstacle, but some other design choices are deal breakers. The use of session identifiers is another deal breaker. I do see hopeful signs. 1 to 2 of 2. Writing Documentation Using DocBook. Copyright © 1997-2000, 2001-2002 David Rugge, Mark Galassi, Eric Bischoff, Michel Goossens This document can be freely redistributed according to the terms of the GNU General Public License.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Abstract This document is a tutorial on how to write documentation in DocBook, and generate HTML and PDF from the XML sources. The description of the DTD elements is general in nature, whereas some tools and the location of system files relate to the CERN XML set-up.

This material is based in part on "A crash-course in DocBook", which was itself created from a fusion of three documents: