On Fri, Nov 30, 2018 at 12:48:48PM +0000, Balázs Lengyel wrote: > Hello, Joe, Jurgen, > > RFC6020 doesn't really register� file extensions, but rather media types. > I don't feel we need a new mediatype for this as we really use json and > xml. However I see it useful to document in the file extension that this > is not just any plain old XML; it is yang instance data in XML format.� > Alternatives: > > 1. Use the .yid file extension (my favorite) > 2. Use 2 separate file extensions: .yidxml, .yidjson > 3. just use .xml and .json >
I would have used .json or .xml; the content of the file after all is self-describing and tools like 'file' might learn how to recognize the content. Extensions like .yidxml and .yidjson looks a bit horrible to me and so far I never had any real problems using .json and .xml for arbitrary json and xml files (and .json and .xml helps generic tools so calling it .yid means that I have to go and teach tools that .yid is either .json and .xml). Try loading .json and .xml in your favourite editor and then load a .yid file. Big difference for my editor. So from my perspective, do nothing (and then people and tools will likely use option 3). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
