container-brainstorming - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:21:34Z

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

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

	This page exists to brainstorm around the concept of ‘containers’ in microformats.		This page exists to brainstorm around the concept of ‘containers’ in microformats.

GeorgeBrock: /* Markup proposals */ Proposed using prefixes to indicate shared properties

2010-04-17T13:07:08Z

Markup proposals: Proposed using prefixes to indicate shared properties

@@ Line 203: / Line 203: @@
     <!-- include pattern -->
     <a class="item microformat_detail" href="#review_item">Aziza</a>
 </div>
 </source>

GeorgeBrock: /* Existing container elements */ Add hProduct contains hReviews example

2010-04-17T12:25:37Z

Existing container elements: Add hProduct contains hReviews example

← Older revision		Revision as of 12:25, 17 April 2010
Line 101:		Line 101:
	* <code>hresume</code> in [[hResume]] — hResume contains an hCard for the owner, which could indicate default properties (<code>fn</code>) for <code>experience</code> business cards.		* <code>hresume</code> in [[hResume]] — hResume contains an hCard for the owner, which could indicate default properties (<code>fn</code>) for <code>experience</code> business cards.
	* <code>hreview-aggregate</code> in [[hReview-aggregate]] can contain other hReviews, as such could be used as a container to share the <code>item</code> with each component <code>hreview</code>.		* <code>hreview-aggregate</code> in [[hReview-aggregate]] can contain other hReviews, as such could be used as a container to share the <code>item</code> with each component <code>hreview</code>.
			* <code>hproduct</code> in [[hProduct]] can contain one or more reviews ([[hReview]] or [[hReview-aggregate]]), this should allow the reviews to all use the containing <code>hproduct</code> as their <code>item</code>.

	=== hreview-set ===		=== hreview-set ===

BenWard: /* markup proposals */ Started list of existing containers.

2009-07-30T06:35:57Z

markup proposals: Started list of existing containers.

