[bgrainger]

On the home page, "For more detailed information take a look at the specification." links to https://www.domainverification.org/spec which is a 404.

`dig 4i7ozur385y5nsqoo0mg0mxv6t9333s2rarxrtvlpag1gsk8pg._dv.dvexample.com TXT` returns: ;; ANSWER SECTION: 4i7ozur385y5nsqoo0mg0mxv6t9333s2rarxrtvlpag1gsk8pg._dv.dvexample.com. 0 IN TXT "@dv=1;d=Example user emali;e=2025-01-01;s=[seo;email;marketing;storage;security];p=[serviceprovider1.com];sn=[service.serviceprovider.com];h=4i7ozur385y5nsqoo0mg0mxv6t9333s2rarxrtvlpag1gsk8pg"

There's a typo in "Example user emali".

These simple mistakes don't engender confidence in the proposal.

[susadmin]

How do syntax errors dissuade you from the proposal? Is not design separate from implementation? Is it not true that a well-designed specification, proposal, etc. can be poorly implemented?

[hiatus]

If you got a job offer that was riddled with spelling mistakes and had the wrong name, would that inspire confidence in your future place of work? It's not a huge stretch of the imagination that small, obvious issues could mean larger, more complex issues lurking.

[elliottinvent]

I'd say "riddled with spelling mistakes" is a bit strong in our example (I realise you weren't claiming that about the site).

I got it out early to get some feedback. The 404 spec link is a bad one (since fixed) but the typo in the DNS record is forgivable I think – very impressed anyone spotted that.

[hiatus]

To be clear, my comment was directly addressing my parent's comment of

> How do syntax errors dissuade you from the proposal? Is not design separate from implementation?

I would not characterize your content as "riddled with spelling mistakes" and apologize if you read if that way.

[elliottinvent]

Huge thanks for pointing these out.

I moved the spec to /docs/spec very recently and forgot to update that link on homepage – fixed now.

"Emali" is a new typo for me, will fix that in the DNS record, thanks.