Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[?] consolidate namespaces to simplify prop_set editing?? #25

Open
briesenberg07 opened this issue Jul 30, 2022 · 1 comment
Open

[?] consolidate namespaces to simplify prop_set editing?? #25

briesenberg07 opened this issue Jul 30, 2022 · 1 comment
Labels
no 'not gonna do this (right now)' question xsd to do with schemas for prop_set instances, get_prop_set instance, etc.

Comments

@briesenberg07
Copy link
Contributor

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.
@briesenberg07 briesenberg07 added xsd to do with schemas for prop_set instances, get_prop_set instance, etc. question labels Jul 30, 2022
@briesenberg07
Copy link
Contributor Author

Related: sinopia_maps #23 (entering prefixes for prop_set > sinopia child elements makes data entry more laborious)

@briesenberg07 briesenberg07 changed the title [?] consolidate prop_set schema files in map_storage [?] consolidate namespaces to simplify prop_set editing?? Jan 28, 2023
@briesenberg07 briesenberg07 added the no 'not gonna do this (right now)' label Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
no 'not gonna do this (right now)' question xsd to do with schemas for prop_set instances, get_prop_set instance, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@briesenberg07