api stands for something…what about copyright?
this weeks lecture was very interesting for me due to the nature in which online networking is managing to reach boundless avenues. the thought on the use of API’s is something that us (media producers) are going to have to understand and take full advantage of…the idea of efficiency with less effort is very appealing but does the registration of material (i.e. copyright) enter the frame at all? it was something that popped into my head as i went back through the lecture notes and couldn’t see anything in there so i decided to go looking myself.
so does providing an open api whereby individuals can piggyback content such as photos, information, videos etc flirt with the ideals of copyright? the answer seems to lie with the end user - it’s provided as a tool, whether you use it correctly is totally up to you. but does this suffice? this is the questionable part for media producers – it may enhance workability but what if your productions are intentionally or unintentionally used and distributed?
one such case i found involved flickr’s open api and a user involving his photographs which also lead me to look at the U.S Induce Act. really, do open api’s induce infringement and should providers be held accountable for breach? read what i’ve read:
