Recent changes to 393: availabilityhttp://sourceforge.net/p/tei/feature-requests/393/2014-07-31T21:01:27Z#393 availability2014-07-31T21:01:27Z2014-07-31T21:01:27ZLou Burnardhttp://sourceforge.net/u/louburnard/http://sourceforge.net5b6d78881198f5f8e1f0c86ebfd844078d22ab25<div class="markdown_content"><ul>
<li><strong>status</strong>: open --&gt; closed</li>
</ul></div>#393 availability2014-06-06T10:23:46Z2014-06-06T10:23:46ZLou Burnardhttp://sourceforge.net/u/louburnard/http://sourceforge.net1ae057ef4e9a4a894d1c821baaa05d0e9de37d2d<div class="markdown_content"><p>Made &lt;msDesc&gt; declaring as of rev 12909. Another option would be to add &lt;availability&gt; as a child of &lt;recordHist&gt;</p></div>#393 availability2014-05-19T20:39:18Z2014-05-19T20:39:18ZLou Burnardhttp://sourceforge.net/u/louburnard/http://sourceforge.net008e3ddf4c09c566829fd97f754b9ecfa4f0862a<div class="markdown_content"><p>The use case Thorsten describes above (different availabilitys for different msdescs in a single document) could be addressed by using @decls. &lt;availability&gt; is already a member of att.declarable, but &lt;msDesc&gt; is not currently a member of att.declaring. I suggest that adding it to that class would be an easy way of resolving this issue.</p></div>#393 availability2013-11-13T16:03:37Z2013-11-13T16:03:37ZJames Cummingshttp://sourceforge.net/u/jcummings/http://sourceforge.net868aa3ecb2c80aff450d8afdb4938c2ad28ae068<div class="markdown_content"><ul>
<li><strong>assigned_to</strong>: James Cummings --&gt; Lou Burnard</li>
<li><strong>Group</strong>: RED --&gt; AMBER</li>
<li><strong>Priority</strong>: 5 --&gt; 1(low)</li>
</ul></div>availability2012-10-08T11:14:48Z2012-10-08T11:14:48ZTorsten Schassanhttp://sourceforge.net/u/schassan/http://sourceforge.net47b07c3df6580929f014b617d8b03c385251dad4<div class="markdown_content"><p>Right now if used within msDesc, availability has to be used as child of adminInfo, thus I tend to understand that it describes the availability of the manuscript/the text bearing object. If it should describe the availability of the description it might have to be placed (and thus to be allowed) within recordHist.</p>
<p>If we want to allow to distinguish between the two cases it might be necessary to add to the definition this object-related aspect, e.g. "supplies information about the availability of a text or of an object"</p></div>availability2012-10-08T11:14:48Z2012-10-08T11:14:48ZTorsten Schassanhttp://sourceforge.net/u/schassan/http://sourceforge.net7ef7874e686b677f73f1bdd9c2ed73f15319bd72<div class="markdown_content"><p>Ticket 393 has been modified: availability<br />
Edited By: James Cummings (jcummings)<br />
_priority updated: u'5' =&gt; u'1(low)'<br />
_milestone updated: u'RED' =&gt; u'AMBER'<br />
Owner updated: u'jcummings' =&gt; u'louburnard'</p></div>availability2012-10-08T11:14:48Z2012-10-08T11:14:48ZTorsten Schassanhttp://sourceforge.net/u/schassan/http://sourceforge.net1647d6dedc84148050b05468320954f72ad10ba2<div class="markdown_content"><p>Ticket 393 has been modified: availability<br />
Edited By: Lou Burnard (louburnard)<br />
Status updated: u'open' =&gt; u'closed'</p></div>