nfoWare Hard Hat Stage

nfoNote n060101
  Creative Commons License
Diary & Job Jar

nfoWare>notes>
2006>01>

n060101a>
 0.00 2013-11-13 09:10 -0800

Status

Date

Description
   
nfoWare> repaving> 2007-08-04 announcement>


nfoWare Is Being Repaved.

Migration to a new server introduced a number of problems that require repairs.  In addition to those defects, some older pages also need to be modified and reorganized for consistency across all of nfoWare.  While the site is being repaved to accomplish both kinds of improvements, you may notice discrepancies and problems with links to site content.

Check the Site Repaving Project pages for additional details on the known defects and the approach to correction and upgrade.  Contact the nfoWare author with questions and to report any defects that you notice.

 
 
     
     
     
     
     
in progress 2013-11-13 Repave the Construction Structure and Styles throughout the folio: n060101, n060101a, n060101b, n060101c, n060101d, n060101e, n060101f, n060101g, and n060101h.  Check the properties for the .mht, .png, xml, and gif pages as well.
  2006-01-11 When we can complete enough of these work items, sweep the completed ones onto an archive to this page, making the top page easier to work with.
  2006-01-11 We need a rule for attribution that works as an automatically-acceptable attribution for material.  This is basically like citation, but there needs to be an example.
  2006-01-09 Apply notes #49.58-59 to the creation of the attribution practice.
in progress 2006-01-08 Make work-specific attributions in RDF license information as part of the HTML code of the attribution text.  These do not have to be in comments so long as there is no mixed content or other content text.  N060101c, N060101d, N060101e, N060101f, N060101g
in progress 2006-01-08 For trademarks, use a citation preceding the statement: N060101c, N060101d, N060101e, N060101f, N060101g
in progress 2006-01-08 The attributions about trademarks should provide a citation of the page and then link to the local copy and its cache.  This allows for the appropriate connection of local material that can be consulted without requiring availability of another site or even an internet connection (depending on where the pages have been packaged and/or cached). Correct the links to allow for that once N060101g is in place.
  2006-01-08 This folio is to be an example of how to account for use of a license and the practices around it. It can be referenced from other applications on nfoCentrale sites without having to be replicated.  (Some will be replicated, but much of the documentation and tutorial material can be referenced without duplication).  The other source is TROSTing, which is about the pattern and template for this, rather than this itself.  When TROSTing has that material, this material can cross-reference it.  That material can refer to this and other places as applications of the pattern(s).  Work toward that.
  2006-01-07 For N060101e, find examples of citations in electronic documents (e.g., on the inside title page of a document template and this might have a special form of attribution too - for the template, not documents fashioned wiht it).
  2006-01-07 For N060101e, find examples of citations in text files (e.g., in the manifest for a package). [dh:2006-01-08 This is a good reason to have created a package of this material.]
  2006-01-04 In the handling of derivative works, point out that with this license there is no penalty for assuming that one has created a derivative work and making attribution accordingly.  This is illustrated with N060101c and N060101d where derivative-work status is conceded without concern, regardless of whether it might actually be a compilation.  We don't have to worry about that because it is completely safe to behave as if the overall work is a derived work.  In the case of N060101g, the presence of a derivative is pretty clear, even though it might also, in this case, qualify as fair use.  We don't have to care if we simply provide the necessary attribution.
in progress 2006-01-04 Make sure that the occurrences of the Creative Commons corporate logo and logotype images all link to the creative commons home page and nowhere else: N060101c,  N060101d, N060101e.  Account for all occurrences, with N060101b, and the "you are here" blocks, on the policies-replica page.
in progress 2006-01-04 Review links throughout N060101c through N060101h and have them be in scholarly form and give attribution, however it is asked for: N060101c, N060101d, N060101e,  N060101f,
  2006-01-04 The attributions made in N060101 will provide an example of how it is to work when making attributions to nfoWare material.  I need to have a clear transitive operation.  [dh:2006-01-08 This is intended to be handled in N060101h.]
in progress
2006-01-04		 2006-01-03 Provide the proper attribution on each page for the material used on that page from the Creative Commons site: N060101c, N060101d, N060101e, N060101f, N060101g
  2006-01-03 After the folio is completed and purple-numbered, it can be replicated to ODMdev and backfactored onto TROSTing.
in progress 2006-01-03 Purple-number this material: N060101c, N060101d, N060101e, N060101f, N050101g, N060101h
  2006-01-02 Link N060101e to the N060101f page and other practices pages as they are included
  2006-01-02 The N060101 cover might be the place for "How to Honor this License," and "How to Use This License Yourself" as well as links to places where the principle is described (e.g., at TROSTing.org).
in progress 2006-01-02 Complete the trademark policy links on N060101dg.
in progress
2006-01-04		 2006-01-02 There is a license statement given for the licenses themselves.  Find that on the Creative Commons site and apply its conditions to the portrayals of the licenses here: N060101c, N060101d, N060101e, N060101f, N060101g
  2006-01-02 Consider making N060101i for a set of guidelines for honoring the rules of the game in applying the CC-by 2.5 license, making it easy to honor the license, etc. [dh:2006-01-04 This might work better off of the folio cover.  I am not sure how I want this to work until I have all of the other pieces up to speed.  Maybe N060101h does the job already]
  2006-01-01 The TROST infoNote can be referenced as a resource and for application to other cases. 
