Hi, making a quick review of the latest changes in the new FM interfaces I've found Schema. Glad it is there, since I was using a kind of type registry on complex-features branch, and it seems to fit perfectly for that need. So I just wondered how one Schema instance would relate to another(s), like in xml schema imports. Or if they might relate at all.
Think on the following situation: you're parsing a "community schema", aka, arbitrarily complex GML schema. For a given schema, all includes are going to be kept on the same Schema instance, but what happens with imports? should the parsed Schema for my schema1.xsd hold a reference for the Schema instance holding gml*.xsd? A common situation would be needing to go look for a type of an attribute which, though its not directly defined in the FeatureType, belongs to the same "substitution group" than one of the FeatureType's defined attributes... You could answer that no backpointer is needed, since I should be looking for the "imported" schema by namespace through JNDI or whatever discovery mechanism, but what if I'm importing gml2 in one schema and gml3 in another? don't gml2 and gml3 share the same namespace? I might be just ramping, but wanted to chek if I'm missing some key point. -- Gabriel Roldán ([EMAIL PROTECTED]) Axios Engineering (http://www.axios.es) Tel. +34 944 41 63 84 Fax. +34 944 41 64 90 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
