[ 
https://jira.duraspace.org/browse/DS-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25276#comment-25276
 ] 

Ivan Masár commented on DS-1199:
--------------------------------

I spent some non-trivial time trying to figure this out and I can say this 
won't be a one-liner fix in DSpace. I doubt this is a problem with DSpace at 
all because SWORD server v2 uses the org.swordapp server to generate the 
servicedocument, which in turn uses org.apache.abdera to construct the ATOM 
document. So we may need to figure out a fix in org.swordapp and persuade them 
to adopt it or we'll have to fork it in Maven (like we already do e.g. with our 
customized Cocoon).

I'm still not sure that the XML declaration is a necessary part servicedocument 
(or of an XML document, for that matter), so if you can confirm this, please 
provide a link to some specification.
UTF-8 is properly declared in HTTP headers of our servicedocument response, so 
I tend to think any client which would ignore it is broken.

Side-notes:
1. Our SWORD implementation(s) pretty much assume UTF-8 will be used and this 
is hardcoded.
2. What the XML declaration needs to say is UTF-8, not ISO-8859-1 (see 1. 
above). This shouldn't be a problem for Kathi because ISO-8859-1 is a subset of 
UTF-8.
3. SWORD server v1 sends the XML declaration correctly (and this is rather 
easily editable in the DSpace source).
                
> SWORD V2 Service Document does not have XML processing tag with encoding
> ------------------------------------------------------------------------
>
>                 Key: DS-1199
>                 URL: https://jira.duraspace.org/browse/DS-1199
>             Project: DSpace
>          Issue Type: Bug
>          Components: SWORD
>    Affects Versions: 1.8.2
>         Environment: All
>            Reporter: Kathi Fletcher
>            Priority: Major
>
> Tested the SWORD V2 service document 
> (http://demo.dspace.org/swordv2/servicedocument) on the demo server at 
> http://demo.dspace.org. The service document needs <?xml version="1.0" 
> encoding="ISO-8859-1"?> to be valid XML. Otherwise it breaks on the accented 
> chars in the body.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to