AttributeDefinition multivalued to single value attribute?

[Cantor, Scott]

> I suppose because we wanted to return an explicit "true" or "false" to the SP. If
> we simply don't return the hasFoo attribute they'd have to infer hasFoo=false. I
> suppose if we must, we can go back to them and see if the design change is
> feasible for them.

It has to be, or they will have a bug because there is no way anybody can ever assume any attribute is present, that's just not done. You have to handle it (even if that means a Forbidden or whatever). So it's pretty obvious that handline missing as "whatever the default should be" is just a given.

-- Scott