RefGuid and non-1st class citizens of repository

[Paolo F Cantoni]

We've created some automation to automatically⁽¹⁾ link physical attributes (for example W3C elements in a W3C Complex Datatype) to conceptual characteristics (attributes in a Business (Data) Object).

We could have used the link to attribute feature of relationships to establish this mapping, but that would create diagrams buried under a mass of arcs.
So, we decided to use a RefGuid tagged value to hold the Guid of the conceptual attribute against the physical attribute. The Guid value is set by the automaton.  In the Tagged Values window, the tagged value (correctly) shows the name of the conceptual attribute.  However, should we want to change the value, we can't - because attributes aren't available on the menu...  They are second class citizens.

It seems to me that they should be available (perhaps via a dialog extension - since it's more rare to connect to features than elements).
Thoughts?

Paolo

⁽¹⁾ via name derivation mapping

[Geert Bellekens]

Paulo,

I've used this mechanism loads of times and i've always been able to select attributes manually from the tagged values window.
This is what's in the description of my tagged value

Type=RefGUID;
Values=Attribute;
AppliesTo=Attribute;

Geert

[Paolo F Cantoni]

Paulo,

I've used this mechanism loads of times and i've always been able to select attributes manually from the tagged values window.
This is what's in the description of my tagged value

Type=RefGUID;
Values=Attribute;
AppliesTo=Attribute;

Geert

Thanks for that Geert.  It partly gets around my problem.  The Tagged Value can apply to different types of elements and features.  I was hoping, by not mentioning the specific types that I could avoid having to "spell them out explicitly".  Indeed, the Dialog says <Any> for the types list (at bottom left), when you leave them out!  So I thought it should allow me to select any type of thing.  But it doesn't.

It seems to me that if no Value is specified and no Applies To specified, it should apply to <All> and allow <All> values (note the semantic clarification - we often, colloquially, say Any when we mean All).

Paolo

[Geert Bellekens]

I think you can make a comma separated list of all the possible Values
But AFAIK there's no shortcut that allows everything to be linked.
But it shouldn't be too hard to to come up with an extensive list of all possible types this tagged value may refer too.

Geert

[Paolo F Cantoni]

Yes, for the present, this seems the only way. 

But what about the current, broken, dialog?
If it's only allowing look-up for <some> types, then it should list them.  If it really means <all>, then it should allow all.

Should I report a bug?

Paolo

[Geert Bellekens]

Should I report a bug?

Paolo

You can, not sure if they are very willing to fix this type of issue.

Geert

[Paolo F Cantoni]

Should I report a bug?

Paolo

You can, not sure if they are very willing to fix this type of issue.

Geert

Reported,

Paolo