spec icon indicating copy to clipboard operation
spec copied to clipboard

how to address attributes/properties?

Open BenediktBurger opened this issue 2 years ago • 3 comments

We're developing a laboratory control protocol LECO and are looking for a way to encode messages. open-rpc seems to be great for encoding method calls. We need, however, to access attributes/properties of the remote object (i.e. read/write variables of that object). Is there any suggestion, how to do it via open-rpc or is there any other useful protocol?

json-schema seems to do the job of encoding attributes, but cannot handle method calls.

Does anyone use a combination of open-rpc and json-schema?

BenediktBurger avatar Mar 29 '23 09:03 BenediktBurger

Welcome to OpenRPC! Thank you for taking the time to create an issue. Please review the guidelines

github-actions[bot] avatar Mar 29 '23 09:03 github-actions[bot]

@bmoneke Thanks for checking out openrpc. OpenRPC is simply put a description of methods using JSON Schema + some other stuff. In OpenRPC, json-rpc params and results are represented as "ContentDescriptors" - basically a wrapper for the JSON schema that describes the data type. You might find some of these examples useful:

https://playground.open-rpc.org/?url=https://raw.githubusercontent.com/open-rpc/examples/master/service-descriptions/simple-math-openrpc.json

BelfordZ avatar Jul 06 '23 17:07 BelfordZ

I know, how params for rpc calls are represented. My question touches a different point: Is there a possibility to describe class/instance attributes?

As far as I know, json-rpc does not define how to get/set variables/attributes, but only how to call methods remotely.

Therefore, I think, open-rpc only describes a remote methoc call, but not a "remote variable getting/setting". Am I right?

BenediktBurger avatar Jul 18 '23 10:07 BenediktBurger