|
osdir.com mailing list archive F.A.Q. -since 2001! |
|
|
|
Date: Prev Next Date Index Thread: Prev Next Thread Index
Website Performance Monitoring On Feb 11, 2006, at 9:33 PM, Johannes Ernst wrote:
Reasonable implementation guidelines (non-normative) might be: 1) if broken HTML is displayed as something reasonable in a reasonably standard browser, a user will expect that any identity markup in this page will be similarly understood by a YADIS implementation, just like the broken HTML is understood by the browser. 2) if the YADIS implementation cannot make sense out of the (broken) HTML, it displays a reasonable error message that indicates that. After a glance at the wiki, I think all these things belong in the Implementor's Guide, which I guess is just an informative spec. Should we just start writing it, and move all discussion on there? Or wait till consensus before we create it? Joseph Anthony Pasquale Holsten 24R E 24th St Tulsa OK 74114-2406 mailto:pantosys@xxxxxxxxx xmpp:pantosys@xxxxxxxxx tel:+1* 918 813 2447
Thread at a glance:
Previous Message by Date:Re: Broken HTML SupportI'd propose that YADIS take no "official" position -- at least at this time -- on this issue. It's virtually impossible to be crisp on an issue like that ... Reasonable implementation guidelines (non-normative) might be: 1) if broken HTML is displayed as something reasonable in a reasonably standard browser, a user will expect that any identity markup in this page will be similarly understood by a YADIS implementation, just like the broken HTML is understood by the browser. 2) if the YADIS implementation cannot make sense out of the (broken) HTML, it displays a reasonable error message that indicates that. Johannes Ernst NetMesh Inc. http://netmesh.info/jernst Next Message by Date:Re: Broken HTML SupportMy take: please start collecting notes or writing any time. On Feb 11, 2006, at 20:27, Joseph Holsten wrote: On Feb 11, 2006, at 9:33 PM, Johannes Ernst wrote: Reasonable implementation guidelines (non-normative) might be: 1) if broken HTML is displayed as something reasonable in a reasonably standard browser, a user will expect that any identity markup in this page will be similarly understood by a YADIS implementation, just like the broken HTML is understood by the browser. 2) if the YADIS implementation cannot make sense out of the (broken) HTML, it displays a reasonable error message that indicates that. After a glance at the wiki, I think all these things belong in the Implementor's Guide, which I guess is just an informative spec. Should we just start writing it, and move all discussion on there? Or wait till consensus before we create it? Joseph Anthony Pasquale Holsten 24R E 24th St Tulsa OK 74114-2406 mailto:pantosys@xxxxxxxxx xmpp:pantosys@xxxxxxxxx tel:+1* 918 813 2447 Johannes Ernst NetMesh Inc. http://netmesh.info/jernst Previous Message by Thread:Re: Broken HTML SupportI'd propose that YADIS take no "official" position -- at least at this time -- on this issue. It's virtually impossible to be crisp on an issue like that ... Reasonable implementation guidelines (non-normative) might be: 1) if broken HTML is displayed as something reasonable in a reasonably standard browser, a user will expect that any identity markup in this page will be similarly understood by a YADIS implementation, just like the broken HTML is understood by the browser. 2) if the YADIS implementation cannot make sense out of the (broken) HTML, it displays a reasonable error message that indicates that. Johannes Ernst NetMesh Inc. http://netmesh.info/jernst Next Message by Thread:Re: Broken HTML SupportMy take: please start collecting notes or writing any time. On Feb 11, 2006, at 20:27, Joseph Holsten wrote: On Feb 11, 2006, at 9:33 PM, Johannes Ernst wrote: Reasonable implementation guidelines (non-normative) might be: 1) if broken HTML is displayed as something reasonable in a reasonably standard browser, a user will expect that any identity markup in this page will be similarly understood by a YADIS implementation, just like the broken HTML is understood by the browser. 2) if the YADIS implementation cannot make sense out of the (broken) HTML, it displays a reasonable error message that indicates that. After a glance at the wiki, I think all these things belong in the Implementor's Guide, which I guess is just an informative spec. Should we just start writing it, and move all discussion on there? Or wait till consensus before we create it? Joseph Anthony Pasquale Holsten 24R E 24th St Tulsa OK 74114-2406 mailto:pantosys@xxxxxxxxx xmpp:pantosys@xxxxxxxxx tel:+1* 918 813 2447 Johannes Ernst NetMesh Inc. http://netmesh.info/jernst
|
|