That use case chart is kind of interesting. Like, it's not a flat URI scheme leaving structure up to controllers. But it's also not a fully defined ontology.

That use case chart is kind of interesting. Like, it's not a flat URI scheme leaving structure up to controllers. But it's also not a fully defined ontology. Pick a use case description in section three. Any one. Each one could provoke an entire domain-specific organization into heated arguments about subrequirements and subsubrequirements. Even if this recommendation doesn't make it, it's neat. Any way you turn you walk into this system, right?