<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Best Practice;  Short vs Long Namespaces in code in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/best-practice-short-vs-long-namespaces-in-code/m-p/263585#M216715</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello all,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When referencing entities stored in Alfresco, particularly when using the Javascript APIs (in Java we can often use the rich QName object to model qualified names), we frequently have a choice about how we refer to the qualified name of an aspect, property, path element etc - we can use the full namespace, say, &lt;/SPAN&gt;&lt;STRONG&gt;{&lt;A href="http://surevine.com/alfresco/aclient/foobar}myentity" rel="nofollow noopener noreferrer"&gt;http://surevine.com/alfresco/aclient/foobar}myentity&lt;/A&gt;&lt;/STRONG&gt;&lt;SPAN&gt; or a shortened version, perhaps &lt;/SPAN&gt;&lt;STRONG&gt;sv:myentity&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My question is fairly simple: Is the use of one form generally preferred over the other?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've just updated our internal coding standards to suggest that developers use the shorter form rather than the longer one to improve readability, but I'd be interested to know what others thoughts were.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks in advance,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Simon&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 May 2011 13:57:49 GMT</pubDate>
    <dc:creator>simon_white</dc:creator>
    <dc:date>2011-05-10T13:57:49Z</dc:date>
    <item>
      <title>Best Practice;  Short vs Long Namespaces in code</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/best-practice-short-vs-long-namespaces-in-code/m-p/263585#M216715</link>
      <description>Hello all,When referencing entities stored in Alfresco, particularly when using the Javascript APIs (in Java we can often use the rich QName object to model qualified names), we frequently have a choice about how we refer to the qualified name of an aspect, property, path element etc - we can use th</description>
      <pubDate>Tue, 10 May 2011 13:57:49 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/best-practice-short-vs-long-namespaces-in-code/m-p/263585#M216715</guid>
      <dc:creator>simon_white</dc:creator>
      <dc:date>2011-05-10T13:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice;  Short vs Long Namespaces in code</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/best-practice-short-vs-long-namespaces-in-code/m-p/263586#M216716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;One important difference is that the "short name" is your prefix, whereas the full URI is global and fixed forever.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; The picture does get a little muddy where APIs don't specify their own namespace resolvers or like the java script API are perhaps over simplified.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The short name prefix is for your convenience, I suggest you use that one.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2011 14:16:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/best-practice-short-vs-long-namespaces-in-code/m-p/263586#M216716</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2011-05-10T14:16:07Z</dc:date>
    </item>
  </channel>
</rss>

