[XCON] draft-jennings-xcon-media-control-01
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[XCON] draft-jennings-xcon-media-control-01
Looking pretty good. Some comments here too, though:
- First, is it the case that "conference convener" is the same as
"conference owner" as defined in other docs? If so, then, consistent with
some comments Mary Barnes made in a different context, might we not then
use the same term in all docs? If not, what's the difference?
- In Section 3, the paragraph describing how the template and parameters
are fixed and "MAY NOT be manipulated...": The second sentence begins with
a definitive statement ("can only ..."), followed by a statement ("could
only ...") that weakens the first statement. This needs to be cleaned up.
- Section 5.2, note about needing a better name for "parameters". Not sure
what's really wrong with "parameter," but PLEASE don't use "instantiation
value"! How 'bout "attribute"?
- Section 5.4, question as to whether we want to define "in" and "out"
relative to the server: Yes! ;-)
- Section 5.5: I think it would be useful to provide some short examples at
the outset -- e.g. "toggle buttons, pull-downs menus, radio buttons" and
the like. As written, this discussion is too abstract, with the actual
manifestations of these particular controls only becoming clear later in
the document.
It would also seem to make more sense if the subsections of 5.5
corresponded to the list of "control types" given at the top of p. 12. No?
- Section 5.5.7: This begs for greater clarity. The example by itself is
insufficient, IMHO.
- Section 5.5.8: Is a "list" really a control?
- Section B.1.1.4: The implied definition of controls here doesn't seem to
jive with the definition in the body of the doc.
Regards, Keith
_______________________________________________
XCON mailing list
XCON at ietf.org
https://www1.ietf.org/mailman/listinfo/xcon
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.