Hi Council (and also CC'ing MartinH), As I was implementing it for a local project, I improved the docxtotei stylesheet by having it put <anchor/> elements in to indicate the range of the comment. As I'm sure you know in MS Word and Libreoffice and similar programs when creating a 'comment' you can highlight a bit of text associated with it. Currently this was treating them in a similar way as as we do footnotes, a note added at the point of the w:commentReference. The change to add in an <anchor/> also indicating the start/end of the highlighted range was really quite easy. See https://github.com/TEIC/Stylesheets/issues/275 for the details. I initially thought it best to do this with a milestone, forgetting that @unit was mandatory on that now, but then re-thought and decided that <anchor/> would be better. Now on to the problem! I pushed two changes: https://github.com/TEIC/Stylesheets/commit/5291228473a8036ea576b7cb6434d3b0d... where I did the actual change but using <milestone/> and https://github.com/TEIC/Stylesheets/commit/e9b92381fd6d3d23d3bba4e2142dce027... where I changed this to <anchor/>. This all works as expected for the local project here and all well and good. But when pushing to jenkins I seem to have made stylesheets-dev unstable. The parsed console output is at: http://jenkins.tei-c.org/job/Stylesheets-dev/2230/parsed_console/ where you can see that there are 6 warnings all of the type: === /var/lib/jenkins/jobs/Stylesheets-dev/workspace/Test/rxxsd.xsd:4:115: warning: schema_reference.4: Failed to read schema document 'http://www.w3.org/2004/10/xml.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. === And indeed the root element in http://www.w3.org/2004/10/xml.xsd is not xsd:schema but xs:schema ... but if that were really the problem surely we'd have noticed it before now. Any idea how my change to docxtotei could cause an XSD related warning? Or is this just coincidence of some type? I've scratched my head about this and can't figure out what caused it. Thoughts? -James -- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
This is a bit mysterious. I don't see how it could have anything to do with what you did. I know the W3C asks people not to link directly to schemas on their site; they may have detected a repeated pattern of accessing the schemas from our server and decided to block it. If that's the problem then the answer presumably is to find whatever is trying to access it and link to a local copy of it. We have a file with that name in P5/Test. Cheers, Martin On 2017-06-29 04:07 AM, James Cummings wrote:
Hi Council (and also CC'ing MartinH),
As I was implementing it for a local project, I improved the docxtotei stylesheet by having it put <anchor/> elements in to indicate the range of the comment. As I'm sure you know in MS Word and Libreoffice and similar programs when creating a 'comment' you can highlight a bit of text associated with it. Currently this was treating them in a similar way as as we do footnotes, a note added at the point of the w:commentReference. The change to add in an <anchor/> also indicating the start/end of the highlighted range was really quite easy. See https://github.com/TEIC/Stylesheets/issues/275 for the details. I initially thought it best to do this with a milestone, forgetting that @unit was mandatory on that now, but then re-thought and decided that <anchor/> would be better.
Now on to the problem!
I pushed two changes: https://github.com/TEIC/Stylesheets/commit/5291228473a8036ea576b7cb6434d3b0d... where I did the actual change but using <milestone/> and https://github.com/TEIC/Stylesheets/commit/e9b92381fd6d3d23d3bba4e2142dce027... where I changed this to <anchor/>. This all works as expected for the local project here and all well and good. But when pushing to jenkins I seem to have made stylesheets-dev unstable. The parsed console output is at: http://jenkins.tei-c.org/job/Stylesheets-dev/2230/parsed_console/ where you can see that there are 6 warnings all of the type:
=== /var/lib/jenkins/jobs/Stylesheets-dev/workspace/Test/rxxsd.xsd:4:115: warning: schema_reference.4: Failed to read schema document 'http://www.w3.org/2004/10/xml.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. ===
And indeed the root element in http://www.w3.org/2004/10/xml.xsd is not xsd:schema but xs:schema ... but if that were really the problem surely we'd have noticed it before now.
Any idea how my change to docxtotei could cause an XSD related warning? Or is this just coincidence of some type? I've scratched my head about this and can't figure out what caused it.
Thoughts?
-James
On 29/06/17 13:44, Martin Holmes wrote:
This is a bit mysterious. I don't see how it could have anything to do with what you did.
Good, glad it isn't just me.
I know the W3C asks people not to link directly to schemas on their site; they may have detected a repeated pattern of accessing the schemas from our server and decided to block it. If that's the problem then the answer presumably is to find whatever is trying to access it and link to a local copy of it. We have a file with that name in P5/Test.
Maybe we should change to use that? Or better yet there is one in stylesheets-dev at https://github.com/TEIC/Stylesheets/blob/dev/Test/xml.xsd -James
Cheers, Martin
On 2017-06-29 04:07 AM, James Cummings wrote:
Hi Council (and also CC'ing MartinH),
As I was implementing it for a local project, I improved the docxtotei stylesheet by having it put <anchor/> elements in to indicate the range of the comment. As I'm sure you know in MS Word and Libreoffice and similar programs when creating a 'comment' you can highlight a bit of text associated with it. Currently this was treating them in a similar way as as we do footnotes, a note added at the point of the w:commentReference. The change to add in an <anchor/> also indicating the start/end of the highlighted range was really quite easy. See https://github.com/TEIC/Stylesheets/issues/275 for the details. I initially thought it best to do this with a milestone, forgetting that @unit was mandatory on that now, but then re-thought and decided that <anchor/> would be better.
Now on to the problem!
I pushed two changes: https://github.com/TEIC/Stylesheets/commit/5291228473a8036ea576b7cb6434d3b0d... where I did the actual change but using <milestone/> and https://github.com/TEIC/Stylesheets/commit/e9b92381fd6d3d23d3bba4e2142dce027... where I changed this to <anchor/>. This all works as expected for the local project here and all well and good. But when pushing to jenkins I seem to have made stylesheets-dev unstable. The parsed console output is at: http://jenkins.tei-c.org/job/Stylesheets-dev/2230/parsed_console/ where you can see that there are 6 warnings all of the type:
=== /var/lib/jenkins/jobs/Stylesheets-dev/workspace/Test/rxxsd.xsd:4:115: warning: schema_reference.4: Failed to read schema document 'http://www.w3.org/2004/10/xml.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. ===
And indeed the root element in http://www.w3.org/2004/10/xml.xsd is not xsd:schema but xs:schema ... but if that were really the problem surely we'd have noticed it before now.
Any idea how my change to docxtotei could cause an XSD related warning? Or is this just coincidence of some type? I've scratched my head about this and can't figure out what caused it.
Thoughts?
-James
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
Hrmm. I modified all references to the xml.xsd to point to it locally and that seems to have solved the problem. -James On 29/06/17 14:50, James Cummings wrote:
On 29/06/17 13:44, Martin Holmes wrote:
This is a bit mysterious. I don't see how it could have anything to do with what you did.
Good, glad it isn't just me.
I know the W3C asks people not to link directly to schemas on their site; they may have detected a repeated pattern of accessing the schemas from our server and decided to block it. If that's the problem then the answer presumably is to find whatever is trying to access it and link to a local copy of it. We have a file with that name in P5/Test.
Maybe we should change to use that? Or better yet there is one in stylesheets-dev at https://github.com/TEIC/Stylesheets/blob/dev/Test/xml.xsd
-James
Cheers, Martin
On 2017-06-29 04:07 AM, James Cummings wrote:
Hi Council (and also CC'ing MartinH),
As I was implementing it for a local project, I improved the docxtotei stylesheet by having it put <anchor/> elements in to indicate the range of the comment. As I'm sure you know in MS Word and Libreoffice and similar programs when creating a 'comment' you can highlight a bit of text associated with it. Currently this was treating them in a similar way as as we do footnotes, a note added at the point of the w:commentReference. The change to add in an <anchor/> also indicating the start/end of the highlighted range was really quite easy. See https://github.com/TEIC/Stylesheets/issues/275 for the details. I initially thought it best to do this with a milestone, forgetting that @unit was mandatory on that now, but then re-thought and decided that <anchor/> would be better.
Now on to the problem!
I pushed two changes: https://github.com/TEIC/Stylesheets/commit/5291228473a8036ea576b7cb6434d3b0d... where I did the actual change but using <milestone/> and https://github.com/TEIC/Stylesheets/commit/e9b92381fd6d3d23d3bba4e2142dce027... where I changed this to <anchor/>. This all works as expected for the local project here and all well and good. But when pushing to jenkins I seem to have made stylesheets-dev unstable. The parsed console output is at: http://jenkins.tei-c.org/job/Stylesheets-dev/2230/parsed_console/ where you can see that there are 6 warnings all of the type:
=== /var/lib/jenkins/jobs/Stylesheets-dev/workspace/Test/rxxsd.xsd:4:115: warning: schema_reference.4: Failed to read schema document 'http://www.w3.org/2004/10/xml.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. ===
And indeed the root element in http://www.w3.org/2004/10/xml.xsd is not xsd:schema but xs:schema ... but if that were really the problem surely we'd have noticed it before now.
Any idea how my change to docxtotei could cause an XSD related warning? Or is this just coincidence of some type? I've scratched my head about this and can't figure out what caused it.
Thoughts?
-James
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
participants (2)
-
James Cummings -
Martin Holmes