![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi,this looks really good; a simple XML format, XSLT provided, registry served both as XML and proper XHTML.
Here are a few question/suggestions though...: 1) When you say
All existing URLs to protocol registries shall continue to work, and the new formats will be available from our website at http://www.iana.org/protocols/ as they are rolled out.
...is that just for a transition period? Will the new formats eventually served for the old URLs?
2) I think it would be good to have stable HTTP URLs both to registries and individual registrations. For "simple" registries, would it be possible to assign predictable and stable id attributes to the XML (and the XHTML), so linking to fragments would work?
3) Registry format: I like registries that not only reference RFCs, but also tell their readers which section of the document has the reference. Will this be supported as an option?
4) Finally an idea for future work: use GRDDL (<http://www.w3.org/TR/grddl/>) to extract RDF from the registries.
BR, Julian PS: Are people involved with this present in Dublin? _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.