> It seems to me that you are the one who is pulling in details from today, asserting that they must be incorporated into any law, and then pointing out how that's a bad idea.
You say this but then go on to pull in far more detail from today than I have...
> My lone assumption is a business that provides user-facing software. That's it. With that assumption, I'm arguing for the principle that when a business provides customers a human-targeted "UI", they need to provide a corresponding machine-usable "API" that bypasses the accidental complexity of human interaction. We know there must be a machine-friendly format before the user-friendly format, because the software is itself operating on a machine.
False. Actual machine friendly formats are not the same as the data structures that power UIs.
>> the business has chosen the architecture, and the law would mandate accessibility.
> Well this isn’t what you said before.
>This is what I said before. Having some type of public API is not "architecture". It's mandating open access to the same thing any front end needs to access anyway.
As already stated, the front end is not the same thing as an api suitable for clients. Maintaining a stable API is quite different from building a front-end site.
> Authentication and sign up: It's a public API, so this is irrelevant for read access.
Is it? Front ends often require sign up for read access. Why wouldn’t an API?
> For ordering, the same exact account system as using the web/app UI.
Wait - I thought your idea was architecture neutral. Why are you talking about the web ui?
> You keep ignoring existing implementations, pretending like what I'm saying would require some huge ground-up design rather than tweaks to what already exists.
Ahh, so this is just about how things are built today with minor tweaks.
> Data formats: The company. If a company is big enough to dictate formats, then they're big enough for developers to pay attention to.
Ok, so your law requires people to dictate formats?
> After the custom of using aggregators for shopping becomes commonplace, it becomes in their own interest to stick with common formats rather than get left behind.
Aggregators owned by whom? Google, Facebook, Amazon?
> Bugs: The company, while leaving the old "buggy" version in place for some period of time.
Seems like you have just introduced an architectural requirement to be able to run old versions in parallel with new ones. Who determines the person of time?
> you're imagining that any such law would be useless since a company could just deliberately create an unusable API. But courts see right through those type of "bad faith" approaches.
You are the only one talking about bad faith. I’m simply pointing out that supporting API clients requires architecture that is different from only supporting UI visitors.
If you are iterating on the UI frequently, and changing the structures that supports that UI, the by definition you don’t have a stable API unless you engineer one separately. No bad faith needed.