The reasoning behind storing sinopia_type and child element .xsd at sinopia_maps, and not at map_storage, was an idea that prop_set instances would be used to create MAP derivatives for other platforms/in other formats than for Sinopia. But this may be too far off and/or not feasible. Consolidation of schema files may have advantages. Note that some bulk element-prefix editing would be involved.
The reasoning behind storing
sinopia_typeand child element .xsd at sinopia_maps, and not at map_storage, was an idea that prop_set instances would be used to create MAP derivatives for other platforms/in other formats than for Sinopia. But this may be too far off and/or not feasible. Consolidation of schema files may have advantages. Note that some bulk element-prefix editing would be involved.