id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc	parents
543	atom feed IDs: reevalaute taguri	Elrond		"Our atom feeds use taguris (RFC 4151).

First thing to re-evaluate: Do we want to/have to use taguris in this place?
There might be good reasons to want this.

taguris have the form `{ownerid_namespace}:{localpart}`. This is so they are human generatable AND universal unique. the `{ownerid_namespace}` is formed of `{DNSname_or_email},{date}`. The date is the time when the domain/email was owned by the author. This is so that a domain can go to a new owner, which in turn has a new namespace.

For feeds owned by a user, we can use the registration date of the user. We ''currently'' use the *current* year. Which is plain wrong. Because the id should never change after first being shipped. So this should be fixed ''soon''.

For site feeds we currently use ''2011'' as the date. We probably should switch this over to something like the ""deploy date"". The problem is how to find out about it. We could use the date of the oldest entry in the db, but that will change when the oldest image gets deleted by the owner. (""You may not delete the master goblin image."", hoho). No easy solution currently available."	enhancement	closed	major		programming	no-action