<?xml version="1.0"?>
<article xmlns="http://pkp.sfu.ca" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" locale="en_US" date_submitted="2016-10-19" stage="production" date_published="2016-10-19" section_ref="ART" seq="2" access_status="0" xsi:schemaLocation="http://pkp.sfu.ca native.xsd"><id type="internal" advice="ignore">36</id><title locale="en_US">CAPTURE OF SO2 BY LIMESTONE IN A 71 MWe PRESSURIZED FLUIDIZED BED BOILER</title><abstract locale="en_US"><p>A 71 MW<sub>e</sub> pressurized fluidized bed coal combustor was operated. A wide variety of coals were burnt under fly ash recycle conditions. Limestone was fed to the combustor as bed material as well as sorbent. The emission of SO<sub>2</sub> and limestone attrition rate were measured. A simple mathematical model of SO<sub>2</sub> capture by limestone with intermittent solid attrition was applied to the analysis of the present experimental results. Except for high sulfur fuel, the results of the present model agreed with the experimental results.</p></abstract><type locale="en_US">Text</typ
The XML elements are not showing because the browser is trying to display the XML as HTML. To see the raw XML you’ll need to save the page or View Source.
Regards,
Alec Smecher
Public Knowledge Project Team
This is source from page view source of that unsuccessful export of issue:
Validation errors:
unterminated entity reference Chemical Engineering Niigata University
unterminated entity reference Chemical Engineering Niigata University
unterminated entity reference Chemical Engineering Niigata University
Internal error: xmlSchemaVDocWalk, there is at least one entity reference in the node-tree currently being validated. Processing of entities with this XML Schema processor is not supported (yet). Please substitute entities before validation..
Element '{http://pkp.sfu.ca}issue': Missing child element(s). Expected is ( {http://pkp.sfu.ca}articles ).
In issue XML, as you can see above, there seem to be no articles. I’ll try to imagine (figure out) why is this happening… At the moment I have no idea… :-\
@vvucic, I believe it is because of some special characters (I think in this case “&”) that are not escaped properly. I just wonder how does it work in article export