Statistics
Displaying 1 To 3 Of 3 Comments New Zealand Government Feed Standard (Consultation) That’s a pertinent question. The work we’re doing now is aimed at demonstrating feed-based solutions that deliver significant cost-savings across the agency. So if new funding is required it should be available from costs saved elsewhere. Details coming soon. Comment Posted By Matt On November 26, 2008 @ 10:20 am Here is a quick & dirty first cut at what the Web Standards might say about feeds. The agency/website should publish a core feed meeting the following requirements: • Machine discoverable from the home page (DNS root) • Human discoverable from the home page (clear labelling) • Atom format (see Feeds spec…) • Publish all new/changed items for at least the previous 7 days (to ensure continuity for aggregators/readers) • Publish all (website) items as far as possible. (including news, consultations, reports, alerts, media releases etc. Probably not specify categories.) • Publish the full content of each item (as opposed to a summary with a link). This is important for many reasons: • Times should be specified in the NZ zone +1200. Comment Posted By Matt On August 14, 2008 @ 5:53 pm hCard Microformat Creator for New Zealand [updated 15 July 2008] Thanks Pete. There are a couple of issues… Having both address and geo lat/long within the hcard introduces data redundancy (and potential for mismatched address/geo). Also the co-ordinates that Google and other geo-coders return is an approximation: a street address doesn’t convert to a single lat/long. Our current plan is to make it clearer about when it is appropriate to use both address AND lat/long. We’re planning a tabbed interface where input is either address OR geo, with an explanation of how to combine them when appropriate. But, yes we’ll publish the lat/long as returned by the Google geo-coder when it processes an address. I’m interested in feedback on this. Comment Posted By Matt On May 30, 2008 @ 12:30 pm
Comments Posted By Matt
<link rel=”alternate” type=”application/atom+xml” …
– for accessibility - users can easily access item content independent of the web site
– for offline viewing - feed readers can load the feed content for later viewing offline (for commuters, slow rural connections etc)
– for mobile devices - mobile readers are optimised for loading and displaying feed content
– for speed/usability - reading full content is much quicker than following a link to the source website
– for mash-ups - full content is required to enable manipulation for unforeseen uses
