Re: [xml2rfc] XInclude should be used instead of PI include
Kesara Rathnayake <kesara@staff.ietf.org> Tue, 27 June 2023 04:46 UTC
Return-Path: <kesara@staff.ietf.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B538DC151076 for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 21:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KBzGv0-2Ln0F for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 21:46:36 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05407C14CE24 for <xml2rfc@ietf.org>; Mon, 26 Jun 2023 21:46:35 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-98e1d3be004so316998266b.1 for <xml2rfc@ietf.org>; Mon, 26 Jun 2023 21:46:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20221208.gappssmtp.com; s=20221208; t=1687841193; x=1690433193; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=UKVAVRkkc9cOvcVwVb26R8638FuCD8DcevjaFujw8e8=; b=ouUvyidcLpUq3RLjKJF6EYF2jzQjqIzH/2JZyWRZ8JtARBiB66XO17LCGGKNrvkgwg KccpkSgJqpHTaphoMb86/SXvhXEd8hEdLKSBsZSVLLmjTIQIaadBPEoiLrCOFNgATV05 NLiSA4brcXqO7EnrcjIwceqSIePkxr62Z+YOEbE4IgTHFd4F6cbL/Ujd0JYt06O3suo8 pjQ9hr8PyFwZzHct+ZU8Avtlz6I+IDBJb2FzuM5fyfec7g6dT7FCIRH6ZBWCDRIR3MUh k1FZ8b0WVvsQnbUUfUQZ/RqGvwm0IhF84YjbwCMktivGm4S3lEbD8XfM5iCfAKvZ3wL/ PhMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687841193; x=1690433193; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=UKVAVRkkc9cOvcVwVb26R8638FuCD8DcevjaFujw8e8=; b=XRBcDKk25/qibtSQ7XhmOkdcad8jYPCxm49ipXvPpiwweMMqqwE3FUhX8wIg+d6dgZ mwmVk+96xzuUFxX8pQ6U4LBPHf5eJAbROV9nf+7GtmwNpnRz7Y1QFaxd21kYJVhY4vRr M2CXkqGe7DWd4940S/RDdF9micRrIgfeavKdd4PugQhNHBulyQf2tW+ow1p27lQDsx5t Awbh+Q9uPOK85viJPtfOr4Whn9cAEDto+ClXW2XDkvRMVUS6efb7fl4m4BCEDcQmHTFq SnKDB4D0piHAfu1AJsraYz+WpxCj4VI4Ndpf+J3o0d/RHV4jjkS0+OCSIMYHJM0ARUhg 8QbA==
X-Gm-Message-State: AC+VfDwHjz9FRMSA51L7mWQjegekZPhcZYJYhIekmy2q0s7N9Yscx3Mb /1jIi9+7lb/689CiAeHHa1g+s8DqcGSYt0QnGfcezAjRKVLFYesUzC65Kg==
X-Google-Smtp-Source: ACHHUZ5Cv51931AS8f+ohlwH1A4XPOiXiqlobS8iLuAn8lpd3KsBGN3EFoKLUgrr8sMQcTw/Q07l6lCPXjzrpzPS5bQ=
X-Received: by 2002:a17:906:730c:b0:988:9ec1:a8c5 with SMTP id di12-20020a170906730c00b009889ec1a8c5mr22869783ejc.55.1687841193311; Mon, 26 Jun 2023 21:46:33 -0700 (PDT)
MIME-Version: 1.0
References: <m2v8f9ua1d.wl-randy@psg.com> <1C2D7469-A3FE-4029-9F5F-649E2AC3B390@nostrum.com> <m2ttutu5b9.wl-randy@psg.com> <CAD2=Z86oWFs6yPm6Fzt1S4HbFJnP8t=qE58c8NnFo-L=UouRiw@mail.gmail.com> <m2o7l1u11k.wl-randy@psg.com>
In-Reply-To: <m2o7l1u11k.wl-randy@psg.com>
From: Kesara Rathnayake <kesara@staff.ietf.org>
Date: Tue, 27 Jun 2023 16:46:22 +1200
Message-ID: <CAD2=Z86Nr1KnpPQNNu55kL75i5D9CaHXa0WDngkKxBJMLeHU+A@mail.gmail.com>
To: Randy Bush <randy@psg.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, xml2rfc@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/JI4CjqOIUUR4jPAX6WV8RACibT8>
Subject: Re: [xml2rfc] XInclude should be used instead of PI include
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jun 2023 04:46:39 -0000
Hi Randy, On Tue, 27 Jun 2023 at 13:49, Randy Bush <randy@psg.com> wrote: > > > Unless I'm missing something obvious here > > that's my traditional role > :) > > xml2rfc has implemented "XInclude" similarly to RFC PI include. Both > > look at the cache directory for the BibXML first. So "XInclude" will > > work offline if you have BibXML references in the cache directory. > > i read https://authors.ietf.org/en/references-in-rfcxml and see no clue > to a "cache directory." > That document needs some improvement. You can provide a cache directory with `--cache, -c = PATH ` See https://ietf-tools.github.io/xml2rfc/#appendix-B.5-1.4.1 And use `--no-network, -N` to avoid network resolvers. See https://ietf-tools.github.io/xml2rfc/#appendix-B.4-1.6.1 > as discussed the other day, i rsync as much as i can, though some are > broken these weeks. > > RSY="/usr/bin/rsync -vaHx --delete" > > $RSY rfc-editor.org::rfcs-text-only $HOME/rfcs > $RSY rsync.ietf.org::internet-drafts $HOME/ids > # old + new, though i really want only old > $RSY rsync.ietf.org::id-archive $HOME/ids.old > # for xml2rfc > $RSY rsync.ietf.org::xml2rfc.bibxml/bibxml $HOME/refs/rfc > $HOME/bin/do-allid > > that last being a ruby blob i was given the last time things broke for > me > After setting up your rsync data directories, how do you run xml2rfc? What configuration options do you use? Cheers, Kesara > i am old and slow, so need specific recipes. > > randy -- Kesara Rathnayake Senior Software Development Engineer - IETF Administration LLC kesara@staff.ietf.org
- [xml2rfc] XInclude should be used instead of PI i… Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Carsten Bormann
- Re: [xml2rfc] XInclude should be used instead of … Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Carsten Bormann
- Re: [xml2rfc] XInclude should be used instead of … Robert Sparks
- Re: [xml2rfc] XInclude should be used instead of … Kesara Rathnayake
- Re: [xml2rfc] XInclude should be used instead of … Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Robert Sparks
- Re: [xml2rfc] XInclude should be used instead of … Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Kesara Rathnayake
- Re: [xml2rfc] XInclude should be used instead of … Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Carsten Bormann
- Re: [xml2rfc] XInclude should be used instead of … Kesara Rathnayake
- Re: [xml2rfc] XInclude should be used instead of … Kesara Rathnayake
- Re: [xml2rfc] XInclude should be used instead of … Carsten Bormann
- Re: [xml2rfc] XInclude should be used instead of … Kesara Rathnayake
- Re: [xml2rfc] XInclude should be used instead of … Jay Daley
- Re: [xml2rfc] XInclude should be used instead of … Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Julian Reschke
- Re: [xml2rfc] XInclude should be used instead of … Carsten Bormann
- Re: [xml2rfc] XInclude should be used instead of … Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Kesara Rathnayake
- Re: [xml2rfc] XInclude should be used instead of … Carsten Bormann
- Re: [xml2rfc] XInclude should be used instead of … Kesara Rathnayake
- Re: [xml2rfc] XInclude should be used instead of … Randy Bush
- Re: [xml2rfc] XInclude should be used instead of … Carsten Bormann