<?xml version="1.0"?>
<oembed><version>1.0</version><provider_name>Blog of an overweight SharePoint addict</provider_name><provider_url>http://www.myfatblog.co.uk</provider_url><author_name>Cimares</author_name><author_url>http://www.myfatblog.co.uk/index.php/author/reginald/</author_url><title>Avoiding SharePoint Internal Name Pain - Blog of an overweight SharePoint addict</title><type>rich</type><width>600</width><height>338</height><html>&lt;blockquote class="wp-embedded-content" data-secret="giEMMyKe9Y"&gt;&lt;a href="http://www.myfatblog.co.uk/index.php/2014/04/avoiding-sharepoint-internal-name-pain/"&gt;Avoiding SharePoint Internal Name Pain&lt;/a&gt;&lt;/blockquote&gt;&lt;iframe sandbox="allow-scripts" security="restricted" src="http://www.myfatblog.co.uk/index.php/2014/04/avoiding-sharepoint-internal-name-pain/embed/#?secret=giEMMyKe9Y" width="600" height="338" title="&#x201C;Avoiding SharePoint Internal Name Pain&#x201D; &#x2014; Blog of an overweight SharePoint addict" data-secret="giEMMyKe9Y" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" class="wp-embedded-content"&gt;&lt;/iframe&gt;&lt;script type="text/javascript"&gt;
/* &lt;![CDATA[ */
/*! This file is auto-generated */
!function(d,l){"use strict";l.querySelector&amp;&amp;d.addEventListener&amp;&amp;"undefined"!=typeof URL&amp;&amp;(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&amp;&amp;!/[^a-zA-Z0-9]/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret="'+t.secret+'"]'),o=l.querySelectorAll('blockquote[data-secret="'+t.secret+'"]'),c=new RegExp("^https?:$","i"),i=0;i&lt;o.length;i++)o[i].style.display="none";for(i=0;i&lt;a.length;i++)s=a[i],e.source===s.contentWindow&amp;&amp;(s.removeAttribute("style"),"height"===t.message?(1e3&lt;(r=parseInt(t.value,10))?r=1e3:~~r&lt;200&amp;&amp;(r=200),s.height=r):"link"===t.message&amp;&amp;(r=new URL(s.getAttribute("src")),n=new URL(t.value),c.test(n.protocol))&amp;&amp;n.host===r.host&amp;&amp;l.activeElement===s&amp;&amp;(d.top.location.href=t.value))}},d.addEventListener("message",d.wp.receiveEmbedMessage,!1),l.addEventListener("DOMContentLoaded",function(){for(var e,t,s=l.querySelectorAll("iframe.wp-embedded-content"),r=0;r&lt;s.length;r++)(t=(e=s[r]).getAttribute("data-secret"))||(t=Math.random().toString(36).substring(2,12),e.src+="#?secret="+t,e.setAttribute("data-secret",t)),e.contentWindow.postMessage({message:"ready",secret:t},"*")},!1)))}(window,document);
/* ]]&gt; */
&lt;/script&gt;
</html><thumbnail_url>http://www.myfatblog.co.uk/wp-content/uploads/2014/04/SharePointInternalNamePain.jpg</thumbnail_url><thumbnail_width>439</thumbnail_width><thumbnail_height>115</thumbnail_height><description>For the majority of users, the inner workings of SharePoint don&#x2019;t hold much interest, but there is one aspect that you might find worthwhile to understand, especially if you are responsible for creating lists or libraries that yourself or others may want to customise later with XSLT, DisplayTemplates or even access using the Client Side &hellip; Continue reading</description></oembed>
