Jefsey,Lots of questions, most of which I suspect are not really related to ltru. I'll answer these questions here, but I suspect there are better places for continued discussion on these topics.
On Sep 20, 2006, at 5:18 AM, r&d afrac wrote:
Do you have a completion date in mind?
As I've indicated, we hope to have the first set of XML-ized registries available for comment around the beginning of 2007. Further publication will depend on input from the affected communities.
Do you take advantage of this to make them ISO 11179 conformant? Will it be organised as an ontology? Will you adopt a Dublin Core approach?
If these are appropriate. I am not an XML expert and will look to others to provide advice on the best way of representing IANA registry data externally.
Will you include a secure update annoucement list?
I'm unsure of what you mean. We will, in the relatively near future, be PGP signing IANA announcements.
Will you include a consistency check solution for comparing two versions of a registry?
Yes.
Will you include a daily distributed status of these checks to avoid millions of unnecessary down loads.
Hadn't considered it, but if this is desirable, IANA can publish diffs of the registry updates.
Will you include a single IANA procedure for registry management and review (mailing list, reviewer, appeals, cross registry consistency, CVS).
Having a consistent approach to registry management is a goal. How we manage registries internally is something that is evolving (as you might guess).
Will you support a multilingual approach?
Not IANA's call. What is contained within the vast majority of registries is defined by the IETF.
Have you planned a distributed dissemination mechanism?
There have been discussions along these lines, but nothing formalized as yet.
Have you planned a procedure/hooks for personal extensions?
No. Rgds, -drc _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.