Re: [netmod] yang-json document

Andy Bierman <andy@yumaworks.com> Thu, 05 February 2015 22:41 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7179B1A6F0E for <netmod@ietfa.amsl.com>; Thu, 5 Feb 2015 14:41:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 PMFT-NYQA-ks for <netmod@ietfa.amsl.com>; Thu, 5 Feb 2015 14:41:10 -0800 (PST)
Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 544241A87B3 for <netmod@ietf.org>; Thu, 5 Feb 2015 14:41:06 -0800 (PST)
Received: by mail-lb0-f170.google.com with SMTP id w7so12534350lbi.1 for <netmod@ietf.org>; Thu, 05 Feb 2015 14:41:04 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=7dzO9X60O8QYrwl0mtolNCfI63M0mK1FUZ1+GbswxQ8=; b=J26fHSG76yPgkTnNVW9weK3+RhMlf8IGx2YNCw+QLFVL1k40N1yOEN5mERHhMbtOWU bfdNLkV2UR6AuxFKloIY4lft4C8hBVk5Q4iqxao2ww/edNXwq8vY+c8NiTX3IclLns47 G6mtv6JgQzEwwwJ0LIcsvOVWpZFP+n4kfcOax9j+qZFa9tQhXwv4TEN1FNMHFalWLSIR SJL+dx9WwR15It3m+oHPv+jXRhaE/Koj5hQKSxcJ91ylffiph8TZ5FydtHGypBwmeyvH dAIYbI3rVCS7yZ8fxVxiJ4/HkD0ZCwDmgqoU1CuxKulOvNu25AnlMUCaR0GZdD0itvCI DOog==
X-Gm-Message-State: ALoCoQlJpu008k1OQeUr22X8k7/2V8+RulXTYz2MEmx5EMBJXGFNvGwCASJ9A4kx67uK9vm71T13
MIME-Version: 1.0
X-Received: by 10.152.28.129 with SMTP id b1mr317892lah.37.1423176064831; Thu, 05 Feb 2015 14:41:04 -0800 (PST)
Received: by 10.112.78.3 with HTTP; Thu, 5 Feb 2015 14:41:04 -0800 (PST)
In-Reply-To: <20150205220903.GA52795@elstar.local>
References: <20150205.135210.818152609244122122.mbj@tail-f.com> <15CBB080-9288-4881-8F28-DE1A24279820@nic.cz> <CABCOCHQ03Owgo5Zb-jcenDNGqT1_gRazbSG+LUU_Pi7NpNDArA@mail.gmail.com> <20150205.214557.720578496688087827.mbj@tail-f.com> <CABCOCHRH-21xtxjG5MPM6Xib7BoYdGp6ag04FeZZ0SzvZOXUvg@mail.gmail.com> <20150205214630.GA52009@elstar.local> <CABCOCHTfipJALMF28BTkyioCThFswEDy645mgBJvk3a9i61zSg@mail.gmail.com> <20150205220903.GA52795@elstar.local>
Date: Thu, 05 Feb 2015 14:41:04 -0800
Message-ID: <CABCOCHTc3hyhJ15fwOv7riyOLbCOyrYhPjeJw73J+ureqhpRuA@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Andy Bierman <andy@yumaworks.com>, Martin Bjorklund <mbj@tail-f.com>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/k5ejOA5xDaBL8e0CP_2AmBF5y4s>
Subject: Re: [netmod] yang-json document
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 05 Feb 2015 22:41:12 -0000

On Thu, Feb 5, 2015 at 2:09 PM, Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de> wrote:
> On Thu, Feb 05, 2015 at 01:57:16PM -0800, Andy Bierman wrote:
>>
>> That YANG text was written without any use-cases in mind.
>> If a YANG module is written that has a use-case for unconstrained XML,
>> then anyxml is ready to use.
>>
>> I have never seen anyxml actually used that way.
>> In every case, there is a schema to apply, known to
>> the implementation somehow.  In every case there are
>> only YANG nodes expected. No PIs. No mixed context.
>>
>> So I do not believe this is a real problem.
>> I think YANG 1.1 could spend a lot of effort defining
>> schema rules for unconstrained data, but this might not
>> help address the real uses of anyxml.
>>
>
> The argument "my code has a more specific interpretation and I believe
> everybody else does the same" only works if everybody confirms it. I
> have not seen that confirmation. Hence, to fix this, we have Y34-05
> for YANG 1.1.
>
> This thread is about the current JSON mapping document, which is based
> on YANG 1.0. Again, the argument "my code has a more specific
> interpretation and I believe everybody else does the same" only works
> if everybody confirms it. As long as we do not have a confirmation
> that everybody happens to do what your code does, I think we have to
> assume that anyxml means what RFC 6020 says, any xml.
>

Maybe you misunderstood.
anyxml is being used as a placeholder for a "real schema"
that YANG is unable to express.  "my code knows how
to pick the real schema for this anyxml blob" is part of
the data model or protocol definition.

I don't think Y34-05 addresses this issue.

Even the "blog" use-case expects valid HTML to be specified
in the anyxml, not free-form, any XML.


> /js
>

Andy

> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>