hatom-faq - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:23:52Z

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

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

	Frequently asked questions about [[hAtom]].		Frequently asked questions about [[hAtom]].

Tantek: improved a few of the FAQs, add FAQ about not (re)using 'title' and 'summary' for hAtom

2009-07-06T01:51:03Z

improved a few of the FAQs, add FAQ about not (re)using 'title' and 'summary' for hAtom

← Older revision		Revision as of 01:51, 6 July 2009
Line 1:		Line 1:
	<h1>hAtom FAQ</h1>		<entry-title>hAtom FAQ</entry-title>

	~~__TOC__~~		Frequently asked questions about [[hAtom]].

	~~This page is for documenting Q&A about~~ [[~~hatom\|hAtom~~]].		If you have a new question to ask, Please consider first asking your question on the microformats [[IRC]] channel, or the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list.

	~~If you have a new question to ask, Please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list.~~		== Editing this Page ==

	~~<h2>~~Editing this Page~~</h2>~~
	Please do not use "?" or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.		Please do not use "?" or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.

	~~<h2> Q&A <h3>~~		== Is hAtom intended to replace RSS or Atom ==
			''Is hAtom intended to replace RSS or Atom?''

	~~== Is~~ hAtom intended to replace RSS or Atom ==		No, hAtom is not intended to replace RSS or Atom. While most weblogs and other websites do provide their latest articles in a separate XML side file (in RSS and/or Atom format), older articles are typically not provided in such XML feed files.

	~~No,~~ hAtom ~~is not intended to replace RSS or Atom. While most weblogs~~ and ~~other websites do provide their latest~~ articles ~~in a structured fashion (via RSS and/or Atom feeds)~~, ~~most of them do not provide their older articles~~ in ~~a structured way. This is one of the problems that hAtom can solve~~.		hAtom allows all blog posts and articles to be published with episodic structure, especiallly those in archives.

	== Is there a way to hide to the entry author information ==		== Is there a way to hide to the entry author information ==

	''My client does not want to display their name after every post, but would like this to be valid. Can I hide the author info in an abbr tag or something?''		''My client does not want to display their name after every post, but would like this to be valid. Can I hide the author info in an abbr tag or something?''

Line 24:		Line 22:
	''Answer required for multiple authors?''		''Answer required for multiple authors?''

	== Why does hAtom use class ~~name namespaces~~ ==		Blogs with multiple authors display each author's name near their blog posts.

			== Why does hAtom use class names with prefixes ==
			''Why does hAtom use class names with prefixes?''

			The mailing list archives have the reasoning in depth (would be nice to extract those and explain them here), but in summary: since we were reusing the semantics of the IETF Atom standard, we very much wanted to reuse the vocabulary as well to minimize confusion and mean precisely the same semantics as defined in the Atom RFC 4287, and thus a few of the hAtom properties use class names that appear to have shared prefixes (entry-title, entry-content, entry-summary) in order to literally reuse those terms from the Atom RFC (title, content, summary) with the Atom-specific semantics defined therein, rather than the generic semantics, e.g. "summary" has a much more general purpose semantic that is utilized broadly by multiple microformats.

			== Could hAtom instead use title content and summary ==
			''Instead of entry-title, entry-content and entry-summary, could hAtom use title, content and summary?''

			In short no.

			In general newer microformats do re-use properties from previous microformats (per the [[naming-principles]], specifically, minimal vocabulary).

			However, in order to reflect the precise Atom semantics as defined in RFC 4287, we chose specific class names for capturing and communicating Atom Entry title, Atom Entry content and Atom Entry summary.

			'title' already means job title as defined by [[hCard]], and per the [[naming-principle]] of not using the same term for two different meanings, we are not reusing title (which is just as well, as historically the term 'title' has been quite ambiguous, and presentation-centric, in numerous metadata efforts and formats).

			Similarly, 'summary' is already defined by [[hCalendar]], much more broadly than Atom's definition of summary.

	~~You can read through the archives for the reasoning in depth~~, ~~but in~~ summary~~: since we were reusing the semantics of the IETF Atom standard~~, ~~we very much wanted~~ to ~~reuse the vocabulary as well~~ to ~~minimize confusion~~ and ~~mean precisely~~ the ~~same~~ semantics as defined in the Atom RFC 4287, and thus a few of the hAtom properties appear to be prefixed (entry-title, entry-content, entry-summary) in order to literally reuse those terms from the RFC (title, content, summary).		Since these three Atom Entry elements (title, summary, content) are often used together, it makes sense to prefix them all to communicate their explicit tying and connection to the Atom Entry semantics.

Brian: reverting spam

2008-12-20T19:01:46Z

reverting spam

← Older revision		Revision as of 19:01, 20 December 2008
Line 1:		Line 1:
	~~lalitapas~~
	~~elchichid~~
	<h1>hAtom FAQ</h1>		<h1>hAtom FAQ</h1>

