>>> 1.) It seems like it should be a Design Pattern and not just something >>> for a single Microformat >> --- we do, ...
Point of clarification, I meant that we specify a solution that could be used multiple places as opposed to one that just applied to "money." The "include" pattern is a syntax for which we still need to define the semantics. It's a conduit, not a solution. >> ... If you are trying to shave off bits, then this doesn't do much for you, because you replace, <span class="type">USD</span>, with <a href="#id-ref" class="include" />, not much saving for a single value, but good for referencing full hCards for people and organizations. Actually if you use my examples from prior email in the case of money, that can shave off a *lot*. Plus it can make the file much easier to maintain. >> --- this is starting to sound like a solution to a non-problem. Nada! In previous email I gave numerous examples that people are publishing and several of them had lots of different currencies marked up with *lots* of prices. Par exemple: http://www.oxfordjournals.org/access_purchase/2007/institution_price_list.ht ml There are more where that came from if needed. Note I do my best to give real world usage examples on this list, not just hypotheticals. >> --- i would agree, we are bound to the semantics of HTML - we want as much interoperablity as possible, so you'd have to find elements that already exist that can serve this purpose. Anything wrong with <div> and <span> enclosing the entire user-supplied content? >> "do we have a solution to a problem, or are we find a problem for a solution?" Hopefully you see from my example we have the former, no? -Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Suda Sent: Friday, October 20, 2006 8:38 AM To: Microformats Discuss Subject: Re: [uf-discuss] Page-Global solution to Size Considersations (wasSize considerations (or how to choose)) On 10/20/06, Mike Schinkel <[EMAIL PROTECTED]> wrote: > Maybe the size per amount marked-up can be addressed by focusing on > providing a page-global solution? > I don't know what's been discussed along those lines but here are my > three > cents: > > 1.) It seems like it should be a Design Pattern and not just something > for a single Microformat --- we do, the include pattern allows you to specify data, and then throughout the rest of the page, reference it. If you are trying to shave off bits, then this doesn't do much for you, because you replace, <span class="type">USD</span>, with <a href="#id-ref" class="include" />, not much saving for a single value, but good for referencing full hCards for people and organizations. > 2.) I think it should allow multiple "defaults"; consider a page with > 1500 money values where 500 are in USD, 500 are in GBP, and 500 are in > EUR. Plus satisfying #1 would require multiples. --- this is starting to sound like a solution to a non-problem. We should really try to stick with what people are ALREADY publishing, making-up theorietical issues and solutions isn't the best use of our time. > 3.) I think it should be able to be applied anywhere in the document; i.e. > inside the <body> tag. Consider a Wiki or a CMS that doesn't allow a > page author to modify the headers of a page. --- i would agree, we are bound to the semantics of HTML - we want as much interoperablity as possible, so you'd have to find elements that already exist that can serve this purpose. We have explored <object> and <a>, <link> and @profile are good, but like you said they are somewhat outside of what normal CMSs handle. Ultimately, this also refers back to the question, "do we have a solution to a problem, or are we find a problem for a solution?" -brian -- brian suda http://suda.co.uk _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss