Sponsorised links
29 October 2009
OWL 2 Web Ontology Language Document Overview
Sponsorised links
26 October 2009
25 October 2009
zoie - Project Hosting on Google Code
Zoie is a real-time search and indexing system built on Apache Lucene. In a real-time search/indexing system, a document is made available as soon as it is added to the index. This functionality is especially important to time-sensitive information such as news, job openings, tweets etc.
getElementsBySelector - CSS Query Selector for HTML DOM < Scripts < Python < Bin-Co
getElementsBySelector is a python function which takes a standard CSS style selector and returns an array of elements objects from the document that match that selector. This is a frequently used function in JavaScript - if you use a library. Its kind of meaning less to have this function in the server side - unless you are doing screen-scarping. Then its very useful. Recently, I had to work on a Django app that does a bit of screen-scrapping - so I created this function to aid me.
14 October 2009
Huddle.net project management
02 October 2009
RFC 5545 - Internet Calendaring and Scheduling Core Object Specification (iCalendar)
This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol.
01 October 2009
30 September 2009
Lucid Imagination » Solr’s New Clustering Capabilities
One of the new things in Solr 1.4 that I am particularly excited about is the new document and search results clustering capabilities. This is an optional module that lives in Solr’s contrib/clustering directory and was added via SOLR-769.
27 September 2009
25 September 2009
Techniques for WCAG 2.0
"Techniques for WCAG 2.0" provides information to Web content developers who wish to satisfy the success criteria of Web Content Accessibility Guidelines (WCAG) 2.0 [WCAG20]. Techniques are specific authoring practices that may be used in support of the WCAG 2.0 success criteria. This document provides "General Techniques" that describe basic practices that are applicable to any technology, and technology-specific techniques that provide information applicable to specific technologies. The World Wide Web Consortium only documents techniques for non-proprietary technologies; the WCAG Working Group hopes vendors of other technologies will provide similar techniques to describe how to conform to WCAG 2.0 using those technologies. Use of the techniques provided in this document makes it easier for Web content to demonstrate conformance to WCAG 2.0 success criteria than if these techniques are not used.
24 September 2009
Simple API for Cloud Application Services
The Simple Cloud API is here to bring cloud technologies to PHP and the PHP philosophy to the cloud. With it, developers can start writing scalable and highly available applications that are still portable. If you're looking for code to start playing around with immediately, you'll find the first file storage, document storage, and simple queue interfaces with adapters for major cloud vendors here.
But this project is about more than just code. Zend has once again invited the open source community and software vendor of all sizes in to a dialogue that benefits all. And this time we're working with the companies that are leading the cloud revolution.
23 September 2009
tinyPM » Product Features Overview
tinyPM is a light and efficient tool allowing your teams to enhance the software development process with:
* using user stories as requirements
* backlog management with user stories estimated in points
* iteration planning with easy user story assignment
* sharing task boards across distributed teams
* tracking agile project metrics
* using wiki to document team's knowledge
Prefixes, not that complicated. | Garbage Collection
We were able to come up with rules that make using prefixes in almost any context simpler. Note, these are for the most part AUTHORING guidelines, not requirements when reading:
1. Reusing the same prefix in the same document with different meanings is horribly confusing (”If you did that, I’d break your figures.”). Possible to figure out, but not really desirable. Seems like a reasonable place for a warning.
2. Defining all the prefixes in one place makes it simpler to keep track of them. But understood when it would be simpler to define a new prefix for a section of content.
3. “Couldn’t you have a simple tool that just shows you what prefixes are defined at any point in the document?” How such a tool has failed to exist in the XML world… may write this.
18 September 2009
WOFF File Format
Accessibilité du Web - Label AccessiWeb - Critères AccessiWeb - 95 critères (version linéaire)
13 September 2009
The Web At A New Crossroads
12 September 2009
Nihon Katchû Seisakuben -- An Online Japanese Armour Manual
11 September 2009
10 September 2009
