Legislation.gov.uk

  • 2,129 views
Uploaded on

Background and overview of technical approach and architecture for legislation.gov.uk site.

Background and overview of technical approach and architecture for legislation.gov.uk site.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,129
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
22
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Each format has advantages, and so each looks at others advantages jealously:\nHTML's ubiquity\nXML's flexibility and ease of parsing\nRDF's reach to a real-world\nJSON's practicality\n\nOne result is ghettoisation: "you should not exist! you have no point! I am all that's needed!"\nAnother result is self-doubt: "what am I here for? what should I be?"\n
  • \n
  • \n
  • URLs that address structures within formats help those formats to be used together. They can be used for their strengths, without being compromised.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Transcript

  • 1. legislation.gov.ukJeni Tennisonhttp://www.jenitennison.com/blog/@JeniT
  • 2. Work of many
  • 3. Overview• UK Legislation• Goals• Architecture• Expert Participation• Lessons learned
  • 4. UK Legislation
  • 5. integration of two sites OPSI and SLD
  • 6. many types of legislation from 1267 to modern day
  • 7. Data sources• as-enacted legislation (OPSI) • PDFs • pre-1988 OCRd • post-1988 SGML/XML data sources• revised legislation (SLD) • February 1991 "base date" • different XML format
  • 8. semi-structured documents headings, numbered provisions
  • 9. new legislation published every working day
  • 10. versioning amendments & extents
  • 11. Goals
  • 12. Usable• user experience • oriented around personas of real users • clear provisos so you know what youre looking at• reuser experience • variety of formats (HTML snippets, XML, RDF, PDF) • feeds for access• integration between the two
  • 13. Open• open standards • non-proprietary formats• open source • use open source technologies where appropriate • open source our code - https://github.com/legislation/legislation• open licence • all available under Open Government Licence
  • 14. RESTful• URIs for everything • every item of legislation • every level within it • every version of them • every view of them • every format of them• HTTP status codes / content negotiation• typed link for every transition
  • 15. Architecture
  • 16. work /id/ukpga/1985/67expression 303 See Other /ukpga/1985/67/scotland /ukpga/1985/67/2001-04-01 /ukpga/1985/67manifestation Content-Location /ukpga/1985/67/data.xml /ukpga/1985/67/data.pdf /ukpga/1985/67/data.htm information architecture FRBR model
  • 17. work /id/ukpga/1985/67/section/6expression 303 See Other/ukpga/1985/67/section/6/scotland /ukpga/1985/67/section/6/2001-04-01 /ukpga/1985/67/section/6manifestation Content-Location/ukpga/1985/67/section/6/data.xml /ukpga/1985/67/section/6/data.pdf /ukpga/1985/67/section/6/data.htm same for every fragment parts / chapters / sections
  • 18. tables of contents access at any level
  • 19. timelines access any point in time
  • 20. custom XML format crown legislation markup lang.
  • 21. browsing and searching views from Atom feeds
  • 22. single source multiple views
  • 23. caching & delivery CDN caching cache static files web server transformation pipeline engine XSLT & XSL-FOstorage & queries XML database XML & XQuery system architecture native XML
  • 24. caching & delivery Akamai caching Squid static files Apache transformation Orbeon XSLT & XSL-FOstorage & queries MarkLogic XML & XQuery system architecture native XML
  • 25. Expert Participation
  • 26. Data quality• data is out of date • 100,000 unapplied effects • can apply 10,000/year; parliament makes 15,000• help others help us (and themselves) • open source as a model • editorial team retains control & ensures quality • framing participant tasks • reviewing participant work
  • 27. New requirements• new types of information • effects & research • tasks & workflows • participants & permissions & messages• new levels of interactivity • read/write platform • dynamic, native web interface
  • 28. lingua franca application-native data HTML JSON concise hard to get wrongsingle source format web-native data XML RDF flexible graph model other formats are better for other things
  • 29. caching & delivery CDN caching cache static files web server transformation pipeline enginedocuments XML database triplestore data new architecture XML and RDF data
  • 30. displays driven by RDF transformed by XSLT
  • 31. HTML JSON URIsXML RDF URIs are the keys weak, flexible links
  • 32. Lessons learned
  • 33. User and re-user focus• integrated API and UIs • guarantees relevance • help re-users understand information • help developers debug• URIs are key • addressability • sharability • understanding of underlying resource model
  • 34. Agility• native XML eases development • provides flexible access into documents • avoids data model mismatches• native RDF eases development too! • ease of combining information from different sources • querying with SPARQL• schema-free & extensible aids agility
  • 35. Pitfalls• performance • caching • batch processing• proprietary software • rely on non-standard functions & tools • partition code
  • 36. Summary• complex documents • added value from having them on the web• layered architecture • make the most of single-source publishing• web standards • long-term flexibility• if we can do it with legislation ...
  • 37. Questions?