[tei-council] Permissions for use of images. Was: Drafts of new Guidelines sections

[Martin Holmes]

I'm guessing from the silence on this that we don't actually have a 
place to store correspondence supporting rights/permissions to use other 
people's screenshots, page-images etc. in the Guidelines.

I think it would be a sensible idea to do this. The options would be:

  - Store this correspondence in a central location on the TEI Website 
(through the CMS)

  - Store it in a central location in SVN

  - Store it by convention alongside the image itself, in e.g. 
P5/Source/Guidelines/en/Images, in a zip file with the same filename as 
the image but a zip extension.

Thorts?

Cheers,
Martin

On 13-10-17 05:48 AM, Martin Holmes wrote:
> Hi Kevin,
>
> I wasn't asking about the place to store the images; I was asking where
> to store the emails or letters giving permission to use the images.
>
> I have used Oxygen's change-tracking feature, but I think that's more
> appropriate for collaborative editing, rather than presenting a document
> for comments.
>
> Cheers,
> Martin
>
> On 13-10-16 11:10 PM, Kevin Hawkins wrote:
>> On 10/16/13 5:21 PM, Martin Holmes wrote:
>>> Hi all,
>>>
>>> I'm currently working on a draft of new material for the Front Matter
>>> section VI, "Languages and Character Sets", which involves adding two
>>> new sections, adding to the title, and including some new items in the
>>> bibliography. I want to bring the first draft of these changes to the
>>> Council meeting in November.
>>>
>>> I'm wondering what the best way to do this would be. I could introduce
>>> all the changes directly into the Guidelines code, and let everyone have
>>> at them in-place, but that's probably not appropriate because Council
>>> will likely want substantial edits so they may not be ready for the
>>> release that follows rapidly on the November Council meeting. At the
>>> same time, I do want to present them in the context of the existing
>>> Guidelines so the appearance and integration is clear, for me and for
>>> everyone else. The alternative would be to work on a local copy which I
>>> can build into a Guidelines version which has the changes, and then
>>> merge them back into trunk by manual diffing once everyone is happy.
>>> Which would you recommend? Lou, when you did the very substantial
>>> changes for the genetic editing module, how did you go about it?
>>>
>>> I realize this is exactly the sort of situation git is designed for
>>> (fork and merge later). I generally argue against git because it's too
>>> complicated for our needs, so I appreciate the irony here, but this is
>>> the first time since I've been on Council I've found myself wanting this
>>> functionality; it doesn't happen often.
>>
>> In the past, I've copied and pasted from the HTML version of the
>> Guidelines into Microsoft Word, turned on change tracking, edited, and
>> saved the result as a PDF for sharing.  Unfortunately, when you do this,
>> all of the changes need to be redone in the ODD file.
>>
>> <oXygen/> has a feature for tracking changes using PIs that presents
>> functionality similar to what Word has:
>>
>> http://www.oxygenxml.com/xml_editor/change_tracking_and_review.html
>>
>> So reviewing the changes essentially requires that you have <oXygen/>.
>>
>>> On a related issue: I've obtained one set of permissions for the use of
>>> a document image, I have another request under consideration, and more
>>> will probably come along by the time I've finished. We've typically
>>> acknowledged this sort of thing with an inline note in the Guidelines
>>> text, like this from PH:
>>>
>>> <note place="bottom">The image is taken from the collection at <ptr
>>> target="http://ancilla.unice.fr/Illustr.html"/>, and was digitized from
>>> a copy in the Bibliothèque Municipale de Lyon, by whose kind permission
>>> it is included here.</note>
>>>
>>> but presumably the original letters or emails are stored somewhere to
>>> back up the acknowledgements. Where would that be?
>>
>> I think we do regularly store local copies of images in case the
>> external links break.  If I do this:
>>
>> cd P5/Source/Guidelines/en/
>> grep 'url=".............' *.xml | more
>>
>> I see we have paths to images in one of the following places:
>>
>> .
>> Images/
>> figs/
>>
>> However, I'm confused because the images themselves all seem to be in
>> Images/ .
>>
>> --Kevin
>>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)