Automated Content Access Protocol: Difference between revisions

Revision as of 21:41, 22 March 2018

Revision as of 18:09, 16 March 2019

Line 1:

{{Distinguish|text= [[Application Configuration Access Protocol]] (ACAP)}}

'''Automated Content Access Protocol''' ("ACAP") was proposed in 2006 as a method of providing machine-readable permissions information for content, in the hope that it would have allowed automated processes (such as search-engine web crawling) to be compliant with publishers' policies without the need for human interpretation of legal terms. ACAP was developed by organisations that claimed to represent sections of the publishing industry ([[World Association of Newspapers]], [[European Publishers Council]], [[International Publishers Association]]).<ref>[http://www.the-acap.org/FAQs.php#faq15 ACAP FAQ: Where is the driving force behind ACAP?]</ref> It was intended to provide support for more sophisticated online publishing business models, but was criticised for being biased towards the fears of publishers who see search and aggregation as a threat<ref name="douglas">{{cite web |url=http://blogs.telegraph.co.uk/technology/iandouglas/3624601/Acap_a_shot_in_the_foot_for_publishing/ |title=Acap: a shot in the foot for publishing |first=Ian |last=Douglas |date=3 December 2007 |work=[[The Daily Telegraph]] |publisher= |accessdate=3 May 2012}}</ref> rather than as a source of traffic and new readers.