wpgsh / cloud4water

Apache License 2.0
0 stars 0 forks source link

WEMP data model review #15

Closed asd1245dss closed 7 years ago

asd1245dss commented 8 years ago

I've read the diagrams muti-times,but still unclear about some points.

  1. User is one-to-many with Object through U-O, G-O,Organization.So how to deal with the situation that the same objects occured at all these three relations(Overrifing,Union and so on).After reading the section API Methods,I found that there's only one api can be used for fetching permissions at the same time.Is this means that the situation will never occure?
  2. The definition of the field transitive in the U-O and G-O
  3. What's the specific function of the Permissions .In my view,one can fetch the permissions through the other relation.
  4. ~~qq 20160909085220 The explains above seems puzzled us.If the A,B,C,D is the same things?~~
  5. The major difference between transitive-permission and non-transitive-permission is that the former can be available for their children but the latter can only applyed for themself, If I understand correctly?
  6. ~~image image Are there any differences for the TokenServlet and AuthorizeServlet in the WEMP and Authn App?~~

asd1245dss commented 8 years ago

@alexlukichev image According to the data model, if the project can only be related to the town or it can build relationship with any geographic object?

alexlukichev commented 8 years ago

In this data model the project is directly related to a town entity. You can however reconsider the hierarchy. Although I wouldn't recommend having parent links to more than 1 entity class from a project.