<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:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Commercial vs. Open Source Functionality</title>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</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=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Studio Lite will most likely only support a
fixed default layout. Once it generates the layout you could edit it by
modifying the XML. Time and resources is the major constraint on this.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I could make them available for both
Windows and Red Hat 3. On Linux the providers are .so libraries.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Bob<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Jason Birch
[mailto:Jason.Birch@nanaimo.ca] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, March 23, 2006
2:00 PM<br>
<b><span style='font-weight:bold'>To:</span></b> users@mapguide.osgeo.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [mapguide-users]
Commercial vs. Open Source Functionality</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Will Studio Lite not be supporting the
creation of layouts?</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>I think that making a binary distribution
of the FDO providers available would be a great idea. Would you be
able to support both Linux and Windows with this (are they loadable
modules in Linux?)</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Jason</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabIndex=-1>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</span></font></b><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Robert
Bray [mailto:robert.bray@autodesk.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, March 23, 2006
12:51<br>
<b><span style='font-weight:bold'>To:</span></b> users@mapguide.osgeo.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [mapguide-users]
Commercial vs. Open Source Functionality</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Some more answers…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>1. The initial Studio Lite will be a
subset, with support for creating SDF and SHP data sources, layers, and maps.
It’s all just an HTML based web application though so pretty easy for
someone in the open source domain to extend.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>2. That’s the plan. Studio Lite
should be available sometime in the spring and Studio does not expire until
October 1.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>3. The Open Source effort behind FDO is
taking longer than we would like. In the interim would folks on this list mind
getting binaries for these so that you could at least make use of them?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I can’t comment on pricing at the
moment because it is not finalized, but I can tell you that it will be sold on
a subscription basis. The one other benefit to going commercial besides Oracle,
SQL Server, and our OEM coordinate system library is the availability of
product support. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Bob<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabIndex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Buscher, Shane
[mailto:Shane.Buscher@nngco.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, March 23, 2006
12:27 PM<br>
<b><span style='font-weight:bold'>To:</span></b> users@mapguide.osgeo.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [mapguide-users]
Commercial vs. Open Source Functionality</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>I appreciate everyone's response and am glad that some input
from Autodesk was received. I am especially interested in pursuing the
use of this product because I see it solving many of our technical needs.
I know that AutoDesk needs to make money off of this somehow since they are
embracing open source instead of competing against it. So kudos to
Autodesk and the OS community for partnering on this endeavor. I think
ESRI is losing serious ground with the advent of Google Maps, and now MapGuide.
</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>A majority of the answers were provided, although it generated a
couple more: </span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>1) Will Studio Lite support everything it currently has
available (or supposed to have available)? From a development end I need
to know whether you will be able to make all the data source connections (wms,
sql server, sde, etc…) with studio lite, for example. </span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>2) Will Studio Lite be available before Studio Preview expires,
avoiding a gap in time where OS developers have no authoring tool?</span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>3) Are there any tentative release dates for some of the OS
functionality? Also, any pricing being made available for the commercial
products? </span></font><o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>Thanks,</span></font> <o:p></o:p></p>
<p><font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:
"Courier New"'>Shane</span></font> <o:p></o:p></p>
<p style='margin-bottom:12.0pt'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>Content-Type:
multipart/alternative;<br>
boundary="----_=_NextPart_001_01C64EA2.165BC440"<br>
Date: Thu, 23 Mar 2006 09:49:09 -0800<br>
From: Robert Bray <robert.bray@autodesk.com><br>
Subject: [mapguide-users] Commercial vs. Open Source Functionality<br>
</span></font><br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>Thanks
Jason good answers. Let me just confirm (with my Autodesk hat<br>
on). When we launched mapguide.osgeo.org we moved all of the core source<br>
code for MapGuide into open source (you can see our daily development by<br>
subscribing to the commits e-mail list). Both the open source and<br>
commercial versions of the product are built from this one code base. We<br>
actually deleted our internal source tree, so any changes to open source<br>
will appear in commercial and vice versa. Now that said, we are a<br>
business and need to make money in order to keep producing software. So<br>
the commercial version will have additional functionality, but these<br>
will be more like add-ons that come with the commercial distribution<br>
(the core code will be the same).<br>
<br>
<br>
<br>
1. Studio is a commercial product. There is an open source web-based<br>
variation in the works that we plan to have available later this spring.<br>
It will not be as functional as the commercial version, but it will be a<br>
full open source project.<br>
<br>
<br>
<br>
2. The Open Source release will eventually contain providers for SDF,<br>
SHP, ArcSDE, MySQL, ODBC, WMS, and WFS. As Jason points out, Frank W is<br>
working on a Raster provider based on GDAL and we would really like to<br>
get a PostGIS provider developed. These same providers (with the<br>
exception of GDAL) are shipping with the upcoming release of Autodesk<br>
Map. Getting them ready for that release has taken priority over getting<br>
them ready for open source. Again we are a business and need to fund all<br>
of this somehow.<br>
<br>
<br>
<br>
As for investment, we have put over two years of development into this<br>
product. We have big plans for it and absolutely no intention of<br>
abandoning it.<br>
<br>
<br>
<br>
Bob<br>
<br>
<br>
<br>
_____ <br>
<br>
From: Jason Birch [</span></font><a href="mailto:Jason.Birch@nanaimo.ca"><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>mailto:Jason.Birch@nanaimo.ca</span></font></a><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>]<br>
Sent: Thursday, March 23, 2006 10:05 AM<br>
To: users@mapguide.osgeo.org<br>
Subject: RE: [mapguide-users] Commercial vs. Open Source Functionality<br>
<br>
<br>
<br>
Your questions are shared by many. This is just my interpretation, but<br>
the information that Autodesk has revealed so far indicates that:<br>
<br>
<br>
<br>
1. Studio will be strictly commercial (it contains AutoCAD components)<br>
but Autodesk will be creating an open source "Studio Lite"
application<br>
for authoring maps.<br>
<br>
<br>
<br>
2. ArcSDE and WMS providers will be in the Open Source edition, as will<br>
ODBC which you can use to access aspatial data in SQL Server. The<br>
Essential FDO guide provides more information on this:<br>
</span></font><a href="https://fdo.osgeo.org/docs/FET_TheEssentialFDO.pdf"><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>https://fdo.osgeo.org/docs/FET_TheEssentialFDO.pdf</span></font></a><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>
Currently the<br>
providers not slated for OS release are Oracle, SQL Server (spatial) and<br>
Raster. This last one is a bit of a sticking point, but I believe that<br>
Frank W is working on a GDAL Raster provider.<br>
<br>
<br>
<br>
3. The OS version of the MapGuide code is the only version. The<br>
<st1:place w:st="on"><st1:City w:st="on">Enterprise</st1:City></st1:place>
package that Autodesk is selling will of course have<br>
additional applications and plugins provided with it, but the entire<br>
community will benefit from enhancements to the core, which is on its<br>
own pretty impressive. As a commercial entity, Autodesk is in this to<br>
make money, and will be doing so with a combination of services and<br>
software sales, similar to the Red Hat model.<br>
<br>
<br>
<br>
Jason<br>
<br>
<br>
<br>
_____ <br>
<br>
From: Buscher, Shane [</span></font><a href="mailto:Shane.Buscher@nngco.com"><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>mailto:Shane.Buscher@nngco.com</span></font></a><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>]<br>
Sent: Thursday, March 23, 2006 05:45<br>
To: users@mapguide.osgeo.org<br>
Subject: [mapguide-users] Commercial vs. Open Source Functionality<br>
<br>
All right, I'm a little frustrated at this point trying to figure out<br>
the current direction of MapGuide OS and MapGuide Commercial. I'm<br>
trying to choose between several competing technologies in the web<br>
mapping arena, including ArcIMS, MapGuide OS, MapGuide Commercial, and<br>
MapServer. <br>
<br>
1. Is the MapGuide Studio product going to become strictly a commercial<br>
product? I see it expires in October. If so, what authoring tool is<br>
going to be made available for the OS users, if any?<br>
<br>
2. There's a lot of vaporware advertising going on, especially in the<br>
data provider category. I have SQL Server, ArcSDE, and WMS
consumption<br>
requirements. These are documented as being supported, but you quickly<br>
realize they are not post-install. Are these functionalities only going<br>
to be made available in the Commercial product? This is what it seems.<br>
<br>
What is the general direction for both OS and Commercial? Are they<br>
going to be one in the same, with only support being the difference<br>
between the two? Or, will Autodesk just add functionality independently<br>
of the OS project, leaving the open source community to catch up?<br>
<br>
Maybe this is not the right forum to ask these questions, but I don't<br>
know where else to ask. It's important to know the direction of these<br>
products, as I'm looking for a long term solution.<br>
<br>
Thanks in advance.<br>
<br>
Shane Buscher<br>
GIS/Compliance Systems<br>
Northern Natural Gas<br>
402.398.7841</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Shane
Buscher</span></font> <br>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>GIS/Compliance
Systems</span></font> <br>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Northern
Natural Gas</span></font> <br>
<font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>402.398.7841</span></font>
<o:p></o:p></p>
</div>
</body>
</html>