<!-- Creative Commons License -->
<a rel="license" 
   href="http://creativecommons.org/licenses/by/2.5/">
<img alt="Creative Commons License" border="0" 
     src="http://creativecommons.org/images/public/somerights20.png" /></a><br />
This work is licensed under a 
<a rel="license" 
   href="http://creativecommons.org/licenses/by/2.5/">Creative Commons 
   Attribution 2.5 License</a>.
<!-- /Creative Commons License -->

<!--

<rdf:RDF xmlns="http://web.resource.org/cc/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<Work rdf:about="">
<license rdf:resource="http://creativecommons.org/licenses/by/2.5/" />
</Work>

<License rdf:about="http://creativecommons.org/licenses/by/2.5/">
<permits rdf:resource="http://web.resource.org/cc/Reproduction" />
<permits rdf:resource="http://web.resource.org/cc/Distribution" />
<requires rdf:resource="http://web.resource.org/cc/Notice" />
<requires rdf:resource="http://web.resource.org/cc/Attribution" />
<permits rdf:resource="http://web.resource.org/cc/DerivativeWorks" />
</License>

</rdf:RDF>

-->

1.4 The <License> element of the RDF description serves to identify characteristics of that license distinguished using the given Uniform Resource Identifier (URI) <http://creativecommons.org/licenses/by/2.5/>.   It is irrelevant to interpretation of the <License> element whether that URI serves as a link to any content and what the subject-matter of such content might be.  All that matters (for the RDF description) is the usage of the URI in all of its occurrences as an RDF attribute.  It is a desirable practice (honored for the Creative Commons licenses) to have the Uniform Resource Locators (URLs) link to human-meaningful and/or machine-processable resources that are relevant to and in some way consistent with the RDF description and vice versa.  This has been done with resources at the Creative Commons site and URL <http://web.resource.org/cc/> (2006a).

1.5 The <Work> element of the RDF description serves to identify the work and the license that is available for it.  The rdf:about="" attribute is a convention by which the subject is taken to be the URI of the resource at hand (Manola & Miller 2004, Appendix A).  The intended interpretation, in this case, is that the licensed work is that which is embodied in the HTML code in which the comment-embedded <rdf:RDF> element appears.

1.6 Multiple licenses can be specified for a work by listing URIs for each of them as <license>-element resources of a <Work> element.  The intended interpretation is that any one of them may be chosen in making a given use of the work (web.resource.org 2006a).  <License> elements for describing properties of each license, if provided, offer a mechanical determination of basic conditions of a license.  To honor the license conditions, it is still necessary to know the precise terms.  For example, the following <License> element is usable for the Academic Free License 2.1, one that has the same qualities but many important differences in detail (OSI 2006).

<License rdf:about="http://www.opensource.org/licenses/afl-2.1.php">
    <permits rdf:resource="http://web.resource.org/cc/Reproduction" />
    <permits rdf:resource="http://web.resource.org/cc/Distribution" />
    <requires rdf:resource="http://web.resource.org/cc/Notice" />
    <requires rdf:resource="http://web.resource.org/cc/Attribution" />
    <permits rdf:resource="http://web.resource.org/cc/DerivativeWorks" />
</License>
 

1.7 The recommended insertion is like a rubber stamp (section 1.3).  It applies to the web page in which it is inserted.  It does not include any descriptive material about the particular work (e.g., author, title, date of creation, and sources from which the work is derived).  This form is very useful for repetitive application to a set of web pages and across an entire site. 

1.8 Works can be identified explicitly.  It is possible to add work-identifying information in the <Work> element.  This can appear in the same or additional comment-embedded <rdf:RDF> element.  It can even appear in a separate place.  For example, this work has the following HTML comment at the end of the attribution citation (Hamilton 2006):

<!-- 
<rdf:RDF xmlns:cc="http://web.resource.org/cc/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<cc:Work rdf:about="">
<dc:Identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">
http://nfoWare.com/notes/2006/01/N060101f.htm
</dc:Identifier>
<dc:title>Creative Commons License: Web-Page Notice Procedure</dc:title>
<dc:creator><cc:Agent>Dennis E. Hamilton</cc:Agent></dc:creator>
<dc:rights><cc:Agent>Dennis E. Hamilton</cc:Agent></dc:rights>
<cc:license rdf:resource="http://creativecommons.org/licenses/by/2.5/" />
<dc:date rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2006-01-11</dc:date>
<dc:format>text/html</dc:format>
<dc:type rdf:resource="http://purl.org/dc/dcmitype/Text" />
<dc:source rdf:resource="http://creativecommons.org/license/results-one?license_code=by" />
<dc:source rdf:resource="http://creativecommons.org/policies" />
<dc:conformsTo rdf:resource="http://creativecommons.org/policies" />
<dc:references rdf:resource="http://creativecommons.org/technology/metadata/" />
<dc:references rdf:resource=http://creativecommons.org/education/publish-website" />
<dc:references rdf:resource="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/" />
<dc:references rdf:resource="http://www.opensource.org/licenses/afl-2.1.php" />
<dc:references rdf:resource="http://web.resource.org/cc/" />
<dc:references rdf:resource="http://web.resource.org/cc/schema.rdf" />
</cc:Work>
</rdf:RDF> 
-->

 

2. Usage Considerations

2.1 The web-page insertion code was obtained from (Creative Commons 2006a).   The .png version of the image (shown at 1.1) was captured at the same time.  There is a supporting tutorial (Creative Commons 2006d).

2.2 the nfoWare site and materials use a copy of the Creative Commons "Some Rights Reserved" Copyright License Mark image.  This assures that the image is presented properly when the nfoWare material is accessible and the Creative Commons site is not. The use of a copy may inhibit the delivery of a cookie and also bypass any Creative Commons counting of page views that include presentation of the image.

2.3 On the Internet, some firewalls and filters will suppress the image as advertising.  The heuristics that are used to determine when an image is or is not part of adware are crude and have no ability to recognized exceptions that the viewer might find acceptable.  Limited experimentation suggests that there is no single action that will overcome that classification.

2.4 It is important to honor the requirements for use of Creative Commons trademarks.  For example, the usage of Creative Commons trademarks on this site make linkages to the Creative Commons site as required by the models from the Creative Commons site and the Creative Commons Policies (Creative Commons 2006b). 

2.5 Illustrative usages that are not declarations of a license (e.g., in section 1.1) also honor the trademark requirements.  The RDF content is not present in examples and links have rel="nofollow" attributes rather than rel="license". This avoids confusion with genuine license notices.  The illustrative HTML in section 1.3 is not recognized as an HTML-coded license description because its HTML code does not have the form of a comment-embedded RDF element.

2.6 Because comment-embedded RDF descriptions are only visible when examining the HTML code, it is important to review the code for document-specific descriptions that should not be carried forward unaltered into a derivative work or when the page is updated.

3. nfoWare Practice

3.1 If an nfoWare page is covered by the license, the bottom of the page will contain a notice along with its "you are here" text:

3.2 Except for the repositioning of the image and text elements, this notice conforms to the recommendation (section 1).  There is a version of this notice for each different style of nfoWare page (e.g., construction structure, construction material, and standard page).

3.3 The link in "licensed" is directed to the local deed statement with its expanded information about how the license is applied for nfoWare.   This link supplements the generic linkages that are part of the standard Creative Commons notice.

3.4 An important purpose for the supplemental material is specifying how to make acceptable attribution when a page does not provide an explicit attribution section.