Bug 6594: Schema.org span nesting improvements
authorDan Scott <dan@coffeecode.net>
Thu, 22 Aug 2013 15:47:12 +0000 (11:47 -0400)
committerGalen Charlton <gmc@esilibrary.com>
Wed, 28 Aug 2013 13:50:06 +0000 (13:50 +0000)
commitfa68cda549a14fa0286c07035faa6bfa5654b536
tree64a1418c33dc0473e7cb0108cfad29b9a26f15ba
parent1a50854d4fd4154013ae35dfd397fffaa0210d83
Bug 6594: Schema.org span nesting improvements

So, it turns out that the <a href> was causing a new "chain" to be
invoked, thus nesting the <span> elements for properties within the <a
href> actually caused the properties to be attached to that new chain
rather than the containing object. Therefore, wrap the <span> elements
around the <a href> elements where applicable.

Thanks to Manu Sporny in #rdfa for helping me to sort this out.

Signed-off-by: Dan Scott <dan@coffeecode.net>
Signed-off-by: Jared Camins-Esakov <jcamins@cpbibliography.com>
I tested by validating against the Google rich snippet tool,
validator.nu, and linter.structured-data.org. All were satisfied
with the microdata markup, and the properties that are set make
sense.

These patches are only for MARC21 XSLT view, but I think it is worth
pushing them even without the NORMARC and UNIMARC markup, so that
people can start to test out schema.org microdata in Koha, and
refine the implementation.

Signed-off-by: Chris Cormack <chris@bigballofwax.co.nz>
FWIW I agree with Jared, it is essentially a no-op in terms of what
the user sees, so is safe.

Signed-off-by: Galen Charlton <gmc@esilibrary.com>
koha-tmpl/opac-tmpl/prog/en/xslt/MARC21slim2OPACDetail.xsl