Add IDL of Objects features

[VeskeR]

No description provided.

[sacOO7]

Suggested change

	class LiveObject: // RTLO*
	class BaseRealtimeObject: // RTLO*

Since both LiveMap and LiveCounter extend this class and are part of RealtimeObjects, it makes sense to name the class BaseRealtimeObject.

[sacOO7]

Additionally, we agreed to avoid using LiveObject/LiveObjects in the code.

[VeskeR]

we agreed to not use term "LiveObjects" (plural) in the code specifically when talking about the feature "Objects".

"LiveObject" (singular) is a name for any "live object" - "live map", "live counter", "live list" (in the future)

[VeskeR]

It is way easier to call something a "live object" (as we do in our conversations) and refer to it as "LiveObject" in the spec.
Since it also looks like that it shouldn't be necessary to expose LiveObject type to the public (kotlin and - and swift too I believe - implementations don't expose it) I'd prefer we stick to a simple name in the spec

[sacOO7]

Then better if we call it BaseLiveObject or BaseObject since it's extended by LiveMap, LiveCounter and not exposed externally. wdyt

[VeskeR]

But... why? I don't see a clear reason to change it. If it's not a public type then the name itself is not that important, and LiveObject type name accomplishes what we need it to do in the spec. And if it is exposed publicly (which it currently is in ably-js) we can't just change the name in the spec as we would also need to update ably-js implementation.

I really don't want to go through all spec PRs and update the LiveObject name to something else given it does what it need to right now

[sacOO7]

Okay, since it's an internal type, we can ignore the naming convention.

[sacOO7]

lgtm