- markup (76)
- xml (11)
- xslt (23)
- pipelines (8)
- atom (9)
- overlapping markup (6)
- schema (11)
- creole (5)
- dtll (1)
- xforms (1)
- xpath (1)
- xquery (2)
- coding (2)
- datagovuk (1)
- genealogy (4)
- hardware (1)
- linked data (16)
- modelling (1)
- named graphs (1)
- opendata (1)
- provenance (1)
- psi (3)
- skos (1)
- sparql (4)
- Talis (7)
- unicode (1)
- uri (4)
- versioning (1)
- visualisation (6)
- web (78)
- google (4)
- html5 (5)
- jQuery (2)
- rdf (46)
- ontologies (2)
- rdfa (8)
- rdfQuery (5)
- rest (6)
- wikis (1)
- work (3)
- legislation (2)
- xmlsummerschool09 (2)
- life (28)
- children (5)
- equality (6)
- gtd (1)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (11)
- ukgc09 (1)
- xtech (9)
- xtech2008 (3)
- blog (8)
- drupal (3)
Recent posts
- 4 days 3 hours ago
- 2 weeks 4 days ago
- 7 weeks 1 day ago
- 14 weeks 4 days ago
- 15 weeks 6 days ago
Recent comments
- Claytor370 (not verified)
- satya sahoo (not verified)
- meanto (not verified)
- meanto (not verified)
- meanto (not verified)
Re: The Real Deal: data.gov.uk
Interesting post again Jeni.
I tend to follow a similar approach when making my RDF. Typically I clean up the original data (though usually in a text editor like editplus if I’m honest) and then I run python scripts to produce the RDF.
The URIs for our data (when we’ve fixed a URI scheme) will look something like
http://…/id/7000000000000123
OS data (well OS MasterMap) gives unique (16 digit) IDs to all features - these are called TOIDs. Our URIs will be based on these TOIDs.
I’m coming close to finishing the administrative geography RDF so that should soon give you something to “owl:sameAs” to.