RolcnAlael: zelcoeltelto

2008-12-20T06:35:39Z

zelcoeltelto

← Older revision		Revision as of 06:35, 20 December 2008
Line 1:		Line 1:
			lalitapas
	elchichid		elchichid
	<h1>hAtom FAQ</h1>		<h1>hAtom FAQ</h1>

OlocnAdron: bastacoolod

2008-12-19T23:47:18Z

bastacoolod

← Older revision		Revision as of 23:47, 19 December 2008
Line 1:		Line 1:
			elchichid
	<h1>hAtom FAQ</h1>		<h1>hAtom FAQ</h1>

Tantek: Reverted edit of Sl8Cmu, changed back to last version by Tantek

2007-07-13T11:50:23Z

Reverted edit of Sl8Cmu, changed back to last version by Tantek

← Older revision		Revision as of 11:50, 13 July 2007
Line 3:		Line 3:
	__TOC__		__TOC__

	This page is for documenting Q		This page is for documenting Q&A about [[hatom\|hAtom]].

			If you have a new question to ask, Please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list.

			<h2>Editing this Page</h2>
			Please do not use "?" or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.

			<h2> Q&A <h3>

			== Is hAtom intended to replace RSS or Atom ==

			No, hAtom is not intended to replace RSS or Atom. While most weblogs and other websites do provide their latest articles in a structured fashion (via RSS and/or Atom feeds), most of them do not provide their older articles in a structured way. This is one of the problems that hAtom can solve.

			== Is there a way to hide to the entry author information ==

			''My client does not want to display their name after every post, but would like this to be valid. Can I hide the author info in an abbr tag or something?''

			In the case of single author: If a page is authored by only one author ever, then implied "address" as author can be used whereby in the absense of a valid hCard example within the hAtom being found, the parser will use the hCard information in the <address> element and hCard of the page (See final clause of hAtom address author field http://microformats.org/wiki/hatom#Entry_Author). This negates the need to specify an author in each entry.

			''Answer required for multiple authors?''

			== Why does hAtom use class name namespaces ==

			You can read through the archives for the reasoning in depth, but in summary: since we were reusing the semantics of the IETF Atom standard, we very much wanted to reuse the vocabulary as well to minimize confusion and mean precisely the same semantics as defined in the Atom RFC 4287, and thus a few of the hAtom properties appear to be prefixed (entry-title, entry-content, entry-summary) in order to literally reuse those terms from the RFC (title, content, summary).

Sl8Cmu at 10:50, 13 July 2007

2007-07-13T10:50:51Z

← Older revision		Revision as of 10:50, 13 July 2007
Line 3:		Line 3:
	__TOC__		__TOC__

	This page is for documenting Q~~&A about [[hatom\|hAtom]].~~		This page is for documenting Q

	~~If you have a new question to ask, Please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list.~~

	~~<h2>Editing this Page</h2>~~
	~~Please do not use "?" or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.~~

	~~<h2> Q&A <h3>~~

	~~== Is hAtom intended to replace RSS or Atom ==~~

	No, hAtom is not intended to replace RSS or Atom. While most weblogs and other websites do provide their latest articles in a structured fashion (via RSS and/or Atom feeds), most of them do not provide their older articles in a structured way. This is one of the problems that hAtom can solve.

	~~== Is there a way to hide to the entry author information ==~~

	~~''My client does not want to display their name after every post, but would like this to be valid. Can I hide the author info in an abbr tag or something?''~~

	In the case of single author: If a page is authored by only one author ever, then implied "address" as author can be used whereby in the absense of a valid hCard example within the hAtom being found, the parser will use the hCard information in the <address> element and hCard of the page (See final clause of hAtom address author field http://microformats.org/wiki/hatom#Entry_Author). This negates the need to specify an author in each entry.

	~~''Answer required for multiple authors?''~~

	~~== Why does hAtom use class name namespaces ==~~

	You can read through the archives for the reasoning in depth, but in summary: since we were reusing the semantics of the IETF Atom standard, we very much wanted to reuse the vocabulary as well to minimize confusion and mean precisely the same semantics as defined in the Atom RFC 4287, and thus a few of the hAtom properties appear to be prefixed (entry-title, entry-content, entry-summary) in order to literally reuse those terms from the RFC (title, content, summary).

Tantek: Reverted edit of ZrcD58, changed back to last version by Phae

2007-06-22T14:39:57Z

Reverted edit of ZrcD58, changed back to last version by Phae

← Older revision		Revision as of 14:39, 22 June 2007
Line 3:		Line 3:
	__TOC__		__TOC__

	This page is for documenting Q		This page is for documenting Q&A about [[hatom\|hAtom]].

			If you have a new question to ask, Please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list.

			<h2>Editing this Page</h2>
			Please do not use "?" or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.

			<h2> Q&A <h3>

			== Is hAtom intended to replace RSS or Atom ==

			No, hAtom is not intended to replace RSS or Atom. While most weblogs and other websites do provide their latest articles in a structured fashion (via RSS and/or Atom feeds), most of them do not provide their older articles in a structured way. This is one of the problems that hAtom can solve.

			== Is there a way to hide to the entry author information ==

			''My client does not want to display their name after every post, but would like this to be valid. Can I hide the author info in an abbr tag or something?''

			In the case of single author: If a page is authored by only one author ever, then implied "address" as author can be used whereby in the absense of a valid hCard example within the hAtom being found, the parser will use the hCard information in the <address> element and hCard of the page (See final clause of hAtom address author field http://microformats.org/wiki/hatom#Entry_Author). This negates the need to specify an author in each entry.

			''Answer required for multiple authors?''

			== Why does hAtom use class name namespaces ==

			You can read through the archives for the reasoning in depth, but in summary: since we were reusing the semantics of the IETF Atom standard, we very much wanted to reuse the vocabulary as well to minimize confusion and mean precisely the same semantics as defined in the Atom RFC 4287, and thus a few of the hAtom properties appear to be prefixed (entry-title, entry-content, entry-summary) in order to literally reuse those terms from the RFC (title, content, summary).

ZrcD58 at 13:06, 22 June 2007

2007-06-22T13:06:26Z

← Older revision		Revision as of 13:06, 22 June 2007
Line 3:		Line 3:
	__TOC__		__TOC__

	This page is for documenting Q~~&A about [[hatom\|hAtom]].~~		This page is for documenting Q

	~~If you have a new question to ask, Please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] list.~~

	~~<h2>Editing this Page</h2>~~
	~~Please do not use "?" or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc.~~

	~~<h2> Q&A <h3>~~

	~~== Is hAtom intended to replace RSS or Atom ==~~

	No, hAtom is not intended to replace RSS or Atom. While most weblogs and other websites do provide their latest articles in a structured fashion (via RSS and/or Atom feeds), most of them do not provide their older articles in a structured way. This is one of the problems that hAtom can solve.

	~~== Is there a way to hide to the entry author information ==~~

	~~''My client does not want to display their name after every post, but would like this to be valid. Can I hide the author info in an abbr tag or something?''~~

	In the case of single author: If a page is authored by only one author ever, then implied "address" as author can be used whereby in the absense of a valid hCard example within the hAtom being found, the parser will use the hCard information in the <address> element and hCard of the page (See final clause of hAtom address author field http://microformats.org/wiki/hatom#Entry_Author). This negates the need to specify an author in each entry.

	~~''Answer required for multiple authors?''~~

	~~== Why does hAtom use class name namespaces ==~~

	You can read through the archives for the reasoning in depth, but in summary: since we were reusing the semantics of the IETF Atom standard, we very much wanted to reuse the vocabulary as well to minimize confusion and mean precisely the same semantics as defined in the Atom RFC 4287, and thus a few of the hAtom properties appear to be prefixed (entry-title, entry-content, entry-summary) in order to literally reuse those terms from the RFC (title, content, summary).

Phae: /* Is hAtom intended to replace RSS or Atom */

2006-12-11T13:58:06Z

Is hAtom intended to replace RSS or Atom

← Older revision		Revision as of 13:58, 11 December 2006
Line 20:		Line 20:
	''My client does not want to display their name after every post, but would like this to be valid. Can I hide the author info in an abbr tag or something?''		''My client does not want to display their name after every post, but would like this to be valid. Can I hide the author info in an abbr tag or something?''

	(~~something about~~ hAtom 0.~~2 here~~?)		In the case of single author: If a page is authored by only one author ever, then implied "address" as author can be used whereby in the absense of a valid hCard example within the hAtom being found, the parser will use the hCard information in the <address> element and hCard of the page (See final clause of hAtom address author field http://microformats.org/wiki/hatom#Entry_Author). This negates the need to specify an author in each entry.

			''Answer required for multiple authors?''

	== Why does hAtom use class name namespaces ==		== Why does hAtom use class name namespaces ==

	You can read through the archives for the reasoning in depth, but in summary: since we were reusing the semantics of the IETF Atom standard, we very much wanted to reuse the vocabulary as well to minimize confusion and mean precisely the same semantics as defined in the Atom RFC 4287, and thus a few of the hAtom properties appear to be prefixed (entry-title, entry-content, entry-summary) in order to literally reuse those terms from the RFC (title, content, summary).		You can read through the archives for the reasoning in depth, but in summary: since we were reusing the semantics of the IETF Atom standard, we very much wanted to reuse the vocabulary as well to minimize confusion and mean precisely the same semantics as defined in the Atom RFC 4287, and thus a few of the hAtom properties appear to be prefixed (entry-title, entry-content, entry-summary) in order to literally reuse those terms from the RFC (title, content, summary).