Change detection and notification: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
Alter: doi. Add: bibcode, arxiv, date. Removed URL that duplicated unique identifier. Removed parameters. | You can use this bot yourself. Report bugs here. | Activated by Headbomb | via #UCB_webform
Bender the Bot (talk | contribs)
m History: HTTP → HTTPS for CNN Money, replaced: http://money.cnn.com/ → https://money.cnn.com/
Line 6:
Monitoring options vary by service or product and range from monitoring a single web page at a time to entire web sites. What is actually monitored also varies by service or product with the possibilities of monitoring text, links, documents, scripts, images or screen shots.
 
With the notable exception of Google's patent filings related to [[Google Alerts]], [[intellectual property]] activity by change detection and notification vendors is minimal.<ref>{{cite web |title=He created Google Alerts. Now he's an almond farmer |date=4 April 2016 |url=httphttps://money.cnn.com/2016/04/04/smallbusiness/naga-kataru-google-alerts/ |publisher=[[CNN]] |accessdate=9 September 2016}}</ref> No one vendor has successfully leveraged exclusive rights to change detection and notification technology through patents or other legal means.{{Citation needed|reason=Just as one can not prove a negative, one can not cite sources that do not exist|date=September 2016}} This has resulted in significant functional overlap between products and services.
 
==Architectural approaches==