RequestedAttributes and EntityAttributes

[Cantor, Scott]

On 6/10/14, 1:45 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>So that fills in a lot of blanks.   Thanks.
>
>I'll need to regroup and take stock and the report back (I have a minor
>niggle about what we do about isRequired in the case where we are an
>Attribute not a RequestedAttribute, but that will sort itself out)

I think it will probably just need to be carried into the ObjectMetadata,
so the objects we put there are probably of a type that will have a
subtype that carries the flag, mirroring the Attribute/RequestedAttribute
relationship.

>Any suggestions for the filter name (since "AttributeInMetadata" is
>taken),
>or (and I like this) shall we just widen the schema for
>AttributeInMetadata
>to allow the configuration to specify where it gets the data from
>(Query/ACS/EntityAttributes).

Oh, I would say that AttributeInMetadata we reserve to mean "from the
RequestedAttributes in an ACS", and define something else for the
EntityAttributes case (which I think we already did?).

As for queries, I would not implement that in the filter engine. It may be
simpler to code there because of duplication, but I don't think it belongs
there, I'd rather do it explicitly in an Action inside the query flows.

Since the actual code there is simple iteration and handing off compares
to objects, it should not be onerous to do.

It's a different semantic in my opinion, since it's a filter applied by
the requester, so I think it's better to separate it.

-- Scott