<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=020000814-25102006><FONT face=Arial
color=#0000ff size=2>Hi Haris,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=020000814-25102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=020000814-25102006><FONT face=Arial
color=#0000ff size=2>Comments below ...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=020000814-25102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=020000814-25102006><FONT face=Arial
color=#0000ff size=2>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=020000814-25102006><FONT face=Arial
color=#0000ff size=2>Orest.</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> Haris Kurtagic [mailto:haris@sl-king.com]
<BR><B>Sent:</B> Wednesday, October 25, 2006 6:53 AM<BR><B>To:</B>
dev@fdo.osgeo.org<BR><B>Subject:</B> [fdo-dev] fdo 3.2<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial size=2>I've read FDO 3.2
changes, and it looks like good changes.</FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial><FONT size=2>One of things
if I understood correctly is that we will be able to use any characters in
schema.<SPAN class=020000814-25102006><FONT
color=#0000ff> </FONT></SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial><FONT size=2><SPAN
class=020000814-25102006><FONT color=#0000ff>[Orest] The provider can specify
which characters are not allowed in a name. But, if one provider decides to
support a character that is not supported by other providers, you may have
problems applying schema used in one provider against another provider unless
you handle some sort of name mangling.</FONT></SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial size=2>I have couple of
comments:</FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial size=2>1.
</FONT></SPAN><SPAN class=859422910-25102006><FONT face=Arial size=2>I saw
changes in defining more exactly geometry type - good.</FONT></SPAN><SPAN
class=859422910-25102006><FONT face=Arial size=2></FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial size=2>I miss very much
rectangle or optimized rectangle especially in queries.</FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial size=2>Now in filter
provider gets polygon for some actions in MG, but basically it is rectangle
and</FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial size=2>for some providers
like for Oracle is important to know if it is rectangle or really
polygon.</FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial><FONT size=2>Of course,
provider can figure it out from points but it is no way it should be.<SPAN
class=020000814-25102006><FONT
color=#0000ff> </FONT></SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial><FONT size=2><SPAN
class=020000814-25102006></SPAN></FONT></FONT></SPAN> </DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial><FONT size=2><SPAN
class=020000814-25102006><FONT color=#0000ff>[Orest] The FGF polygon in
this case is derived from the OGC simple feature spec which I don't believe has
an explicit optimized rectangle representation such as in Oracle. While this is
something Oracle supports, other targets may not have such capabilities. It
is something that possibly could be added to the FGF spec, but we
would then need to add a capability for providers to indicate that they
don't handle that polygon
representation.</FONT> </SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial size=2>2.
</FONT></SPAN><SPAN class=859422910-25102006><FONT face=Arial size=2>After
coping fdo class from one provider to another, trough AplySchema, it is
difficult to get class definitions from newly created
classes.</FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial size=2>
Geometry/Class/schema name can be changed from one provider to
another.</FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial><FONT size=2>
It would be nice to have reader (like for insert geometries) which would return
map original class-new class, so the procedure is not dependent on keeping same
names.<SPAN class=020000814-25102006><FONT
color=#0000ff> </FONT></SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial><FONT size=2><SPAN
class=020000814-25102006></SPAN></FONT></FONT></SPAN> </DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial><FONT size=2><SPAN
class=020000814-25102006><FONT color=#0000ff>[Orest] Fdo does not expect that
the class name would be changed by the provider. That is, if you define a
particular class name with apply schema, a subsequent describe schema would
return the same class name. A provider may limit the allowable class
names via length limits and valid characters. Note that class names in FDO
are logical schema concepts as opposed to physical schema concepts such as
table names. Providers that can support a logical / physical mapping
will map class names to table names where a class name may not be identical
to the physical table name.</FONT></SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=859422910-25102006><FONT face=Arial
size=2>Haris</FONT></SPAN></DIV></BODY></HTML>