Clarify /usr/share purpose : are executed resources allowed

[Jeff Johnson]

Currently /usr/share is defined as “Architecture-independent data”

However data is a pretty meaningless concept in computer science (what is not
data), and the operational difference between /usr/lib(64) and /usr/share seems
to be architecture-dependant (multilib) resources one side, and architecture
independant resources the other side

Unfortunately some FHS readers insist the current wording means anything
executed one way or another should go in /usr/lib(64) (Libraries for
programming and packages). Notwithstanding the fact that
architecture-independant java bytecode (jar file) is usually deployed in
/ust/share, as are webapps (php pages included), font files (embedded font
hinting instructions included), etc

Please clarify /usr/lib(64) and /usr/share intent so there is no room for
pointless arguments.