adding finer-grained access based on "web concepts"

[dret]

not sure whether that's out of scope: https://github.com/dret/webconcepts has the idea of "concepts" and "values", which at some level are close to IANA registries and the values in them. it focuses on web-API level things. but there is some data to play around with: http://webconcepts.info/specs/IETF/RFC/ lists 177 RFCs and there is structured data about them. http://webconcepts.info/JSON explains the JSON data available, but i could easily create other data (in XML or JSON) if that would work better.
if there is an opportunity to support this more structured view of RFCs, that would be nice, and i'd be willing to put some effort into making data available from http://webconcepts.info/.

[mnot]

Interesting. I think the most direct way to do this would be to process the concepts into tags.json; that file labels various things as groups (see the front page for several examples).

If you want to do that, I'll help out; otherwise not sure when I'd get to it.

[dret]

so would that mean to produce a tags.json that as tag name would have the concept, and as value would have the concept value? for example RFC 4287 would then have the concept shown on http://webconcepts.info/specs/IETF/RFC/4287 defined in tags.json?
that should be easy to do, the question is how to most easily generate the data, and then how to combine or integrate it into EveryRFC. one tags.json for each RFC?
if you can give me an example (let's stick with RFC 4287 for this) of how you want the data to look like, and how you want it delivered, then it should be easy to generate this.