For anyone who knows anything about JCR/JSR-170, there is a &quot;node type&quot; called nt:file, which represents a file type resource. <br><br>We have a &quot;asset&quot; type node at the moment, which is kind of analagous to a file (and it is stored in folders). 
<br><br>As the repository is kind of like a filesystem (ine one sense, in another its queryable like a database and presented like one) it is possible, if we choose, to expose things via WebDAV for applications like Excel to save into. This opens up a lot of possibilities.
<br><br>I wanted to get peoples thoughts on making our &quot;asset&quot; node be an &quot;nt:file&quot; type - from an API point of view most of this can and will be hidden, more of a small structural change to allow future flexability. At the moment the asset type just stored content as a string or byte[] as needed - with an nt:file it would be slightly more formally defined to be closer to a file. 
<br><br>Is it worth the effort?&nbsp; Is this something that excites or interests people: <br><br>FYI, if one was to browser the repo as a (virtual) file system, it would look something like: <br><br>/root<br>&nbsp; /packages<br>&nbsp;&nbsp;&nbsp; /package name
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /assets<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /Rule1.drl <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /Rule2.drl....<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /Something.xls<br>&nbsp;&nbsp;&nbsp; /another package ....<br>&nbsp;/categories ...<br>&nbsp;/statuses<br>&nbsp;/configuration ... <br><br><br>