-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Why don't they update existing namespaces? (Groundspeak, Topografix...) #4
Comments
Regarding GS 1.0 -> 1.0.1: Maybe it's because the semantics of the |
Perhaps. I wonder why they didn't make it 100% backward-compatible. For example, they might have added One might suspect that perhaps GS 1.0.1 was introduced soon after GS 1.0 and they thought no one will care. But then, we change the namespace? That kind of huge change is hard to miss. So this theory doesn't hold either. |
Yes, they obviously made some mistakes. See also the bug in 1.0 and 1.0.1 versions, which allowed an unlimited number of |
... and they had to add this GPX version switch to their user profile settings because they failed in making it backward compatible. Shit happens. ;) |
Quotes from here and here:
Caring about schema definitions, and caring about XML namespaces, are two different things. They have defined their elements in a specific namespace, but then, released a new version of the schema, ordering all developers to move all elements to a different namespace, instead of extending the existing one. Why not simply update the previous XSD file? I don't understand this logic. We must be missing something...
I will start a separate thread for that. Perhaps one day, someone, will enlighten us :)
The text was updated successfully, but these errors were encountered: