optimus-issues: Difference between revisions
Jump to navigation
Jump to search
(add see also section with link to external issues list at Google Code) |
m (added a warning message to warn users that Optimus is not working atm.) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Optimus]] is a [[validator]] for microformats. This page documents known issues grouped by area of support. Feel free to add new issues, or comment on existing issues. | [[Optimus]] is a [[validator]] for microformats. This page documents known issues grouped by area of support. Feel free to add new issues, or comment on existing issues. | ||
== Optimus validator is temporary not working! == | |||
Therefore any page you will check will return the message: "Microformats at this page have no errors. Congratulations." which is a false message. We will update this page when and if Optimus will work again. | |||
== issues with 0.8 == | == issues with 0.8 == | ||
=== JSON output b0rked === | |||
http://github.com/DmitryBaranovskiy/optimus/issues/#issue/11 | |||
=== hAtom validation === | === hAtom validation === | ||
==== properties are errantly reported as not specified ==== | ==== properties are errantly reported as not specified ==== | ||
Bug reported 2009-05-27: | |||
[http://microformatique.com/optimus/?format=validate&uri=http%3A%2F%2Fmicroformats.org%2F When validating microformats.org], Optimus states on a single [[hAtom]] hentry that both: <blockquote><p>Required property ‘author’ not specified.</p><p>Required property ‘updated’ not specified.</p><p>Required property ‘bookmark’ not specified.</p><p> Required property ‘entry-title’ not specified.</p></blockquote> and <blockquote><p>author ... Ben Ward</p><p>updated / 2009-05-15T01:16:43</p><p>bookmark / [http://microformats.org/blog/2009/05/15/rich-snippets-microformat-search/ In Search of Microformats]</p><p>entry-title / In Search of Microformats</p></blockquote> obviously if Optimus can find those properties on the hentry, then they are not "not specified". | [http://microformatique.com/optimus/?format=validate&uri=http%3A%2F%2Fmicroformats.org%2F When validating microformats.org], Optimus states on a single [[hAtom]] hentry that both: <blockquote><p>Required property ‘author’ not specified.</p><p>Required property ‘updated’ not specified.</p><p>Required property ‘bookmark’ not specified.</p><p> Required property ‘entry-title’ not specified.</p></blockquote> and <blockquote><p>author ... Ben Ward</p><p>updated / 2009-05-15T01:16:43</p><p>bookmark / [http://microformats.org/blog/2009/05/15/rich-snippets-microformat-search/ In Search of Microformats]</p><p>entry-title / In Search of Microformats</p></blockquote> obviously if Optimus can find those properties on the hentry, then they are not "not specified". | ||
| Line 9: | Line 18: | ||
==== bookmark is not required ==== | ==== bookmark is not required ==== | ||
Bug reported 2009-05-27: | |||
According to [[hatom#Schema|hAtom]], rel-bookmark is an optional property of hentry, however, [http://microformatique.com/optimus/?format=validate&uri=http%3A%2F%2Fmicroformats.org%2F when validating microformats.org], Optimus states: <blockquote><p> Required property ‘bookmark’ not specified.</p></blockquote>. | According to [[hatom#Schema|hAtom]], rel-bookmark is an optional property of hentry, however, [http://microformatique.com/optimus/?format=validate&uri=http%3A%2F%2Fmicroformats.org%2F when validating microformats.org], Optimus states: <blockquote><p> Required property ‘bookmark’ not specified.</p></blockquote>. | ||
| Line 14: | Line 24: | ||
=== better error documentation === | === better error documentation === | ||
* Enhancement: Whenever Optimus reports an error or warning, it would be great if the error message linked to the section of the specification that is being violated. | * Enhancement request 2009-05-27: Whenever Optimus reports an error or warning, it would be great if the error message linked to the section of the specification that is being violated. | ||
== see also == | == see also == | ||
* [[optimus]] | * [[optimus]] | ||
* [http://code.google.com/p/mf-optimus/issues/list Optimus issues list on Google Code] | * [http://code.google.com/p/mf-optimus/issues/list Optimus issues list on Google Code] | ||
* [[debugging-tools]] | |||
Latest revision as of 07:44, 6 February 2012
Optimus is a validator for microformats. This page documents known issues grouped by area of support. Feel free to add new issues, or comment on existing issues.
Optimus validator is temporary not working!
Therefore any page you will check will return the message: "Microformats at this page have no errors. Congratulations." which is a false message. We will update this page when and if Optimus will work again.
issues with 0.8
JSON output b0rked
http://github.com/DmitryBaranovskiy/optimus/issues/#issue/11
hAtom validation
properties are errantly reported as not specified
Bug reported 2009-05-27:
When validating microformats.org, Optimus states on a single hAtom hentry that both:
Required property ‘author’ not specified.
Required property ‘updated’ not specified.
Required property ‘bookmark’ not specified.
Required property ‘entry-title’ not specified.
and
author ... Ben Ward
updated / 2009-05-15T01:16:43
bookmark / In Search of Microformats
entry-title / In Search of Microformats
obviously if Optimus can find those properties on the hentry, then they are not "not specified".
- Expected behavior: if Optimus finds a property on an hentry, then it should not complain about that property being not specified.
bookmark is not required
Bug reported 2009-05-27:
According to hAtom, rel-bookmark is an optional property of hentry, however, when validating microformats.org, Optimus states:
Required property ‘bookmark’ not specified.
.
- Expected behavior: Optimus should not state that rel-bookmark is required on hentry, and if rel-bookmark is not specified, Optimus should perhaps simply provide a warning, that
better error documentation
- Enhancement request 2009-05-27: Whenever Optimus reports an error or warning, it would be great if the error message linked to the section of the specification that is being violated.