<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=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<title>Re: [fdo-internals] FDO RFC 7 - Add New Methods to FdoClassDefinition</title>
<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:12.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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>“</span><span style='font-size:10.0pt'>to advertise the fact that
a class is a combination of other classes.”<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt'>Which makes me think the
class “is computed”. In this case could we reuse the existing Get/SetIsComputed()
?<br>
<br>
</span><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-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
fdo-internals-bounces@lists.osgeo.org
[mailto:fdo-internals-bounces@lists.osgeo.org] <b>On Behalf Of </b>Robert
Fortin<br>
<b>Sent:</b> Friday, July 27, 2007 12:24 PM<br>
<b>To:</b> fdo-internals@lists.osgeo.org<br>
<b>Subject:</b> Re: [fdo-internals] FDO RFC 7 - Add New Methods to
FdoClassDefinition<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p><span style='font-size:10.0pt'>As Barbara said, we woud like to advertise
the fact that a class is a combination of other classes.<br>
<br>
The use case; make a distinction in the application between the general class
and this type of class. In our case we would like to indicate to the user by
using a different icon in the UI. Simple use case but we have no way to find
this info at the moment.<br>
<br>
It might be possible to use a different term that could include OGR concept and
view concept. I would not got as far a introducing an interface/type over
FeatureClass though.<br>
<br>
RF<br>
<br>
RF<br>
--------------------------<br>
Sent from my BlackBerry - Please excuse typo and syntax.<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 Jul 27 11:39:35 2007<br>
Subject: RE: [fdo-internals] FDO RFC 7 - Add New Methods to FdoClassDefinition<br>
<br>
The 'view' term may be not the most fortunate because it is immediately<br>
associated with RDBMS views. It should indicate that this is a virtual<br>
object in the datastore and therefore a class mapped to that object is<br>
virtual too. And that class "virtuality" we wanted to expose. It is
not<br>
only about limitation, but also about dependencies. Class B may depend<br>
on Class A, if Class B is based on the subset of data in Class A. Class<br>
B disappears when Class A is dropped.<br>
<br>
Barbara.<br>
<br>
> -----Original Message-----<br>
> From: fdo-internals-bounces@lists.osgeo.org [<a
href="mailto:fdo-internals-">mailto:fdo-internals-</a><br>
> bounces@lists.osgeo.org] On Behalf Of Frank Warmerdam (External)<br>
> Sent: Friday, July 27, 2007 11:03 AM<br>
> To: FDO Internals Mail List<br>
> Subject: Re: [fdo-internals] FDO RFC 7 - Add New Methods to<br>
FdoClassDefinition<br>
><br>
> Robert Fortin wrote:<br>
> > It's up to the application to decide what to do with this property.<br>
For<br>
> > example, the application might not allow to update on view-based<br>
class<br>
> > because it can conflict with the actual feature class data. The<br>
view<br>
> > might still be updatable.<br>
> ><br>
> > Also, the application don't have to react on it if they don't want<br>
to.<br>
> > The application might not care about this property. It's different<br>
than<br>
> > having a non-standard query per provider where the application is<br>
> > enforced to do processing based on the provider connection. It
just<br>
> > advertise some information hidden otherwise.<br>
><br>
> Robert,<br>
><br>
> With clarification on the semantics of the "is a view" property,
I'm<br>
still<br>
> left scratching my head as to it's purpose. What's the point of a<br>
flag<br>
> indicating something is a view when the application is still left<br>
guessing<br>
> what the implications of this are?<br>
><br>
> And as a provider writer, how do I know what I should mark as a view<br>
in<br>
> drivers that aren't terrible RDBMS oriented, such as OGR? For<br>
instance,<br>
> in OGR I have a concept of executing a somewhat arbitrary SQL query<br>
which<br>
> produces a resultset with many properties of a view (it isn't a 1:1<br>
> analog of a table). Is it reasonable for me to mark it as a view?<br>
><br>
> I think it is up job of the RFC proposer to make a convincing case for<br>
> the utility of this property. Just saying some applications can<br>
ignore it<br>
> isn't sufficient. I feel the property effectively muddies the waters<br>
> as I understand it so far, and that is a net negative for FDO.<br>
><br>
> Best regards,<br>
> --<br>
><br>
---------------------------------------+--------------------------------<br>
------<br>
> I set the clouds in motion - turn up | Frank Warmerdam,<br>
warmerdam@pobox.com<br>
> light and sound - activate the windows | <a
href="http://pobox.com/~warmerdam">http://pobox.com/~warmerdam</a><br>
> and watch the world go round - Rush | President OSGeo,<br>
<a href="http://osgeo.org">http://osgeo.org</a><br>
><br>
> _______________________________________________<br>
> fdo-internals mailing list<br>
> fdo-internals@lists.osgeo.org<br>
> <a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a><br>
<br>
_______________________________________________<br>
fdo-internals mailing list<br>
fdo-internals@lists.osgeo.org<br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-internals">http://lists.osgeo.org/mailman/listinfo/fdo-internals</a></span><o:p></o:p></p>
</div>
</body>
</html>