IETF Logo Mail Archive

Re: [netmod] Whitespace in XML encoding - allowed ?

Ladislav Lhotka <lhotka@nic.cz> Wed, 10 October 2018 06:53 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C800A130E91 for <netmod@ietfa.amsl.com>; Tue, 9 Oct 2018 23:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 QfoXgdf0dPht for <netmod@ietfa.amsl.com>; Tue, 9 Oct 2018 23:53:52 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 7DA13130E89 for <netmod@ietf.org>; Tue, 9 Oct 2018 23:53:52 -0700 (PDT)
Received: from birdie (unknown [IPv6:2001:718:1a02:1::380]) by mail.nic.cz (Postfix) with ESMTPSA id B98EA6082A; Wed, 10 Oct 2018 08:53:50 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1539154430; bh=CXcdtW4x9f246YqUEMLVINiH8dwYJ4VkgN24z0csWn4=; h=From:To:Date; b=u5q3kX39P1G5xjitpIgvCkbDr+rm4yT8QVA6Sp7XlCCkUj0+3XpqPSx9tRFr7bdHx XjwxfmbMKt/eFhOvd/vc09VE9CAell8bxUTdVb7OtKOdJ20GIZeVa6Ut3uUgFuRu+K kriF4yjASQdKV5HJZMC1GqOFq24caeWSTtZRXONg=
Message-ID: <522f0552fb49a4eee7931fde98004f3ed2e58a9c.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Kent Watsen <kwatsen@juniper.net>, Balázs Lengyel <balazs.lengyel@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>
Date: Wed, 10 Oct 2018 08:53:50 +0200
In-Reply-To: <BFEC1F81-8447-4B51-82CB-0E944E843F63@juniper.net>
References: <14e78aaa-4508-970a-d1a0-e091ffaf5c8e@ericsson.com> <871s8zh0cu.fsf@nic.cz> <BFEC1F81-8447-4B51-82CB-0E944E843F63@juniper.net>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.1
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/PWnYqofXX0zAMTMOZ2PLWf4MglY>
Subject: Re: [netmod] Whitespace in XML encoding - allowed ?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2018 06:53:55 -0000

On Tue, 2018-10-09 at 17:24 +0000, Kent Watsen wrote:
> As Martin points out, this is how XML works.
> 
> As a result, XML instance documents are poster-child examples for why long
> lines occur sometimes, and where the artwork-folding draft shines when placing
> said examples into drafts.
> 
> Lada, good point, but would there be a layer violation?

Which layers do you mean? XML and YANG parser on top of it? An XML processor is
expected to pass the whitespace unchanged to the application (except for EOL
normalization), and it is up to the YANG parser how the data is interpreted.

Lada

> 
> Kent // contributor
> 
> 
> 
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

v2.23.0 | Report a Bug | By Email