Confirm
891
edits
Changes
→Functional Specification
'''[[|]]5. Output'''<br>Add on<br>The attribution will be created based on the type of content is being pulled. If the content is an image, attribution information is printed below the image with the same width as the image and using left alignment. In this instance, the attribution information should also be embedded in the image metadata. Text should be formatted as a quote with 3px spacing on all sides with attribution information on the new line (e.g.<br/>), 2px smaller and in italics. Text output can use a standard web font at 12 pixels, making the attribution information 10px. Videos will be attributed with the attribution information followed by a <br/> tag and subsequently, the link information. When a video is downloaded, attribution information will be embedded in the file.<br>Plugin<br>The attribution will be created based on the type of content is being pulled. If the content is an image, attribution information is printed below the image with the same width as the image and using left alignment. In this instance, the image will also link back to the original source. Text should be formatted as a quote with 3px spacing on all sides with attribution information on the new line (e.g.<br/>), 2px smaller and in italics. Text output can use a standard web font at 12 pixels, making the attribution information 10px. Videos will be linked or embedded with the attribution information on the next line. <br>
'''[[|]]6. Existing Technologies'''<br>Citation Machine: http://citationmachine.net/<br>Xpert: http://www.nottingham.ac.uk/xpert/attribution/<br>CC Metadata Humanizer: http://code.creativecommons.org/~john/ <br>OCW cite/attribute: http://ocw.korea.edu/ocw<br>Wikimedia Commons: http://commons.wikimedia.org<br>Technical Considerations<br>This functional spec assumes that RDFa and metadata will be accessible. The persons responsible for the implementation of this functional spec will need to determine which interfaces allow the usage of stored RDFa or metadata and how the API must be implemented to pull the data. For purposes of the functional specification, the authors have assumed all interfaces have open metadata.
<br> '''[[|]]7. Technical Considerations'''<br>
This functional spec assumes that RDFa and metadata will be accessible. The persons responsible for the implementation of this functional spec will need to determine which interfaces allow the usage of stored RDFa or metadata and how the API must be implemented to pull the data. For purposes of the functional specification, the authors have assumed all interfaces have open metadata.
7.1 Security<br>This section needs to detail whether or not the attribution can be deleted. If the add on or plugin pulls the metadata and prints it with text or HTML, the user has the ability to delete the data. Does it matter?
