[ 
https://issues.apache.org/jira/browse/UIMA-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070155#comment-15070155
 ] 

Marshall Schor commented on UIMA-4563:
--------------------------------------

The requirement seems to be to use commercially reasonable efforts to insure 
..a Visitor is provided with clear and comprehensive information.. and consents 
to ... [the use of] cookies or other information...

My feeling is that the standard you suggest might fall short of this test, 
especially with regards to the consent part.  I can just imagine that the vast 
majority of users that are looking at the DUCC Demo probably don't have a 
thought about any of this. 

There's probably some solution short of  changing the demo pages themselves.  
Some ideas: copying what others (not Apache websites, but other commercial 
websites) are doing on the main page with regard to consent, and/or having the 
link from the main Apache website that goes to the DUCC DEMO go via a 
click-here-to-consent page (not part of the DUCC DEMO itself.) 

Finally, it appears that search engines find and index the ducc demo site 
directly.  Searching for Apache Ducc Demo - the 4th site is the direct link (so 
there would be no notification, if someone used this path).  So, maybe we do 
need to have the privacy link / mechanism directly on that page, too?



> Traffic monitoring using Google Analytics
> -----------------------------------------
>
>                 Key: UIMA-4563
>                 URL: https://issues.apache.org/jira/browse/UIMA-4563
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Website
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>
> Apparently, the ASF main page uses Google Analytics now as well, so I think 
> we can also do that - they have privacy statement that we can simply reuse.
> http://www.apache.org/foundation/policies/privacy.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to