eBooks and libraries, the right to eRead? #ebooks14

About once a year I go to some meeting or another on libraries and eBooks. I nearly always come back from it struck by the tension between libraries, as institutions of stability and the rapid pace at which technology companies are driving forward eBook technology.  This year’s event of that type was the Scottish Library and Information Council’s 13th annual eBook conference. The keynote from Gerald Leitner, chair of the European Bureau of Library, Information and Documentation Associations task force on eBooks was especially interesting to me in introducing the Right to eRead Campaign. facebooktwittergoogle_plusredditpinterestlinkedinmail

Euclid in colour and technology for learning

I work in the area commonly known as Learning Technology, or Educational Technology.  I don’t have much time for trying to pin down what exactly constitutes “technology” in that context, and certainly none for considerations like “printing is technology, does that count”.  But today I bought a book which does quite literally(*) illustrate advances in printing applied to learning.

euclid2The book is a reprint of the Oliver Byrne’s The first six books of the elements of Euclid in which coloured diagrams and symbols are used instead of letters for the greater ease of learners which was first published in 1847. Instead of the conventional referencing of lines, shapes and angle by letters used in geometry text books. So instead of:

Proposition 30: Straight lines parallel to the same straight line are also parallel to one another.

Let each of the straight lines AB and CD be parallel to EF.
I say that AB is also parallel to CD.
Let the straight line GK fall upon them. Since the straight line GK falls on the parallel straight lines AB and EF, therefore the angle AGK equals the angle GHF.
Again, since the straight line GK falls on the parallel straight lines EF and CD, therefore the angle GHF equals the angle GKD.
But the angle AGK was also proved equal to the angle GHF. Therefore the angle AGK also equals the angle GKD, and they are alternate.
Therefore AB is parallel to CD.
Therefore straight lines parallel to the same straight line are also parallel to one another.

This book has:euclid1

Colour printing of books was not common in 1847, it only became commercially viable after the invention new printing techniques in the C19th and mass production of cheap synthetic dyes, starting with mauvine in 1856, so this can fairly be called advanced technology for its time. Like many uses of technology to enhance learning, when colour printing of text books did become commonplace, it wasn’t used with the same imagination as shown by the pioneers.

* except, of course, that “literally” means according to the written word and this is a book of pictures. #CetisPedantry

facebooktwittergoogle_plusredditpinterestlinkedinmail

Licence information in schema.org and LRMI

When the Learning Resource Metadata Initiative (LRMI) technical working group started its work it focused on identifying the properties and relationships that were important for educational resources but could not be adequately expressed using schema.org as it then stood. One of those important pieces of information was the licence under which a resource was released, and so the LRMI spec from the start had the property useRightsUrl  “The URL where the owner specifies permissions for using the resource.” When schema.org adopted most of the LRMI properties, useRightsUrl was an exception, it was not adopted pending further consideration–not surprising really given the wide-ranging applicability of licence information beyond learning resources.

Back in June the good news came that with version 1.6 of schema.org included a license property for Creative Works that does all that LRMI wanted, and more.

What does this mean for LRMI adopters?

Some adopters of LRMI have already started using useRightsUrl.  Such implementations are valid LRMI but not valid schema.org, which means that they will only be understood by applications that have been written specifically to understand LRMI and not by the general purpose web-scale search applications. This is sub-optimal.

In passing, let me mention another complication. With schema.org you have a choice of syntax: microdata and RDFa 1.1 lite. With RDFa there was already a mechanism for identifying a link to a licence, that is rel=”license”.  Just to complicate a little more, RDFa allows name spacing, and the term license appears in at least three widely used namespaces: HTML5, Dublin Core Terms, and the Creative Commons Rights Expression Language–hopefully this will never matter to you.  To exemplify one of these options I’ll use the HTML that you get when you use the Creative Commons License Chooser (but let’s be absolutely clear, what I am writing about applies to any type of license whether the terms be open or commercial):

<a rel="license" href="http://creativecommons.org/licenses/by/4.0/">

The good news is that all these options play nicely together, you can have the best of all worlds.

If you are already using itemprop=”useRightsUrl” to identify the link to a licence using LRMI in microdata, you can also use the license property and rel=”license”. The following  LRMI microdata with a bit RDFa thrown in works:

<html>
  <body itemscope itemtype="http://schema.org/CreativeWork">
    <a itemprop="license useRightsUrl" rel="license"
        href="https://creativecommons.org/licenses/by/4.0/">
        Creative Commons Attribution 4.0 International (CC BY 4.0) licence
    </a>
  </body>
</html>

If you are using LRMI / schema.org in RDFa, then the following is valid

<html>
  <body vocab="http://schema.org/" typeof="CreativeWork">
    <a rel="license useRightsUrl"
       href="https://creativecommons.org/licenses/by/4.0/">
       Creative Commons Attribution 4.0 International (CC BY 4.0) licence
    </a>
  </body>
</html>

License does what LRMI asked for and more

In my opinion the schema.org license property is superior to the LRMI useRightsUrl for a few reasons. It does everything that LRMI wanted by way of identifying the URL of the licence under which the creative work is released, but also:

  • It belongs to a more widely recognised namespace, especially important if you are wanting to generate RDF data
  • I prefer the semantics of the name and definition: a license can include  restrictions of use as well as grant rights and permissions.
  • the range, i.e. the type of value that can be provided, includes Creative Works as well as Urls

That last points allows one to encode the name, url, description, date, accountable person and a whole host of other information about the licence (albeit at the cost of the not being able to do so alongside LRMI’s useRightsUrl quite so simply)

Summary

The inclusion in schema.org of the license property is good news for aims for LRMI. If you use LRMI and care about licensing you should tag the information you provide about the license with it. If you already use LRMI’s useRightsUrl or RDFa’s rel=”license” there is no need to stop doing so.

facebooktwittergoogle_plusredditpinterestlinkedinmail