triples: Difference between revisions
(stub) |
(Undo revision 64948 by Elf Pavlik (Talk), remove superfluous analogy of triples that has no technical merit) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
'''<dfn>triples<dfn>''' in the context of data markup typically refers to having three pieces of information as part of a statement, e.g. object predicate subject. | '''<dfn>triples</dfn>''' in the context of data markup typically refers to having three pieces of information as part of a statement, e.g. object predicate subject. | ||
__TOC__ | |||
== Problem of unnecessary complexity == | |||
Explaining triples is hard for some reason. | |||
It always takes more time to explain to explain triples rather than simple property:value constructs as in microformats and JSON. | |||
Thus there's inevitably fewer people that can understand anything [[RDF]]/[[linked-data]] etc. which means: | |||
* fewer authors | |||
* fewer developers | |||
* fewer libraries | |||
... etc. | |||
The larger problem is that triples are more than just complicated, they are <strong>unnecessarily complicated</strong>. | |||
Standards, formats, protocols, applications can get along fine without them (thus making them unnecessary - AKA [https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it YAGNI]). | |||
microformats are proof of this (good enough, triples unnecessary) for HTML based data. | |||
JSON is proof of this from API consumers' perspective. | |||
With [[microformats2]] [[parsers]] that can turn HTML+microformats into canonical JSON, both problems are solved. | |||
And thus triples are more appealing to data architects than folks who want to ship features as quickly as possible (e.g. http://indiewebcamp.com), who can't be bothered to learn about the greater complexity of triples. | |||
== See Also == | == See Also == | ||
Latest revision as of 18:35, 20 July 2018
This article is a stub. You can help the microformats.org wiki by expanding it.
triples in the context of data markup typically refers to having three pieces of information as part of a statement, e.g. object predicate subject.
Problem of unnecessary complexity
Explaining triples is hard for some reason.
It always takes more time to explain to explain triples rather than simple property:value constructs as in microformats and JSON.
Thus there's inevitably fewer people that can understand anything RDF/linked-data etc. which means:
- fewer authors
- fewer developers
- fewer libraries
... etc.
The larger problem is that triples are more than just complicated, they are unnecessarily complicated.
Standards, formats, protocols, applications can get along fine without them (thus making them unnecessary - AKA YAGNI).
microformats are proof of this (good enough, triples unnecessary) for HTML based data.
JSON is proof of this from API consumers' perspective.
With microformats2 parsers that can turn HTML+microformats into canonical JSON, both problems are solved.
And thus triples are more appealing to data architects than folks who want to ship features as quickly as possible (e.g. http://indiewebcamp.com), who can't be bothered to learn about the greater complexity of triples.