]]>
]]>
]]>
The W3C published 2 days ago the OWL2 Recommendation, made by 12 documents. A great step further in SW technologies, 5 years after the first OWL Recommendation !
]]>
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 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.
Huddle.net combines award-winning online collaboration, live conferencing, project management software and document sharing.
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.
]]>
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.
]]>
"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.
]]>
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.
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
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.
This document specifies a simple compressed file format for fonts, designed primarily for use on the web. The WOFF format is directly based on the table-based sfnt structure used in TrueType[1], OpenType[2] and Open Font Format[3] fonts, which are collectively referred to as sfnt-based fonts. A WOFF font file is simply a repackaged version of a sfnt-based font in compressed form. The format also allows font metadata and private-use data to be included separately from the font data. WOFF encoding tools convert an existing sfnt-based font into a WOFF formatted file, and user agents restore the original sfnt-based font data for use with a webpage. In general, the structure and contents of decompressed font data should match that of the original font file. Tools producing WOFF font files may provide other font editing features such as glyph subsetting, validation or font feature additions but these are considered outside the scope of this format. Independent of these features, both tools and user agents must assure that the validity of the underlying font data is preserved.
Ce document contient la liste des 95 critères du référentiel AccessiWeb v1.1 affichés linéairement. Il a été créé le 9 juin 2008 en français.
Technology was then the black sheep, having left overnight millionaires destitute and without change to afford their $4 lattes. Even the posers had left San Francisco and gone back to suburbia to be office managers at Walmart. It was a sad time for everyone — that is, except the die-hards and the hackers. The web for them had never been about making money, but about reshaping culture and toppling the old order. 2003, therefore, was the perfect time for a resurgence: the people who kept pushing on in the Valley and elsewhere were a concentrated motley crew of innovators and builders. They cared about technology for technology’s sake and about developing and advancing web culture. What they didn’t realize, however, was that the services and technologies that they were destined to build would need to be cobbled and sewn together using a system that would fight them every step of the way — not out of spite — but because of its architecture. By definition the network available was decidedly anti-human: in 2003, there was only the document-centric web.
It was originally my intention to produce an issue of the Compleat Anachronist pamphlet series which would enable an armourer with fairly average skills to produce a good Japanese armour. The idea has grown to the point where it’s probably too unweildy for such a publication. Also, using the Web to present the information allows me to use color photographs and color illustrations to clarify things that are simply not well presented in a black-and-white printed document. There was another problem, though: specifically, the issue of what constitutes “proper” Japanese armour for use in the Society for Creative Anachronism. Unfortunately, many aspects of Japanese armour fly in the face of thirty-odd years of SCA-style combat. What this means is that, in many instances, a decision will have to be made — namely, are you making armour for combat or for dress? I will present dress armour primarily, as I am a firm believer in authenticity of appearance. Where concessions for SCA combat must be made, I will explain the necessary diversions and provide explanations on how to finish the armour in either functional or authentic form.
]]>
I assume this is such an esoteric bug that I don't need to create recommendations on fixing it. I just wanted to document it in case someone else comes across this bug
]]>
]]>
]]>