[xml2rfc] reference src attribute
<Axel.Nennker@telekom.de> Mon, 29 May 2017 13:36 UTC
Return-Path: <prvs=31523e19a=Axel.Nennker@telekom.de>
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 20858128D44 for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 06:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level:
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 xBmRUuQ5UFma for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 06:36:27 -0700 (PDT)
Received: from mailout23.telekom.de (MAILOUT23.telekom.de [80.149.113.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1C95128A32 for <xml2rfc@ietf.org>; Mon, 29 May 2017 06:36:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1496064987; x=1527600987; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=Rqhyp7j1XFFTzTalij//MYmnXznw1JP/wTLOaJ+1FsE=; b=RrabEvGiDE2WL64Jqjof5tr7qRjG+0+3Rt4Rsn0W5qtwkLXmqRAevjHZ mjhAoMnO5HL2I9eCm9mJLxWqTkFVuT7h3RkshExn4ROHT1EMW1lDfPMU0 Xlq7BjuCxw726VCrUjWlPwzPGFiPAQmyMzeo7B3EmWAVex1S666alZAiC yuAHv8QHpuIp9/6IupFwN9F3ioRu1JjNhOPMiT7HhdLlk16unU9Rd8Z0p B5tEs0XV2phOqeJu78dehOf7X+syB+8Xa0c99kyDq6d6LhEwsoxdOYM+m eaUjwy6icPi7/5Niy0gCsJTCKnA1+hrh0qBk+i9pRERbxe732LxkbOEXs Q==;
Received: from q4de8psa04t.blf.telekom.de ([10.151.13.130]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 May 2017 15:36:24 +0200
X-IronPort-AV: E=Sophos;i="5.38,414,1491256800"; d="scan'208";a="676827833"
Received: from he101654.emea1.cds.t-internal.com ([10.134.226.15]) by Q4DE8PSA04V.blf.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 May 2017 15:36:09 +0200
Received: from HE101654.emea1.cds.t-internal.com (10.134.226.15) by HE101654.emea1.cds.t-internal.com (10.134.226.15) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 29 May 2017 15:35:53 +0200
Received: from HE101654.emea1.cds.t-internal.com ([fe80::c5be:f1ce:9ef6:7491]) by HE101654.emea1.cds.t-internal.com ([fe80::c5be:f1ce:9ef6:7491%27]) with mapi id 15.00.1263.000; Mon, 29 May 2017 15:35:53 +0200
From: Axel.Nennker@telekom.de
To: xml2rfc@ietf.org
Thread-Topic: reference src attribute
Thread-Index: AdLYe9TSVTSQMZKZTBGiEWI7rthETw==
Date: Mon, 29 May 2017 13:35:53 +0000
Message-ID: <e4ece38ae0fa49ff84342949e89ddfef@HE101654.emea1.cds.t-internal.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.33.93]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/WQX4Ec_LT-7tvDYPGPwosR0jXSw>
Subject: [xml2rfc] reference src attribute
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <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: Mon, 29 May 2017 13:36:29 -0000
Hi, I looked at the issue tracker and did not find a similar proposal back until 2013 where I stopped looking. I apologize if this has been asked and rejected before. I am wondering why a reference in xml2ref cannot point to a xml2ref document and the "front" element is pulled from that xml2ref document. Example: When the processor encounters this element in an xml2ref document: <reference src=" https://bitbucket.org/openid/mobile/raw/tip/draft-mobile-client-initiated-backchannel-authentication.xml" /> It would pull the first child "/rfc/front[0]" from that document and treat it as if it were the first child of this reference. Maybe kids that are legal for /ref/front but illegal for //reference/front must be ignored. Does this make sense? Cheers Axel https://trac.tools.ietf.org/tools/xml2rfc/trac/search?changeset=on&milestone=on&ticket=on&wiki=on&q=reference&page=13&noquickjump=1
- [xml2rfc] reference src attribute Axel.Nennker
- Re: [xml2rfc] reference src attribute Julian Reschke