<?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 Re: Best practices: Content Model namespace prefix in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/best-practices-content-model-namespace-prefix/m-p/233178#M186308</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks Nancy,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have already bought jpotts's book.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My concern is with searching the contents if I use different namespaces for model files people, project, commercial etc.. instead of 1.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Also in my requirement some document types are common in Project,People and Commercial. So I thought to put those types in super type &lt;/SPAN&gt;&lt;STRONG&gt;org&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I will implement my model in multiple files each with its own namespace and prefix. Also I have created separate model file to define all constraints.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Nikesh&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Aug 2009 09:19:53 GMT</pubDate>
    <dc:creator>nikes</dc:creator>
    <dc:date>2009-08-20T09:19:53Z</dc:date>
    <item>
      <title>Best practices: Content Model namespace prefix</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/best-practices-content-model-namespace-prefix/m-p/233176#M186306</link>
      <description>Hi guys I need suggestion to design content model containing various departments documents.I am developing a solution for our organization which stores all types of documents from various departments say….Presales&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Various documents like Proposal, Presentations, Product Knowledge base etc…….P</description>
      <pubDate>Wed, 19 Aug 2009 11:49:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/best-practices-content-model-namespace-prefix/m-p/233176#M186306</guid>
      <dc:creator>nikes</dc:creator>
      <dc:date>2009-08-19T11:49:25Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices: Content Model namespace prefix</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/best-practices-content-model-namespace-prefix/m-p/233177#M186307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello Nikesh,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jeff Potts has a good article about content models on his site, you can find it here &lt;/SPAN&gt;&lt;A href="http://ecmarchitect.com/categories/content-management/alfresco-developer-series" rel="nofollow noopener noreferrer"&gt;http://ecmarchitect.com/categories/content-management/alfresco-developer-series&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You should read the entire article but here is a brief excerpt:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Don't&amp;nbsp;be&amp;nbsp;afraid&amp;nbsp;to&amp;nbsp;have&amp;nbsp;more&amp;nbsp;than&amp;nbsp;one&amp;nbsp;content&amp;nbsp;model&amp;nbsp;XML&amp;nbsp;file.&amp;nbsp;We&amp;nbsp;haven't&amp;nbsp;talked&amp;nbsp;about&amp;nbsp;exactly&amp;nbsp; &lt;BR /&gt;how&amp;nbsp;content&amp;nbsp;models&amp;nbsp;are&amp;nbsp;defined&amp;nbsp;yet,&amp;nbsp;but&amp;nbsp;when&amp;nbsp;it&amp;nbsp;is&amp;nbsp;time&amp;nbsp;to&amp;nbsp;implement&amp;nbsp;your&amp;nbsp;model,&amp;nbsp;keep&amp;nbsp;this&amp;nbsp;in&amp;nbsp; &lt;BR /&gt;mind:&amp;nbsp;It&amp;nbsp;might&amp;nbsp;make&amp;nbsp;sense&amp;nbsp;to&amp;nbsp;segment&amp;nbsp;your&amp;nbsp;models&amp;nbsp;into&amp;nbsp;multiple&amp;nbsp;namespaces&amp;nbsp;and&amp;nbsp;multiple&amp;nbsp; &lt;BR /&gt;XML&amp;nbsp;files.&amp;nbsp;Names&amp;nbsp;should&amp;nbsp;be&amp;nbsp;descriptive.&amp;nbsp;Don't&amp;nbsp;deploy&amp;nbsp;a&amp;nbsp;model&amp;nbsp;file&amp;nbsp;called&amp;nbsp;“customModel.xml”&amp;nbsp; &lt;BR /&gt;or&amp;nbsp;“myModel.xml”.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;Nancy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Aug 2009 18:00:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/best-practices-content-model-namespace-prefix/m-p/233177#M186307</guid>
      <dc:creator>nancyg</dc:creator>
      <dc:date>2009-08-19T18:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices: Content Model namespace prefix</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/best-practices-content-model-namespace-prefix/m-p/233178#M186308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks Nancy,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have already bought jpotts's book.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My concern is with searching the contents if I use different namespaces for model files people, project, commercial etc.. instead of 1.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Also in my requirement some document types are common in Project,People and Commercial. So I thought to put those types in super type &lt;/SPAN&gt;&lt;STRONG&gt;org&lt;/STRONG&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I will implement my model in multiple files each with its own namespace and prefix. Also I have created separate model file to define all constraints.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Nikesh&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Aug 2009 09:19:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/best-practices-content-model-namespace-prefix/m-p/233178#M186308</guid>
      <dc:creator>nikes</dc:creator>
      <dc:date>2009-08-20T09:19:53Z</dc:date>
    </item>
  </channel>
</rss>

