Home | Public Area

Comment #00258 - Parameter Entity for Global Attributes (RDFa) - z39.96-2012.pdf

Comment 258
Addressed (Unresolved)
ANSI/NISO Z39.96-2012, JATS: Journal Article Tag Suite (version 1.0) (Revision 0)
Comment Submitted by
Jeffrey Beck
2013-05-10 11:14:04
This request is submitted by Jeff Beck on behalf of the BITS working group. It was originally submitted by Imsieke, Gerrit, le-tex" <gerrit.imsieke@le-tex.de> through the JATS List.

Request: Please add a parameter entity for global attributes. We wish to allow formatting (CSSa) and semantic (RDFa) markup in attributes.

Background: This leads to another wish: we currently patch each element that is allowed to carry an @xml:lang attribute in the following way:

<define name="sec-atts" combine="interleave">
<ref name="css_attributes"/>
<ref name="Rdfa.attrib"/>
</define>

If there were a parameter entity for global attributes in the DTD (which may default to @xml:lang), it would be easier to add orthogonal, attributes-based vocabularies.

RDFa is intended for marking up multiple-choice tests and the like. We’d prefer not to use JATS-style content-type attributes for that because RDFa is more expressive and we can use the same vocabulary in HoBoTS and in HTML (where we’ll probably have Javascript widgets that turn RDFa-enriched books into interactive test applications).

We use CSSa for conveying the original InDesign style information and local formatting overrides, after translating them into CSS properties and attaching them as XML attributes. One reason for using CSSa is that we want to be able to express formatting that should appear in the
same way in every rendering. For example, we can just pass thru the properties for handwriting fonts – css:font-family="cursive", extra spacing after paragraphs – css:margin-bottom="12pt", font color – css:color="device-cmyk(0,1,1,0)", or table cell backgrounds – css:backgroundcolor="
device-cmyk(0,0,0,0.2)". They will find their way to the HTML and EPUB renderings almost unaltered – except that they’ll translate into CSS rules or HTML style attributes, and except that color values will be converted to RGB.
Submitter Proposed Solution
The BITS Working Group forwards this to JATS for a response.
Jeffrey Beck
2013-11-27 10:48:55

Thank you for your comment. The JATS Standing Committe has addressed your request. Non-normative supporting materials including schemas with these additions in place should be available soon.

The Standing Committee's recommendation is:

• Add a parameter entity to hold global attributes (named “jats-common-atts”) and add this parameter entity to
the attribute list of each element in the Tag Sets. For now, the only content of this parameter entity will be the
@id attribute. This new parameter entity will enable users to customize the NISO JATS Tag Sets by adding
attributes such as @xml:lang, CSS classes, and RDFa attributes to all elements.


This parameter entity addition must be done in such a way that duplication warnings for the @id attribute do
not occur. This will require changes to current attribute list parameter entities. Thus, while the new parameter
entity will cause no existing NISO JATS documents to break, it may break customizations. Document this
clearly for existing users.


• In recognition of the fact that the @id attribute, although optional for most elements, is required for some
elements, this request will be implemented using two parameter entities: one for common attributes where the
@ID attribute is optional and one for common attributes where the @id attribute is required:
     • common-atts
     • jats-common-atts-id-required
• Additionally, the global attributes will not be placed onto the <mml:math> element.


• The global attributes will be placed on to the table elements for both the XHTML-inspired table models and
the CALS-based OASIS Exchange table model.