-
Notifications
You must be signed in to change notification settings - Fork 57
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
site-wide location configuration for metadata files #605
Conversation
@JeniT - having read through the new section on site-wide metadata location, it all makes sense. Including the example provides extra clarity. +1 from me for merge. |
I only have an editorial (a.k.a. bike-shedding) issue: is the variable name But that is bike-shedding, I am o.k. with the text otherwise. |
I'm happy to use another name for the variable. Ones I thought of were |
'location' is probably most neutral… |
…own-location # Conflicts: # syntax/index.html
…own-location # Conflicts: # syntax/index.html
Haven't heard back form @mnot on this. It would be nice to have consensus to commit the PR and close the issue. |
Looks good. You might want to be a bit tighter on what "not found" means - think you mean HTTP 404 or 410. However, you should also consider:
You may not need to go that that level of detail, just worth thinking about. |
@mnot do you have any suggested wording? My first reaction to your comment was to try to refer to https://fetch.spec.whatwg.org/ but I think we will have problems referring to that in a normative way. |
Perhaps the paragraph could simply be the following:
Alternatively, somewhat more normative:
Status 5xx may be transient, and convey no useful information to affect processor behavior other than to fail with an error. |
I may miss something, but... I was looking at the section with the example. The text says that
may lead to
Note that this also affects the default value for the file. |
The steps defined in Site-wide Location Configuration say to expand the template using Note that expanding a URI Template does not create an absolute URL necessarily, so it does need to be resolved against something. We specify how this is to be done explicitly. |
Ah.
Indeed. I missed that; sorry for the noise! |
…own-location # Conflicts: # tests/index.html # tests/manifest-json.jsonld # tests/manifest-json.ttl # tests/manifest-rdf.jsonld # tests/manifest-rdf.ttl # tests/manifest-validation.jsonld # tests/manifest-validation.ttl # tests/manifest.csv
… to find metadata.
Both the cachability of .well-known/csvm and the at-risk text can probably use some word-smithing. |
I have incorporated wordsmithing from this thread. @gkellogg could you check the |
site-wide location configuration for metadata files
fixes #555
I took a look and decided to make this as simple, and specific to CSV on the Web, as possible, to avoid delays. So the definition is just a file of URI templates.
@mnot I'd appreciate your review.