<!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><TITLE>Re: [fdo-internals] New RFC posted</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16525" name=GENERATOR>
<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: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; 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 {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
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=714502121-21082007><FONT face=Arial
color=#0000ff size=2>Thanks.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=714502121-21082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=714502121-21082007><FONT face=Arial
color=#0000ff size=2>Sounds like there is some ambiguity on what you would
expect MOD or REMAINDER to return. Can we just specify that for FDO the
sign of the return value must always be positive? Or that it must follow
some other rule? I'd hate to leave it up to the client to guess
what will be returned, based on the provider.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=714502121-21082007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=714502121-21082007><FONT face=Arial
color=#0000ff size=2>I'm not sure what I was talking about with code
pages. Perhaps I misread the intention of the Translate function, thinking
that it would be used to translate a string from one character set to another,
rather than being a string replacement function.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=714502121-21082007><FONT face=Arial color=#0000ff
size=2>Couple other minor picky questions:</FONT></SPAN></DIV>
<DIV><SPAN class=714502121-21082007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=714502121-21082007><FONT face=Arial color=#0000ff size=2>- For
the function Sign, what would be the returned values? 0 or 1 for positive
or negative? Something else?</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=714502121-21082007>- Is
the Instr position 0 or 1 based? What does it return if the value
doesn't exist?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=714502121-21082007>-
Would it be possible to add an integer DIV function as well? Or is this
just assumed when dividing integer values? Showing some ignorance of FDO
operations here...</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=714502121-21082007>Am I
getting annoying yet? :)</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=714502121-21082007></SPAN></FONT><FONT face=Arial color=#0000ff
size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=714502121-21082007>Jason</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT><BR></DIV>
<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> Tuesday, August 21, 2007 12:41<BR><B>To:</B> FDO
Internals Mail List<BR><B>Subject:</B> RE: [fdo-internals] New RFC
posted<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d">Hi
Jason<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d">Sorry for the
late response on this as I did not get to do it during my
vacation.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d">The issues with
the geometric functions like <I>area</I> and <I>length</I> are with coordinate
system/projection support. It is expected that this will result in some
discussion within the group. FDO includes coordinate system specification via
spatial context, but FDO itself does not expose any projection capabilities nor
does it specify use of coordinate system packages. Most providers do not have
coordinate system packages available internally. MapGuide for instance does all
of its projection work separately, outside of FDO. So, we should discuss what
happens if the data is lat/long for example.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d">Unlike the
geometric functions, the functions documented in RFC 8 are rather simple. The
idea was to keep those separated from the geometric functions to ensure nothing
gets overlooked and allow progress on implementing the basic functions while
discussion on geometric functions goes ahead.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d">As for the
functions <I>MOD</I> and <I>REMAINDER</I>, although the basically perform a
similar kind of operation, they are defined differently. The distinction is with
the sign of the return value: in case of the function MOD, it corresponds to the
sign of the divisor, in case of the function REMAINDER, it corresponds to the
sign of the dividend. Usually, in number theory, the remainder (independent of
the functions) is always a positive number. However, with software products this
might not be the case.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d">As for the math
operators with date functions, there was no intent to support such operators
other than on months. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d">As for the code
page question, I am not sure where you are heading here. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d">Thanks<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; COLOR: #1f497d">
Thomas<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: blue"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; 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-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; 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, August 03, 2007 6:39 PM<BR><B>To:</B>
fdo-internals@lists.osgeo.org<BR><B>Subject:</B> Re: [fdo-internals] New RFC
posted<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN-BOTTOM: 12pt"><SPAN style="FONT-SIZE: 10pt">Hi Jason<BR><BR>I
will see what I can do. I am just leaving for my vacation and have to get back
to you on this next week (although being on vacation, I'll still try to answer
mails). I hope it can wait until then.<BR><BR>Thanks<BR><BR>
Thomas<BR><BR>--------------------------<BR>Sent from my BlackBerry Wireless
Handheld (www.BlackBerry.net)<BR><BR><BR>----- Original Message -----<BR>From:
fdo-internals-bounces@lists.osgeo.org
<fdo-internals-bounces@lists.osgeo.org><BR>To: FDO Internals Mail List
<fdo-internals@lists.osgeo.org><BR>Sent: Fri Aug 03 18:06:32
2007<BR>Subject: RE: [fdo-internals] New RFC posted<BR><BR>Could you maybe
outline those issues? <BR><BR>It would be helpful if we could all have an
idea of what is coming up and see how it fits together, rather than being fed
RFCs / problems piecemeal.<BR><BR>I was able to read the PDF version, btw, and
it answers most of my questions. I still don't know what the difference
between Mod and Remainder is though :)<BR><BR>A couple functions raise questions
for me<BR><BR>- the date functions have month math operators, but none for other
units?<BR>- is there a common way of specifying code pages that all providers
should understand? I don't know much about this
area.<BR><BR>Jason<BR><BR> _____ <BR><BR>From:
fdo-internals-bounces@lists.osgeo.org [<A
href="mailto:fdo-internals-bounces@lists.osgeo.org">mailto:fdo-internals-bounces@lists.osgeo.org</A>]
On Behalf Of Thomas Knoell<BR>Sent: Friday, August 03, 2007 14:53<BR>To:
fdo-internals@lists.osgeo.org<BR>Subject: Re: [fdo-internals] New RFC
posted<BR><BR><BR><BR>For the geometry functions, there are different issues to
address which we thought is better suited to be outlined
separately.<BR><BR>Thanks<BR><BR>
Thomas<BR><BR>--------------------------<BR>Sent from my BlackBerry Wireless
Handheld (www.BlackBerry.net)<BR><BR><BR>----- Original Message -----<BR>From:
fdo-internals-bounces@lists.osgeo.org
<fdo-internals-bounces@lists.osgeo.org><BR>To: FDO Internals Mail List
<fdo-internals@lists.osgeo.org><BR>Sent: Fri Aug 03 17:45:04
2007<BR>Subject: RE: [fdo-internals] New RFC posted<BR><BR>Is there any specific
reason for that ?<BR><BR><BR><BR> Haris<BR><BR><BR><BR>From:
fdo-internals-bounces@lists.osgeo.org [<A
href="mailto:fdo-internals-bounces@lists.osgeo.org">mailto:fdo-internals-bounces@lists.osgeo.org</A>]
On Behalf Of Thomas Knoell<BR>Sent: Friday, August 03, 2007 11:40 PM<BR>To:
fdo-internals@lists.osgeo.org<BR>Subject: Re: [fdo-internals] New RFC
posted<BR><BR><BR><BR>Spatial functions will be handled
separately.<BR><BR>--------------------------<BR>Sent from my BlackBerry
Wireless Handheld (www.BlackBerry.net)<BR><BR><BR>----- Original Message
-----<BR>From: fdo-internals-bounces@lists.osgeo.org
<fdo-internals-bounces@lists.osgeo.org><BR>To: FDO Internals Mail List
<fdo-internals@lists.osgeo.org><BR>Sent: Fri Aug 03 17:35:42
2007<BR>Subject: RE: [fdo-internals] New RFC posted<BR><BR>I’ve noticed there is
no any Spatial Functions. What is a reason for that?<BR><BR><BR><BR>Thank
you,<BR><BR>Haris<BR><BR><BR><BR>From: fdo-internals-bounces@lists.osgeo.org [<A
href="mailto:fdo-internals-bounces@lists.osgeo.org">mailto:fdo-internals-bounces@lists.osgeo.org</A>]
On Behalf Of Thomas Knoell<BR>Sent: Friday, August 03, 2007 9:35 PM<BR>To: FDO
Internals Mail List<BR>Subject: [fdo-internals] New RFC
posted<BR><BR><BR><BR>Hi,<BR><BR><BR><BR>A new RFC (<A
href="http://trac.osgeo.org/fdo/wiki/FDORfc8">http://trac.osgeo.org/fdo/wiki/FDORfc8</A>)
has been posted. The RFC addresses the enhancement of the FDO well known
(expression) function list to include additional, commonly used
functions.<BR><BR><BR><BR>Please review the RFC. Any comments/suggestions and
questions are welcome. All feedback is expected by the end-of-day August 10th
2007. If no changes are required it is my intent to motion that a vote for the
acceptance of the RFC be made and subsequently voted on by the
PSC.<BR><BR><BR><BR>Thanks<BR><BR><BR><BR>
Thomas<BR><BR><BR><BR><BR><BR></SPAN><o:p></o:p></P></DIV></BODY></HTML>