http://blog.gmane.org/gmane.text.xml.rfc hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.text.xml.rfc/2921 <pre>https://github.com/nicowilliams/lyx2rfc It works well enough that I can actually write a lengthy I-D (in progress) that xml2rfc (old version) formats with minimal complaints: xml2rfc: warning: &lt;appendix/&gt; element is deprecated, use &lt;section/&gt; instead around input line 422 xml2rfc: warning: &lt;?rfc symrefs=?&gt; now defaults to "yes" around input line 436 Also, I need to add various metadata to cover PIs like whether to generate toc and so on, but it's really quite functional now. I suppose I should include a screenshot, but, there's plenty at lyx.org to get started with. Note that normally I'm very much a VIM in a screen(1) kind of a person. I just got tired of &lt;xml/&gt;, what can I say. LyX doesn't have VI keybindings, which sucks for me, but I still want to try this out for a while. Nico -- </pre> Nico Williams 2012-05-17T17:20:41 http://comments.gmane.org/gmane.text.xml.rfc/2917 <pre>xml2rfc: error: list doesn't contain element 4 around input line 168 Even if I remove all &lt;list&gt; elements I still get this. What's it mean? Nico -- </pre> Nico Williams 2012-05-12T01:08:15 http://comments.gmane.org/gmane.text.xml.rfc/2909 <pre>Has anyone written an XSLT to convert from latexml's schema to xml2rfc schema? The latexml schema is here: http://dlmf.nist.gov/LaTeXML/manual/schema/ . The reason I ask is that I'm wondering if LyX could be made to output Internet-Drafts by way of exporting to tex, then applying latexml, then postprocess with an XSLT stylesheet to convert to xml2rfc schema, finally typeset with xml2rfc. Then we'd have a WYSYWIG Internet-Draft editing tool. Nico -- </pre> Nico Williams 2012-05-03T20:33:33 http://comments.gmane.org/gmane.text.xml.rfc/2906 <pre>Is there some way to get xml2rfc to start looking where I want it to for an input file? Right now the initial browsing directory is /home/gwz, but I would much prefer that it was something else... </pre> Glen Zorn 2012-04-26T08:42:58 http://comments.gmane.org/gmane.text.xml.rfc/2905 <pre>As mentioned in a previous thread on "postcode city order", the declaration and rendering of &lt;postal&gt; elements in xml2rfc is very U.S.-centric and should be improved for international use. I'd very much appreciate the usage of a postal address format based on international treaties, not U.S. specifics. Below, I want to provide a bunch of quickly collected information regarding this topic. In Europe and other treaty nations, (nation-wide) postal codes (a.k.a. delivery codes) and international country designations (international postal codes, CEPT Codes) are combined (with a delimiting hyphen in between) and placed in front of the city name, e.g., as posted by Eliot Lear on 28 Feb 2012, 21:26:03 +0100 : | CH-8620 Wallisellen | Switzerland When this preferred form of postal code is used but postal routing through non-treaty nations with manual interpretation of addresses (by humans) is not necessary (as is common for postage via air mail), the spelled-out country name in the additional, trailing line of the address as shown above is not needed: | CH-8620 Wallisellen is sufficient for international postage. (Note that, as with E.163 telephone numbers where the "+xx " country prefix is not part of national dial strings, the postal "xx-" country designation is usually not included in strictly intra-national postal usage.) Important: The CEPT country identifiers are country designations with a varying number of (uppercase-only) latin letters, _not_ ISO 3166 country codes. These postal (CEPT) country identifiers are "borrowed by reference" (in a similar way as the DNS uses ISO 3166-1 country codes for ccTLD names) from the list of car country symbols -- a.k.a. international "Distinguishing Signs" or "UN Vehicle Codes" --, as established by the United Nation's Convention on Road Traffic (Geneva, 19 Sept 1949, Article 20 + Annex 4, and updated Vienna, 8 Nov 1968, Article 37 + Annex 3 -- see http://www.iadc-club.net/DK4/iadc/pr2/eng_con.asp ) Hence, for car country identification as well as for postal addresses, you have for instance the single-character codes: A - Austria B - Belgium C - Cuba D - Germany E - Spain F - France H - Hungary I - Italy J - Japan L - Luxembourg N - Norway P - Portugal S - Sweden V - Holy See (Vatican) ... and the three-character codes: EST - Estland FIN - Finland IRL - Ireland RSM - San Marino RUS - Russia SLO - Slovenia ... while yet other codes are the same as in ISO 3166-1, e.g.: CH - Switzerland DK - Denmark FL - Liechtenstein GB - U.K. GR - Greece HR - Croatia IL - Israel IS - Island MC - Monaco NL - Netherlands PL - Poland UA - Ukraine ... and still others are equal to the ISO 3166-2 3-letter codes. See the Wikipedia article on car country symbols (in German): http://de.wikipedia.org/wiki/Liste_der_Kfz-Nationalit%C3%A4tszeichen A comprehensive resource on country code systems is: http://www.unc.edu/~rowlett/units/codes/country.htm For more, in-depth information on postal addressing, refer to the Universal Postal Union (UPU.INT), e.g. at http://www.upu.int/en/activities/addressing/standards.html (documents do not seem to be "readily available" at large). Kind regards, Alfred. </pre> Alfred Hönes 2012-04-25T13:13:36 http://comments.gmane.org/gmane.text.xml.rfc/2892 <pre>I'm wondering if it would be possible to add a "periodspace" PI keyword so that XML like this &lt;xref target="RFC3550"&gt;Schulzrinne, et al.&lt;/xref&gt; lists using multiple clock rates produces text like this Schulzrinne, et al. [RFC3550] lists using multiple clock rates rather than text like this Schulzrinne, et al. [RFC3550] lists using multiple clock rates (note extraneous space between "et al." and " [RFC3550]". Should be a straightforward clone of the colonspace keyword... </pre> Glen Zorn 2012-04-23T04:30:16 http://comments.gmane.org/gmane.text.xml.rfc/2888 <pre>The RFC Document Style guide says: Many RFC documents have appendixes, which may be very extensive. In non-RFC documents, authors often position Appendixes at the very end, after the references. However, RFCs that have large and dense technical Appendix sections make it difficult for a reader to find references that precede the appendixes. In such cases, putting the references later may be advisable. Notwithstanding the final sentence there, xml2rfc enforces putting the references before any other section in the back matter. I assume that xml2rfc is simply enforcing the DTD from RFC 2629: &lt;!ELEMENT back (references?,section*)&gt; However, the DTD seems to be wrong on this point. I have an I-D in process that will put some back-matter content sections before the references, so I suppose I'll need to ask the RFC Editor production team to fix the order after the document is approved by the IESG (assuming it is, of course!). Peter </pre> Peter Saint-Andre 2012-04-19T21:10:13 http://comments.gmane.org/gmane.text.xml.rfc/2885 <pre>Hi everyone, I have learned that the ITU-T has made a change in the way it prefers its Recommendations to be displayed. Was: ITU-T Recommendation XXX Now: Recommendation ITU-T XXX Let me demonstrate Old/New: OLD: NEW: [ITU.X509.2000] International Telecommunications Union, "Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks", Recommendation ITU-T X.509, March 2000. What's the best way to effect this sort of change? Eliot </pre> Eliot Lear 2012-04-19T12:23:39 http://comments.gmane.org/gmane.text.xml.rfc/2884 <pre>Hi there, I just updated rfc2629.xslt (&lt;http://greenbytes.de/tech/webdav/rfc2629xslt.zip&gt;) to use XSLT2, when available. With these changes, the code should continue to run in old XSLT1 processors (such as found in browsers), but also in XSLT2 implementations that do not have the exslt:node-set extension function anymore (such as Saxon 9.4 HE). The change shouldn't cause any problems, but I haven't automated the testing of the in-browsers XSLT implementations, so it would be nice if "early adopters" help me watch for potential regressions... Best regards, Julian </pre> Julian Reschke 2012-04-14T11:26:56 http://comments.gmane.org/gmane.text.xml.rfc/2882 <pre>I'm running xml2rfc locally on a Mac OS 10.6 host and I have downloaded the RFC citation library. The citations are now in a folder, bibxml, in the same directory as my source .xml file AND another copy of bibxml is in the same directory as the xml2rfc executable. When I run xml2rfc with an xml input file that contains the following: &lt;note title="Requirements Language"&gt; &lt;t&gt;The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in &lt;xref target="RFC2119"&gt;RFC 2119&lt;/xref&gt;.&lt;/t&gt; &lt;/note&gt; I get 'unable to find external file "reference.RFC.2119.xml" or "reference.RFC.2119.xml.xml"' How do I let xml2rfc know where the citation file is to be found? P.S. This source file converts properly and without error using the online xml2rfc service. Thanks in advance for your help, --Keith _______________________ Keith Hazelton (khazelton&lt; at &gt;gmail.com) UW-Madison; Internet2 MACE _______________________________________________ xml2rfc mailing list xml2rfc&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/xml2rfc </pre> Keith Hazelton 2012-04-07T17:13:41 http://comments.gmane.org/gmane.text.xml.rfc/2880 <pre>I'm running xml2rfc locally on a Mac OS 10.6 host and I have downloaded the RFC citation library. The citations are now in a folder, bibxml, in the same directory as my source .xml file AND another copy of bibxml is in the same directory as the xml2rfc executable. When I run xml2rfc with an xml input file that contains the following: &lt;note title="Requirements Language"&gt; &lt;t&gt;The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in &lt;xref target="RFC2119"&gt;RFC 2119&lt;/xref&gt;.&lt;/t&gt; &lt;/note&gt; I get 'unable to find external file "reference.RFC.2119.xml" or "reference.RFC.2119.xml.xml"' How do I let xml2rfc know where the citation file is to be found? P.S. This source file converts properly and without error using the online xml2rfc service. Thanks in advance for your help, --Keith _______________________________________________ xml2rfc mailing list xml2rfc&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/xml2rfc </pre> Keith Hazelton 2012-04-07T17:30:02 http://comments.gmane.org/gmane.text.xml.rfc/2873 <pre>Hi all, Could you please allow an URL for input at http://xml.resource.org/ Can it please be implemented that I can give someone a link such as http://xml.resource.org/cgi-bin/xml2rfc.cgi?input=http://blah.com/rfc.xml&amp;output=html and upon viewing this link, one will see the HTML rendering of the RFC in XML which is provided as a parameter in the link. Thanks, Pander </pre> Pander 2012-03-22T09:19:00 http://comments.gmane.org/gmane.text.xml.rfc/2870 <pre>http://Old.nabble.com/RFC-format%3A-any-discussions-at-the-paris-IETF--to33334621.html is the discussion thread. Rfc-interest&lt; at &gt;rfc-editor.org Is the mailing list. </pre> Larry Masinter 2012-03-11T23:47:30 http://comments.gmane.org/gmane.text.xml.rfc/2841 <pre>I was wondering if anyone has created a conditional preprocessor for xml2rfc where alternative content could be supplied for the .html and .html.pdf editions of the document, even if the .txt version remains ASCII only and with ASCII art, the .html version could be rendered with actual unicode characters. I'm not imagining automatic conversion, but just manually supplying alternative in the .xml source. _______________________________________________ xml2rfc mailing list xml2rfc&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/xml2rfc </pre> Larry Masinter 2012-03-10T00:09:40 http://comments.gmane.org/gmane.text.xml.rfc/2840 <pre>Hi, folks, This one still seems to remain un-fixed. Any chance to fix it? Thanks! Best regards, Fernando -------- Original Message -------- Subject: Bad RFC 1108 expansion? Date: Wed, 03 Mar 2010 03:43:58 -0300 From: Fernando Gont &lt;fernando&lt; at &gt;gont.com.ar&gt; To: xml2rfc&lt; at &gt;xml.resource.org Folks, &lt;xref target="RFC1108"/&gt; incorrectly expands to: Could anybody please fix this one? Thanks! (for this, and for maintaining the tool!) Kind regards, </pre> Fernando Gont 2012-02-29T11:46:46 http://comments.gmane.org/gmane.text.xml.rfc/2823 <pre>Hi everyone, Outside of the United States it is often (though certainly not universally) true that postcodes are expected to come before cities. For instance, my work address would be as follows: Richtistrasse 7 CH-8620 Wallisellen Switzerland It would be nice if there were a simple way to indicate postcode order. Perhaps as a parameter to address, such as the following: &lt;address postcode="beforecity"&gt; With of course the appropriate default being "afterregion". What do others think? Eliot </pre> Eliot Lear 2012-02-28T20:26:03 http://comments.gmane.org/gmane.text.xml.rfc/2822 <pre>Folks, This is a kind of market research query. I periodically get queries about what ABNF parsers there are, and the IETF errata log now has an entry for a testing engine for ABNF. I'm not aware of an ABNF homesite, which is the kind of place such things are usually listed. If anyone knows of one, what is it's URL. If no one knows of such a site, do you think it would be helpful to form one? abnf.* are taken. My current thought is abacknaur.org but better choices are welcome. Thoughts? Thanks d/ ps. no this isn't an ABNF list, but there isn't one. </pre> Dave Crocker 2012-02-28T15:37:59 http://comments.gmane.org/gmane.text.xml.rfc/2821 <pre>Section 4.1.1 of the current xml2rfc README file contains a significant typo for a new keyword. It would be nice if that confusing glitch could be corrected: s/text-list-sybols/text-list-symbols/ ^ The trailing sentence of the same section indicates that such directives are "normally put ... at the beginning of the document". However, several PIs are commonly reset inside drafts to achieve specific formatting goals, for instance "subcompact", "rfcedstyle", "artworklines", "artworkdelimiter", and experience showed that changing the values of these directives works as intuitively expected; yet, I suspect that doesn't work for "text-list-symbols", which I wanted to apply specifically to achieve the appearance of an original document being updated now. Question: What was the intended behavior for "text-list-symbols": effective globally for whole document, or working modally (last given PI applies) ? Kind regards, Alfred. </pre> Alfred Hönes 2012-02-24T19:19:38 http://comments.gmane.org/gmane.text.xml.rfc/2820 <pre>Hello, The http://xml.resource.org/authoring/xml2rfc2-dev.log URL as seen on http://xml.resource.org/experimental.html does not work. grtz, </pre> Miek Gieben 2012-02-20T15:23:54 http://comments.gmane.org/gmane.text.xml.rfc/2818 <pre>Hello, have trouble trying to reference draft-ietf-pwe3-vccv-for-gal-00 in my draft. I've done this: &lt;!DOCTYPE rfc SYSTEM "rfc2629.dtd"[ &lt;!ENTITY VCCV-GAL-PW SYSTEM " http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-pwe3-vccv-for-gal-00.xml "&gt; ]&gt; ... &lt;xref target="I-D.draft-ietf-pwe3-vccv-for-gal-00" /&gt; ... &amp;VCCV-GAL-PW; ... And I get this error: INPUT: 520 ms (276 elems, 346 attrs, 1128 spaces, 13980 chars) [Error] INPUT:568:8: An element with the identifier "I-D.draft-ietf-pwe3-vccv-for-gal-00" must appear in the document. Suggestion, help or clue greatly appreciated. Regards, Greg _______________________________________________ xml2rfc mailing list xml2rfc&lt; at &gt;ietf.org https://www.ietf.org/mailman/listinfo/xml2rfc </pre> Greg Mirsky 2012-02-18T01:07:45 http://comments.gmane.org/gmane.text.xml.rfc/2810 <pre>Hello, I just started playing with xml2rfc version 2, to see how it works wrt version 1 and pandoc2rfc. Version two seems to work OK, and creates a nice looking text file. I made the following observations. It seems the Roman list style isn't supported anymore -- this was a hidden feature in xml2rfc version 1: WARNING: No %c or %d found in list format string: format %i. Or uppercase: WARNING: No %c or %d found in list format string: format %I. Also non Roman uppercase letters don't work anymore: WARNING: No %c or %d found in list format string: format %C. Also, lines like: &lt;?xml version='1.0' encoding='UTF-8'?&gt; Halfway through the document, make the parsing fail. xml2rfc(1) handles this OK (just skips it, I assume?) These lines are easily created when cutting and pasting a reference into your doc. xml2rfc(1) uses two parameters on the command line: xml2rfc &lt;infile&gt;.xml &lt;outfile&gt;.txt xml2rfc(2) discards the second one and writes &lt;infile&gt;.txt I'm not a fan of xml2rfc(1)'s behavior, but making xml2rfc(2) behave different makes upgrading harder... Things like: &lt;section title="section" anchor="section"&gt; &lt;xref target="section"/&gt;. are expanded to "Section 2.1" in xml2rfc(1) and to see "[section]" in xml2rfc(2). xml2rfc(1) add two spaces after a end-of-sentence dot, xml2rfc(2) one: 1: "back" section of an RFC. The easiest way is to create a template 2: "back" section of an RFC. The easiest way is to create a template XML In hanging paragraphs the same happens, two spaces for xml2rfc(1) and one space for xml2rfc(2). grtz, </pre> Miek Gieben 2012-02-15T10:26:40 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.text.xml.rfc