triples - Revision history

Tantek: Undo revision 64948 by Elf Pavlik (Talk), remove superfluous analogy of triples that has no technical merit

2018-07-20T18:35:11Z

Undo revision 64948 by Elf Pavlik (Talk), remove superfluous analogy of triples that has no technical merit

← Older revision		Revision as of 18:35, 20 July 2018
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 ==

Elf Pavlik: added Usage in Microformats

2015-05-07T18:08:58Z

added Usage in Microformats

← Older revision		Revision as of 18:08, 7 May 2015
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 ==

Tantek: TOC, YAGNI

2013-09-04T16:35:53Z

TOC, YAGNI

← Older revision		Revision as of 16:35, 4 September 2013
Line 2:		Line 2:

	'''<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 ==		== Problem of unnecessary complexity ==
	Explaining triples is hard for some reason.		Explaining triples is hard for some reason.
Line 16:		Line 16:
	The larger problem is that triples are more than just complicated, they are <strong>unnecessarily complicated</strong>.		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).		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.		microformats are proof of this (good enough, triples unnecessary) for HTML based data.

Tantek: Problem of unnecessary complexity

2013-07-02T01:09:26Z

Problem of unnecessary complexity

← Older revision		Revision as of 01:09, 2 July 2013
Line 2:		Line 2:

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

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

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

Tantek: /

2013-07-02T00:50:52Z

← Older revision		Revision as of 00:50, 2 July 2013
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.

	== See Also ==		== See Also ==

Tantek: stub

2013-07-02T00:50:37Z

stub

New page

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

== See Also ==
* [[RDF]]
* [[rdfa]]
* [[linked-data]]