Sunday, October 30, 2005
I took care of the two clear oversights -- isComment and isBreakpoint. The validator no longer flags them as errors.
There's a new test case, a simple script, that has comments and a breakpoint.
In general, where the validator says "must," it's referring to a rule established by the spec; when it says "should" it's calling on something from the guidelines for validation document.
The validator is a practical tool, based on the spec and the guidelines. As I said in the announcement, the XML spec takes precedence, after that, the OPML spec, then the guidelines.
I expect to write more docs over time, and I'm thinking about what to do about existing types not supported by the validator, and how to handle new types created in the near and far future.
# Posted by on 10/30/05; 12:43:22 AM - --
I suppose it goes without saying that I am no icon designer.
In case it needs saying, let me say it. "I am no icon designer."
So one thing on the to-do list for the OPML Validator is to get a beautiful icon that people will display with pride for OPML that works well with OPML search engines, editors, directory browsers, and what-have-you.
So if you're a designer, please work on this, and post a pointer to your work in the comments below.
# Posted by on 10/30/05; 5:05:29 PM - --
© Copyright 2000-2011, Scripting News, Inc.
OPML is a trademark of Scripting News, Inc.
Posted: 11/22/11; 8:32:22 AM.