Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] Grouper design call, Wednesday, 124June 2009, 1200EDT (1600Z)

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] Grouper design call, Wednesday, 124June 2009, 1200EDT (1600Z)

Chronological Thread 
  • From: Tom Barton <>
  • To: Chris Hyzer <>
  • Cc: "" <>
  • Subject: Re: [grouper-dev] Grouper design call, Wednesday, 124June 2009, 1200EDT (1600Z)
  • Date: Wed, 24 Jun 2009 11:03:41 -0500

The slightly tweaked version is at:


Chris Hyzer wrote:
Regarding the attribute framework, first off, if you didn't see my CAMP pres
yet, take a look (it is what is on the wiki, in powerpoint form):

Note: Tom made some tweaks, but I don't know where the camp link is... Tom
can you upload to Grouper wiki the new one on top of the old one, or forward
around the link?

I have been making objects for the attribute framework. I can make an
attribute def, give it two names, and persist. (see GSH commands below).
The multi-name thing doesn't seem like it has a good solution for a design.
It is for when two attributes (probably permissions) have generally the same
config, but different attribute instances with different names. For a lot of
attributes we wont need this, but when we do, it will be convenient. The
current design (to make queries simple, and maintain data integrity), is to
mandate that all attributes (or permissions or scopes) have a def part, and a
name part.

The def part will specify what type it is (attribute, permissions, scope),
what the attribute can be assigned to (membership, or group, etc), what type
of value it is (int, string, marker, etc), what it can be assigned to (a list
of groups, or like strings in the namespace), if it is multivalued, if it can
be multiassigned, etc. The def part itself has a name, description, and can
be public or not (if not, then only usable in the stem or substems for
assignments). I might add a constraint that says if the def and more than
one name (will help ui's). I would think that if not more than one name,
then the convention will be the def has the same name as the

gsh 4% resetRegistry()
This db user 'grouper_v1_5' and url
'jdbc:mysql://localhost:3306/grouper_v1_5' are allowed to be changed in the
Registry reset: all data deleted, and default data inserted, e.g. root stem
gsh 5% grouperSession = GrouperSession.startRootSession();
gsh 6% root = StemFinder.findRootStem(grouperSession);
stem: name='' displayName='' uuid='76f9364d-e24f-4d01-91ae-1189abd4c091' gsh 7% top = root.addChildStem("top", "top display name");
stem: name='top' displayName='top display name' uuid='a1efba70-c191-439d-9602-49e8b76848c5' gsh 8% attributeDef ="test", AttributeDefType.attr);
gsh 9% org1 =, "org1",
"Organization 1");
gsh 10% org2 =, "org2",
"Organization 2");
gsh 11%


-----Original Message-----
From: Tom Barton
Sent: Tuesday, June 23, 2009 11:20 PM

Subject: [grouper-dev] Grouper design call, Wednesday, 124June 2009,
1200EDT (1600Z)

Wednesday, 24 June 2009, 1200EDT/1700BST/1800CEST (1600Z), 60 minutes

+1-866-411-0013 (toll free US/Canada Only)
+1-734-615-7474 (Non-US/CA, non-toll free, no dialout) (SIP)
PIN: 0109331 (followed by "#")


1. administrivia
. <>
. approve minutes
. review AIs
. next meeting
. agenda bash

2. report from camp and advanced camp, upcoming & potential

3. Jim Fox's ldap source adapter

4. is <> really fixed?

5. highly available grouper-ws

6. attribute framework

7. AI review


Archive powered by MHonArc 2.6.16.

Top of Page