-
Notifications
You must be signed in to change notification settings - Fork 21
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
How is the DEPRECATED indication handled ? #210
Comments
@edriouk can you confirm that anything |
We still set Dfamily and DsubFamily for filtering, however they should be completely deprecated. |
The meaning of "DEPRECATED" must be different from |
To me we should be even more precise than this: deprecated: developers are discouraged from using it, a warning is raised by the tool when encountering it and there is a porting period (say 18 months) At the end of the porting period, we just remove the element from the spec (logged in the change log). If we do not do that DEPREACTED will stay forever and depending on implementation it may or may not be supported properly... |
I think we need to make use of schema version in the tools. BTW, this mechanism could also help in case of unknown elements and attributes. |
Actions are:
After this list is available revisit this issue. |
Today in the specs, some items are tagged as DPRECATED like the Dfamily for the conditions (only):
It seems that this criteria is not supported any more.
So, is it more than deprecated, is it removed ?
The text was updated successfully, but these errors were encountered: