[fdo-internals] FDO RFC 43 - Standard FDO Class Naming Conventions

[Haris Kurtagic]

I don't believe that we would be able to normally (without all providers
having metadata) achieve that same full qualified name for FDO class is kept
across all providers.

I assume that your problems are pretty much same as I had in Fdo2Fdo
application, how to know which name will come back from provider after
applying schema.
Perhaps, providers could return additional info about names of newly created
classes.

Haris

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Wednesday, October 28, 2009 10:21 AM
To: fdo-internals at lists.osgeo.org
Subject: Re: [fdo-internals] FDO RFC 43 - Standard FDO Class Naming
Conventions


Naming standardisation is sorely needed. Currently in FDO Toolbox, I'm
having
to code provider-specific hacks because of this naming discrepancy. I
shouldn't have to be doing this.

- Jackie


zspitzer wrote:
> 
> I have posted RFC 43 for review
> 
> http://trac.osgeo.org/fdo/wiki/FDORfc43
> 
> -- 
> Zac Spitzer -
> http://zacster.blogspot.com
> +61 405 847 168
> 
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
> 
> 

-- 
View this message in context:
http://n2.nabble.com/FDO-RFC-43-Standard-FDO-Class-Naming-Conventions-tp3904
182p3904311.html
Sent from the FDO Internals mailing list archive at Nabble.com.
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals