Colloque – 9/11/18 – Big Data : risques et opportunités ?
Updated on 12.11.2018
Print
Share
La croissance phénoménale des capacités de traitement de l’information a permis le développement d’outils qui offrent, par la combinaison et le croisement de larges volumes de données, de nouvelles perspectives industrielles et commerciales.
Le Big Data permet de mieux cibler les attentes des clients dans le cadre des activités de recherche et développement, de réduire certains coûts par une affectation plus efficace des ressources, d’améliorer la gestion des stocks, de faciliter la prise de décision thérapeutique… Les applications et opportunités sont multiples et suscitent l’enthousiasme des entreprises.
Pour le juriste, le Big Data est en outre synonyme de nouvelles questions sur la protection des investissements liés à la mise au point de ces outils, sur les limites d’utilisation des données, sur les responsabilités en cas de défaillance de ces nouveaux instruments…
À l’occasion du vingtième anniversaire de la revue RDTI, le sujet du Big Data était parfait, afin de faire le lien entre l’analyse juridique des innovations technologiques, qui constitue l’ADN de la revue, et la protection des données sous tous ses angles (vie privée, propriété intellectuelle, sécurité informatique, contrats informatiques, protection du consommateur), qui depuis sa fondation en 1979 est l’un des sujets de prédilection du Centre de Recherche Informatique, Droit et Société (CRIDS), dont émane la RDTI.
Venez écoutez les interventions d’Alexandre Cruquenaire et de Jean-François Henrotte !
Print
Share
Share this content:
Colloque – 9/11/18 – Big Data : risques et opportunités ?
Le présent site Internet utilise des cookies. Certains cookies sont nécessaires au bon fonctionnement du site Internet et ne peuvent être refusés si vous souhaitez visiter ce site. D'autres This website uses cookies. Some cookies are necessary for the proper functioning of this website and cannot be refused if you wish to visit this website. Other cookies are used for playing videos and analysis: Cookies Policy. You can refuse them if you wish. RefuseSettingsACCEPT ALL
The necessary cookies are essential for the proper functioning of the website. This category only includes cookies that provide basic functionality, website security, language management, document downloads and online consultation.
Cookie
Type
Duration
Description
_wpas_session
session
30 minutes
This cookie is used by Awesome Support (online consultation / SOS) to keep track of website state between page loads and to store temporary information essential to the website's ability to work properly.
More info: https://getawesomesupport.com/documentation/awesome-support/cookies/
cookielawinfo-checkbox-necessary
persistent
11 months
This cookie is set by GDPR Cookie Consent plugin. The purpose of this cookie is to check whether or not the user has given the consent to the usage of cookies under the category 'Necessary'.
cookielawinfo-checkbox-non-necessary
persistent
11 months
This cookie is set by GDPR Cookie Consent plugin. The purpose of this cookie is to check whether or not the user has given their consent to the usage of cookies under the category 'Non-Necessary'.
PHPSESSID
session
This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookie and is deleted when all the browser windows are closed.
pll_language
persistent
1 year
This cookie is set by Polylang and is used to remember the language selected by the user when he comes back to visit again the website. This cookie is also used to get the language information when not available in another way. Examples are ajax requests or the login page.
More info: https://polylang.pro/doc/is-polylang-compatible-with-the-eu-cookie-law/
viewed_cookie_policy
persistent
1 hour
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
This cookie is set by Wordpress and is used to store the authentication details on login. The authentication details include the username and double hashed copy of the password. However, this usage of the cookie is limited to the admin console area, the backend dashboard of the website.
Here [hash] represents the value that is obtained by applying a specific mathematical formula applied to the username and password. It is to ensure that the input values are safe, and no one can access these data using the cookies as it is difficult to ‘unhash’ the hashed data.
More info : https://wordpress.org/support/article/cookies/
wordpress_logged_in_[hash]
persistent
14 days
This cookie is set by Wordpress and is used to indicate when you are logged in, and who you are. This cookie is maintained on the front-end of the website as well when logged in.
More info: https://wordpress.org/support/article/cookies/
wordpress_test_cookie
session
This cookie is set by Wordpress and is used to store the authentication details on login. The authentication details include the username and double hashed copy of the password. However, this usage of the cookie is limited to the admin console area, the backend dashboard of the website.
Here [hash] represents the value that is obtained by applying a specific mathematical formula applied to the username and password. It is to ensure that the input values are safe, and no one can access these data using the cookies as it is difficult to ‘unhash’ the hashed data.
More info: https://wordpress.org/support/article/cookies/
This cookie is set by Wordpress and is used to customize the view of your admin interface and the front-end of the website. The value represented by [UID] is the individual user ID of the user as given to them in the users' database table.
More info: https://wordpress.org/support/article/cookies/
Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
More info: https://policies.google.com/technologies/types?hl=en