-
Notifications
You must be signed in to change notification settings - Fork 3
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
Organization context added #234
base: master
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 |
---|---|---|
|
@@ -21,8 +21,14 @@ | |
"type": "Property", | ||
"value": "P1D" | ||
}, | ||
"category": { | ||
"type": "Property", | ||
"value": "Fire Department" | ||
} | ||
"isAvailableForOrganization": [ | ||
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. if it is a multi-instance attribute, you have to use 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. Understood |
||
{ | ||
"type": "Property", | ||
"value": "Agglomération Provence Verte" | ||
Comment on lines
+26
to
+27
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. I would instead see this as a relationship 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. Agreed. Will update with new Organization type |
||
}, | ||
{ | ||
"type": "Property", | ||
"value": "Gendarmerie" | ||
} | ||
] | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
{ | ||
"id": "urn:ngsi-ld:UserProfile:123456789", | ||
"type": "UserProfile", | ||
"userInfos": { | ||
"type": "JsonProperty", | ||
"json": { | ||
"familyName": "Smith", | ||
"givenName": "John", | ||
"email": "[email protected]" | ||
} | ||
}, | ||
"organization": { | ||
"type": "Property", | ||
"value": "Agglomération Provence Verte" | ||
} | ||
Comment on lines
+12
to
+15
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. if groups and groups membership are managed in KC, you can't duplicate them here (actually, Stellio already manages this info) 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. We do this for SMBT though, for "Conch" & "Autre". That way can verify who has what access on the front via Admin account. For example, Admin user is approving an Authorization which has a relationship of "givenTo" which is a UserProfile id. That way we can then download the UserProfile and check which keys they have access to. Is there another way to achieve this? |
||
} |
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.
it is a type, not an attribute? if so, it should be Organization.
and this one is better suited: https://schema.org/Organization
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.
also, is it a group or an organization?
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.
Both I suppose. They used the terminology "Organism". I can swap to Organization entities. Would be better to have them separate anyways for managing them (adding, deleting, updating)