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

Missing error in p:load for html media type #280

Closed
xml-project opened this issue Dec 11, 2019 · 3 comments · Fixed by #316
Closed

Missing error in p:load for html media type #280

xml-project opened this issue Dec 11, 2019 · 3 comments · Fixed by #316
Assignees
Labels
standard step library Issues for the standard step library

Comments

@xml-project
Copy link
Member

The current spec does not contain an error to be raised, if the processor is not able to load an HTML document. I think we should add this.

@ndw
Copy link
Collaborator

ndw commented Dec 11, 2019

There is no such thing as a not-well-formed HTML5 document. I don't think any error is possible; but I don't object to adding an explicit error code. I suppose XD0060 is also possible.

@xml-project
Copy link
Member Author

There is no such thing as a not-well-formed HTML5 document.

I am not sure I understand what this means. ;-))

Anyway: p:load is supposed to produce an XDM instance. Is it garanteed, that any HTML5 document can be represented by an XDM instance?

@ndw
Copy link
Collaborator

ndw commented Dec 11, 2019

Yes. Any random sequence of characters produces a well-formed XDM tree if you parse it with an HTML5 parser. But for consistency, I'm happy with an explicit error code in case there is something that does raise an error.

@xml-project xml-project added the standard step library Issues for the standard step library label Dec 22, 2019
@ndw ndw self-assigned this Jan 1, 2020
@ndw ndw closed this as completed in #316 Jan 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
standard step library Issues for the standard step library
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants