Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] grouper attribute framework

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] grouper attribute framework

Chronological Thread 
  • From: Tom Zeller <>
  • To: Chris Hyzer <>
  • Cc: "" <>
  • Subject: Re: [grouper-dev] grouper attribute framework
  • Date: Thu, 11 Jun 2009 08:41:22 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws;; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=Cs/Zdb/anYmTafsD1AV9O0jHgSF+cqbKOZyCsemQezVE/K+VqkF9QfDXFjMJNWCfNZ P+Z5OpmADIUu2VsG7JJpqrgnMUbSc38fXB7VQ5H+5Y+T9pjIAnoWENlRi3p0ti/yFpVW gKJlxpFkYVzcrlOPA17324S00IVWPMoptH+es=

I'm wondering if we might want to support/encourage namespaces in attribute names.

(I think there's folks on this list with lots of experience with such things :-)

My rationale is that often a group is represented as a collection of attributes, whether it be for provisioning, auditing, or transmission across a wire, and it might be beneficial for a consumer to be able to determine attribute 'metadata' based on name, since a consumer might have access only to an attribute's name and value.

For example, an attribute describing a stem might be named "grouper:stemAttribute:name".

I don't think we need any special code, we should consider an attribute name to be a String, but in practice we should use a reasonably simple naming convention - which I hope others will have more experience suggesting.


On Thu, Jun 11, 2009 at 1:19 AM, Chris Hyzer <> wrote:

There was already a wiki page on the attribute framework, and I updated it.

Note, this doesn't specify which release the features will go in, I assume 1.5 will be a limited edition as we get started with attributes.  :)

Let me know any feedback.


Archive powered by MHonArc 2.6.16.

Top of Page