ResourceName validity

[Carol Burt <cburt@2ab.com>]

Konstantin added the following requirement to the ResourceNameComponent and
to the ResourceNamingAuthority

"A datum element of  type xxx is invalid if either name_string or
value_string member has empty value."

I think that this is too restrictive.  We are prohibiting very simple names
in domains that may have simple needs.  For example it is possible to
imagine a naming scheme that only uses name portion of the namespace.  (In
fact we have such a resource defined right now in the rules repository of
our prototype).   Perhaps we should say that both the name AND value cannot
be empty.

The same holds for the AuthorityId... if I'm in a limited domain I may
choose not to provide one.  

And requiring that Operation not be null means that you couldn't provide
access control at the Resource Level... you must go to the operation level.
 I could see saying that if the Operation is null then access must be
allowed to any operation of the named resource.

Carol



_________________________________________________________
Carol Burt                                             2AB, Inc.
cburt@2ab.com                                     Integration Architects
205-621-7455                                        www.2ab.com
Member, OMG Architecture Board          OMG Domain Member

   --  integrating yesterday's systems with today's technology --
----------------
Broadcast message to hrac-rfp from Carol Burt <cburt@2ab.com>.
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.