You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the spec, the object's identifier starts with the type of agent, rather than the generic agent-target. If I search the text for "agent-target", that's the name for the object type but I never see it used as a literal value in the JSON examples.
And since that type is an open-vocab, a proper fix should handle user-defined agent types as well:
I played some more and the way Roaster creates agent definitions doesn't seem to match what's in the spec. I created a net-address agent in Roaster:
But the example in the spec (section 7.10) looks rather different:
In the spec, the object's identifier starts with the type of agent, rather than the generic agent-target. If I search the text for "agent-target", that's the name for the object type but I never see it used as a literal value in the JSON examples.
And since that type is an
open-vocab
, a proper fix should handle user-defined agent types as well:The text was updated successfully, but these errors were encountered: