<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" 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 12 (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]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@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:10.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Times New Roman","serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:blue'>Hi Jason<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'>Actually, this is how it is currently
working. FDO provides a list of well-known functions with defined signatures.
This list may be enhanced/reduced by a provider if additional functions/signatures
are supported or not supported resp. The provider implements the execution of
the request. For example, a call to a expression function MOD may be replaced
with a call to the (native) “%” operator in the SQL Server
provider.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'>What the RFC proposes is to enhance
a class used to define a expression function to include a property that
categorizes the function. This class – for example – is used in FDO
to define the list of well-known functions. The RFC does not change any
current behavior.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'> Thomas<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Jason Birch<br>
<b>Sent:</b> Wednesday, August 01, 2007 11:44 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: RFC Reminder<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>I'm
a little concerned about leaving the list of supported expressions up to
the provider.</span><span style='font-size:12.0pt'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>I'd
prefer to have these expressions and their signatures defined at the FDO
level in a generic way, and then allow each provider to implement them or
not. Otherwise, we'll have clients having to write provider-specific code
to implement basically the same functionality. I can't think of a spatial
example off the top of my head, but I'd hate to have to use NVL for Oracle and
COALESCE for PostgreSQL rather than NOT IS NULL for both.</span><span
style='font-size:12.0pt'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>Or
perhaps the current well known expressions could be expanded as rapidly as
possible, and arbitrate naming and signature differences as they are
encountered? If two providers implement the same functionality, then once
the function is defined as well known one of them could just write a stub
translating the well known name/signature into the proprietary version?</span><span
style='font-size:12.0pt'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>Jason</span><span
style='font-size:12.0pt'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-family:
"Tahoma","sans-serif"'>From:</span></b><span style='font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org [mailto:fdo-internals-bounces@lists.osgeo.org]
<b>On Behalf Of </b>Thomas Knoell<br>
<b>Sent:</b> Wednesday, August 01, 2007 08:29<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: RFC Reminder</span><span
style='font-size:12.0pt'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'>Hi Dan<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'>Since the proposal is to enhance
the create-methods, the default value for the category parameter needs to be a
neutral value like FdoFunctionCategoryType_Unspecified to be backwards
compatible.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'>I don’t agree that FDO should
have a function-to-category mapping. How many functions should be part of the
mapping structure? There are lots of them in – for example –
Oracle. Should they all be known to FDO and mapped to a category? It is the
provider that sets the list of supported expression functions together with the
supported signatures and at that time the category may be set as well.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'> Thomas<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Dan Stoica<br>
<b>Sent:</b> Wednesday, August 01, 2007 11:17 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: RFC Reminder<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Also, the default value for the category is </span><span
lang=EN style='color:black'>FdoFunctionCategoryType_Unspecified;<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN style='color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN style='color:#1F497D'>I think it will be way
better to use a hardcoded mapping <b>{function_name, function_category}</b> in
FDO. Example: “Max” will belong to “Math” etc.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Unless the caller decides to change it (in 0.01% of the cases)
the category input parameter is unused which makes life easier.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dan.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Haris
Kurtagic<br>
<b>Sent:</b> Tuesday, July 31, 2007 5:55 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RE: RFC Reminder<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Would it make sense to expand further Geometry Category with :<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Spatial Aggregate Functions<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Coordinate System Transformations Functions<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Geocoding Functions<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in'><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-</span><span
style='font-size:7.0pt;color:#1F497D'>
</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Geometry Functions<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>... ?<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This is sample how Oracle Spatial divides Geometry Functions.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:.25in'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Haris<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Thomas Knoell<br>
<b>Sent:</b> Tuesday, July 31, 2007 11:42 PM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> [fdo-internals] RE: RFC Reminder<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:blue'>Hi,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'>Thanks to everyone who provided
comments on this RFC posting. Based on the comments the RFC has been updated. Please
review the new version of the RFC and comment on it if required by end of the
day tomorrow (August 1<sup>st</sup>). If no changes are required, I intent to
motion that a vote for the acceptance of the RFC is made and subsequently voted
on by the PSC.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'>Thanks<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:blue'> Thomas<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:blue'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-family:"Tahoma","sans-serif"'> Thomas Knoell <br>
<b>Sent:</b> Friday, July 27, 2007 11:13 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RFC Reminder<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi everyone<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>As indicated in an e-mail dated July 17<sup>th</sup>, FDO
RFC 5 (<a href="http://trac.osgeo.org/fdo/wiki/FDORfc5">http://trac.osgeo.org/fdo/wiki/FDORfc5</a>)
had been posted and is ready for review. Please complete the review of the RFC
and comment on it by end-of-day Tuesday, July 31<sup>st</sup>. If no changes
are required, it is my intent to motion that a vote for the acceptance of RFC5
be made and subsequently voted on by the PSC. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal> Thomas<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>