I'm to understand that Atom has adopted the Tag URI as a a perferred GUID for an Atom 1.0 feed. I've begun to use the Tag URI in my work.
Eventually, I found myself parsing the Tag URI in Java, and I've begun to wonder why the Tag URI scheme did not follow the pattern of a hierarchical URI. It is instead an opaque URI. This means that the nifty parser built into the Java URI class only extracts a scheme, scheme specific part, and fragment. tag:agtrz,com:payload#fragment Had Tag URI been specified as a heirarical, the parser would be able to extract more payload from the URI. tag://agtrz.com,2005/path?query#fragment Same parser, more to play with. I've asked the authors of the RFC, but apparently, I was unable to convey my concerns about this. -- Alan Gutierrez - [EMAIL PROTECTED] - http://engrm.com/blogometer/
