include-pattern-strawman

(Difference between revisions)

Jump to: navigation, search
(Related Pages)
(another possibility)
Line 1: Line 1:
-
= Toby Inkster's Minimally Verbose Solution =
+
=Include pattern Strawmen=
 +
 
 +
Possible variations on the [[include-pattern|include pattern]], to resolve issues of accessibility (with empty anchors) and server load (with include):
 +
 
 +
== Toby Inkster's Minimally Verbose Solution ==
An alternative way of implementing the include pattern in a less verbose, and hopefully more accessible manner:
An alternative way of implementing the include pattern in a less verbose, and hopefully more accessible manner:
Line 25: Line 29:
If people can find real-life uses of the hash character in existing sites that would conflict with this proposed usage pattern, then perhaps another character could be used. I rather like '@foo', or maybe even a combination such as '@#foo'.
If people can find real-life uses of the hash character in existing sites that would conflict with this proposed usage pattern, then perhaps another character could be used. I rather like '@foo', or maybe even a combination such as '@#foo'.
-
== Including data in the middle of an element ==
+
=== Including data in the middle of an element ===
Above, the examples show how an element can be logically included as the first or last child of another element. For including data into the middle of an element, we need to be a tiny bit more verbose and insert a dummy element (in this case a <span> element) where the included content should go:
Above, the examples show how an element can be logically included as the first or last child of another element. For including data into the middle of an element, we need to be a tiny bit more verbose and insert a dummy element (in this case a <span> element) where the included content should go:
Line 38: Line 42:
</pre>
</pre>
-
= Related Pages =
+
==Andy Mabbett==
 +
See  <http://microformats.org/discuss/mail/microformats-discuss/2008-January/011422.html et seq.
 +
 
 +
:<code><foo id="birminghamid" class="locality">Birmingham</foo></code>
 +
 
 +
then:
 +
 
 +
:<code><foo class="adr birminghamid">[...]</foo></code>
 +
 
 +
or
 +
 
 +
:<code><foo class="adr part-microformat birminghamid">[...]</foo></code>
 +
 
 +
or
 +
 
 +
:<code><foo class="adr use-birminghamid">[...]</foo></code>
 +
 
 +
or
 +
 
 +
:<code><foo class="adr uses-birminghamid">[...]</foo></code>
 +
 
 +
or
 +
 
 +
:<code><foo class="adr include-birminghamid">[...]</foo></code>
 +
 
 +
or
 +
 
 +
:<code><foo class="adr includes-birminghamid">[...]</foo></code>
 +
 
 +
or
 +
 
 +
:<code><foo class="adr locality-birminghamid">[...]</foo></code>
 +
 
 +
or
 +
 
 +
:<code><foo id="birminghamid">Birmingham</foo></code>
 +
 
 +
:[...]
 +
 
 +
:<code><foo class="adr locality-birminghamid">[...]</foo></code>
 +
 
 +
Note: "birminghamid" used for clarity; "birmingham" would be the semantically correct value.
 +
 
 +
== Related Pages ==
{{include-pattern-related-pages}}
{{include-pattern-related-pages}}
* [[User:TobyInk|Toby Inkster]]
* [[User:TobyInk|Toby Inkster]]

Revision as of 19:41, 3 February 2008

Contents

Include pattern Strawmen

Possible variations on the include pattern, to resolve issues of accessibility (with empty anchors) and server load (with include):

Toby Inkster's Minimally Verbose Solution

An alternative way of implementing the include pattern in a less verbose, and hopefully more accessible manner:

 <p>We have three branches in <span class="locality" id="ldn">London</span>,
 including our head office in <span class="locality" id="ken">Kensington</span>:</p>
 <ul>
   <li class="adr #ldn">
     <span class="street-address">123 Oxford Street</span>
   </li>
   <li class="adr #ken #ldn">
     <span class="street-address">5 Kensington High Street</span>
   </li>
   <li class="adr #ldn">
     <span class="street-address">1 Pall Mall</span>
   </li>
 </ul>

The order of the space-delimited class attributes should be considered significant -- that is, in <foo class="bar #baz"> the content referred to by #baz is logically included as the last child of the <foo> element, but in <foo class="#baz bar">, it is logically included as the first child. (See below for an example where the included element should occur in the middle of the element content.)

Yes, the hash mark is valid in the class attribute, though rarely used because it won't work with CSS 1 selectors.

If people can find real-life uses of the hash character in existing sites that would conflict with this proposed usage pattern, then perhaps another character could be used. I rather like '@foo', or maybe even a combination such as '@#foo'.

Including data in the middle of an element

Above, the examples show how an element can be logically included as the first or last child of another element. For including data into the middle of an element, we need to be a tiny bit more verbose and insert a dummy element (in this case a <span> element) where the included content should go:

 <p>Our head office is in <span id="ldn" class="locality">London</span> at:
 <p class="adr">
   <span class="street-address">5 Kensington High Street</span><br>
   <span class="#ldn"></span>
   <span class="postal-code">SW7 1AA</span>
 </p>

Andy Mabbett

See <http://microformats.org/discuss/mail/microformats-discuss/2008-January/011422.html et seq.

<foo id="birminghamid" class="locality">Birmingham</foo>

then:

<foo class="adr birminghamid">[...]</foo>

or

<foo class="adr part-microformat birminghamid">[...]</foo>

or

<foo class="adr use-birminghamid">[...]</foo>

or

<foo class="adr uses-birminghamid">[...]</foo>

or

<foo class="adr include-birminghamid">[...]</foo>

or

<foo class="adr includes-birminghamid">[...]</foo>

or

<foo class="adr locality-birminghamid">[...]</foo>

or

<foo id="birminghamid">Birmingham</foo>
[...]
<foo class="adr locality-birminghamid">[...]</foo>

Note: "birminghamid" used for clarity; "birmingham" would be the semantically correct value.

Related Pages

include-pattern-strawman was last modified: Wednesday, December 31st, 1969

Views