RIM suggested changes

["Nieman, Scott" <Scott.Nieman@NorstanConsulting.com>]

Farrukh,  I woke up in the middle of the night (again) regarding a few
topics:

1) I believe that objectType attribute needs to be in the Object class.
Consider the use case of someone "submitting" an object.  In order for the
SO to upload the submission, the SO must specify WHAT it is; a schema, a
classification scheme, a package, etc.  the objectType of the submission
needs to be known too.  Knowing the objectType tells me how to parse it,
persist it, etc.

2) I think we need to have ExternalObject stay the same, and somehow the
definition got modified (based on the meeting yesterday).  I believe we need
a specific objectType that refers to objects that are physically "external"
to the "local" registry.  This is a unique scenario since if the
ExternalObject resides in another registry, we need to know how to
authenticate to that registry.  There may be an association needed between
this object and the security object.  

3) As you integrate the Security information model, look at the statement in
line 195 vs. line 245.  Line 195 states the Permission object is the
top-level (??) object.  However, in processing (Line 245) we are actually
instantiating the Principal object which appears to be a state management
object (which in itself could be extended in the future).  So as we
instantiate the Principal object, the Permission object becomes more of a
helper to set the Principal object based on the "identity" of the user, the
roles played etc.  This is NOT to state that the model is wrong, but the
language for the information model becomes more clearer in totally separate
section (bootstrap), and some of that language needs to be include in the
RIM.

Good luck today!
Regards,

Scott

-----Original Message-----
From: Farrukh Najmi - JavaSoft East
To: Nieman, Scott; 'ebxml-regrep@lists.ebxml.org'
Sent: 12/19/00 5:19 PM
Subject: Re: Teleconference : 12/21/2000  12:30-4pm CDT : RIM discussion
follo w-up


I will distribute the RIM v0.43 document sometime by 5pm tomorrow or
earlier. I realize this leaves little time for
reading it. However, given our Jan 12 deadline it is the best we can
achieve. The delta changes will include:

-Changes based on Information Model "Take 3" proposal
-Changes based on the security proposal that Krishna had distributed

Both are module changes based on this afternoons very productive meeting

--

Regards,
Farrukh

"Nieman, Scott" <Scott.Nieman@NorstanConsulting.com> wrote:
>Date: Tue, 19 Dec 2000 16:35:14 -0600
>
>
>Meeting Date: 12/21/2000
>Meeting Time: 12:30-4pm CDT (please note CDT)
>
>The dialup information is:
>USA: 800.892.0357  
>Sorry no toll-free for International callers: usa 612.352.7899
>Meeting ID #8186	
>25 locations setup
>
>Agenda: Review the RIM updates based on input from 12/19 telcon.  
>
>Please read the document prior to the call.
>
>Regards,  
>
>Scott