in progress
2006-01-04		 2006-01-01 On the deeds and license statements, there needs to be clear cases that these are not covered under the license offered on this site, but under Creative Commons itself.  The attribution policy must make clear exceptions for this and I need to also raise the level of care to avoid enveloping someone else's copyrighted material.  This is similar to the open-source envelop case for material with different authorship and with different license and notice requirements.  [dh:2006-01-01 I think 2.5 is sublicensable.  Check that.  dh:2006-01-02 No, it is explicitly not sublicensable, which means the attribution stack must be preserved.  That is actually how we want it.]
  2006-01-01 Attribution needs to be discussed on the folio cover page along with the other intentions and the trustworthiness angle.
  2006-01-01 The Web Text Notice needs to be modified or augmented by the approach I have used to handle my standard "you are here" and avoidance of filtering as a banner ad.  Maybe I don't need to handle that here, leaving it to the CC site and the TROSTing site.  Well, I need the specific instructions specified for CC-by 2.5.
in progress
2006-01-04		 2006-01-01 Create a generic attribution requirement for these web pages, with examples.  See the note below.
in progress
2013-11-13		 2006-01-01 Test all of the pages and the links in the posted version of this folio, making corrections as needed.
in progress
2006-01-04		 2006-01-01 Do we want to specify a form of attribution for these pages?  [dh:2005-05-04 I don't think it is needed for these pages, although it might be on a copyright page linked from the copyright notice, when there is one.  Attribution is mostly not interesting for ordinary web pages.  But I'm still thinking it over.  Maybe a default when no other attribution is specified.][dh:2005-06-17 Because we need to use normal text links to here and to the license at CC, there is an opportunity to tie to an attribution requirement in conjunction with our inclusion.  This would be preserved and shared under both by2.0 and by2.5.]
  2006-01-01 I need to find a reference for the .mht format and how to view it and how to understand its format, as part of providing a rigorous account for TROSTing.  [dh:2006-01-01 It is also a toolcraft matter.   Need some way to signal that on pages.  Maybe I need a symbol and a way to indicate the particular toolcraft that is involved, not unlike the document-engineering links on professional-appearance NuovoDoc pages.]
