<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;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Times New Roman","serif";
        color:windowtext;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.EmailStyle18
        {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>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='color:blue'>I defined the function types based
on what those functions were referred to. In a FDO context, this may not have
been the correct classification. I have no problem with re-wording this and classify
the area and length functions as math (or any other suggestion the discussion
results in) rather than intrinsic functions. I don&#8217;t think aggregate will
work as those are functions that operate on a single object rather than a set
of objects.<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:blue'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='color:blue'>FDO can give a provider information
about the supported functions via the FDO interface <i><o:p></o:p></i></span></p>

<p class=MsoNormal><i><span style='color:blue'>FdoIExpressionCapabilities::GetWellKnownFunctions()</span></i><span
style='color:blue'>. &nbsp;So, theoretically, a provider can check what is
already supported and depending on the outcome add additional, provider
specific functions. However, I am not sure if you want to call this a function
registry.<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:blue'><o:p>&nbsp;</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>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='color:blue'>&nbsp; Thomas<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:blue'><o:p>&nbsp;</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> Friday, July 27, 2007 11:31 AM<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> RE: [fdo-internals] RFC Reminder<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>I'm
wondering if it might make sense to put&nbsp;spatial functions into their own
category, rather than lumping them into intrinsic.&nbsp; Actually I'm not
entirely sure what an intrinsic function&nbsp;means in this context, maybe it's
the same as&nbsp;spatial :)&nbsp; Hmm.&nbsp; I guess this doesn't make all that
much sense either though, as there are spatial aggregate functions and spatial
conversion functions.</span><span style='font-size:12.0pt'><o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt'>&nbsp;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-family:"Arial","sans-serif";color:blue'>This
isn't related to the RFC, but is there some kind of function registry in
FDO?&nbsp; I'm wondering what the potential is for providers to expose
provider-specific functions that do the same thing but are named differently?</span><span
style='font-size:12.0pt'><o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt'>&nbsp;<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>&nbsp;</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> Friday, July 27, 2007 08:13<br>
<b>To:</b> FDO Internals Mail List<br>
<b>Subject:</b> [fdo-internals] RFC Reminder</span><span style='font-size:12.0pt'><o:p></o:p></span></p>

<p class=MsoNormal>Hi everyone<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</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>&nbsp;</o:p></p>

<p class=MsoNormal>Thanks<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>&nbsp; Thomas<o:p></o:p></p>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>