<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Cycling again / addresses</title>
	<atom:link href="http://blog.j12.org/2008/04/cycling-again-addresses/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.j12.org/2008/04/cycling-again-addresses/</link>
	<description>musings of a bunny roaming the frontiers cyberspace</description>
	<pubDate>Fri, 21 Nov 2008 09:03:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: bunny</title>
		<link>http://blog.j12.org/2008/04/cycling-again-addresses/#comment-15310</link>
		<dc:creator>bunny</dc:creator>
		<pubDate>Wed, 09 Jul 2008 14:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.j12.org/?p=23#comment-15310</guid>
		<description>Interesting interview at:

http://aligned-assets.blogspot.com/2008/06/interview-with-ias-gayle-gander.html

It is interesting how they say the high pricing at the moment has out back a aim they have which seems to come from there being the &lt;a href="http://www.govtalk.gov.uk/gdsc/html/frames/BS7666Address.htm" rel="nofollow"&gt;BS7666&lt;/a&gt; standard of all software storing address in BS7666 with UPRNs. This would certainly help with some of problems at my work we have with addresses. But with how prices are and inertia to continue as have been very unlikely to be used.

The fields the addresses are held in are limiting and not constant due to way implemented, and there is a mismatch between how some templates use fields and how data is transferred from these fields to other systems. This should be changed anyway to ensure accuracy and BS7666 layout would seem as good as any. And I like some aspect of how structured over the way PAF is structured but both beat present, which mangles or truncates many addresses imported from the PAF.

&lt;a href="http://www.idea.gov.uk/idk/aio/6055969" rel="nofollow"&gt;Structure of NPLG&lt;/a&gt;

&lt;a href="ftp://ftp.royalmail.com/Downloads/public/cmwalk/doc/active/doc21800003/PAF_Digest_Dec_03.pdf" rel="nofollow"&gt;Structure of PAF&lt;/a&gt;
</description>
		<content:encoded><![CDATA[<p>Interesting interview at:</p>
<p><a href="http://aligned-assets.blogspot.com/2008/06/interview-with-ias-gayle-gander.html" rel="nofollow">http://aligned-assets.blogspot.com/2008/06/interview-with-ias-gayle-gander.html</a></p>
<p>It is interesting how they say the high pricing at the moment has out back a aim they have which seems to come from there being the <a href="http://www.govtalk.gov.uk/gdsc/html/frames/BS7666Address.htm" rel="nofollow">BS7666</a> standard of all software storing address in BS7666 with UPRNs. This would certainly help with some of problems at my work we have with addresses. But with how prices are and inertia to continue as have been very unlikely to be used.</p>
<p>The fields the addresses are held in are limiting and not constant due to way implemented, and there is a mismatch between how some templates use fields and how data is transferred from these fields to other systems. This should be changed anyway to ensure accuracy and BS7666 layout would seem as good as any. And I like some aspect of how structured over the way PAF is structured but both beat present, which mangles or truncates many addresses imported from the PAF.</p>
<p><a href="http://www.idea.gov.uk/idk/aio/6055969" rel="nofollow">Structure of NPLG</a></p>
<p><a href="ftp://ftp.royalmail.com/Downloads/public/cmwalk/doc/active/doc21800003/PAF_Digest_Dec_03.pdf" rel="nofollow">Structure of PAF</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
