@reiver ⊼ (Charles) :batman:@reiver@mastodon.social: 6/ That doesn't mean inventing has no value. (It does.) But, I feel that the repository of specifications under organizational bodies (e.g., IETF) and community groups (e.g., FEP) are not the place for them. .

Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @reiver@mastodon.social
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-02 00:38:05)
5/

People are of course able to decide for themselves which of №1, №2, and №3 they feel are acceptable scenarios for publishing specifications under organizational bodies (e.g., IETF) and community groups (e.g., FEP), but —

But, I feel only №1 and №2 are acceptable scenarios.

I.e., I feel that specifications published under organizational bodies (e.g., IETF) and community groups (e.g., FEP), should be DOCUMENTING not inventing.

...
---Reply---
@reiver ⊼ (Charles) :batman:@reiver@mastodon.social (2026-05-02 00:40:23)
6/

That doesn't mean inventing has no value. (It does.)

But, I feel that the repository of specifications under organizational bodies (e.g., IETF) and community groups (e.g., FEP) are not the place for them.

.


---Replies---

silverpill@silverpill@mitra.social (2026-05-02 04:04:25)
@reiver I didn't know there is a debate. It seems obvious to me that these places should facilitate both practices. In case of inventing, this is the equivalent of "building in the open", that is, when you want to gather as much feedback as possible as early as possible.