done
2006-01-19		 2006-01-08 I am running against the clock on the ODMdev starter kit, which must be moved from Blocco, incorporated in the ODMA Compagno material, and then released on 2006-01-15.  Get this material to the point where the license notices appear on the nfoWare site.  Then move on.  The cloning into ODMdev will not happen until the starter kit is brought under the same VSS and web server.
done 0.50
2006-01-11		 2006-01-08 N060101f needs a description of what the actual form is on nfoWare web pages, illustrated by the current page itself.
done 0.50 2006-01-11 In cleaning up the 0.50 materials, make sure that the explicit-attribution RDF is updated (mainly the date entry): N060101, N060101c, N060101d, N060101e, N060101f
done 0.50
2006-01-11		 2006-01-10 On N060101d-f, attribution/source/revision indentations are all screwy.  Fix them.  Use N060101c as the model.
done 0.50
2006-01-11		 2006-01-10 On N060101c, there's a lot of material that shows up before the Deed is seen.  Maybe a denser, definition-list format would work better instead.
done 0.50 2006-01-11 The NuovoDoc page on ODM licensing is relevant and should be referenced from N060101
done 0.50
2006-01-11		 2006-01-10 On N060101 the version/draft-notice block is no longer needed.  We might need a little table of contents and a synopsis, but that's a different game.
done
2006-01-11		 2006-01-10 The RDF comment has vanished from C000003f, C000004f, and C000005f.  Fix that by putting it where it doesn't disappear.  [dh:2006-01-11 It works between the lines of the text, but not inside the <a> or <img> elements.  It passes through multiple levels of inclusion just fine too.]
done
2006-01-11		 2006-01-02 Review the TROSTing "You are Here" inclusions and their RDF insertions and adapt them to the required Attribution 2.5 form. 
done
2006-01-11		 2006-01-10 We need to make sure that the RDF is not stripped in the default.asp when it is served up.  There may be no way to prevent this.
done 2006-01-10 Make a custom notice inclusion at the default.htm cover page of the front porch
done
2006-01-10		 2006-01-09 Create notice versions for C000003f and see that it can share properly through C000003c.  Then do the same for C000004f and C000005f to get the Attribution 2.5 notices as the ones used by default on all pages.
done 2006-01-10 Bring TROST /construction/c000003c over as nfoWare /construction/c000003f for customizing.
done 2006-01-10 Lift the image called for in the current web-page notice insertion and put it on /images
done
2006-01-10		 2006-01-09 Upload the material to the web site as a safety measure.
done
2006-01-09		 2006-01-02 Tie N060101e to other material and make sure it is reachable from other material.  This is about how we make notices.
done 0.50 2006-01-09 Redo the folio cover to reflect where were are in this particular folio, simplifying as appropriate.
done 0.50
2006-01-08		 2006-01-02 There is a PDF and Adobe XMP case as well, although Microsoft Word 2003 output as PDF preserves a non-web text notice and its links (double-check that).  Tie that into the N060101e material.
done 0.50 2006-01-08 Cite the metadata and RDF information resources and discuss them on: N060101e, N060101f
done 0.50 2006-01-08 Update N060101f to match the style of the earlier folio pages.  Adjust the citations to make it clear that this is a procedure we are adopting, based on models from the Creative Commons site.  Cross link back and forth to the N060101e page. 
done 0.50
2006-01-07		 2006-01-04 Update N060101e to match the style of the earlier folio pages.  Adjust the citations to make it clear that this is a procedure we are adopting, based on models from the Creative Commons site.
done 0.50 2006-01-04 On the deed replica, N060101c, give self-attribution and update the top block to include better support for satisfying attribution requirements.
done 0.50
2006-01-04		 2006-01-01 Attribution needs to be a new bullet at the top of the deed specimen. [dh:2006-01-02 Yes, this is needed on N060101c.]
done 0.50 2006-01-04 On the deed replica, N060101c, give attribution to the Creative Commons Trademark policy and assert compliance with that policy.
done 0.50 2006-01-04 On the deed replica, N060101c, give attribution to the original source in the manner specified by the Attribution 2.5 license. 
done
2006-01-04		 2006-01-03 Download the latest policy statement and cache it in the folio. [dh:2006-01-04 In N060101g.mht]
done 0.50 2006-01-04 On the deed replica, N060101c, change the "By:" image, a Creative Commons License Button, to refer to the Creative Commons license page that describes the symbol and use the "Attribution" alternate text in compliance with the Creative Commons Trademark Policy.
done 0.50 2006-01-04 On the deed replica, N060101c, change the "Commons Deed" image that includes the Creative Commons logotype to link directly to the Creative Commons home page and provide the "Creative Commons" alternate text, in compliance with the Creative Commons Trademark Policy.
done 0.00
2006-01-04		 2006-01-03 Create a version-progression block on N060101g.
done 0.00
2006-01-04		 2006-01-04 Make a version control progression block on N060101h.
done 0.00
2006-01-04		 2006-01-02 Make N060101h into the attribution default page. [dh:2006-01-04 This is just a placeholder and it should be an example of what we do and how to do likewise, or something like that.]
done 0.00
2006-01-03		 2006-01-02 Make N060101g into the trademark policies page.
done
2006-01-03		 2006-01-02 Add a version-progression block and some front matter to N060101f so there is some context.  [dh:2006-01-02 I also introduced a specimen of what the notice looks like.]
done 2006-01-03 Change the title of N060101f and also link to the use of the image on N060101e.
done 2006-01-02 Make N060101f into the trademark policy information and cache. [dh:2006-01-02 web-notice procedure]
done 2006-01-02 The current image is a .png according to the web-inclusion instructions.  Use it on N060101e.  It must be used on all web-page notices too.
done 2006-01-02 Give the N060101e page a version-progression history block too.
done
2006-01-02		 2006-01-01 Make N060101e into the initial cache of the web-page instructions. [dh:2006-01-02 text-notice procedure]
done 0.10 2006-01-02 Make N060101b take N060101c as the current material.
done 0.10 2006-01-02 Add a version-progression block to N060101c.
done 0.10 2006-01-02 Complete the deed links on N060101d
done 0.10
2006-01-02		 2006-01-01 Make N060101c into the initial deed document cache.
done 0.10 2006-01-02 Add a version-progression block to N060101d for tracking versions of the Legal Code.
done
2006-01-02		 2006-01-01 Make N060101d into the initial cache of the full-text license.
done
2006-01-02		 2006-01-01 Version this page
done
2006-01-02		 2006-01-01 Make N060101b into a standard top-level summary.  [dh:2006-01-02 We technically don't need an include case, but it is worthwhile to do document-engineering anyhow.  Start with the usual placeholder, then include from the proper section.]
done 2006-01-02 The N051201 placeholder is not needed.  It serves as a source of copies for customization though.  Bring it over to N060102 as a source there.
done 2006-01-01 Review the scavenged items brought over with this page for what's needed here on N060101.
done 2006-01-01 Create this page with the Lab Notebook folio style, customizing from TROST infoNote i050403a
Revision History:
0.00 2006-01-01-21:08 Prepare Creative Commons License Folio for nfoWare
The TROSTing InfoNote i050403 work items that apply to adoption of the Creative Commons Attribution 2.5 license are adapted here and further work items and notes captured.
Construction Structure (Hard Hat Area)
Creative Commons License You are navigating nfoWare.
This work is licensed under a
Creative Commons Attribution 2.5 License.

created 2006-01-01-21:08 -0800 (pst) by orcmid
$$Author: Orcmid $
$$Date: 13-11-13 9:11 $
$$Revision: 65 $