Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:35:35Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:35, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~XMDP origins~~</entry-title>~~		{{DISPLAYTITLE:XMDP origins}}

	An essay by [[User:Tantek\|Tantek Çelik]] on the origins of [[XMDP]]. To be wikified.		An essay by [[User:Tantek\|Tantek Çelik]] on the origins of [[XMDP]]. To be wikified.

Tantek: typo

2009-08-22T18:12:51Z

typo

← Older revision		Revision as of 18:12, 22 August 2009
Line 15:		Line 15:
	</source>		</source>

	The terms "vcard" and "fn" which are used as class names are defined by the [http://microformats.org/profile/hcard hCard XMDP] and ~~can~~ the respective URLs for those terms are created by referencing the fragment IDs in that document:		The terms "vcard" and "fn" which are used as class names are defined by the [http://microformats.org/profile/hcard hCard XMDP] and the respective URLs for those terms are created by referencing the fragment IDs in that document:

	* vcard: http://microformats.org/profile/hcard#vcard		* vcard: http://microformats.org/profile/hcard#vcard

Tantek: posted essay on origins based on material I've emailed/posted many years ago, updated with a few recent bits

2009-08-22T18:07:56Z

posted essay on origins based on material I've emailed/posted many years ago, updated with a few recent bits

New page

<entry-title>XMDP origins</entry-title>

An essay by [[User:Tantek|Tantek Çelik]] on the origins of [[XMDP]]. To be wikified.

When I was working on [[XFN]] (effectively the first microformat), I specifically designed the underlying technology of XHTML Meta Data Profiles ([[XMDP]]) to *enable* all HTML rel/class additions/extensions (what would later become known as "microformats") to be *optionally* bound by URLs. And not just any URLs, but URLs that were compatible with and looked like RDF vocabulary URLs that ended with a "#" and term name. This was a deliberate design decision on my part, because I knew that there would be those who preferred to define their terms with URLs. Here is an HTML markup fragment that demonstrates this with the above-mentioned [[hCard]]:

<source lang=html4strict>
<html><head profile="http://microformats.org/profile/hcard">
<title>a document with hCards</title></head>
<p class="vcard"><span class="fn">Jeni Tennison</span> wrote an article,
<cite><a href="http://www.jenitennison.com/blog/node/124">HTML5/RDFa Arguments</a></cite>,
that compares and critically analyzes HTML5 and RDF approaches to representing and publishing data.
</p>
</html>
</source>

The terms "vcard" and "fn" which are used as class names are defined by the [http://microformats.org/profile/hcard hCard XMDP] and can the respective URLs for those terms are created by referencing the fragment IDs in that document:

* vcard: http://microformats.org/profile/hcard#vcard
* fn: http://microformats.org/profile/hcard#fn

Thus providing the necessary URLs for any (meta)data system that stores/reasons about data based on vocabulary based on URLs (whether RDF or some other URL-based vocabulary store).

In practice, few people use XMDP profiles, well, except for at least the millions [http://wordpress.com Wordpress blogs] out there - just view source on them and you'll find: <code><nowiki>profile="http://gmpg.org/xfn/11"</nowiki></code> near the top of the page.

The point is that those that want to use profiles have the *option* of using them, while not burdening everyone else with doing so.

[[User:Tantek|Tantek]] 18:07, 22 August 2009 (UTC)

== see also ==
* [[XMDP]]

xmdp-origins - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

Tantek: typo

Tantek: posted essay on origins based on material I've emailed/posted many years ago, updated with a few recent bits