Move registry into its own XML file #8
Conversation
msporny
left a comment
msporny
left a comment
There was a problem hiding this comment.
Agree with the notion behind this PR... but if it breaks the live preview, we shouldn't do it.
| <c>blake2s-248</c><c>0xb25f</c><c>active</c><c><xref target="RFC7693">RFC 7693</xref></c> | ||
| <c>blake2s-256</c><c>0xb260</c><c>active</c><c><xref target="RFC7693">RFC 7693</xref></c> | ||
| </texttable> | ||
| ®istry; |
There was a problem hiding this comment.
Hmm, do you know if this change will break the browser-based rendering of the specification? Note that you can view a live version of the latest editor's draft here: https://w3c-dvcg.github.io/multihash/index.xml ... is this PR going to break that browser-based preview?
There was a problem hiding this comment.
I was not aware of that but the preview is incomplete anyway because it does not include references. I could extend the .xsl file to fix this.
There was a problem hiding this comment.
Yes, please do, if possible. I'm not paying too much attention to the how... just that we want the browser-based rendering to continue to work.
2 participants
This simplifies update to make sure the registry always contains the current table.