Re: matching attribute and capability was Re: LC model draft draft-ietf-forces-model-07.txt

There is no correlation between capabilities and attributes.  In 
essence, capabilities are read-only attributes.
The relationship between specific capabilities and specific other 
attributes or groups of attributes is captured only in the descriptions.

Note that the most common seet of capabilities, which are correlated, 
are captured in the element properties.  That is where write access, 
and for arrays size limits, are recorded.

Is there more text on this needed?  If so, can you suggest where?

Yours,
Joel M. Halpern

At 06:31 AM 10/25/2006, tom.petch wrote:
>I am unclear from the I-D whether or not there is any formal matching of a
><capability> with an <attribute>, given they will often come in 
>'matched pairs'.
>
>Say a port group has an attribute giving a maximum of two ports while the
>capability is one.  The <capability> has a <name> and elementID, the 
><attribute
>has a <name> and elementID; is there any relationship between the two pairs of
>data?
>
>Related to this, is the namespace of elementID for <capability> the same as or
>distinct from the namespace of elementID for <attribute>?.
>
>
>Tom Petch
>
>
>----- Original Message -----
>From: "Patrick Droz" <[email protected]>
>To: <[email protected]>
>Sent: Friday, October 13, 2006 10:36 AM
>Subject: LC model draft draft-ietf-forces-model-07.txt
>
>
> > I would like to issue last call on the model draft. As this is
> > a fairly large document the LC will last for 3 weeks and will
> > therefore end just before the next IETF. It is draft:
> > draft-ietf-forces-model-07.txt
> > and can be found at:
> > http://www.ietf.org/internet-drafts/draft-ietf-forces-model-07.txt
> >
> > A number of people have indicated that if the document is in
> > LC they would thoroughly review the document. I hope people will
> > stick to their promises.
> >
> > Regards,
> > Patrick
> >
> >
> >