From: stpeter@jabber.org (Peter Saint-Andre) Date: Fri, 31 May 2002 17:25:30 -0500 (CDT) Subject: [xml2rfc] working on a remote server In-Reply-To: <008501c208e9$980b8850$a100000a@easyinc> Message-ID: No, *my* bad. I had those lines commented out. :0 But Marshall and I figured out that there's an extraneous 'fi;' at the end of line 4 in xml2rfc.tcl in version 1.12, so anyone using the script may need to edit line 4 to get things working correctly. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.html On Fri, 31 May 2002, Marshall Rose wrote: > > I've got #!/bin/sh -- does this need to point to something else? How do I > > determine where my TCL interpreter lives? > > my bad. it should run unaltered on your unix system (so starting with "#!" > is just fine). > > the question is why your shell sees this: > > #!/bin/sh > # the next line restarts using the correct interpreter \ > if test ! -z "$DISPLAY"; then exec wish "$0" "$0" "$@"; \ > elif test ! -z "$1"; then exec tclsh "$0" "$0" "$@"; fi; \ > else echo "usage: $0 filename" >&2; exit 1; fi > > it just ignores it and keeps running /bin/sh on the rest of the file. > > the thing going on in these five lines is this: the bourne shell (/bin/sh) > doesn't "do" multi-line comments, but tcl does. what this means is that you > can have the same file containing both shell and tcl commands. > > when /bin/sh reads the file, it does the "if" which results in either an > "exec" or an "exit" > > when tcl reads the file, it skips the 3-line "if" because it's all one > comment. > > > so, there are two ways to approach this: > > the "right" way is to ask "what /bin/sh & os are you running" because > whatever it is, it's wrong... > > the "wrong" way is for you to write your own script, say "xml2html.sh" that > looks like this: > > #!/bin/sh > exec tclsh .../xml2rfc.tcl xml2html "$@" > > i'd go with the "wrong" way since it should work okay. > > /mtr > > From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Fri, 31 May 2002 14:24:42 -0700 Subject: [xml2rfc] working on a remote server References: Message-ID: <008501c208e9$980b8850$a100000a@easyinc> > I've got #!/bin/sh -- does this need to point to something else? How do I > determine where my TCL interpreter lives? my bad. it should run unaltered on your unix system (so starting with "#!" is just fine). the question is why your shell sees this: #!/bin/sh # the next line restarts using the correct interpreter \ if test ! -z "$DISPLAY"; then exec wish "$0" "$0" "$@"; \ elif test ! -z "$1"; then exec tclsh "$0" "$0" "$@"; fi; \ else echo "usage: $0 filename" >&2; exit 1; fi it just ignores it and keeps running /bin/sh on the rest of the file. the thing going on in these five lines is this: the bourne shell (/bin/sh) doesn't "do" multi-line comments, but tcl does. what this means is that you can have the same file containing both shell and tcl commands. when /bin/sh reads the file, it does the "if" which results in either an "exec" or an "exit" when tcl reads the file, it skips the 3-line "if" because it's all one comment. so, there are two ways to approach this: the "right" way is to ask "what /bin/sh & os are you running" because whatever it is, it's wrong... the "wrong" way is for you to write your own script, say "xml2html.sh" that looks like this: #!/bin/sh exec tclsh .../xml2rfc.tcl xml2html "$@" i'd go with the "wrong" way since it should work okay. /mtr From: stpeter@jabber.org (Peter Saint-Andre) Date: Fri, 31 May 2002 15:43:50 -0500 (CDT) Subject: [xml2rfc] working on a remote server In-Reply-To: <002501c208e0$afbad9f0$a100000a@easyinc> Message-ID: > in general, this looks like that your shell isn't running tcl to interpret > the script, instead it's running the bourne shell. I've got #!/bin/sh -- does this need to point to something else? How do I determine where my TCL interpreter lives? > i frequently do things like > > % ~/bin/xml2rfc.tcl foo.xml > % ~/bin/xml2rfc.tcl /bar/foo.xml foo.html looks beautiful, hopefully i'll get to that point :) > also, what version of xml2rfc are you running? just pulled it off the website, so xml2rfc-1.12 also i have tcl8.2, but files convert fine in tclsh thanks! /stpeter From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Fri, 31 May 2002 13:20:56 -0700 Subject: [xml2rfc] working on a remote server References: Message-ID: <002501c208e0$afbad9f0$a100000a@easyinc> > Ideally I'd write a shell script to handle all this, but I don't see a way > to run xml2rfc.tcl from the command line. I followed the instructions at > http://xml.resource.org/pipermail/xml2rfc/2001-November/000067.html but I > get errors: > > ~/cvs/ietf$ ./xml2html draft-saintandre-jabber-core-00.xml > ./xml2html: package: command not found > ... in general, this looks like that your shell isn't running tcl to interpret the script, instead it's running the bourne shell. the thing to do is to take a look at xml2rfc.tcl using vi (so you can see funny characters, e.g., CTRL-M on UNIX). what you want to make sure is that: first, there aren't any funny characters; and, second, that the string that follows the "#!" refers to where your tcl interpreter is. i frequently do things like % ~/bin/xml2rfc.tcl foo.xml % ~/bin/xml2rfc.tcl /bar/foo.xml foo.html etc., and the shell knows to invoke the tcl interpreter to do all the heavy lifting. also, what version of xml2rfc are you running? /mtr From: stpeter@jabber.org (Peter Saint-Andre) Date: Fri, 31 May 2002 15:11:35 -0500 (CDT) Subject: [xml2rfc] working on a remote server Message-ID: First off, thanks for xml2rfc, it makes my life much easier! Here's my story. I edit my Internet-Drafts on a remote server with no windowing system. The working directory for my I-Ds is actually a CVS directory because I have my docs under source control. I have copied xml2rfc.tcl into ~/cvs/ietf/ but I would like the output files to go into a different directory so that I can view them via the web without exiting tclsh and copying the output file to another directory. What do I need to change in xml2rfc.tcl to do this? Can I modify dirname? Ideally I'd write a shell script to handle all this, but I don't see a way to run xml2rfc.tcl from the command line. I followed the instructions at http://xml.resource.org/pipermail/xml2rfc/2001-November/000067.html but I get errors: ~/cvs/ietf$ ./xml2html draft-saintandre-jabber-core-00.xml ./xml2html: package: command not found ./xml2html: namespace: command not found ./xml2html: namespace: command not found ./xml2html: namespace: command not found ./xml2html: proc: command not found ./xml2html: return: bad non-numeric arg `\[\]' ./xml2html: return: can only `return' from a function or sourced script ./xml2html: line 70: syntax error near unexpected token `}' ./xml2html: line 70: ` }' Any suggestions? Thanks! Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.html From: xml2rfc@lists.xml.resource.org (Doug Royer) Date: Thu, 30 May 2002 09:45:37 -0600 Subject: [xml2rfc] proposed enhancements References: <3CF5468B.5CC3F122@Royer.com> <20020529181542.177224dc.mrose@dbc.mtview.ca.us> Message-ID: <3CF64921.B06BEC1C@Royer.com> This is a cryptographically signed message in MIME format. --------------msCD014A4CE0152413C5A3F622 Content-Type: multipart/mixed; boundary="------------7F1D9E9F410F60E2342EBF71" This is a multi-part message in MIME format. --------------7F1D9E9F410F60E2342EBF71 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Marshall Rose wrote: > > > Your can ALSO release a PostScript (and PDF?) RFC. As long > > as the PostScript version and text version have exactly the > > same information. With of course the PostScript version looking > > better. So, why not allow images in the HTML version? > > because the text version is required to be definitive... I agree that the text version *is* the authoritative version. But how does that negate having non-stick images in PostScript, PDF, and HTML? If no one wants to do that work - then okay. But per RFC guidelines, you can do that in PostScript and release the PostScript version (with its pretty images) at the same time as the authoritative and equivalent text version. --------------7F1D9E9F410F60E2342EBF71 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:INET-Consulting LLC adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;-29152 fn:Doug Royer end:vcard --------------7F1D9E9F410F60E2342EBF71-- --------------msCD014A4CE0152413C5A3F622 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIKQwYJKoZIhvcNAQcCoIIKNDCCCjACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B88wggSZMIIEAqADAgECAhA85nVyQ1LlncKock/RLC9dMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDEyMjAwMDAw MFoXDTAyMTAxMjIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0B CQEWDmRvdWdAcm95ZXIuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7uTPDnj/U t/EKae6vnKPIWpCI2HoHAl3n5uSf/gIwD4Z+j3gewsR0Dm70bjAcWxwps6FNphsMUBolBwKo L73DGK8NNSz+G8fvzMrDa6SA+Pv/hv0IhkqqmCkEdgawKzzs3i3t3qQy8zOVhXNQSkhUvzlu TDNi0FS2bsCepU7hwwIDAQABo4IBODCCATQwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMDAGCmCGSAGG+EUBBgcEIhYgMTgwNjlhZjY3YjMyNzNhNTAyMzQw MWRjMjU3MWY3NjQwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20v Y2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQAirjMwaw74Gbr3M61qm+BnzaNOeTMvriFN twfq1XDwgW4VBGhP1jHFL1bg6TJwEonPLJepixj0Y6/SahwkG1QUo86aCyJSyrB7qWl5q4PI XvjcGvN3jgVLlM5CYcXIyEXL9sGm8hxdxPB15yKd519QNkzNp+sd5QU8Ww5DM0AYczCCAy4w ggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYT AlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1 MTIyMzU5NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5 L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24g Q2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVk MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xU v7zodyqdufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbaw NkIztW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQAB o3wwejARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsG CCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYB Af8CAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEe kmptL/bxndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPH vhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWi kK5uMYICPDCCAjgCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW YWxpZGF0ZWQCEDzmdXJDUuWdwqhyT9EsL10wCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMjA1MzAxNTQ1MzdaMCMGCSqGSIb3DQEJ BDEWBBTpmqAUPA+/nst9IkC5dP00IeqN+TBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIB KDANBgkqhkiG9w0BAQEFAASBgHyP9ZA9Fydm2TCazB48M+zhDy1ydQ8wipvoBqUuMi59uo2K +oGfzjhW+Sqd8hqqlWWQsWVdivnWD4smIhzJRRSs331pS+iKVQJ8qtzudIhY9e1RgDR3oKuX f4iB397te9ML8/rh9z/7UkiieIYe/xUwLDZ44RceoWtfRfjijhAY --------------msCD014A4CE0152413C5A3F622-- From: molter@tin.it (Marco Molteni) Date: Thu, 30 May 2002 09:39:45 +0200 Subject: [xml2rfc] THANKS for xml2rfc :-) Message-ID: <20020530073945.5263.qmail@cobweb.example.org> Hi all, I am writing my first draft. Being a Unix fanatic, I tried with the nroff machinery, then some friends suggested xml2rfc... and everything looked sweet. I really want to thank Marshall Rose for giving away this tool. If we meet somewhere, a beer is waiting for you :-) Marco Molteni From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Wed, 29 May 2002 23:29:39 -0700 Subject: [xml2rfc] proposed enhancements In-Reply-To: References: <20020529142734.62d49938.mrose@dbc.mtview.ca.us> Message-ID: <20020529232939.3f05e2a2.mrose@dbc.mtview.ca.us> > Given: > > As explained in , the host MUST ... > > Currently I get: > > As explained in "Security Considerations", the host MUST ... > > I'd like a processing option to generate: > > As explain in Section 4.1 the host MUST ... > > and have the tool handle the numbering automatically for me. > > (I agree that the former is nicer to read, but in long docs, with long > section headings, a section number makes things easier to find.) > > Make sense? err, no. are we talking about text or html output? input text output html output ----- ----------- ----------- Section 1.2 foo's-title References: <3CF5468B.5CC3F122@Royer.com> Message-ID: <20020529181542.177224dc.mrose@dbc.mtview.ca.us> > Your can ALSO release a PostScript (and PDF?) RFC. As long > as the PostScript version and text version have exactly the > same information. With of course the PostScript version looking > better. So, why not allow images in the HTML version? because the text version is required to be definitive... /mtr From: rohan@cisco.com (Rohan Mahy) Date: Wed, 29 May 2002 15:41:28 -0700 (Pacific Daylight Time) Subject: [xml2rfc] proposed enhancements In-Reply-To: <20020529142734.62d49938.mrose@dbc.mtview.ca.us> Message-ID: On Wed, 29 May 2002, Marshall Rose wrote: > > 1) internal cross references using xref always display the section > > heading which can be verbose. It would be nice to have an option to use > > the section number instead. Perhaps this could be an xref attribute, > > something like... > > if you use text, doesn't the "right" thing happen? > > /mtr Hi, Given: As explained in , the host MUST ... Currently I get: As explained in "Security Considerations", the host MUST ... I'd like a processing option to generate: As explain in Section 4.1 the host MUST ... and have the tool handle the numbering automatically for me. (I agree that the former is nicer to read, but in long docs, with long section headings, a section number makes things easier to find.) Make sense? thanks, -rohan From: rohan@cisco.com (Rohan Mahy) Date: Wed, 29 May 2002 15:28:05 -0700 (Pacific Daylight Time) Subject: [xml2rfc] proposed enhancements In-Reply-To: Message-ID: On Wed, 29 May 2002, Julian Reschke wrote: > > From: xml2rfc-admin@lists.xml.resource.org > > [mailto:xml2rfc-admin@lists.xml.resource.org]On Behalf Of Rohan Mahy > > Sent: Wednesday, May 29, 2002 5:40 PM > > To: xml2rfc@lists.xml.resource.org > > Subject: [xml2rfc] proposed enhancements > > > > > > Hi, > > > > I think the xml2rfc is excellent. I have some proposed enhancements for > > future versions. Please accept my apologies from any duplicate > > suggestions. > > > > 1) internal cross references using xref always display the section > > heading which can be verbose. It would be nice to have an option to use > > the section number instead. Perhaps this could be an xref attribute, > > something like... you didn't comment on this one. is this now soemwhere on the "nice-to-have" list? > > 2) external cross references currently use the [1] notation. I imagine > > that folks working in the security area especially would appreciate the > > option to generate references using the reference convention of the crypto > > community [Bra98]. Likewise I imagine this could be an xref attribute... > > > > That's available as xmlrfc processing instruction. ok, it was not immediately clear from the description that the symrefs instruction did that. > > 3) It would be really nice to be able to include images as alternates to > > ASCII artwork when generating the HTML version. This is the only > > compelling reason to still generate a postscript or PDF version of a doc. > > > >
> > ... begin ASCII art from hell.... > >
> > How do you get them into an RFC (which as ASCII by definition). you use it for internet drafts which you can submit in multiple formats. when generating nroff or text you display the ascii artwork; when generating the html you display the alternate content instead. the SIP specification, for example, has line drawings in the PDF and postscript versions and comparable ASCII art in the (normative) text version. People refer to the text version for reference, but they always use the PDF version for their first read through. > > 4) when there are more than two or three authors, the footer displays: > > > > Firstauthor, et al. > > > > sometimes it would be nice to have a more descriptive footer (like "The > > FOOBAR WG Chairs", or "The IAB", or whatever.) > > The format for the footer is defined by the RFC editor. see (for example) the footer in RFC2804 "IAB & IESG" > > 5) generating PDF automatically of the HTML version would be lovely... > > I'm working on that. excellent thanks, -rohan From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Wed, 29 May 2002 14:27:34 -0700 Subject: [xml2rfc] proposed enhancements In-Reply-To: References: Message-ID: <20020529142734.62d49938.mrose@dbc.mtview.ca.us> > 1) internal cross references using xref always display the section > heading which can be verbose. It would be nice to have an option to use > the section number instead. Perhaps this could be an xref attribute, > something like... if you use text, doesn't the "right" thing happen? /mtr From: xml2rfc@lists.xml.resource.org (Doug Royer) Date: Wed, 29 May 2002 15:22:19 -0600 Subject: [xml2rfc] proposed enhancements References: Message-ID: <3CF5468B.5CC3F122@Royer.com> This is a cryptographically signed message in MIME format. --------------msBCABF47100E27DE69B7829C6 Content-Type: multipart/mixed; boundary="------------9ED60AA63EAAC5CD45487A41" This is a multi-part message in MIME format. --------------9ED60AA63EAAC5CD45487A41 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Julian Reschke wrote: > > > 3) It would be really nice to be able to include images as alternates to > > ASCII artwork when generating the HTML version. This is the only > > compelling reason to still generate a postscript or PDF version of a doc. > > > >
> > ... begin ASCII art from hell.... > >
> > How do you get them into an RFC (which as ASCII by definition). Your can ALSO release a PostScript (and PDF?) RFC. As long as the PostScript version and text version have exactly the same information. With of course the PostScript version looking better. So, why not allow images in the HTML version? > > 4) when there are more than two or three authors, the footer displays: > > > > Firstauthor, et al. > > > > sometimes it would be nice to have a more descriptive footer (like "The > > FOOBAR WG Chairs", or "The IAB", or whatever.) > > The format for the footer is defined by the RFC editor. I do not think it is not a forced issue - as long as it fits you can have multiple. Even the newest ID-proposal does not force one author on the footer. --------------9ED60AA63EAAC5CD45487A41 Content-Type: text/x-vcard; charset=us-ascii; name="Doug.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Doug Royer Content-Disposition: attachment; filename="Doug.vcf" begin:vcard n:Royer;Doug tel;pager:pager@Royer.com tel;cell:208-520-4044 tel;fax:866-594-8574 tel;work:866-594-8574 x-mozilla-html:FALSE url:http://Royer.com/People/Doug org:INET-Consulting LLC adr:;;1795 W. Broadway #266;Idaho Falls;Idaho;83402;U.S.A. version:2.1 email;internet:Doug@Royer.com title:Chief Executive Manager x-mozilla-cpt:;-29152 fn:Doug Royer end:vcard --------------9ED60AA63EAAC5CD45487A41-- --------------msBCABF47100E27DE69B7829C6 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIKQwYJKoZIhvcNAQcCoIIKNDCCCjACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC B88wggSZMIIEAqADAgECAhA85nVyQ1LlncKock/RLC9dMA0GCSqGSIb3DQEBBAUAMIHMMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5 IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAyMDEyMjAwMDAw MFoXDTAyMTAxMjIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO ZXRzY2FwZSBGdWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0B CQEWDmRvdWdAcm95ZXIuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7uTPDnj/U t/EKae6vnKPIWpCI2HoHAl3n5uSf/gIwD4Z+j3gewsR0Dm70bjAcWxwps6FNphsMUBolBwKo L73DGK8NNSz+G8fvzMrDa6SA+Pv/hv0IhkqqmCkEdgawKzzs3i3t3qQy8zOVhXNQSkhUvzlu TDNi0FS2bsCepU7hwwIDAQABo4IBODCCATQwCQYDVR0TBAIwADCBrAYDVR0gBIGkMIGhMIGe BgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t L0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMCAQEaPVZlcmlTaWduJ3Mg Q1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJ YIZIAYb4QgEBBAQDAgeAMDAGCmCGSAGG+EUBBgcEIhYgMTgwNjlhZjY3YjMyNzNhNTAyMzQw MWRjMjU3MWY3NjQwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20v Y2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQAirjMwaw74Gbr3M61qm+BnzaNOeTMvriFN twfq1XDwgW4VBGhP1jHFL1bg6TJwEonPLJepixj0Y6/SahwkG1QUo86aCyJSyrB7qWl5q4PI XvjcGvN3jgVLlM5CYcXIyEXL9sGm8hxdxPB15yKd519QNkzNp+sd5QU8Ww5DM0AYczCCAy4w ggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYT AlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1 MTIyMzU5NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5 L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24g Q2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVk MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xU v7zodyqdufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbaw NkIztW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQAB o3wwejARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsG CCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYB Af8CAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEe kmptL/bxndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPH vhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWi kK5uMYICPDCCAjgCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3Jl cG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9W ZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBW YWxpZGF0ZWQCEDzmdXJDUuWdwqhyT9EsL10wCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMjA1MjkyMTIyMjJaMCMGCSqGSIb3DQEJ BDEWBBR6PNRq5mQl7/b+1MSe4UUFgvZaRjBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIB KDANBgkqhkiG9w0BAQEFAASBgDAbvrheoURwXAQ8iE1ifamyG+u4C1ttJ3uZh11FFpaAKFc2 0gxY45kfGTNFze2vZ789FOn5vb8ppapsqA+i1LDPsKq14fS9v9Erpcsi/eOUgMUNpo6g3AuS lBpUIDBudbSEhrWsN79j2d3u5hoZOdyKNPk2Ml+FtjkgE3onBbDg --------------msBCABF47100E27DE69B7829C6-- From: julian.reschke@gmx.de (Julian Reschke) Date: Wed, 29 May 2002 22:47:06 +0200 Subject: [xml2rfc] proposed enhancements In-Reply-To: Message-ID: > From: xml2rfc-admin@lists.xml.resource.org > [mailto:xml2rfc-admin@lists.xml.resource.org]On Behalf Of Rohan Mahy > Sent: Wednesday, May 29, 2002 5:40 PM > To: xml2rfc@lists.xml.resource.org > Subject: [xml2rfc] proposed enhancements > > > Hi, > > I think the xml2rfc is excellent. I have some proposed enhancements for > future versions. Please accept my apologies from any duplicate > suggestions. > > 1) internal cross references using xref always display the section > heading which can be verbose. It would be nice to have an option to use > the section number instead. Perhaps this could be an xref attribute, > something like... > > 2) external cross references currently use the [1] notation. I imagine > that folks working in the security area especially would appreciate the > option to generate references using the reference convention of the crypto > community [Bra98]. Likewise I imagine this could be an xref attribute... > Thet's available as xmlrfc processing instruction. > 3) It would be really nice to be able to include images as alternates to > ASCII artwork when generating the HTML version. This is the only > compelling reason to still generate a postscript or PDF version of a doc. > >
> ... begin ASCII art from hell.... >
How do you get them into an RFC (which as ASCII by definition). > 4) when there are more than two or three authors, the footer displays: > > Firstauthor, et al. > > sometimes it would be nice to have a more descriptive footer (like "The > FOOBAR WG Chairs", or "The IAB", or whatever.) The format for the footer is defined by the RFC editor. > 5) generating PDF automatically of the HTML version would be lovely... I'm working on that. From: rohan@cisco.com (Rohan Mahy) Date: Wed, 29 May 2002 08:40:17 -0700 (Pacific Daylight Time) Subject: [xml2rfc] proposed enhancements Message-ID: Hi, I think the xml2rfc is excellent. I have some proposed enhancements for future versions. Please accept my apologies from any duplicate suggestions. 1) internal cross references using xref always display the section heading which can be verbose. It would be nice to have an option to use the section number instead. Perhaps this could be an xref attribute, something like... 2) external cross references currently use the [1] notation. I imagine that folks working in the security area especially would appreciate the option to generate references using the reference convention of the crypto community [Bra98]. Likewise I imagine this could be an xref attribute... 3) It would be really nice to be able to include images as alternates to ASCII artwork when generating the HTML version. This is the only compelling reason to still generate a postscript or PDF version of a doc.
... begin ASCII art from hell....
4) when there are more than two or three authors, the footer displays: Firstauthor, et al. sometimes it would be nice to have a more descriptive footer (like "The FOOBAR WG Chairs", or "The IAB", or whatever.) 5) generating PDF automatically of the HTML version would be lovely... thanks, -rohan From: mcr@sandelman.ottawa.on.ca (Michael Richardson) Date: Mon, 20 May 2002 17:30:20 -0400 Subject: [xml2rfc] Normative and NON-Normative references In-Reply-To: Your message of "Fri, 17 May 2002 10:13:00 CDT." <3CE51DFC.8AB68B9B@stewart.chicago.il.us> Message-ID: <200205202130.g4KLUK101346@marajade.sandelman.ottawa.on.ca> >>>>> "Randall" == Randall Stewart writes: Randall> Normally when I write an RFC I make Randall> X References Randall> X.1 Normative References Randall> X.2 Non Normative References I asked some weeks ago... ... ... ] ON HUMILITY: to err is human. To moo, bovine. | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[ ] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [ From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Fri, 17 May 2002 10:17:24 -0700 Subject: [xml2rfc] Normative and NON-Normative references In-Reply-To: <3CE51DFC.8AB68B9B@stewart.chicago.il.us> References: <3CE51DFC.8AB68B9B@stewart.chicago.il.us> Message-ID: <20020517101724.6bcce1dc.mrose@dbc.mtview.ca.us> > > Normally when I write an RFC I make > > X References > > X.1 Normative References > > X.2 Non Normative References > > > Or something like that.. > > So what is the proper way to do this with the xml tool? I don't > see anything in the RFC about it... > > Help would be appreciated try this: ... ... /mtr From: randall@stewart.chicago.il.us (Randall Stewart) Date: Fri, 17 May 2002 10:13:00 -0500 Subject: [xml2rfc] Normative and NON-Normative references Message-ID: <3CE51DFC.8AB68B9B@stewart.chicago.il.us> Hi: I have just starting using xml2rfc and am now happily in the thick of converting my drafts to xml :> However I have a stumbling block I just found.. this may be real obvious.. but I would appreciate help on it. I have two types of referecnes Normative and Non-Normative. Normally when I write an RFC I make X References X.1 Normative References X.2 Non Normative References Or something like that.. So what is the proper way to do this with the xml tool? I don't see anything in the RFC about it... Help would be appreciated Note: Scott Bradner has told me that the RFC editor is going to start requiring this type of break out...  Thanks R -- Randall R. Stewart randall@stewart.chicago.il.us 815-342-5222 (cell phone) From: mcr@sandelman.ottawa.on.ca (Michael Richardson) Date: Sun, 05 May 2002 22:14:58 -0400 Subject: [xml2rfc] how to control TOC depth In-Reply-To: Your message of "Tue, 30 Apr 2002 20:08:17 EDT." <200205010008.g4108HD04397@marajade.sandelman.ottawa.on.ca> Message-ID: <200205060215.g462Ewu26556@marajade.sandelman.ottawa.on.ca> -----BEGIN PGP SIGNED MESSAGE----- >>>>> "Michael" == Michael Richardson writes: Michael> The RFC Editor has asked me: >> 2. Shorten the Table of Contents. It is too detailed for a 50 page >> document. We suggest carrying the TOC 2 levels deep. Please see >> "Table of Contents" section at: >> >> http://www.rfc-editor.org/policy.html Michael> Is there a way to provide a clue to the output routines how deep Michael> to go? http://www.sandelman.ca/SSW/freeswan/oeid/killtoodeepcontents.pl fixes the depth being too deep, and replaces the Copyright with the RFC version. I run stuff from Make, as: rfc_pg: utils/rfc_pg.c draft-richardson-ipsec-opportunistic.txt: draft-richardson-ipsec-opportunistic.nr rfc_pg perl utils/killtoodeepcontents.pl draft-richardson-ipsec-opportunistic.nr \ | nroff -ms \ | sed -e 's/FORMFEED\[Page/ \[Page/' | ./rfc_pg -n5 >draft-richardson-ipsec-opportunistic.txt draft-richardson-ipsec-opportunistic.nr: src/draft-richardson-ipsec-opportunistic.xml XML_LIBRARY=$(XML_LIBRARY):./src xml2rfc xml2nroff $? $@ (where utils/rfc_pg.c is from 2-nroff.template file) ] ON HUMILITY: to err is human. To moo, bovine. | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[ ] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 Comment: Finger me for keys iQCVAwUBPNXnH4qHRg3pndX9AQHIvAP7BcCBxh1n5B3927+tqKpVWcin6sHAg6fi QMydm15KgPQN3GE2j5kik7lZkk/McCnbxZR2YwgB0mSqCLSQjpIRUSJ1RXIWb07F IzFHDn1gjIcFqQE9Udk1j0hlgBVpKVey78gpnvzRifm7FLx1kdQ9kUcVCw1ukDjL VhWjBgtqMQI= =pwf3 -----END PGP SIGNATURE----- From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Sun, 5 May 2002 14:48:57 -0700 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <1020581319.722.3.camel@holyspirit> References: <1020356320.528.14.camel@holyspirit> <20020503010012.45ceabdc.mrose@dbc.mtview.ca.us> <1020434619.1491.4.camel@holyspirit> <20020503093427.2a27f1c7.mrose@dbc.mtview.ca.us> <1020581319.722.3.camel@holyspirit> Message-ID: <20020505144857.35767806.mrose@dbc.mtview.ca.us> > By the way, where should I mail to if I want to contribute to the > archive? if you want to contribute to the archive, send the .xml to webmaster@xml.resource.org. to see what completed RFCs already exist, go to http://xml.resource.org/public/rfc/xml/ /mtr From: alan@halfkilo.com (Chu Alan) Date: 05 May 2002 14:55:41 +0800 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <5.1.0.14.2.20020504225849.01b255a8@mira-sjcm-4.cisco.com> References: <1020434619.1491.4.camel@holyspirit> <5.1.0.14.2.20020504225849.01b255a8@mira-sjcm-4.cisco.com> Message-ID: <1020581741.723.6.camel@holyspirit> On Sun, 2002-05-05 at 14:01, Fred Baker wrote: > At 07:26 PM 5/3/2002 +0200, Julian Reschke wrote: > >I don't think you can just put something under the GPL if all you did was > >editing the text format... RFC's copyright belongs to IETF. > > yes. I'd suggest that this be run by chair@ietf.org. > > _______________________________________________ > xml2rfc mailing list > xml2rfc@lists.xml.resource.org > http://lists.xml.resource.org/mailman/listinfo/xml2rfc > I feel guilty because of this .... ;( -- Alan From: alan@halfkilo.com (Chu Alan) Date: 05 May 2002 14:48:37 +0800 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <20020503093427.2a27f1c7.mrose@dbc.mtview.ca.us> References: <1020356320.528.14.camel@holyspirit> <20020503010012.45ceabdc.mrose@dbc.mtview.ca.us> <1020434619.1491.4.camel@holyspirit> <20020503093427.2a27f1c7.mrose@dbc.mtview.ca.us> Message-ID: <1020581319.722.3.camel@holyspirit> On Sat, 2002-05-04 at 00:34, Marshall Rose wrote: > > > would you like to license those XML files under GPL? I have created a > > project > > in sourceforge (http://sourceforge.net/projects/xmlrfc/), since they > > have fine > > servers ... ^.^ > > > > Sorry for not asking this on the mailing list first, because I did not > > know > > there is such a mailing list when I for apply the project. > > alan - i don't have a problem in releasing the partial files, but a lot of red flags are raised by the fact that you established a sourceforge project without checking around. enthusiasm is great, but i'm concerned when someone plunges head first into something without doing the most basic research... > > i'll talk to some folks and get back to you. > > /mtr > By the way, where should I mail to if I want to contribute to the archive? -- Alan From: alan@halfkilo.com (Chu Alan) Date: 05 May 2002 14:43:24 +0800 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <5.1.0.14.2.20020504225849.01b255a8@mira-sjcm-4.cisco.com> References: <1020434619.1491.4.camel@holyspirit> <5.1.0.14.2.20020504225849.01b255a8@mira-sjcm-4.cisco.com> Message-ID: <1020581005.722.1.camel@holyspirit> On Sun, 2002-05-05 at 14:01, Fred Baker wrote: > At 07:26 PM 5/3/2002 +0200, Julian Reschke wrote: > >I don't think you can just put something under the GPL if all you did was > >editing the text format... RFC's copyright belongs to IETF. > > yes. I'd suggest that this be run by chair@ietf.org. > > _______________________________________________ > xml2rfc mailing list > xml2rfc@lists.xml.resource.org > http://lists.xml.resource.org/mailman/listinfo/xml2rfc > oops ... I have missed out this point ... *sigh* ... -- Alan From: fred@cisco.com (Fred Baker) Date: Sat, 04 May 2002 23:01:57 -0700 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: References: <1020434619.1491.4.camel@holyspirit> Message-ID: <5.1.0.14.2.20020504225849.01b255a8@mira-sjcm-4.cisco.com> At 07:26 PM 5/3/2002 +0200, Julian Reschke wrote: >I don't think you can just put something under the GPL if all you did was >editing the text format... RFC's copyright belongs to IETF. yes. I'd suggest that this be run by chair@ietf.org. From: julian.reschke@gmx.de (Julian Reschke) Date: Fri, 3 May 2002 19:26:14 +0200 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <1020434619.1491.4.camel@holyspirit> Message-ID: > would you like to license those XML files under GPL? I have created a > project > in sourceforge (http://sourceforge.net/projects/xmlrfc/), since they > have fine > servers ... ^.^ I don't think you can just put something under the GPL if all you did was editing the text format... RFC's copyright belongs to IETF. From: alan@halfkilo.com (Chu Alan) Date: 04 May 2002 00:55:51 +0800 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <20020503093427.2a27f1c7.mrose@dbc.mtview.ca.us> References: <1020356320.528.14.camel@holyspirit> <20020503010012.45ceabdc.mrose@dbc.mtview.ca.us> <1020434619.1491.4.camel@holyspirit> <20020503093427.2a27f1c7.mrose@dbc.mtview.ca.us> Message-ID: <1020444951.1490.13.camel@holyspirit> On Sat, 2002-05-04 at 00:34, Marshall Rose wrote: > > > would you like to license those XML files under GPL? I have created a > > project > > in sourceforge (http://sourceforge.net/projects/xmlrfc/), since they > > have fine > > servers ... ^.^ > > > > Sorry for not asking this on the mailing list first, because I did not > > know > > there is such a mailing list when I for apply the project. > > alan - i don't have a problem in releasing the partial files, but a lot of red flags are raised by the fact that you established a sourceforge project without checking around. enthusiasm is great, but i'm concerned when someone plunges head first into something without doing the most basic research... > > i'll talk to some folks and get back to you. > > /mtr > In fact I have searched on google for a few days, however somehow I did not managed found this mailing list ... I apologize for not asking before hand. :) P.S. oh, by the way, did has style="alphabets" or style="letters" to generates list with a, b, c ... ? -- Alan From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Fri, 3 May 2002 09:34:27 -0700 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <1020434619.1491.4.camel@holyspirit> References: <1020356320.528.14.camel@holyspirit> <20020503010012.45ceabdc.mrose@dbc.mtview.ca.us> <1020434619.1491.4.camel@holyspirit> Message-ID: <20020503093427.2a27f1c7.mrose@dbc.mtview.ca.us> > would you like to license those XML files under GPL? I have created a > project > in sourceforge (http://sourceforge.net/projects/xmlrfc/), since they > have fine > servers ... ^.^ > > Sorry for not asking this on the mailing list first, because I did not > know > there is such a mailing list when I for apply the project. alan - i don't have a problem in releasing the partial files, but a lot of red flags are raised by the fact that you established a sourceforge project without checking around. enthusiasm is great, but i'm concerned when someone plunges head first into something without doing the most basic research... i'll talk to some folks and get back to you. /mtr From: xml2rfc@lists.xml.resource.org (Chu Alan) Date: 03 May 2002 22:03:38 +0800 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <20020503010012.45ceabdc.mrose@dbc.mtview.ca.us> References: <1020356320.528.14.camel@holyspirit> <20020503010012.45ceabdc.mrose@dbc.mtview.ca.us> Message-ID: <1020434619.1491.4.camel@holyspirit> On Fri, 2002-05-03 at 16:00, Marshall Rose wrote: > > Hello, this is my first time to post here ;) > > > > First of all, I want to thanks for the exceptionally good RFC. > > > > Here is my finished RFC 1. > > http://html.uhome.net/rfc1/rfc1.xml > > > > Any comment? > > thanks. if you'd like to make a habit of this, if you go to http://xml.resource.org/public/rfc/xml/, you'll find a small number of RFCs that folks have already put into XML format. feel free to contribute new ones! > > if you're interested, i can provide you with "starter XML" for the ones not already there. these starter files usually have the front and back matter done. all that's missing is the middle! > > /mtr > _______________________________________________ > xml2rfc mailing list > xml2rfc@lists.xml.resource.org > http://lists.xml.resource.org/mailman/listinfo/xml2rfc > would you like to license those XML files under GPL? I have created a project in sourceforge (http://sourceforge.net/projects/xmlrfc/), since they have fine servers ... ^.^ Sorry for not asking this on the mailing list first, because I did not know there is such a mailing list when I for apply the project. -- Alan From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Fri, 3 May 2002 01:00:12 -0700 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML In-Reply-To: <1020356320.528.14.camel@holyspirit> References: <1020356320.528.14.camel@holyspirit> Message-ID: <20020503010012.45ceabdc.mrose@dbc.mtview.ca.us> > Hello, this is my first time to post here ;) > > First of all, I want to thanks for the exceptionally good RFC. > > Here is my finished RFC 1. > http://html.uhome.net/rfc1/rfc1.xml > > Any comment? thanks. if you'd like to make a habit of this, if you go to http://xml.resource.org/public/rfc/xml/, you'll find a small number of RFCs that folks have already put into XML format. feel free to contribute new ones! if you're interested, i can provide you with "starter XML" for the ones not already there. these starter files usually have the front and back matter done. all that's missing is the middle! /mtr From: alan@halfkilo.com (Chu Alan) Date: 03 May 2002 00:18:40 +0800 Subject: [xml2rfc] My first converted RFC (RFC 1) to XML Message-ID: <1020356320.528.14.camel@holyspirit> Hello, this is my first time to post here ;) First of all, I want to thanks for the exceptionally good RFC. Here is my finished RFC 1. http://html.uhome.net/rfc1/rfc1.xml Any comment? -- Alan From: mcr@sandelman.ottawa.on.ca (Michael Richardson) Date: Wed, 01 May 2002 17:31:38 -0400 Subject: [xml2rfc] bibtex reference for RFCs Message-ID: <200205012131.g41LVdA20352@marajade.sandelman.ottawa.on.ca> -----BEGIN PGP SIGNED MESSAGE----- Now that we have this wonderful bibliography in XML of RFCs on xml.resource.org, it seems that it should be trivial to convert to other formats - bibtex for instance. A trivial search revealed some targets: http://liinwww.ira.uka.de/bibliography/Distributed/rfc.html points to ftp://ftp.math.utah.edu/pub/tex/bib/rfc.bib which no longer accepts anon-ftp, but: http://www.math.utah.edu:8080/pub/tex/bib/rfc.html which is HTML-ized, but, a bit of deduction on the above gets me: http://www.math.utah.edu:8080/pub/tex/bib/rfc.bib as the raw file, but whose last entry is 2520. Other hits, include a question in 1990 from someone looking for such an repository... And then there is RFC1807, which defines another format. And... http://www.cc.gatech.edu/classes/RWL/Projects/citation/Docs/Marketing/fall98.nathan.results/bp.html which suggests that it is a program written in Perl to convert from different formats, but no link to the program itself. ] ON HUMILITY: to err is human. To moo, bovine. | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[ ] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 Comment: Finger me for keys iQCVAwUBPNBeuIqHRg3pndX9AQG4UgP/XlFiewK1JfZfWQ240RDxKnDUhyOELNRC 3JFSreY86zkEJkMM6mIdxDwgc0t/2m1E/C2WDZetCCjZ7NxvzW5OpPGKS9Y3UpRA D1GraDrewchetS3ocPQUhdYlteX+FGxQ/dEGJCS9CPJNIuNaVDASs4fQZSI4qnxP VMtVm/huUbY= =eOhm -----END PGP SIGNATURE----- From: mrose@dbc.mtview.ca.us (Marshall Rose) Date: Wed, 1 May 2002 11:25:10 -0700 Subject: [xml2rfc] how to control TOC depth In-Reply-To: <200205010008.g4108HD04397@marajade.sandelman.ottawa.on.ca> References: <200205010008.g4108HD04397@marajade.sandelman.ottawa.on.ca> Message-ID: <20020501112510.232819da.mrose@dbc.mtview.ca.us> > >2. Shorten the Table of Contents. It is too detailed for a 50 page > >document. We suggest carrying the TOC 2 levels deep. Please see > >"Table of Contents" section at: > > > > http://www.rfc-editor.org/policy.html > > Is there a way to provide a clue to the output routines how deep to go? no. i can add something in the next release. for now, just edit the nroff file that you're giving the rfc editor. > In addition, it appears that there may be two reference sections required > according to this new policy. > > A standard way to mark a reference as normative or informative may be required. the element has an optional title attribute and can occur more than once. what folks normally do is: ... ... /mtr From: mcr@sandelman.ottawa.on.ca (Michael Richardson) Date: Tue, 30 Apr 2002 20:08:17 -0400 Subject: [xml2rfc] how to control TOC depth Message-ID: <200205010008.g4108HD04397@marajade.sandelman.ottawa.on.ca> -----BEGIN PGP SIGNED MESSAGE----- The RFC Editor has asked me: >2. Shorten the Table of Contents. It is too detailed for a 50 page >document. We suggest carrying the TOC 2 levels deep. Please see >"Table of Contents" section at: > > http://www.rfc-editor.org/policy.html Is there a way to provide a clue to the output routines how deep to go? In addition, it appears that there may be two reference sections required according to this new policy. A standard way to mark a reference as normative or informative may be required. ] ON HUMILITY: to err is human. To moo, bovine. | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[ ] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 Comment: Finger me for keys iQCVAwUBPM8x74qHRg3pndX9AQHfvwP/QA5Q8hDwgb9nsH44BbRKjeUMAToAbTxB UsLieoYKlWnWeeytcmgsC3DRKCq+m4CuZAOkqBGHidV4HshnMm10p+NKNKUeiciO +79mSouzwOUnpHH8usbJNDbGwJe1qMVxF7OfHDJlqK6BPm88FCqYU1j3F0LJPKDf STTYb1igAQ8= =td5U -----END PGP SIGNATURE-----