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
Section 3.1.1 Must vs SHOULD #332
Comments
I think this is a wording issue where we use "distinguish" in different senses. The requirement is that containers must distinguish between containment and user-managed triples. There are two ways that this may be handled:
Instead of "If an implementation cannot make this distinction", maybe we should say "If user-managed triples using |
"A server that allows user-managed triples with the |
@whikloj 👍 that looks good to me |
@escowles awesome, sorry to get bogged down in wording but it keep confusing me. |
No worries @whikloj ! The new text is much better, and this will help other people from being confused. Can you make a PR, or do you want me to? |
@whikloj 👍 -- your suggestion is much easier to understand. I'll make a PR (since it seems easiest for one of us editors to deal with the formatting and validation requirements) |
I think we need s/user-managed/client-managed/ in the suggested text to align with language in the rest of the spec |
In testing the Modeshape impl, I was reading the spec and I found this interesting paragraph
It seems to me that if you MUST do something then there is no reason to define what to do if you cannot do that. Defining how you are expected to act if you can't perform this action, makes this seem like a SHOULD
The text was updated successfully, but these errors were encountered: