triples

(Difference between revisions)

Jump to: navigation, search
(added Usage in Microformats)
Current revision (18:35, 20 July 2018) (view source)
(Undo revision 64948 by Elf Pavlik (Talk), remove superfluous analogy of triples that has no technical merit)
 
Line 25: Line 25:
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.
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.
-
 
-
== Usage in Microformats ==
 
-
 
-
=== Nested h-card ===
 
-
[[microformats2#h-card_org_h-card]] has two distinct subjects and each of them have property + value pairs.
 
-
 
-
=== h-feed nesting multiple h-entry ===
 
-
[[h-feed]] each h-entry sets new subject and all the property + value pairs refer to it.
 
-
: example in the wild http://pin13.net/mf2/?url=http%3A%2F%2Ftantek.com%2F
 
-
 
== See Also ==
== See Also ==

Current revision

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.

Contents

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:

... 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.

See Also

triples was last modified: Friday, July 20th, 2018

Views