A lack of planning on your part does not constitute an emergency on my part.

— anonymous

Looking for feedback on the current state of the OWTS-01 #specification (Guidelines for Open Web Technologies) as well as the certification process and tiers.

Specification: https://github.com/open-webtech/owta-publications/blob/main/specs/drafts/owts-01.md

Certification Process and Tiers: https://github.com/open-webtech/owta-publications/blob/meta/owta-certification/meta/certification.md

#Consequential:
"#Browsers provide critical #PublicInfrastructure to over five billion people. To cover the high cost of maintaining such complex feats of engineering, #browser vendors and #searchengine providers have improvised a system in which money is levied from search revenue and distributed to browsers. This #specification…formalizes a browser/search #levy that improves on the current one and addresses its shortcomings."

https://darobin.github.io/wise/

#specification pattern versus eliminating conditional logic via polymorphism.

Discuss.

We have a database "rules engine" that I greatly dislike. The maintenance of it is especially troubling.

It is essentially a huge Conditional statement. Which leads me to Martin Fowler's solution: conditionals as polymorphism.

Which led me to use JSON schemas to define the polymorphed classes at runtime. But #polymorphism in #json isnt quite that simple.

I've also considered the #specification pattern. But maintaining specifications is the issue.

Still thinking.