2019-06-28 UTC
# 
[tantek] whereas what's right (or at least better) is understanding / documenting use-cases first from purely a user perspective (why do you want to publish? what would a consuming application do that is special?) and then analysis of related use-cases (noting that my 1-7 above), and only after some reasonable modeling of that, perhaps based on prototypes, discussing how the plumbing (e.g. vocab) *might* work