rename viewingHint to behavior

[jpstroop]

From Editors discussion following Feb. A/V meeting in London: Now that we're dealing with A/V, (A in particular for this question), should we rename viewingHint ro renderingHint?

[azaroth42]

+1 to renaming in Prezi 3.0

[azaroth42]

AV call 08/22: Could rename to something else, if there's a better term than rendering. But general consensus that renaming would be beneficial and this is the time to do it. Can change the name from rendering if we come up with something better.

[azaroth42]

How about displayDirection and displayHint to keep it distinct from the rendering link?

[zimeon]

I think renderingHint applies better to audio-only than displayHint? We had previously noted:

Consider whether or not to rename viewingHint to renderingHint as "viewing" an audio file is weird.

[azaroth42]

From Toronto: As we try to constrain the interpretation of the specification more closely, to make it easier to implement, do we still actually consider them to be "hints"? If we have some MUSTs and error states for the published content, then they seem stronger.

Possible name components:

• rendering / viewer / presentation / request[s,ed]
• hint / directive / behavior / guidelines

[zimeon]

Toronto WG meeting discussion not to more forward without more discussion of names per #1073 (comment) above

[azaroth42]

To move it forwards: I propose behavior

[tomcrane]

👍 to behavior for reasons discussed in Toronto

[zimeon]

👍 for behavior also

[jpstroop]

👍 behavior.

Make sure we spell it properly 😉 🇺🇸

[zimeon]

I might have to take issue with "properly", but we should spell it in the manner agreed

[jpstroop]

Oh right. We should make sure to spell it proper. 😄

[azaroth42]

With the re-rename of renderingHint to behavior, and the meaninglessness of viewingDirection when it comes to raw audio ... shall we put viewingDirection back?

[tomcrane]

yes!

[azaroth42]

Closed by #1316