09.08.2015 Views

Broadband Customer Reporting – XML Release 2 Issue 16.8a

BBCR XML Interface Guide Eff 05/10/09 - BT Wholesale

BBCR XML Interface Guide Eff 05/10/09 - BT Wholesale

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

• Fault Reason• Fault Clear• Fault Detail<strong>XML</strong> <strong>–</strong> Escape CharactersAccording to the W3 consortium 4 , by default, certain characters need to be escaped. Specifically these are “ < ” (less than), “ > ”(greater than),” ‘ “ (apostrophe), “ & “ (ampersand) and “ “ “ (double-quote character a.k.a. ‘speech marks’).The mappings for replacement characters are listed below:Character …Replace With< &lt;> &gt;“ &quot;‘ &apos;&&amp;(newline) &#x0A;Table 1: Escape character mappings<strong>XML</strong> <strong>–</strong> CharsetIn accordance with W3C standards, all <strong>XML</strong> documents will be output using the UTF-8 charset (see http://www.utf-8.com/).MSO Fault <strong>XML</strong>The purpose of the MSO Fault <strong>XML</strong> report is to allow the user to perform a “one-shot” check to see if a given CBUK, Telephonenumber or Service Id is currently impacted by a known MSO. The data returned is the same as the data in the current “MSO FaultSearch” report available on the web.The report itself can be instigated using either the telephone number (DN), the network ID (CBUK no.) or the service id. The checkis done in real time, to see if the reporting service is impacted by a known MSO.4See for example http://www.w3.org/TR/1998/REC-xml-19980210#wf-entities. Also: http://tech.irt.org/articles/js212/.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!