[Roll] Henrik Levkowetz: Re: [xml2rfc] New xml2rfc release: 2.4.7
Michael Richardson <mcr+ietf@sandelman.ca> Thu, 22 May 2014 19:42 UTC
Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 725371A0356 for <roll@ietfa.amsl.com>; Thu, 22 May 2014 12:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level:
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_Fetx5VVv6y for <roll@ietfa.amsl.com>; Thu, 22 May 2014 12:42:17 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C54321A035A for <roll@ietf.org>; Thu, 22 May 2014 12:42:06 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 04DF420036 for <roll@ietf.org>; Thu, 22 May 2014 15:44:32 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 003E963B0B; Thu, 22 May 2014 15:42:04 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id DE60D63B09 for <roll@ietf.org>; Thu, 22 May 2014 15:42:04 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: roll@ietf.org
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="==-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Thu, 22 May 2014 15:42:04 -0400
Message-ID: <19053.1400787724@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/C7OetX32-E-RuVFQe5u2O3aAHGA
Subject: [Roll] Henrik Levkowetz: Re: [xml2rfc] New xml2rfc release: 2.4.7
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 May 2014 19:42:24 -0000
For authors who might be struggling with xml2rfc not working due to xml.resource.org having died.
--- Begin Message ---Hi Michael, On 2014-05-22 20:44 Michael Richardson said the following: > > Henrik Levkowetz <henrik@levkowetz.com> wrote: > > from: > > > http://pypi.python.org/pypi/xml2rfc > > http://tools.ietf.org/tools/xml2rfc2/cli/ > > > The purpose of this release, coming right on the heels of 2.4.6, is > > to add knowledge of alternative bibxml repositories, given that the > > usual site xml.resource.org is currently down. > > > For full details on all tickets, there's always the issue tracker: > > http://trac.tools.ietf.org/tools/xml2rfc/trac/report/. An excerpt > > from the changelog is available below. > > Perhaps you could remind me/us/the community-at-large on how to avoid > embedding xml.resources.org in our ENTITY definitions. I think that we had > no choice with the 1.x tool... but things evolve and get better. Yes. In the 2.x.x series, you can write any of these (a bare reference file name, a file name with correct relative path, and a fully qualified URL): <!ENTITY RFC3552 SYSTEM "reference.RFC.3552.xml"> <!ENTITY RFC3552 SYSTEM "public/rfc/bibxml/reference.RFC.3552.xml"> <!ENTITY RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml"> Additionally, you can keep or omit the '.xml' extension -- 2.x.x will try without, and then with, if needed, if you don't give '.xml'. For the first two above, 2.4.7 will first try to resolve the reference from cache, then from the local file system, then from the 3 internet hosts mentioned in the release notes. Finally, what 2.4.7 will do, in addition to trying the 3 host names in the release notes when you give a bare name or a relative path, is to try to replace 'xml.resource.org' as hostname in the full URL with xml2rfc.ietf.org and xml2rfc.tools.ietf.org, in order to find something which is reachable. I'm not sure the last approach is a good thing long-term, but to get us past the current situation without upsetting the lives of all draft writers, I thought it might help. > I didn't realize until I read this that the ideas on from this list may > already be implemented... I'm afraid I've been under such a deluge of work lately that I haven't managed to follow the list properly :-( Best regards, Henrik _______________________________________________ xml2rfc mailing list xml2rfc@ietf.org https://www.ietf.org/mailman/listinfo/xml2rfc--- End Message ---
-- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works IETF ROLL WG co-chair. http://datatracker.ietf.org/wg/roll/charter/
- [Roll] Henrik Levkowetz: Re: [xml2rfc] New xml2rf… Michael Richardson