[TYPO3-ect] tx_party: Let's get started!

[Daniel Brüßler]

Hello,

the diagram looks very good now!

Yes it's very good to stick to the standard. So it's compatible for
exchanging data.

The standard will get better over the time, so there's no problem, when
some things are not possible in the moment. Only important is to store
what _version of the standard_ the data is using.


++------

Is it possible to store usernames, usergroups and to create
sub-usergroups? If not it would be no problem, so the authentication can
be indipendent. The authentication-datatable can have a foreign-key to
the PartyFramework-data so the name wouldn't be double.

With indipendent auth-data the type-of-authentication can be different
so even role-based login "RBAC" could be possible.

kind regards
Daniel Brüßler




David Toshack schrieb:
> David Bruehlmeier wrote:
>>> I see a document can belong to a group, would be also good if it belongs
>>> to a role, too. (Documentation-Writer, Reviewer, System-Administrator,
>>> Simpsons-Fan)
>> The OASIS spec doesn't feature a role:
>> http://www.bruehlmeier.com/tx_party/oasis/xPIL/xPIL.html#simpleType_DocumentElementEnumeration_Link037F4350
>>
>>
>> The core-extension tx_party should stick to the specs as much as possible.
> 
> I agree with sticking to standards. However, The Party Framework is such
> a good model for people and organizations it would be a shame not to be
> able to replace front and backend users with parties.
> 
> In order to do this, we need to combine some sort of RBAC with the Party
> Framework. I created a page[1] on the TYPO3 wiki some time ago regarding
> TYPO3 Enhanced Rights Management through Role Based Access Control.
> Would this be something we could combine with the Party Framework?
> 
> 
> Cheers,
> David
> 
> [1] http://wiki.typo3.org/index.php/Enhanced_Rights_Management