<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><b><span style="color:#00B0F0">I know more work, but what about doing both formats for some number of versions? Speaking as an old-fart MapServer user, I’m inclined to go the MapServer like format, but I’m sure new folks coming into the
fold would better appreciate a JSON approach.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:#00B0F0"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:#00B0F0">Another thought, rather than have two formats, what about building/including a JSON output converter for MapFile like context. Would lead towards folks running either type of set up for a while. Obviously
need parsers for both though. Also would help in eventual hard conversion to JSON form in the (distant) future?<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:#00B0F0"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:#00B0F0">Bobb<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color:#00B0F0"><o:p> </o:p></span></b></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> <a href="https://github.com/sdlime/mapserver/wiki/MapServer-8.0-Config-File">https://github.com/sdlime/mapserver/wiki/MapServer-8.0-Config-File</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Note one advantage of this format over JSON is that comments (single and multi-line) are much easier...<o:p></o:p></p>
</div>
</div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<pre><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#00B0F0"><o:p> </o:p></span></b></pre>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>