Gregory's Server@hrefna ideas what we can do? Somehow we need to aggregate stuff (people, issues, best practices …) to be able to identify and strive for globally better options than if everybody just were to work independently and thus just optimize locally for whatever the world looks like from their point of view.
|
2 comments
 @hrefna As the guy who ran a site called metamodel.com for many years, I relate :-) Random archive snapshot: https://web.archive.org/web/20071014230454/http://metamodel.com/ |
@J12t Honestly?
I'm going to keep repeating dret's point: https://dret.typepad.com/dretblog/2015/02/json-or-rdf-just-decide.html
We need a metamodel.
We need a way of:
1. Describing extensions (and in the case of AP… core features, like "what the heck is a user")
2. Handshaking on what extensions are supported.
3. Saying what to do if an extension is not supported.
It's too easy right now to write something that is incompatible with the universe but that strictly follows the spec. Compare with, say, the situation with HTTP.
@J12t Honestly?
I'm going to keep repeating dret's point: https://dret.typepad.com/dretblog/2015/02/json-or-rdf-just-decide.html
We need a metamodel.
We need a way of:
1. Describing extensions (and in the case of AP… core features, like "what the heck is a user")
2. Handshaking on what extensions are supported.
3. Saying what to do if an extension is not supported.