Re: [JPP-Devel] named FeatureSchema

[<mic...@fr...>]

Hi Paul and Larry,

Just few questions I wonder about naming schemas :
- What really needs to be named, FeatureSchema or FeatureCollection ?
- Will it be possible to have two different names for identical schemas 
(it should) ?
- Will it be possible to have two different schemas with identical name 
(it should not, but may be the responsability can be let to the user to 
keep it simple) ?
These are just questions to wonder before changing, but at the moment, I 
can't see any drawback with a free attribute name on FeatureSchema as 
proposed by Paul.

Michaël

Larry Becker a écrit :

>Hi Paul,
>
>   Just a few questions regarding the FeatureSchema Name, since I'm
>unable to come up with the use case myself.  I can see that it is
>simpler to look at the Name than to compare all of the attributeNames
>individually, but I would hate to make that assumption and then find
>that the user has deleted an attribute I was depending on.  Also,
>would the FeatureSchema Name be persisted in the Task (.jmp) file, and
>if so how does that affect compatibility?
>
>thanks,
>Larry Becker
>
>On 6/9/07, Stefan Steiniger <ss...@ge...> wrote:
>  
>
>>hei Paul,
>>
>>mhm.. if you write the function (that also supports empty names)
>>this should be possible to include if Michael and Larry agree
>>
>>stefan
>>
>>btw. although you are following specific interests, and changes to the
>>core need to be discussed it is open to you to join the jpp-team
>>
>>Paul Austin schrieb:
>>    
>>
>>>Martin,
>>>
>>>If the FeatureSchema class could be extended to have a name property,
>>>with a getName (and maybe a setName) with a default constructor and a
>>>constructor that takes the name as an argument then that would be great.
>>>As we have default constructor existing code won't break as the name is
>>>optional.
>>>
>>>The advantage of having the name is that if you were doing some
>>>processing of features and don't have reference to the layer you can
>>>find out what type of feature it is and do different processing accordingly.
>>>
>>>Paul
>>>
>>>Martin Davis wrote:
>>>      
>>>
>>>>BTW, the idea of having hum-readable names for FeatureSchemas is a nice
>>>>one.  I'd definitely support adding that functionality, even if it isn't
>>>>exposed right now.
>>>>
>>>>        
>>>>
>>>-------------------------------------------------------------------------
>>>This SF.net email is sponsored by DB2 Express
>>>Download DB2 Express C - the FREE version of DB2 express and take
>>>control of your XML. No limits. Just data. Click to get it now.
>>>http://sourceforge.net/powerbar/db2/
>>>_______________________________________________
>>>Jump-pilot-devel mailing list
>>>Jum...@li...
>>>https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>>
>>>
>>>      
>>>
>>-------------------------------------------------------------------------
>>This SF.net email is sponsored by DB2 Express
>>Download DB2 Express C - the FREE version of DB2 express and take
>>control of your XML. No limits. Just data. Click to get it now.
>>http://sourceforge.net/powerbar/db2/
>>_______________________________________________
>>Jump-pilot-devel mailing list
>>Jum...@li...
>>https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>>    
>>
>
>
>  
>