> On 1 Mar 2017, at 09:06, Juergen Schoenwaelder > <j.schoenwael...@jacobs-university.de> wrote: > > On Tue, Feb 28, 2017 at 11:41:35PM +0000, Kent Watsen wrote: >> >> Hi NETMOD WG, >> >> Please find below draft-2 having the following changes: >> - clarified responsibility 'c' >> - s/encoding/representation/g >> - moved intf-ext-yang from Oct to Dec >> > > So are we going through all NETMOD/NETCONF documents now to replace > 'encoding' with 'representation', which also includes changing > document titles? I am not necessarily against that change but I think > it is good to understand the implications that go well beyond some > charter text. (I did do my own analysis how frequently we have used > encoding in our documents, I assume others have done this as well.) >
I don't think it is necessary to immediately update old RFCs with this new term. I do think though it is important to stop using "encoding". People have to realize that - different representations of conceptual data/resources cannot be automatically translated to each other as the term "encoding" might suggest - it is important to think about what representation to use for a given use case (this may influence the choice of protocols and/or tools). This terminology will also help app folks understand what we are dealing with in NETCONF/NETMOD. Lada > /js > > PS: RFC 7951 JSON Encoding of Data Modeled with YANG. L. Lhotka. August 2016. > > -- > 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/> > > _______________________________________________ > netmod mailing list > netmod@ietf.org > https://www.ietf.org/mailman/listinfo/netmod -- Ladislav Lhotka, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