← Older revision		Revision as of 06:35, 30 July 2009
Line 94:		Line 94:

	== markup proposals ==		== markup proposals ==

			===Existing container elements===

			* <code>vcalendar</code> in [[hCalendar]]
			* <code>hfeed</code> in [[hAtom]]
			* <code>hresume</code> in [[hResume]] — hResume contains an hCard for the owner, which could indicate default properties (<code>fn</code>) for <code>experience</code> business cards.
			* <code>hreview-aggregate</code> in [[hReview-aggregate]] can contain other hReviews, as such could be used as a container to share the <code>item</code> with each component <code>hreview</code>.

	=== hreview-set ===		=== hreview-set ===
	One solution to the problem of multiple reviews of the same item could be to wrap each <code>hReview</code> in a container (hypothetically, <code>hreview-set</code>. The <code>item</code> is a child of the set, and is inherited by each <code>hreview</code> contained within.		One solution to the problem of multiple reviews of the same item could be to wrap each <code>hReview</code> in a container (hypothetically, <code>hreview-set</code>. The <code>item</code> is a child of the set, and is inherited by each <code>hreview</code> contained within.

BenWard: Added hAtom shared date-stamp use case

2009-07-30T06:31:44Z

Added hAtom shared date-stamp use case

← Older revision		Revision as of 06:31, 30 July 2009
Line 80:		Line 80:
	This of course, extends the use of an existing container.		This of course, extends the use of an existing container.

			===hAtom entries published together===

			[[hAtom]] already has parsing rules to look for an <code>address</code> in the page for a shared author, a container-like concept. It already has an <code>hfeed</code> parent node, and this could be used to share other features of the format. For example, a photo album (for which explicit creation datetimes are either unavailable or irrelevant) may be published just as having been taken on a single day. As such, the date will appear once at the head of the page, and each photograph (<code>hentry</code>) will not contain a unique <code>updated</code> date.

	==Shared Aspects of Containers==		==Shared Aspects of Containers==

BenWard: /* hcontainer */ Comment on generic hContainer idea

2009-07-30T06:27:56Z

hcontainer: Comment on generic hContainer idea

← Older revision		Revision as of 06:27, 30 July 2009
Line 147:		Line 147:
	</div>		</div>
	</source>		</source>

			<div class='discussion'>
			* Unconvinced by the generics here. Especially since a lot of microformats already have parent nodes (<code>vcalendar</code>, <code>hfeed</code>). Doesn't self-document. —[[User:BenWard\|BenWard]] 06:27, 30 July 2009 (UTC)
			* In this case, <code>hreview-aggregate</code> could itself have container behaviour; the <code>hreview-aggregate</code> is a container for other <code>hreveiw</code> items, and the <code>item</code> is shared. —[[User:BenWard\|BenWard]] 06:27, 30 July 2009 (UTC)
			</div>

	=== item as a container ===		=== item as a container ===

BenWard: /* Problems */ Added response regarding repurposing `item`.

2009-07-30T06:21:41Z

Problems: Added response regarding repurposing `item`.

← Older revision		Revision as of 06:21, 30 July 2009
Line 151:		Line 151:
	The <code>item</code> microformat is currently used inside <code>hreview</code>s. Use this existing micformat as a container as well. This makes the specification slightly more complicated, since <code>item</code> will be allowed as a parent of <code>hreview</code> as well as a child. This is basically the same proposal as above, but using the name <code>item</code> for the container, instead of a dedicated name.		The <code>item</code> microformat is currently used inside <code>hreview</code>s. Use this existing micformat as a container as well. This makes the specification slightly more complicated, since <code>item</code> will be allowed as a parent of <code>hreview</code> as well as a child. This is basically the same proposal as above, but using the name <code>item</code> for the container, instead of a dedicated name.
	====Problems====		====Problems====

	* This defines two microformats that can be parent child of each other in both directions (<code>hreview</code> and <code>item</code>).		* This defines two microformats that can be parent child of each other in both directions (<code>hreview</code> and <code>item</code>).
	<source lang=html4strict>		<source lang=html4strict>
Line 165:		Line 166:
	</div>		</div>
	</source>		</source>

			* I don't really see that <code>item</code> makes sense as a container here. An item is a singular thing, a collection is wrapping a collection of things. In hReview, or hListing, or anything you'd have <code>container</code> as a structural parent of <code>item</code>. Repurposing <code>item</code> seems very confusing. --[[User:BenWard\|BenWard]] 06:21, 30 July 2009 (UTC)

	=== hreview rating and hreview-aggregate rating use different names ===		=== hreview rating and hreview-aggregate rating use different names ===

Elli: Grammar fix

2009-06-11T16:49:10Z

Grammar fix

← Older revision		Revision as of 16:49, 11 June 2009
Line 169:		Line 169:
	Since the microformat <code>rating</code> is used for both, an <code>hreview</code> that includes an <code>hcard</code> which contains aggregates, effectively imports a second rating. This can be solved by having different names for hreview rating and hreview-aggregate rating. This is not really a container proposal, but it addresses issues of the hreview-aggregate which is currently a container for item.		Since the microformat <code>rating</code> is used for both, an <code>hreview</code> that includes an <code>hcard</code> which contains aggregates, effectively imports a second rating. This can be solved by having different names for hreview rating and hreview-aggregate rating. This is not really a container proposal, but it addresses issues of the hreview-aggregate which is currently a container for item.
	====Problems====		====Problems====
	* This may not be necessary for pages that can use a container ~~to add microformats~~ with minimal impact to the xhtml structure. Pages that cannot use container structure and use includes may still need a solution.		* This may not be necessary for pages that can use a container microformat with minimal impact to the xhtml structure. Pages that cannot use container structure and use includes may still need a solution.
	<source lang=html4strict>		<source lang=html4strict>
	<div class="vcard item" id="review_item">		<div class="vcard item" id="review_item">

Elli: Grammar error

2009-06-11T16:44:56Z

Grammar error

← Older revision		Revision as of 16:44, 11 June 2009
Line 96:		Line 96:
	=== hCard as a container ===		=== hCard as a container ===
	<code>vcard</code> block can contain associated information like reviews and aggregates. <code>hreview</code>s inside an <code>vcard</code> do not need to specify item.		<code>vcard</code> block can contain associated information like reviews and aggregates. <code>hreview</code>s inside an <code>vcard</code> do not need to specify item.
	This also extends to other microformats that ~~can~~ may contain reviews, such as hproduct.		This also extends to other microformats that may contain reviews, such as hproduct.
	Another option is that a vcard that contains other microformat must also specify additional tag, such as <code>hcontainer</code>, <code>item</code> or similar.		Another option is that a vcard that contains other microformat must also specify additional tag, such as <code>hcontainer</code>, <code>item</code> or similar.
	====Problems====		====Problems====

Elli: Fixed explanation of shared aspect

2009-06-11T16:44:19Z

Fixed explanation of shared aspect

← Older revision		Revision as of 16:44, 11 June 2009
Line 88:		Line 88:
	* Inheriting an property into a microformat item within the container		* Inheriting an property into a microformat item within the container
	* Contained items ''overriding'' one or more inherited property		* Contained items ''overriding'' one or more inherited property
	* Alternatively, siblings cannot override properties of other siblings. Example: hcard of reviewer inside hreview cannot override any property of the item hcard (a sibling of the hreview). When a sibling specifies a property of another sibling, it is ignored (Example: hreview contains availability, ~~brand~~ is ignored).		* Alternatively, siblings cannot override properties of other siblings. Example: hcard of reviewer inside hreview cannot override any property of the item hcard (a sibling of the hreview). When a sibling specifies a property of another sibling, it is ignored (Example: hreview contains availability, availability is ignored).

	== markup proposals ==		== markup proposals ==