URML (open robot-intent language): declaring OPC UA Robotics capabilities, plus a license question

[idoco2003]

Hi OPC Foundation maintainers,

URML (urml.dev) is a small open language for describing robot intent. On an industrial arm a user writes pick_from(bin_a); URML checks it against the robot's declared capabilities, then dispatches through the target's command interface. On an OPC-UA-Robotics deployment, that target is the OPC UA Robotics NodeSet. Apache-2.0, no change to your spec proposed, nothing for you to maintain.

Two small things:

1. The UA-Nodeset repo doesn't seem to declare an OSI license on its surface. Is that intentional, or is there a license you'd point to? It decides whether a downstream project can ship an adapter that references the NodeSet.
2. If we wanted to write "this robot's capabilities map to these OPC UA Robotics nodes" into our manifest, is there a convention you'd want us to follow, or is that new ground?

Full write-up if useful: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0214-opc-foundation-ua-nodeset-outreach.md

Thanks for keeping the UA Robotics companion spec a real, usable standard.

Ido Yahalomi (URML, greenvh@gmail.com)

AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.