how to build and publish your own FOAF.rdf

analysis, developer, informatics, tech

Recipe.

Ingredients = exactitude, XML, at least one FOAF friend

STEPS

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: http://www.w3.org/1999/02/22-rdf-syntax-ns#
foaf: http://xmlns.com/foaf/0.1/
rdfs: http://www.w3.org/2000/01/rdf-schema#
<meta name=”author” content=”Person Name
<link rel=”meta” type=”application/rdf+xml” title=”FOAF” href=”http://www.example.com/foaf.rdf

{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: http://j.mp/1yCRRSE

google+, an offer U can’t delete

events, tech

your online interacations are a response to behaviour-inducing stimuli in your online environment.
are you familiar with the term “specialist content behavioural platform”.
how about “personal reality mining”, or “environmental behaviourists”?
developer or internet professional with an ongoing role in many simultaneous online projects? your online identity is not you.
so, you want search not to give you skewed results, based on you, or the stuff you were looking at in your digital roles.
Worse, from Monday 11th November, [http://j.mp/offerUcantdelete] if you want to use their services, google are going to be requiring you to “upgrade” to google+. read at the same time with google [http://j.mp/1aPyYCW] names policy.
this means your offline identity will be bound to your online data.
google are making an offer you can’t delete.
data/everything that can be gathered about you is a commodity.
from 11th November, google requires that you bind your offline identity to this commodity.
the conditionality for using google is that all the data they can gather about you, is bound to your offline identity.
alternative is? do not consent to using these online services.
this anti-pseudonymous ecosystem google is building serves commercial ends, you abdicate your freedom and your mind to these.
so my shared endorsement for google+ is to decline to use personal google+,
‘don’t sell your identity so cheap’.
google+ the wrong kind of networking based on the wrong data.

online role freedom

online role freedom

how to make information from data

analysis, developer, informatics, tech, work

Recipe.

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

STEPS:
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.

visualizing social network analysis shortener

analysis, literature, tech

Observable equivalance juxtaposition through url shortening of the very large meta aggregation of nested analytical information about social networks, standing on the shoulders of dark-matter like background conditionality such as the internet itself and human interactivity.
Yet clicks on this diagram of diagrams visualizing social network analytics short url, http://j.mp/STHLov is now tracked in my profile.

server into retirement emotionality

events, literature

Our lovely hand-built server has been running apps since it became self-aware on 14th january 2003. Today, with due ceremony, operational http, mms, and smtp services were moved and tested OK on another machine. The Windows Server 2003 operating system shutdown was instantiated, the chassis fans run down, and the solidity and robustness of the final shutdown click indicates clearly to me that this server will gladly serve apps, data and content for many more years. As I embraced and fondled the machine gratefully reflecting on the years of service, I tried hard not to anthropomorphise the machine and start assigning feelings to it, computers hate that.

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.