Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need a lax RDFa parsing mode ? #88

Open
domguard opened this issue Jan 24, 2012 · 0 comments
Open

Do we need a lax RDFa parsing mode ? #88

domguard opened this issue Jan 24, 2012 · 0 comments
Assignees
Labels

Comments

@domguard
Copy link

http://bblfish.net/#me chokes on XHTML parsing on the PyRDFA online validator

http://www.w3.org/2007/08/pyRdfa/extract?uri=http%3A%2F%2Fbblfish.net%2F%23me&format=pretty-xml&warnings=true&parser=lax&space-preserve=true

So we could either

  • rely on a less strict parser ( "pyRDFa":http://www.w3.org/2007/08/pyRdfa/#distribution has a "lax" HTML5 fallback mode)
  • kee current validation and catch more errors...
  • consider this later if more errors of this kind are reported

cryptic error message of pyRDFa for this profile :

dist:messageXHTML Parsing error in input file: not well-formed (invalid token): line 73, column 100. Falling back on the HTML5 parser/dist:message

and also :

dist:messageinvalid @rel/@Rev value: 'openid.server'/dist:message
dist:messageinvalid @rel/@Rev value: 'openid2.provider'/dist:message
dist:messageinvalid @rel/@Rev value: 'shortcut'/dist:message

@ghost ghost assigned bennomadic Aug 9, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants