value-class-pattern-brainstorming

(Difference between revisions)

Jump to: navigation, search
(added some notes, better than nested empty span, DRY violation content divergence risk mitigating techniques)
(noted separate advanages, neutral, disadvantage in comparison to nested empty span and/or abbr. minimizing risk, lowering content divergence risk closer to same level as abbr)
Line 26: Line 26:
=== notes ===
=== notes ===
 +
==== advantages ====
* '''Greater semantic re-use.''' The use of the param element to specify a value for its object is in line with the param element's semantics.  The semantic association between the object and the param element is defined in the HTML4 specification.   
* '''Greater semantic re-use.''' The use of the param element to specify a value for its object is in line with the param element's semantics.  The semantic association between the object and the param element is defined in the HTML4 specification.   
* '''Less invention.''' This use of object param is superior to the use of a nested empty span element.  The association of an empty span with its parent is a new semantic not previously defined in the HTML4 specification. Thus this use of object param markup better follows the principle of minimum invention as compared to nested empty span markup.
* '''Less invention.''' This use of object param is superior to the use of a nested empty span element.  The association of an empty span with its parent is a new semantic not previously defined in the HTML4 specification. Thus this use of object param markup better follows the principle of minimum invention as compared to nested empty span markup.
-
* Similar violation of DRY to nested empty span.
+
==== neutral ====
-
* More content divergent violation of DRY than abbr. With abbr, one element is used to express both a human visible string and the property value, thus tying these values closer together (thus reducing risk of divergence). With object param, two elements are used, and thus risk of divergence may be greater than the use of abbr. Possible mitigating techniques that would help keep the property value and the equivalent human visible string closer to each other:  
+
* '''Similar violation of DRY to nested empty span.'''
 +
==== disadvantages ====
 +
* '''Less human visible than abbr DRY violation.''' The contents/values of param elements are not exposed to the user of a browser, unlike the title attribute of abbr which, since it is commonly available as a hover tooltip, is more human visible, thus verifiable, than param.
 +
* '''DRY violation content divergence risk greater than abbr.''' With abbr, one element is used to express both a human visible string and the property value, thus tying these values closer together (thus reducing risk of divergence). With object param, two elements are used, and thus risk of divergence may be greater than the use of abbr. Possible mitigating techniques that would help keep the property value and the equivalent human visible string closer to each other, perhaps as close in the code as they are when using abbr:
*# require param be first child of object
*# require param be first child of object
*# require use of only one param child (allow other child elements)
*# require use of only one param child (allow other child elements)

Revision as of 03:16, 25 August 2008

value excerption pattern brainstorming

The value-excerption-pattern is derived from value-excerpting in hCard. The precise parsing behavior is not yet finalized, so the pattern should be used only with extreme caution.

This brainstorming page is for exploring ideas related to specifying the value-excerption-pattern in more detail and ideas for special case handling of the value-excerption-pattern in combination with specific semantic HTML elements per those elements' particular semantics.

These are merely explorations for now, and should NOT be used in actual content publishing, nor implemented in any production code.

Contents

Editor
Tantek Çelik

object param handling

2008-08-23 Ben Ward and Tantek Çelik brainstormed the following possible special case markup handling for the use of the value-excerption-pattern with the <object> element.

The following markup example documents one way the hCard tel property's type subproperty could be specified with the enumerated value of "cell" while providing the UK English "mobile" as the human visible object text contents:

<object class="type" lang="en-GB">
 <param class="value" name="value" value="cell" />
 mobile
</object>

notes

advantages

neutral

disadvantages

to do

related pages

value-class-pattern-brainstorming was last modified: Wednesday, December 31st, 1969

Views