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

Challenging test err-xd0063-001.xml #217

Closed
xml-project opened this issue Jul 19, 2019 · 4 comments

Comments

@xml-project
Copy link
Contributor

commented Jul 19, 2019

To my reading this should not be an error, but an empty text document.
Prove:

If the content type is not an XML media type or an HTML media type, each text value template is replaced by the concatenation of the serialization of the nodes that result from evaluating the template.

Did I misunderstood this ruling?

@ndw

This comment has been minimized.

Copy link
Contributor

commented Jul 19, 2019

Disprove:

It is a dynamic error (err:XD0063) if the p:inline contains any XML markup and has a content type that is not an XML media type or an HTML media type.

Looks like we have a conflict in the spec. I'll open an issue on the specification that proposes removing err:XD0063.

@xml-project

This comment has been minimized.

Copy link
Contributor Author

commented Jul 19, 2019

Ok, I see your point. To me XD0063 is for this:

<p:inline content-type="text/plain"><element /></p:inline>

Here we have XML markup, while the TVT rule says, that text is inserted. We should make this more precise, but I think we need to keep XD0063.

@ndw

This comment has been minimized.

Copy link
Contributor

commented Jul 19, 2019

Ah. Yes. I see where I got it wrong 😄

I don't know if we need any spec changes or not. But I concur with your analysis.

ndw added a commit to ndw/3.0-test-suite that referenced this issue Jul 19, 2019

@ndw ndw referenced this issue Jul 19, 2019

ndw added a commit that referenced this issue Jul 20, 2019

@xml-project

This comment has been minimized.

Copy link
Contributor Author

commented Jul 20, 2019

fixed with pr #218

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.