Thanks Brian, that appears to have worked! From: OAuth <oauth-boun...@ietf.org> on behalf of Brian Campbell <bcampbell=40pingidentity....@dmarc.ietf.org> Date: Monday, April 27, 2020 at 06:26 To: Vittorio Bertocci <vittorio.bertocci=40auth0....@dmarc.ietf.org> Cc: oauth <oauth@ietf.org> Subject: Re: [OAUTH-WG] Second WGLC on "JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens"
This old thread https://mailarchive.ietf.org/arch/msg/oauth/1ajE-d3nVOFRGLbwMmPViDhEdqw/ has some discussion of working with/around that particular quirk of the htmlizing tool. On Mon, Apr 27, 2020 at 2:34 AM Vittorio Bertocci <vittorio.bertocci=40auth0....@dmarc.ietf.org<mailto:40auth0....@dmarc.ietf.org>> wrote: Thank you for bringing this up Benjamin, you saved me from a long wild goose chase! It' good to know that there's a new rfc format version, but I am a bit worried about venturing there given that I am barely managing the v2 as it is __ v3 still feels pretty experimental, and other than this issue, this spec doesn't give a lot of opportunities to take advantage of the new features (SVG etc). Wondering whether I can find a periphrase to express the same notion without triggering the script, e.g. omitting the word section or changing the order. Thx V. On 4/24/20, 19:02, "Benjamin Kaduk" <ka...@mit.edu<mailto:ka...@mit.edu>> wrote: Just on the xml2rfc bits... On Wed, Apr 22, 2020 at 07:26:40AM +0000, Vittorio Bertocci wrote: > > > Link to section 4.1.2 of SCIM Core is actually linking to section 4.1.2 of this doc. > Oh wow. That’s a feature of XML2RFC,… my source simply says by section 4.1.2 of SCIM Core in a <t> block, and the processor interpret it as an internal link. I’ll need to dig on how to prevent that from happening for this instance. Good catch! The short form is "you can't". You're using the "v2" XML format for xml2rfc, which produces as various output formats text, pdf, and "htmlized" output. The "htmlized" output is called that and not "html" because it's the result of taking the text output and running a script to turn common constructions in I-Ds and RFCs into hopefully-useful HTML formatting. In this case, "Section N" outside of "Section N of [bracketed-reference]" is assumed to be "Section N of the current document", and that's all that the htmlization script is going to give you, since it's not working with the semantic richness of the XML source. We do, however, as of fairly recently have a "v3" XML format, which is capable of producing native HTML output that includes SVG figures and the other exciting features of "v3 XML". For an example, see https://www.ietf.org/id/draft-ietf-tsvwg-datagram-plpmtud-19.html . I personally haven't done any v2-to-v3 conversions yet (too busy reading to have time to do much writing), but the FAQ entry for doing so is at https://www.rfc-editor.org/materials/FAQ-xml2rfcv3.html#name-how-do-i-convert-my-xml-fil<https://www.rfc-editor.org/materials/FAQ-xml2rfcv3..html#name-how-do-i-convert-my-xml-fil> . Hope that helps, Ben _______________________________________________ OAuth mailing list OAuth@ietf.org<mailto:OAuth@ietf.org> https://www.ietf.org/mailman/listinfo/oauth CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
