value-class-pattern-brainstorming
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.
- 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
- 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.
- Similar violation of DRY to nested empty span.
- 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:
- require param be first child of object
- require use of only one param child (allow other child elements)
- require exclusive use of object for value excerption i.e. no using the same object for an actual replaced object and a value excerption
- require "value" attribute be the last attribute specified on the param element
- require equivalent human visible text be placed immediately (allowing for whitespace) following the param
to do
- Browser testing. This code sample must be tested in various browsers to determine how they process and handle pages with such code
- determine which browsers to test (based on popularity, deployment, etc.)
- write a full sample test case using the above object param markup pattern and a complete hCard
- write a more complex sample test case with multiple uses of the object param markup pattern
- test do browsers properly display the UK English text "mobile"?
- test do browsers generate multiple browser (e.g. Webkit, Trident etc.) controls as they would for embedded frames (nested HTML objects)?
- determine any other tests
- Parser implementability. Determine approximately how much work it would be to implement this special case object param support.
- Document in more detail. Assuming browser tests of a simple example pass (proper visible text displayed, page efficiency not compromised by additional control creation), document how to handle/parse this pattern in more detail. Iterate.