how to build and publish your own FOAF.rdf

analysis, developer, informatics, tech


Ingredients = exactitude, XML, at least one FOAF friend


1. look around online for authoritative examples of foaf.rdf files.

2. copy as text, edit (.txt) in notepad, rebuild using your own urn/url variables, save in utf-8 format as an .rdf

3. post in the root directory of your website

4. make page head meta references like this:

<meta charset=”utf-8″>
<html prefix=”rdf:
<meta name=”author” content=”Person Name
<link rel=”meta” type=”application/rdf+xml” title=”FOAF” href=”

{code =replace end quote and greater-than, last 3 lines, but with forward slash, before greater-than in the final line}

5. verify your code using the very cool W3C RDF Validation Results like this:


how to make information from data

analysis, developer, informatics, tech, work


Ingredients = consistent, logical, determined, focus, attention, XML.

1. identify dataset of (wide/narrow) interest to many people, not well exposed by search engines.
2. research and gather a manageable top down list of around 150 examples.
3. analyse and specify around 10 potentially useful things to know about these, common to each.
4. build an XML schema with one example.
5. open / add data for the other 149 using an xmleditor
6. crunch the data again and again to make it of the highest quality.
7. import your XML data back into your application/website.
8. build some xsl templates to display the data well in summary and detail.
9. derive maybe 2 more alternative UI to interrogate the data, such as a frequently occuring word search list function, or a map relating locations with specific examples in your xml.
10. Add at least one intelligent user, purposively looking for information, acting to process towards insight.

scoping mobile site development

developer, production, tech

development and production of custom mobi web apps on our servers? looking at iis .net apps with visual studio for windows phone 7  and/or dotmobi wordpress mobile app toolkit (there are already lots of client device apps)  but then php on iis,  mysql.

for our domains meanwhile, instantmobilizer has been stopgap, but unsatisfactory.

meanwhile would resort to url forward to native m. on wordpress with testing by opera emulator


mobile web apps reloaded 2013, seventeen four thirteen…

turned out that the complexity of device table lookup and content negotiation by the server with the specific device has now gone away.

can now just set device = “ismobi” for redirect to your mobi domain, mobile content site configured with a mobile optimized skin.