-
Notifications
You must be signed in to change notification settings - Fork 36
Proposta di utilizzo di info.x-gdpr per contatti dei responsabili ed … #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 14-metadata-muoversi-lombardia
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,6 +26,19 @@ info: | |
``` | ||
'https://muoversi2015.e015.servizirl.it/planner/rest/soluzioniJson/e015Search?param=milano&maxResult=1' | ||
``` | ||
x-gdpr: | ||
- role: data-controller # contatti della/delle persona titolare del trattamento dei dati | ||
name: nome e cognome | ||
email: email@example.com | ||
- role: data-controller | ||
name: nome2 e cognome2 | ||
email: email2@example.com | ||
- role: data-processor # contatti della/delle persona responsabile del trattamento dei dati | ||
name: nome3 e cognome3 | ||
email: email3@example.com | ||
- role: data-processor | ||
name: nome4 e cognome4 | ||
email: email4@example.com | ||
contact: | ||
name: Technical Management Board di E015 | ||
url: http://www.e015.regione.lombardia.it/PE015/esplora-i-contenuti/i-servizi/muoversi-lombardia | ||
|
@@ -609,15 +622,21 @@ components: | |
run: 'MILANO, Greco Pirelli, Stazione' | ||
transport: '3' | ||
TimetableFermata: | ||
x-gdpr: | ||
class: public | ||
properties: | ||
id: | ||
type: string | ||
stop: | ||
type: string | ||
x: | ||
$ref: '#/components/schemas/Longitudine' | ||
x-gdpr: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Messo così effettivamente viene ignorato dal motore ufficiale, per renderlo corretto potremmo ragionare anche sul senso che avrebbe usare un allOf:
Però credo sia più importante quello che dici nel secondo punto. E' molto meglio definire questo attributo gdpr nello schema "puntato" da $ref. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. afaik gli elementi della lista There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Si anche io ci ho ragionato un po' e sono d'accordo. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yea! |
||
class: public | ||
y: | ||
$ref: '#/components/schemas/Latitudine' | ||
x-gdpr: | ||
class: public | ||
example: | ||
id: '1' | ||
stop: 'Milano, Affori M3, Stazione Ferroviaria' | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stefkohub mi pare sensato.