-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove type
from metadata spec
#28
Comments
There's a saying that goes " required is forever", and I think that removing something that is currently required is not a good idea once the spec is out in the wild. After all, there might be applications reading/writing this that you don't know about. |
@robpvn in protobuf, yes. But if we can find a relatively large segment of clients that aren't implementing this part of the spec, it makes sense not to have unnecessary historical baggage. |
Uh, version it? |
Fair enough. Would it be cut out completely from the spec or moved to suggested? Because I can still see the rationale for having information about overlay or baselayer in an application that opens multiple MBTiles datasources. Obviously, if it is cut out from the spec it would still be possible for people to use it as an option but it would be less, shall we say, discoverable for implementors. |
TileMill doesn't write this and I don't know of any clients that read this now.
The text was updated successfully, but these errors were encountered: