Under this proposal, all of the “publishing inlines” and trademark are added to the set of “ubiquitous inlines”. This will extend the content models of all of the following elements: abbrev accel acronym address application arg artpagenums attribution authorinitials bibliocoverage biblioid bibliomisc bibliomset bibliorelation bibliosource citebiblioid city classname code command confdates confnum confsponsor conftitle constant contractnum contractsponsor contrib country database edition email emphasis envar errorcode errorname errortext errortype exceptionname fax filename firstname funcdef funcparams function givenname guibutton guiicon guilabel guimenu guimenuitem guisubmenu hardware holder honorific interfacename issuenum jobtitle keycap keycode keysym label lineage lineannotation literal manvolnum markup mathphrase methodname modifier mousebutton msgaud msglevel msgorig option optional orgname otheraddr othername package pagenums paramdef parameter personname phone phrase pob postcode productname productnumber property publishername refmiscinfo releaseinfo remark returnvalue revnumber revremark seriesvolnums shortaffil state street subscript superscript surname symbol tag token trademark type uri varname volumenum wordasword year In addition to inlinemediaobject, remark, subscript, superscript, the linking inlines, and alt, these elements would now also allow abbrev, acronym, trademark, date, emphasis, footnote and footnoteref, foreignphrase, phrase, quote, wordasword, firstterm, glossterm, and coref. In the particular case of emphasis, foreignphrase, phrase, quote, firstterm, and glossterm only a limited form of each element would be allowed. A quote, for example, in this context would also have a content model limited to the new definition of “ubiquitious inlines”. The new schema will allow things like: An application and filename.xml.