#291 license tag

DocBook (176)

In June 2011 I did some work for including license information in a docbook article.


The proposal is presented here :
and result is displayed here :

There were no comments, indicating that the need was limited.

Is there a better way to do this ?
legalnotice is one way, but for "standard" licenses there could be an easier way.
Maybe the suggested attributes belong to legalnotice instead of a new tag.
Or is "standard" formatting for "standard" licenses out of the scope of docbook ?

I did an attempt to use legalnotice in 2007 but it was not very successful.
Perhaps a document with the normal creative commons look is just not feasible.

I could try to improve the proposal if there is any interest, and if I get any indication to what needs to be changed.

Thank you



  • Norman Walsh

    Norman Walsh - 2013-02-20

    Can you explain how legalnotice failed to meet you needs?

    It seems to me that a legalnotice and a role attribute would be enough information for the stylesheet to generate the look you want.

  • Fredrik Svensson

    2007 I made this attempt with Legal notice :
    It was pretty verbose, and did not use any xsl for presentation.
    In retrospect that was probably the wrong way to get the Creative Commons look into a document.

    I was looking for a way to get the Creative commons look into some documents, in an easy
    way, and made the license tag suggestion. I was not sure how to extend the legalnotice.
    Maybe <legalnotice role="cc-by 3.0 us"/> then ?
    For me that would be fine as well, I do not need to create a new tag.

    I generate a documents with some images now that has CC license, and currently I do not have a good solution for the legal part.

    How would one write http://article.tree.se/tools/docbook/cc.en.xml in current Docbook ?
    I can try to adapt the http://article.tree.se/tools/docbook/cc.xsl for the same result.

  • Norman Walsh

    Norman Walsh - 2013-11-20

    I couldn't quite work out what the cc.en.xml license was supposed to be, but poking around on creativecommons.org, I came up with this:

    <imagedata fileref="http://i.creativecommons.org/l/by-sa/3.0/88x31.png"/>
    </inlinemediaobject> This work is licensed under a
    <link xlink:href="http://creativecommons.org/licenses/by-sa/3.0/deed.en_US">Creative
    Commons Attribution-ShareAlike 3.0 Unported License</link>.</para></legalnotice>

    That, with some stylesheet work, could do the right thing, I think.

    I'm not actually opposed to doing something new for standard open source licenses, by the way, I'm just trying to understand the scope of the problem.

  • Jirka Kosek

    Jirka Kosek - 2013-11-20

    Also it would be possible to express all necessary CC properties using RDF inside <info> element, there is special RDF vocabulary for this: http://creativecommons.org/ns

    We definitively need to get better understand what is the problem here.

  • Scott Hudson

    Scott Hudson - 2013-11-21

    Here's how I would recommend marking the content up using DocBook Publishers v1.0 and DublinCore with CC license:

    <article version="5.1-variant publishers-1.0" xml:lang="en"
    <title>A Creative Commons Licenced Docbook Article</title>
        <titleabbrev>CC Docbook</titleabbrev>
          <holder xlink:href="http://article.tree.se/tools/docbook/cc">Fredrik Unger</holder>
          <holder xlink:href="http://article.tree.se/tools/docbook/cc">John Smith</holder>
        <dc:title xmlns:dc="http://purl.org/dc/terms/">CC Docbook</dc:title>
        <dc:creator xmlns:dc="http://purl.org/dc/terms/">Fredrik Unger</dc:creator>
        <dcterms:created  xmlns:dcterms="http://purl.org/dc/terms/">2011-02-17</dcterms:created>
        <dcterms:dateCopyrighted  xmlns:dcterms="http://purl.org/dc/terms/">2011</dcterms:dateCopyrighted>
        <dcterms:license xmlns:dcterms="http://purl.org/dc/terms/">http://creativecommons.org/licenses/by/2.5/se/deed.en_US</dcterms:license>
        <dc:source xmlns:dc="http://purl.org/dc/terms/">http://article.tree.se/tools/docbook/cc.en.xml</dc:source>
        This documents try to inclue ways to express the copyright license
        of the document and the document objects using the Creative Commons
        licences. It tries to expand the copyright tag in a natural way
        and provide expected output via an xsl stylsheet extention.
        Many documents online created with docbook is using Creative
        Commons license.  To simplify its use, CC licensing, and inclusion
        of images etc would maybe increase the use of the license.
      <section><title>Including an image in the document</title>
            <dc:title xmlns:dc="http://purl.org/dc/terms/">CC Docbook</dc:title>
            <dc:creator xmlns:dc="http://purl.org/dc/terms/">Fredrik Unger</dc:creator>
            <dcterms:created  xmlns:dcterms="http://purl.org/dc/terms/">2011-02-17</dcterms:created>
            <dcterms:dateCopyrighted  xmlns:dcterms="http://purl.org/dc/terms/">2011</dcterms:dateCopyrighted>
            <dcterms:license xmlns:dcterms="http://purl.org/dc/terms/">http://creativecommons.org/licenses/by/3.0/us/deed.en_US</dcterms:license>
            <dc:source xmlns:dc="http://purl.org/dc/terms/">http://article.tree.se/tools/docbook/line.png</dc:source>
          <holder xlink:href="http://article.tree.se/tools/docbook/line.png">Fredrik Unger</holder>
          <imagedata fileref="line.png" format="PNG"/>
          <phrase>A black line</phrase>
        A black line
  • Fredrik Svensson

    Basically my wish was just an easy way to license works in a way that displays the well known markers of well known licenses.
    I am open to other solutions.

    I can learn Dublin Core or RDFa, I might even be able to scare a xslt template into displaying the proper information in the final document.
    I suggested the license tag with the accompanying xslt sheets to be a simple, maybe too simple solution.

    Thomas Schraitle went this way :
    using this source :
    which is a smilar route I tried back in 2007.

    Thomas goes further to include the full license text.
    Maybe that is leagaly required.

    What are your experiences ? or do people not license/copyright their documents ? how do they attribute an included CC image ? or is your experience more from the corporate world where the legal department writes a long legalnotice + appendixes ?

    I'll be following your discussions and I can understand if it is out of the scope of docbook. If I can help let me know.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks