Search results

Use [[hcard|hCard]] with the <code>logo</code> property for visible icons instead.

== url property == Proposal: add the "url" property as another way for authors to indicate a media resource (in addition to hMe

<dd>This optional property serves as an overview of qualifications and objectives. Re-used from hRevie <dd>This optional property provides information about the person who authored the resume. If the value

<dd>This optional property provides the title or name of an entry, based on the definition of atom:fee <dd>This optional property provides the summary of an entry, based on the definition of atom:summary

...ty with content produced using earlier versions of the specification. This property is syntax compatible with, and thus reuses the semantics of "VERSION" as de <dd>This optional property serves as a short synopsis, title, or name of the review. Re-used from hCal

...ty with content produced using earlier versions of the specification. This property is syntax compatible with, and thus reuses the semantics of "VERSION" as de <dd>This optional property serves as a short synopsis, title, or name of the listing. Re-used from hRe

...cify a <code>url</code> property for the item (in hReview 0.3 having "url" property for the item is only a SHOULD) ...deprecating the <code>version</code> property. is the <code>version</code> property needed? currently it is optional and created invisibly by the [http://micr

==== parsing a p- property ==== ==== parsing a u- property ====

...tize hCards with <code>rel=me</code> or any object with a <code>uid</code> property on the same domain=== Where an object is in a page with a property <code>uid</code> pointing to the same domain as the current page, and/or ma

...ting''', '''dt-published''', '''p-author''', '''e-content''' and the other property class names listed below defined elements as ''properties'' of the h-review ...ot class name'' that indicates an embedded '''[[h-item]]''' for the p-item property.

..." property whose value is the url of the page (source) and is also a "uid" property for the hCard, is the representative hCard for the page. ...step didn't find a representative hCard, then the first hCard with a "url" property that also has the <code>rel="me"</code> relation is the representative hCar

...ple shows an <code>h-entry</code> type microformats2 object, with a single property attached. The <code>h-entry</code> type is [[h-entry|documented on the wiki ...code> member contains an object where every member name is a microformats2 property name, and every member value is an array of the found microformats2 values.

** Intellectual property issues:

...draft-ietf-vcarddav-vcardrev-03.txt latest vCard 4.0 draft] includes a new property "member". This could be leveraged in hCard like so: * This is similar to how the "agent" property already works, so people should already be fairly familiar with it.

** [[hatom-issues#|add url property to hentry]] (open)

...entative h-card was found, if the page contains an h-card with a '''url''' property value which also has a <code>rel=me</code> relation (i.e. matches a URL in ...the page contains '''one single''' h-card, and the h-card has a '''url''' property matching the page URL, that h-card is the representative h-card

=== relationship-status property name === Simple brainstorm proposal: use the property name <code>'''relationship-status'''</code> as a class name on an element m

...iew" for backwards compatibility, detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to ...orporate rel property parsing either as just another property (like a 'u-' property) scoped to the microformat:

'''p-name''', '''e-instructions''', '''p-ingredient''' and the other property classnames listed below define elements as ''properties'' of the h-recipe. See [[microformats-2-parsing]] to learn more about property classnames.

* The bio field should be marked up with the property <code>note</code>, i.e. <code>class="bio"</code> should be <code>class="bio

'''Use the same property names as microformat equivalents''' * All property names must be consistent with their equivalent microformat name. They shoul

| [[rel-dcterms.(property)#conformsTo|DCTERMS.conformsTo]] | [[rel-dcterms.(property)#contributor|DCTERMS.contributor]]

...at least one reader / real world consuming code example to become a draft property: ...ly one of them is an "h-card" then it is used to imply a "p-author h-card" property of the implied "h-feed" and is removed from the "children" array of the imp

Can be used in the ''background-image'' CSS property, next to a geo microformat. It could also indicate that a map opens in a ne

I think that better property name for working tools and conditions will be '''equipments''' -- [[User:Ju

...ay deserve their own section. I would be interested in seeing a class name property "award" if there are a good number of real world examples of online resumes

''Why not exploit the rev property to avoid having to use a different keyword to denote the reverse? --[[User:

**** else parse a child element class for property class name(s) "p-*,u-*,dt-*,e-*" **** if such class(es) are found, it is a property element

...<code>published</code> property, as well as the hAtom <code>updated</code> property. ...arsable, even when the parser does not understand the vocabulary. As such, property names have to be on an explicit attribute, not shared with other, non-data

=== property details ===

...described as "The publishing division which published the comic"; why this property is part of the Menu type is beyond my comprehension

...-name" (note: fixed in microformats2 - flat set of properties, no more "n" property in h-card)

...recommendation is that all properties are made optional, then any required property in Atom could be synthesized, which potentially introduces uncertainty/ambi ...here are some reasons that it would be nice to also have an explicit "url" property for inclusion of URLs to media item resources:

...umeration of valid values. No other microformat thus far has had a version property, and explicit versioning seems like clumsy design: any future changes to th ==Property Details==

* "fn" - is a property name It would be useful to specify the atomic type of a microformats property, e.g. one of the following:

...ng Properties]. However, there is a mix of properties on the second listed property called: "''listing action.'' optional." *# The '''version''' property should be deprecated. No other Microformat (classic or [[microformats-2|new

'''Update''': note that [[vCard4]] has a "gender" property that is likely to be incorporated into the next version of [[hCard]]. ...of births was not carried out, rely on baptism records, A date-of-baptism property is thus required. This could be added to hCard, or be specific to a genealo

<!-- # If a non-representative hCard exists on the page with a UID property which is identical to the target of the link element, then this hCard is ta

...ry-summary</code>''', '''<code>entry-content</code>''' and the other hAtom property classnames listed below define properties of the entry.

*# ''the "publications" property should be "publication" per [[naming]]'' *#* the "publications" property in particular seems a bit off - it probably should have been "publication"

...D. PROPOSED RESOLUTION.''' We are fixing this with [[microformats-2]], all property names have prefixes to avoid such collisions. E.g. 'url' becomes 'u-url' an

...xisting publishing practices of public keys, either with [[hCard]]'s 'key' property, or possibly other solutions. ...rty in a vCard, importable into any Address Book that supports vCard's key property.

...up each person's page with an hCard for them that has a <code>bday</code> property, with even just the year if you want - that could then be used to determine ...and thus differences) should be represented by use of the [[hCard]] 'bday' property, not rel. [[User:Tantek|Tantek]] 19:27, 15 June 2009 (UTC)

'''p-name''', '''p-author''', '''dt-published''' and the other h-entry property classnames listed below define properties of the h-entry. ...is to place it around both the explicitly written content (in the content property or in other specific properties for non-textual content or responses) and w

''Why not exploit the rev property to avoid having to use a different keyword to denote the reverse? --[[User:

...erty, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide ...kes a URL as its value, the <code>href="..."</code> attribute provides the property value.

<a rel="url" href="http://manu.sporny.org/" property="fn">Manu Sporny</a> ...re of : microformats (by adding class and rel attributes), RDFa (by adding property, rel, and about attributes), and microdata (by adding itemscope, itemtype,

* [[xoxo|xoxo]] :: to address property-value data that may be necessary for a complete data representation of a pr

...numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standa === Property details ===

...ards the number of reviews available" - essentially, a "number of ratings" property. ...be available. (Your product snippet may not display if the priceValidUntil property indicates a past date.)"

* post h-entry with property <code>p-comment h-entry</code> (child) for a comment * no need for h-feed because p-comment property value can already be an array

...rst confusion comes from the fact that "item" (currently is a non-existing property) and "listing" elements are not hierachically defined among the other micro ...n. It therefore ''requires'' this information to exist. Maybe the required property should be the url value and the other properties can be optional. [[User:Sp

But to add a URL to the company, there is no "org-url" property (nor should there be), instead, use modularity and a nested hCard for the c Thanks to the flexibility of the URL property, the answer is no, no extensions are necessary. Instead, we use the proper

..., and if at some point the consuming application wants to display that u-* property as an img, they have to either omit or synthesize a fake text alternative. === Include alt property in parent object ===

<p class="p-v"><span class="property">Color:</span> <span class="value">289 Rush</span></p> <h4 class="p-v"><span class="property artist">Small Faces</span></h4>

...numerous review sites and formats in use today on the web. Where possible property names have been chosen based on those defined by the related [[hcard|hCard] === Property details ===

The basic format of hCard is to use vCard object/property names in lower-case for class names, and to map the nesting of vCard object === Property List ===

This method of hCard property indirection via an object element [[include-pattern|has been generalized]]

...numerous review sites and formats in use today on the web. Where possible property names have been chosen based on those defined by the related [[hcard|hCard] === Property details ===

...isting-classes|Using existing class names]] and creating new names, create property names for the profile

* <span id="property-list-n">'''n'''<sup style="font-size:smaller">[[#note1|1]]</sup></span> * <span id="property-list-tel">tel<sup style="font-size:smaller">[[#note2|2]]</sup> (type, value

This method of hCard property indirection via an object element [[include-pattern|has been generalized]]

...ics suggest it would be an appropriate source for the <code>updated</code> property. Example: <http://blog.benward.me/post/250674456> ...if 'updated' is missing, use the latest in time value of: the 'published' property value, and the 'datetime' attributes of all ins and del elements inside the

...arsable, even when the parser does not understand the vocabulary. As such, property names have to be on an explicit attribute, not shared with other, non-data

...Even the text label/title of an outline item could be considered a common property. A few such common properties: ...<code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier examp

=== Why is adr property necessary === === Why is url property necessary ===

* [[xoxo-fr|xoxo]] :: pour adresser les données property-value qui peuvent être nécessaire pour une représentation complète d'un

==Property Details== hListing property details:

...Even the text label/title of an outline item could be considered a common property. A few such common properties: ...<code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier examp

...t pair "entry-" with some arbitrary other word (even existing microformats property name) and have it work or even mean anything. Thus "entry-" is not a stand

==Property Details== hListing property details:

...Most other properties can be parsed by performing a "pivot": treating the property element as a microformat in its own right and finding sub-properties using ...mple within hCard, the agent property may contain a nested hCard. For each property <code>prop</code> which may contain a nested microformat:

.../</nowiki> e.g. http://daveman692.vox.com/profile/ (note issue: empty "n" property. fix: remove "n" from class attribute).

Note: the TYPE needs to be a sub-element of the property (adr, tel, etc) NOTE: EMAIL does NOT have many TYPE attributes, only INTERN ...nd on the parsing side, if there is no "fn" present, but there is an "org" property, then duplicate the "org" value as "fn"

* <span id="property-list-n">'''n'''<sup style="font-size:smaller">[[#note1|1]]</sup> (family-na * <span id="property-list-tel">tel<sup style="font-size:smaller">[[#note2|2]]</sup> (type, value

...erty, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide ...akes a URL as its value, the <code>src="..."</code> attribute provides the property value.

...ations there-of) may apply specific/singular semantics to first value of a property. ...s. Hierarchical data is represented with nested microformats, typically as property values themselves. Properties are all optional and potentially multivalued

#* Yes. In general if the specification does not explicitly forbid it, a property may take multiple values (or be specified multiple times).

...microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to ...microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to

...croformats process. That being said, if you really must include arbitrary property-value data, there is already a microformat for that: [[xoxo]]. Modularly in ...ta is used, then leave it out per microformats [[principles]]. A "version" property was added to [[hReview]] for largely theoretical concerns, but has never be

...marked up as a telephone address, rather than the currently suggested URL property. ...span tags and create the value for N correctly seperated by colons. The FN property will take a string and simply display it. There are two possible renderings

...good to be explicit with such things, and it just so happens that the name property is a compulsory field within an [[hcard|hCard]] as well. So let's add it, u The name is the one required property of hCard. Thus be sure to mark up the name of the person with the class na

...them simpler and reduces chances of error. RDFa has been struggling with 'property' vs. 'rel' issues with just two attributes! - [[User:Tantek|Tantek]]

...a nested hCard item for the review per [[hreview#Property_details|hReview property details: item]]. There are a few problems with the current markup.

* No, property elements must be inside the root class name element. ...oot class name is providing an entire object as the embedded value of that property which then belongs to some other object higher up the tree.

* a class name represents a microformat '''property name''' * a class name represents a microformat '''property that needs special parsing'''

...re posted in tabular form, where the headings on the columns and rows have property values that apply to the cells which themselves are events. E.g. many conf ...efore) any class names on that header cell for determining whether it is a property of the VEVENT.

** continue updating the spec per the inline comment about property references ...ective sections in [[RFC2426]]. add any non-trivial information about each property similar to what [[hreview|hReview]] has.

...of how to use each property correctly should be given with each and every property, not just list a few at the top before the properties have even been define .... Each property has now been listed explicitly. Brief explanations of each property will be added. -Tantek

...ses XML, so any sub-properties are listed in their tree form, property/sub-property. ...contributor) - this can be handled with hCard, but will need an additional property to refine what "creator" means

...microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to ...microformats 2 parsers {{should}} detect the following root class name and property names. A microformats 2 parser may use existing microformats [[parsers]] to

* <span id="property-list-n">'''n'''<sup style="font-size:smaller">[[#note1|1]]</sup></span> * <span id="property-list-tel">tel<sup style="font-size:smaller">[[#note2|2]]</sup> (type, value

...ges, and perhaps try to establish a mapping between them. As microformats property names are based on existing standards (see [[process]], and [[naming-princi

...re already in the current proposal. It may be sensible to have a "synonym" property (as used on http://en.wikipedia.org/wiki/Doronomyrmex_pocahontas), but I do

...always written out in the english version. This requires the addition of a property that may not have been in the sentence to specify "weight" for example. * Requires the definition of a "type" in order for the value to have a property name in the parsed JSON.

...rkup for details of Press Contacts. Example: [http://www.lslps.co.uk/news Property News Page] * [http://iprefer.com/ I Prefer Guest Benefit Program] uses hCard for each property page. Example: [http://iprefer.com/luxury-hotel/Campinas/Royal-Palm-Tower/