<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16481" name=GENERATOR><!--[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-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
LI.MsoListParagraph {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 34
}
SPAN.EmailStyle18 {
FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; FONT-FAMILY: "Times New Roman","serif"; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle19 {
FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: "Times New Roman","serif"; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle20 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle21 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle22 {
FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: "Times New Roman","serif"; TEXT-DECORATION: none; mso-style-type: personal
}
SPAN.EmailStyle23 {
FONT-WEIGHT: normal; COLOR: blue; FONT-STYLE: normal; FONT-FAMILY: "Times New Roman","serif"; TEXT-DECORATION: none; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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 vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=671504018-01082007><FONT face=Arial
color=#0000ff size=2>Hi,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=671504018-01082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=671504018-01082007><FONT face=Arial
color=#0000ff size=2>Yes, my comment wasn't really specific to the RFC. I
guess I'd just like to see a practice that provider-specific functions
are rationalized into the well-known list as quickly as possible.
Otherwise it will be difficult for clients to write good cross-provider
code.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=671504018-01082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=671504018-01082007><FONT face=Arial
color=#0000ff size=2>Jason</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> 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 11:36<BR><B>To:</B> FDO
Internals Mail List<BR><B>Subject:</B> RE: [fdo-internals] RE: RFC
Reminder<BR></FONT><BR></DIV>
<DIV></DIV>
<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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">I'm a
little concerned about leaving the list of supported expressions up to the
provider.</SPAN><SPAN style="FONT-SIZE: 12pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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: 12pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">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: 12pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt"> <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: blue; FONT-FAMILY: 'Arial','sans-serif'">Jason</SPAN><SPAN
style="FONT-SIZE: 12pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><SPAN
style="FONT-SIZE: 12pt">
<HR align=center width="100%" SIZE=2>
</SPAN></DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><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: 12pt"><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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">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: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Dan.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Would
it make sense to expand further Geometry Category with :<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">-</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Spatial
Aggregate Functions<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">-</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Coordinate
System Transformations Functions<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">-</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Geocoding
Functions<o:p></o:p></SPAN></P>
<P class=MsoListParagraph style="TEXT-INDENT: -0.25in"><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">-</SPAN><SPAN
style="FONT-SIZE: 7pt; COLOR: #1f497d">
</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Geometry
Functions<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">...
?<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">This
is sample how Oracle Spatial divides Geometry Functions.<o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Haris<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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>