[comp.protocols.iso.dev-environ] ROS, RON, SAG, and RDA

daa@srv03.UUCP (Dean Arnold) (01/15/91)

I assume RON means "Remote Operations Notation". SAG is SQL Access Group,
a consortium founded to advance the RDA process. So much for a definition of
terms.

While I cannot speak for SQL Access, or for RDA, I am responsible for development of Teradata's SQL Access RDA prototype; I've been using ISODE
from the outset, and would like to point out to those concerned about losing
ISODE functionality that the ASN.1 compiler of ISODE works quite well without
the rosy front end...I only had to make minor modifications to adapt from the
initial ROS version of RDA to the ASN.1 version.

As to a movement to eliminate ROS entirely, I seriously doubt that is the intent of RDA. The decision was based on more practical criteria specific to
RDA's needs, and was not made lightly or without prior attempts to make ROS
work. But after SQL Access began working with the ROS version, it became
apparent that ROS added some overhead that was not needed, and also seemed to
restrict the implementation in other areas (e.g, how to address CCR protocols
within ROSE?).

I believe ROSE has its place, especially for developping small applications
or utilities...but for a major standard of importance like RDA, more
flexibility may be required.