< , > , & , " and ' all have special values ββin XML (for example," start of entity "or" separator of attribute values ββ").
So that these characters are displayed as data (instead of their special meaning), they can be represented by entities ( < for < , etc.).
Sometimes these special values ββare context sensitive (for example, "does not mean" attribute separator "outside the tag), and there are places where they may appear as raw as data. Instead of worrying about these exceptions, the easiest way is to always always represent them as objects, if you want to avoid their special significance, then the only information received is the clear sections of CDATA, where the special meaning is not fulfilled (and & does not start the entity).
if it needs to be replaced by
It should not be represented in any of them. Objects must be completed using a colon.
How you should represent this depends on which bit of your sample data is and which is the markup. You did not say, for example, if <hello> should be data or a start tag for a welcome element.
Quentin
source share