Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The next version of FIX can try, but everyone stopped upgrading FIX versions years ago. Also, once you standardize the liquidity field, you need to think about its values. These expand continuously...it used to be two or three values, now some systems use a dozen or more.

Basically, if you want a protocol for legal documents, you may as well use an existing one, such as PDF, XLS, TeX, etc. Trying to embed more domain knowledge in the protocol will never work at a highly generalized level. It would be like asking HTTP to standardize e-commerce.



Well, let's not forget we're talking about lawyers here, who already work with a versioned single source of truth (The Law).

All I'm asking is that we upgrade their tooling and process.

Your outlook for the abstraction potential seems overly pessimistic.

Most of Law boils down to a cascade of intermingled conditionals, nothing a computer couldn't handle.

Of course a bit of human intervention will always be required, for value judgements and the "hard questions".

However, in my (limited) experience with lawyers, very little of the time and money that a lawsuit consumes goes into the actual decision making.

The overwhelming majority is wasted on process and formalities.


There is no single source of truth. Every court case creates a new version of kaw, called case law.


Well, the body of this case law (and all other laws) is what I refer to as "single source of truth".

Yes, "single source" is very much an euphemism.

In practice it's far from a single source, but rather a poorly synchronized mess. Which is exactly what I'm proposing to fix.

If we were to wrap it into a github-style model then cases could be represented as branches. Case-law would evolve in the form of patches and pull-requests.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: