-
Notifications
You must be signed in to change notification settings - Fork 47
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
Strange mention of Guidance in Requirements #428
Comments
Additional question: Is the "MUST" refering to both "have a URI" and "resolves to a representation resource" ? If yes: Would "have a URL" combine both? |
@akuckartz thanks but this issue is only about a super-basic editorial question! Questions like yours should be addressed later on, when we have clarified whether this sentence is really at the place it was intended to be (I don't think it is, as it stands out compared to what's around) |
That text, in grey, was an early attempt to show how Issues (Requirements) may be addressed. I think Rob authored that one but the logic for the answer was taken from discussion. I have created a commit (to soon be PRed) to remove this now vestigal text from the doc since we are now dealing with Issues directly in GitHub, not in the doc, until final text is agreed to. Closing Issue with commit febbe0d |
@nicholascar thanks for the answer. This sounds very good but I'm not fond of closing the issue until your commit is deployed at https://w3c.github.io/dxwg/profiles/. Where is it? |
Text removed |
Hi @nicholascar
I guess it's you who edited, this, apologies if you're not...
In the current https://w3c.github.io/dxwg/profiles/#requirements I can read:
Is it intended to be like this, with no reference to a github issue?
The text was updated successfully, but these errors were encountered: