hCard Limitations and Known Issues

The following are known issues and limitations of the hCard Editor.

Version 0.9

  • The entire hCard specification is not supported.
  • Some pages will not parse, even after being tidied. The primary culprit seems to be Javascript that isn't commented out.
  • Parsing a large file to find the hCards can be slow. I may not be using XML::XPath right. I plan to rewrite the hCard finder to use regexps sometime and then just use XML::XPath to take apart the cards. Another option is to use something like DbXml to handle the XML tasks.
  • The hCard parser is dependent on the structure of mark-up. The parser expects certain members of the hCard to have specific ancestoral relationships. Thus, you can change the mark-up to suit your needs and the hCard editor will still read it, unless you change the structure. Better use of XPath would probably solve this problem.
  • The hCard appearance styles are hardcoded and somewhat limited. A richer set of styles is needed.
  • Similarly, the output is limited to the layout I like. You can edit it, but who wants to do that? A better option would be to use template (maybe based on XSLT) to layout the card.

Last Modified: Saturday, 26-Nov-2005 13:46:44 MST