-
Notifications
You must be signed in to change notification settings - Fork 61
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
Handling of invalid properties #1673
Comments
My vote would be to ignore the value (and, possibly, issue a warning) |
Where is the current conformance language? I am somehow not seeing it. |
Current language is here: https://w3c.github.io/epub-specs/epub33/rs/#sec-property-datatype Updated language in the open PR is here: https://cdn.statically.io/gh/w3c/epub-specs/fix/issue-808/epub33/rs/index.html#sec-property-datatype |
The issue was discussed in a meeting on 2021-05-13 List of resolutions:
View the transcript7. Handling of invalid propertiesSee github issue #1673. Matt Garrish: when I was making the URL spec change this came up Brady Duga: there are also situations where RS is suppose to ignore in failure case Dave Cramer: right, this causes as little disruption to reading experience as possible
|
@mattgarrish I did not know whether you want to change something on the spec related to this, so I did not close this issue yet. |
Also will close automatically with #1650. I've added the statement to the updated section on expanding property data types (as linked in the above comment). |
For the property data type, we say Reading System concatenation of the base URL and value must result in a valid url string.
So what happens if it doesn't? Must Reading Systems ignore the value? Should they ignore it? Or do we not care?
The text was updated successfully, but these errors were encountered: