Re: [uf-discuss] Examples in Wiki

Can you make a list of places that don't seem consistent and add them to the todo page? On 10/5/06, Ryan King <[EMAIL PROTECTED]> wrote: On Oct 4, 2006, at 9:45 PM, Bob Jonkman wrote: > Hi all: I've been looking at the examples on the Wiki, especially > hCard, hCalendar and hResume. Many of

Re: [uf-discuss] Tentative proposal for "What's New" listings

Wow. Nice job all around! Here's my added twist to it. I took the URI Andy just posted, and sent it through lm orchard's xstlproc on the web to fetch my "rss to hyperscope" xslt and transform it. Since he's got hyperscope on his host, the document displays just fine. Incredible stuff.

Re: [uf-discuss] Four questions about hCard

covers the issue of how to use an hCard to represent an organization:. Some questions for Roger: * Did you see this resource? * If you hadn't seen it, if you had seen it, would it still have been unclear how to mark up for an organiza

Re: [uf-discuss] Four questions about hCard

On 10/7/06, Costello, Roger L. <[EMAIL PROTECTED]> wrote: Hi Folks, 1. Can an organization have an hCard? --- sure, the easiest way to achive this, is to use FN and ORG on the same element ABC Widgets Co. 2. Is the property "n" (name) mandatory? --- no, for companies this is just left blan

[uf-discuss] Four questions about hCard

Hi Folks, 1. Can an organization have an hCard? 2. Is the property "n" (name) mandatory? 3. The property "n" is composed of these subproperties: family-name, given-name, additional-name, name-prefix, name-suffix. Which of the subproperties are mandatory, which are optional? 4. If "n" is mandat

Re: [uf-discuss] Potential accessibility spin-off from hCard

Andy, On an accessibility mailing list, someone asked: Is there a way to make the screen reader know that a number is a phone number or street address so it reads 2-9-1-6 instead of 2,916? To which I have replied (in part): You can mark up a phone number (indeed, a whole address) u

Re: [uf-discuss] Microformats in Form Fields

Someone can mark up a form as an hCard anyway, regardless of whether it's in the spec or not. I imagine at least one person has already tried it after reading this thread, to see what it looks like. Thus, parsers could be subjected to this construct regardless of whether it's in the spec. Thus,

Re: [uf-discuss] Tentative proposal for "What's New" listings

In message <[EMAIL PROTECTED]>, Stephen Paul Weber <[EMAIL PROTECTED]> writes >Wow... this converter has never been through a full-scale test before >(only tested on my own pages)... so ya... that shouldn't happen. I >think I may know the problem, and will try to fix it soon :) Thanks >for findi

Re: [uf-discuss] Potential accessibility spin-off from hCard

In message <[EMAIL PROTECTED]>, Brian Suda <[EMAIL PROTECTED]> writes >You are absolutely right. Adding additional semantics can help all >sorts of non-standard browsers and agents. Indeed - uFs aside, the issue seems to be the standardisation of class names - it's easier for a user agent if ever

Re: [uf-discuss] Potential accessibility spin-off from hCard

You are absolutely right. Adding additional semantics can help all sorts of non-standard browsers and agents. CSS does have an aural style sheet type[1]. This is ment for screen-readers. I'm not sure if anyone actually honors them. In many ways a designer with visual capabilities forcing how a pa

Re: [uf-discuss] Re: X2C (Was Citation Microformat: Lazyweb...)

Thanks for all your comments. I have fixed the Author issue, it now concatenates them with " and ". I have also changed the "" to {} so now i don't have escape quotes. It is all uploaded so you can keep testing. (i still need to escape non-ascii characters, but that is not really an issue with the