csarven on editors-draft
Add shared slash semantics in u… Add strict hierarchy in resourc… (compare)
acl:accessTo: "The acl:accessTo predicate specifies which resources you're giving access to, using their exact URLs as the objects.", so if you want to allow access to just the
/and not the containments, you say just that. If you want to grant access to the containments also, you need
OPTIONS. Headers like
Slugis a good candidate.
I'm open to how we organise branches. I think that editors-draft will be an ongoing thing.. even past the recommendation release. When we make a release, we create a branch and leave that alone as a snapshot. Each release will link back previous release. I wanted to keep close to something I felt comfortable with for now - again, okay to change that. See https://github.com/w3c/ldn/branches/yours for the branches and the readme: https://github.com/w3c/ldn/ linking to live snapshots, test suite, implementation reports etc.. In the LDN case, we had the ED somewhere ( https://linkedresearch.org/ldn/ ) else.
We have the gh-pages for the live approved version. That can actually be editors-draft ( best to resolve solid/specification#8 first) or the latest release. I suppose master acts as staging. There are feature/ branches.. I'm not sure if that fits well for the specs .. or if there is that much difference from wip/ .