-
Notifications
You must be signed in to change notification settings - Fork 5
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
illegal values in <objectDesc> "form" attribute cause errors in editor #311
Comments
yes this is bad news - shall have this chased up tomorrow |
which file was the one affected, so that it can be made available again? |
We fixed the file in question manually by editing the metadata and just
removing the question mark. I will assemble a list of other offending
files.
T
…--
Tom Elliott, Ph.D.
Associate Director for Digital Programs and Senior Research Scholar
Institute for the Study of the Ancient World (NYU)
http://isaw.nyu.edu/people/staff/tom-elliott
Humanities Commons: @paregorios <https://hcommons.org/members/paregorios/>
OrcID: 0000-0002-4114-6677 <http://orcid.org/0000-0002-4114-6677>
On Tue, Aug 8, 2017 at 3:29 PM, James M.S. Cowey ***@***.***> wrote:
which file was the one affected, so that it can be made available again?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#311 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQEdWcsQT3XF6fe5XgA48YIJjCkgbjsks5sWLcXgaJpZM4OxKix>
.
|
Validator versions: SoSOL in eXist some idp.data DCLP EpiDoc xml files have |
Found one example for form="roll?", valid for schema = 8.22 or latest https://github.com/DCLP/idp.data/blob/master/DCLP/62/61362.xml#L34 |
Some characters are prohibited from use in attribute values, but some illegal characters (e.g., "?") have been written into the "form" attribute on the
<objectDesc>
element in XML converted from LDAB (e.g., "roll?").Files like this are invalid XML and shouldn't have been committed to the repository master branch without a successful attempt to validate them.
A user at the NYC workshop undertook to input a text for a DCLP stub file from LDAB that had this problem. He typed in the text and clicked "save." The editor reported an "XML Error" indicating an invalid value for the form attribute. Attempting to navigate back or to "save the broken Leiden plus" (which wasn't broken), resulted in everybody's favorite "we're sorry something went wrong" message.
The text was updated successfully, but these errors were encountered: