The language in question about @orient is: "In situations where a stylesheet or other formatting mechanism specifies table orientation based on other criteria, or for non-paginated outputs, the @orient attribute can be ignored."
As I understand it, this definition is intentionally ambiguous so that processors may do what's right in any given situation (this is often the case when the specification uses "can"). In this case, we do not want to forbid recognizing both, because that could be exactly what somebody needs. However, the language explicitly allows a processor to ignore @orient in situations where it does not make sense. Using both @orient and @rotate could (but does not have to be) one of those situations; that could also be a rule based on output format, or based on a particular author's style preferences.
Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit (http://www.dita-ot.org/)
"Julio Vazquez" ---07/15/2015 10:45:11---Just think I need a little more clarity here. If @orient="land" is specified on <table> should the pFrom: "Julio Vazquez" <jvazquez@vasont.com>
To: <dita-comment@lists.oasis-open.org>
Date: 07/15/2015 10:45
Subject: [dita-comment] @rotate on <entry>