Hi, I am rewriting the tool I use to build a knowledge graph (KG) of all RFCs and ancillary files[1], and I have some questions about what properties of an RFC are mutable.
— The “status” field in the JSON file (in the "ietf/rfc" directory from rsync) changes from time to time, as opposed to the “pub_status” field that was the status at publication time, and thus is immutable. Is there a database with the changes, with timestamp, made to the “status” field? Something like https://www.rfc-editor.org/status_changes.php. — Can the “format” field change, for example, when a new rendering file is added? (related question: I saw both “ASCII” and “TEXT” used in the JSON files. What is the difference between these two formats?) — Is the “keyword” field immutable? — Disturbingly, RFCXML files are now mutable. How do I know that an RFCXML file was modified and that I need to update my KG? — I understand that the RFC(s) associated with STD and BCP change from time to time. Here again, is there a database that provides a history of these changes? — IPR disclosures can be added at any time to an RFC, but are they immutable? — Is there other mutable properties of an RFC that I did not list here (apart the errata)? Thank you. [1] https://datatracker.ietf.org/doc/draft-petithuguenin-rfc-ontology/ -- Marc Petit-Huguenin Email: m...@petit-huguenin.org Blog: https://medium.com/@petithug Profile: https://www.linkedin.com/in/petithug
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ rfc-interest mailing list -- rfc-interest@rfc-editor.org To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
