On 5/09/2012 4:25 AM, Bruce Rich wrote:
Tim,
The spec does not use the term
value
in either Register or Get, so I would not want to introduce a
new term
now. However, the spec does list the attributes applicable to
objects
created using the Template. So my amended proposal is now
I still think you are basically not resolving the confusion with
that approach.
Get should return something from Section 2.2 of the specification
and in fact if you read it that is what it currently states.
This operation requests that the server returns the Managed Object
specified by its Unique Identifier .
And what is Section 2.2 - Managed Object .
That is about as well defined as you can get in terms of the
specification.
Get should not be interpreting parts of a Managed Object to return
or handling anything on an object type specific basis.
Where the confusion exists is that you provide attributes in the
Template when registering and attributes in the template attribute
list and only the attributes in the Template (the managed object)
itself should be returned.
The whole area of mess is actually in section 2.2.6 and not
elsewhere.
Whatever a user places in the Template managed object in the
Register is what SHALL be returned by the Get. That is clear,
simple, and what the current specification states.
The specification is unclear on what you are meant to do with
attributes provided in the template attribute list in a Register and
whether or not it is reasonable to include attributes for the
template as distinct from attributes that the template provides to
objects that reference it in the template itself. That's what we
need to sort out.
Tim.
