-
Notifications
You must be signed in to change notification settings - Fork 63
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
[OracleReview] Hints #1600
Comments
My comment on this: We define our own values as well so we cannot limit to IANA only. However, it would be a valid point to discuss whether we should limit it to what IANA defines + what we define. In any case, restricting these values should be done in TD2.0 since TD1.0 TDs might be using some custom values or annotated ones. |
@egekorkan |
The comment was more generic than this discussion. Suggest to search for "hint" across the entire document. |
I have always some difficulties to change something what was already available in the TD 1.0 such as the mentioned assertion above. Please not that everything what is defined within the information model table are specified as assertion, and is also listed in the implementation report such as: (Please ignore "MAY be included. Type boolean." its only visible in the implementation report and not in the spec) My recommendation is to leave everything as it is. |
from today's TD call, decided to close. @mlagally if you disagree please reopen this issue. |
In several sections, the text talks about hints, e.g. 5.3.4.1 Link:
type: "Target attribute providing a hint indicating what the media type [RFC2046] of the result of dereferencing the link should be."
To achieve interoperability this is not sufficient. it should be an assertion that only media type values defined by IANA MUST be used.
The text was updated successfully, but these errors were encountered: