-
Notifications
You must be signed in to change notification settings - Fork 9
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
First-class citizenship of resources in PWPs #5
Comments
@murata0204 I certainly understand why you might want that, but I am admittedly at a loss to understand how one could make it a reality. Do you have any thoughts on how you would see this working? I'd take some URI syntax examples even as a starting point... |
I am aware of two specifications. |
The draft specifies that Is it ok as an answer to @murata2makoto's concern? |
This issue was discussed in a meeting.
View the transcriptFirst-class citizenship of resources in PWPsGarth Conboy: #5 Laurent Le Meur: Issue 5 - if we summarize - there was an ask that any resource should be addressable via URI/URLs - that’s what we’ve done in the wording Proposed resolution: Existing text resolved this. (Garth Conboy) Garth Conboy: +1 Laurent Le Meur: +1 Ivan Herman: +1 Geoff Jukes: +1 Nick Ruffilo: +1 Joshua Pyle: +1 Ric Wright: +1 Resolution #7: Existing text resolved this. Ivan Herman: before we move to the next topic - i have an admin question for Laurent - When I clean up the minutes, I’ll put in comments on all the resolutions, which means most of the issues can be closed. Will you close them when you have them in the document? Laurent Le Meur: I can close them - but there is one that requires additional action. |
no need to update the draft. |
For the symmetry of PWPs and WPs, all resources in PWPs should be first-class citizens of the web. Thus, any such resource-in-PWP should be addressable by URIs.
Moreover, fragment identifiers should not be used. Use of fragment identifiers implies second-class citizens (in the terminology of RFC 3986, "secondary resource").
The text was updated successfully, but these errors were encountered: