有限数量的 RFC 以 XML 形式提供，位于 http://xml.resource.org/public/ rfc/xml/
您还可以使用来自 http:// /xml.resource.org/public/rfc/bibxml/
A limited number of RFCs are offerd as XML at http://xml.resource.org/public/rfc/xml/
Also you could merge the text data using Bib XML from http://xml.resource.org/public/rfc/bibxml/
IETF 以 HTML 形式维护最低标记的 RFC，例如：
https://www. rfc-editor.org/rfc/rfc2616.html
但标记主要由实现目录的锚点组成；主体标记大部分是
...
。尽管如此，还是可以对这些 RFC 进行一些有意义的解析。
W3C 有一些 HTML 化的 RFC，例如：
http://www.w3.org/Protocols /rfc2616/rfc2616.html
其中标记的语义更丰富，因此可能更适合解析。
IETF maintains minmally-marked-up RFCs in HTML, for example:
https://www.rfc-editor.org/rfc/rfc2616.html
but the markup consists mostly of anchors to implement a table of contents; and main-body markup that is mostly <pre> ... </pre>. Nevertheless, it might be possible to do some meaningful parsing on those RFCs.
W3C has some HTMLized RFCs, for example:
http://www.w3.org/Protocols/rfc2616/rfc2616.html
in which the markup is somewhat richer in its semantics and so perhaps more amenable to parsing.
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
暂无简介
文章 0 评论 0
接受
发布评论
评论（2）
有限数量的 RFC 以 XML 形式提供，位于 http://xml.resource.org/public/ rfc/xml/
您还可以使用来自 http:// /xml.resource.org/public/rfc/bibxml/
A limited number of RFCs are offerd as XML at http://xml.resource.org/public/rfc/xml/
Also you could merge the text data using Bib XML from http://xml.resource.org/public/rfc/bibxml/
IETF 以 HTML 形式维护最低标记的 RFC，例如：
https://www. rfc-editor.org/rfc/rfc2616.html
但标记主要由实现目录的锚点组成；主体标记大部分是
。尽管如此，还是可以对这些 RFC 进行一些有意义的解析。
W3C 有一些 HTML 化的 RFC，例如：
http://www.w3.org/Protocols /rfc2616/rfc2616.html
其中标记的语义更丰富，因此可能更适合解析。
IETF maintains minmally-marked-up RFCs in HTML, for example:
https://www.rfc-editor.org/rfc/rfc2616.html
but the markup consists mostly of anchors to implement a table of contents; and main-body markup that is mostly <pre> ... </pre>. Nevertheless, it might be possible to do some meaningful parsing on those RFCs.
W3C has some HTMLized RFCs, for example:
http://www.w3.org/Protocols/rfc2616/rfc2616.html
in which the markup is somewhat richer in its semantics and so perhaps more amenable to parsing.