This repository was archived by the owner on Mar 14, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathabout_spec.html
More file actions
804 lines (680 loc) · 29 KB
/
about_spec.html
File metadata and controls
804 lines (680 loc) · 29 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
<!DOCTYPE html>
<!-- paulirish.com/2008/conditional-stylesheets-vs-css-hacks-answer-neither/ -->
<!--[if lt IE 7]> <html class="no-js lt-ie9 lt-ie8 lt-ie7" lang="en"> <![endif]-->
<!--[if IE 7]> <html class="no-js lt-ie9 lt-ie8" lang="en"> <![endif]-->
<!--[if IE 8]> <html class="no-js lt-ie9" lang="en"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en"> <!--<![endif]-->
<head>
<meta charset="utf-8" />
<!-- Set the viewport width to device width for mobile -->
<meta name="viewport" content="width=device-width" />
<title>ABOUT file specification v0.8.1</title>
<meta name="Description" content="The purpose of an ABOUT file is to provide a simple way to document the provenance (origin and license) and other important or interesting information about a software component."/>
<meta name="keywords" content="DejaCode.org, automated compliance, ABOUT file, manage open source requirements, license requirements, DejaCode, document provenance, origin and license of software components, origin and license tools" />
<!-- Included CSS Files (Uncompressed) -->
<!--
<link rel="stylesheet" href="stylesheets/foundation.css">
-->
<!-- Included CSS Files (Compressed) -->
<link rel="stylesheet" href="stylesheets/foundation.css">
<link rel="stylesheet" href="stylesheets/app.css">
<link href='http://fonts.googleapis.com/css?family=Lato|Open+Sans:400,300' rel='stylesheet' type='text/css'>
<script src="javascripts/modernizr.foundation.js"></script>
<script src="javascripts/ga-dejacode_org.js" type="text/javascript"></script>
</head>
<body>
<!-- GitHub Ribbon-->
<a href="https://github.com/dejacode/about-code-tool">
<img style="position: absolute; top: 0; left: 0; border: 0;"
src="https://s3.amazonaws.com/github/ribbons/forkme_left_orange_ff7600.png"
alt="Fork me on GitHub">
</a>
<!-- End GitHub Ribbon-->
<!-- Nav Bar -->
<div class="row">
<div class="five columns">
<h1><a href="index.html"><span class="logo"><img src="images/dejacodeorg-logo.png" alt="dejacode.org"/></span></a></h1>
</div>
</div>
<div class="row">
<div class="twelve columns">
<h2>ABOUT File Specification v0.8.1</h2>
<hr />
</div>
</div>
<!-- End Nav -->
<!-- Main Page Content and Sidebar -->
<div class="row">
<div class="nine columns" role="content">
<h2>
Purpose
</h2>
<p>
An ABOUT file provides a simple way to document the provenance (origin and
license) and other important or interesting information about a software component.
An ABOUT file is a small text file stored in the codebase side-by-side
with the software component file or archive that it documents.
No modification of the documented software is needed.
</p>
<p>The ABOUT format is plain text with field name/value pairs separated by a colon.
It is easy to read and create by hand and is designed first for humans,
rather than machines. The format is well-defined and structured just
enough to make it easy to process with software as well.
It contains enough information to fulfill key license requirements such
as creating credits or attribution notices, collecting redistributable
source code, or providing information about new versions of a software component.
</p>
<h2>
Getting Started
</h2>
<p>
A simple and valid ABOUT file named httpd.ABOUT may look like this:
</p>
<pre>
about_resource: httpd-2.4.3.tar.gz
name: Apache HTTP Server
version: 2.4.3
home_url: http://httpd.apache.org
download_url: http://archive.apache.org/dist/httpd/httpd-2.4.3.tar.gz
license_text_file: httpd.LICENSE
notice_file: httpd.NOTICE
copyright: Copyright (c) 2012 The Apache Software Foundation.
license_spdx: Apache-2.0
</pre>
<p>
The meaning of this ABOUT file is:
</p>
<ul>
<li>
The file "httpd-2.4.3.tar.gz" is stored in the same directory and side-by-side with the ABOUT file "httpd.ABOUT" that documents it.
</li>
<li>
The name of this component is "Apache HTTP Server" with version "2.4.3".
</li>
<li>
The home URL for this component is
<a href="http://httpd.apache.org">
http://httpd.apache.org
</a>
</li>
<li>
The file "httpd-2.4.3.tar.gz" was originally downloaded from
<a href="http://archive.apache.org/dist/httpd/httpd-2.4.3.tar.gz">
http://archive.apache.org/dist/httpd/httpd-2.4.3.tar.gz
</a>
</li>
<li>
In the same directory, "httpd.LICENSE" and "httpd.NOTICE" are files that contain respectively the license text
and the notice text for this component.
</li>
<li>
This component
<a href="http://spdx.org/licenses/">
SPDX license identifier
</a>
is "Apache-2.0"
</li>
</ul>
<h2>
Specification
</h2>
<p>
An ABOUT file is an ASCII text file with lines of colon-separated "field name":"value" pairs.
This format is loosely based on the Email header field format as specified in RFC5322/RFC822 at
<a href="http://tools.ietf.org/html/rfc5322">
http://tools.ietf.org/html/rfc5322
</a>.
By reusing this specification, several available tools and libraries can parse and interpret ABOUT files.
Note that while Unicode characters are not supported in an ABOUT file proper, external files can contain UTF-8 Unicode.
</p>
<h3>
ABOUT file name
</h3>
<p>
An ABOUT file name can use a limited set of characters and is suffixed
with a ".ABOUT" extension using any combination of uppercase and lowercase characters.
</p>
<p>
A file name can contain only these US-ASCII characters:
<li> digits from 0 to 9 </li>
<li> uppercase and lowercase letters from A to Z</li>
<li> the "_" underscore, "-" dash and "." period signs. </li>
</p>
<p>
The case of a file name is not significant.
On case-sensitive file systems (such as on Linux), a tool must report an
error if two ABOUT files stored in the same directory have the same lowercase file name.
This is to ensure that ABOUT files can be used across file systems.
The convention is to use a lowercase file name and an uppercase ABOUT extension.
</p>
<h3>
Lines of text
</h3>
<p>
An ABOUT file contains lines of US-ASCII text.
Lines contain field names/values pairs.
The standard line ending is the LF character.
The line ending characters can be any LF, CR or CR/LF and tools must
normalize line endings to LF when processing an ABOUT file.
Empty lines and lines containing only white spaces that are not part of a
field value continuation are ignored.
Empty lines are commonly used to improve the readability of an ABOUT file.
</p>
<h3>
Field name
</h3>
<p>
A field name can contain only these US-ASCII characters:
<li> digits from 0 to 9 </li>
<li> uppercase and lowercase letters from A to Z</li>
<li> the "_" underscore sign. </li>
</p>
<p>
Field names are not case sensitive. For example, "HOME_URL"
and "Home_url" represent the same field name.
</p>
<p>
A field name must start at the beginning of a new line.
It can be followed by one or more spaces that must be ignored.
These spaces are commonly used to improve the readability of an ABOUT file.
</p>
<h3>
Field value
</h3>
<p>
The field value is separated from the field name by a ":" colon.
The ":" colon can be followed by one or more spaces that must be ignored.
This also applies to trailing white spaces: they must be ignored.
</p>
<p>
The field value is composed of one or more lines of plain US-ASCII printable text.
</p>
<p>
When a field value contains more than one line of text,
additional continuation lines must start with at least one space.
In this case, the first space of an additional continuation line is
ignored and should be removed from the field value by tools.
</p>
<p>
In this example the value of the description field spans multiple lines:
</p>
<pre>
description: This is a long description for a
software component that spans multiple lines with arbitrary line breaks.
</pre>
<h3>
Fields are mandatory or optional
</h3>
<p>
As defined in this specification, a field can be mandatory or optional.
Tools must report an error for missing mandatory fields.
</p>
<h3>
Extension and ignored fields
</h3>
<p>
An ignored field is a field with a name that is not defined in this specification.
Custom extension fields are also supported and must be processed by tools as ignored fields unless a certain tool can process a certain extension field.
</p>
<h3>
Fields validation
</h3>
<p>
When processing an ABOUT file, tools must report a warning or error if
a field is invalid.
A field can be invalid for several reasons, such as invalid field name
syntax or invalid content.
Tools should report additional validation error details.
The validation process should check that each field name is
syntactically correct and that fields contain correct values according to
its concise, common sense definition in this specification.
For certain fields, additional and specific validations are relevant such as
checksum verification, URL validation, path resolution and verification, and so forth.
Tools should report a warning for ignored fields.
</p>
<h3>
Fields order and precedence
</h3>
<p>
The field order does not matter with the following exception:
multiple occurrences of a field name are possible and must be interpreted
such that only the last occurrence is considered as the value for this
field name.
Previous occurrences of the same field name must be treated as ignored fields.
</p>
<p>
A tool processing an ABOUT file must issue a warning when a field name
occurs more than once in an ABOUT file (as for any other ignored field).
</p>
<h3>
Field referencing a file
</h3>
<p>
The actual value of some fields may be contained in another file.
This is useful for long texts or to reference a common text in multiple ABOUT files such as a common license text.
In this case the field name is suffixed with "_file" and the
field value must be a path pointing to the file that contains the actual value of the field.
This path must be a POSIX path relative to the path of the ABOUT file.
The file content must be UTF-8-encoded text. This is in contrast with field
values contained directly in an ABOUT file that must be US-ASCII-encoded text and allows to support non-ASCII text content.
</p>
<p>
When an ABOUT file contains both a field name and a _file-suffixed field for the same field name,
both fields must be treated as multiple occurrences of the same field name.
This must be interpreted such that only the last occurrence is considered as the value for this
field name.
</p>
<p>
For example, the full license text for a component is often stored in a separate file named COPYING:
</p>
<pre>
license_text_file: linux.COPYING
</pre>
<p>
In this example, the README file is stored in a doc directory, one directory above the ABOUT file directory, using a relative POSIX path:
</p>
<pre>
license_text_file: ../docs/ruby.README
</pre>
<h3>
Field referencing a URL
</h3>
<p>
The value of a field may reference URLs such as a homepage or a download. In this case the field name is suffixed
with "_url" and the field value must be a valid absolute URL starting with ftp://, http:// or https://.
URLs are informational and the content they may reference is ignored.
For example, a download URL is referenced this way:
</p>
<pre>
download_url: http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.4.20.tar.bz2
</pre>
<h3>
Flag fields
</h3>
<p>
Flag fields have a "true" or "false" value.
True, T, Yes or Y must be interpreted as "true" in any case combination.
False, F, No or N must be interpreted as "false" in any case combination.
</p>
<h3>
Referencing the file or directory documented by an ABOUT file
</h3>
<p>
An ABOUT file documents one file or directory. The mandatory
"about_resource" field points to the documented file or directory.
The value of the "about_resource" field can be a name stored in the same
directory as the ABOUT file
or a POSIX path relative to the path of the ABOUT file.
POSIX paths use a "/" forward slash sign as path separators.
</p>
<p>
A tool processing an ABOUT file must report an error if this field is missing.
</p>
<p>
By convention, an ABOUT file is often stored in the same directory side-by-side to
the file or directory that it documents, but this is not mandatory.
</p>
<p>
For example, a file named django.ABOUT contains the following field to document the
django-1.2.3.tar.gz archive stored in the same directory:
</p>
<pre>
about_resource: django-1.2.3.tar.gz
</pre>
<p>
In this example, the ABOUT file documents a whole sub-directory:
</p>
<pre>
about_resource: downloads/linux-kernel-2.6.23/
</pre>
<p>
In this example, the ABOUT file documents the current directory, using a "." period to reference it:
</p>
<pre>
about_resource: .
</pre>
<p>
Since all paths are interpreted relative to the ABOUT file location, this would also reference the current directory:
</p>
<pre>
about_resource: /
</pre>
<h3>
Other Mandatory fields
</h3>
<p>
When a tool processes an ABOUT file, it must issue an error if these mandatory field are missing.
</p>
<ul>
<li>
name: Component name.
</li>
<li>
version: Component version. A component usually has a version, such as a revision number or
hash from a version control system (for a snapshot checked out from VCS such as Subversion or Git). If not
available, the version should be the date the component was provisioned, in an ISO date format such as 'YYYY-MM-DD'.
</li>
</ul>
<h3>
Optional Information fields
</h3>
<ul>
<li>
spec_version: The version of the ABOUT file format specification used for this file.
This is provided as a hint to readers and tools in order to support future versions of this specification.
</li>
<li>
description and description_file: Component description, as a short text or an external file.
</li>
<li>
download_url: A direct URL to download the original file or archive documented by this ABOUT file.
</li>
<li>
home_url: URL to the homepage for this component.
</li>
<li>
date: The date ('YYYY-MM-DD') when this ABOUT file was created or last validated (such as the date
when the URLs were verified). ISO date format such as 'YYYY-MM-DD'.
</li>
readme and readme_file: Readme information for the component, as a short text or an external file.
</li>
<li>
changelog and changelog_file: Changelog text for the component, as a short text or an external file.
</li>
<li>
news and news_file: News text for the component, as a short text or an external file.
</li>
<li>
news_url: URL to a news feed for the component.
</li>
<li>
notes and notes_file: Notes and comments about the component, as a short text or an external file.
</li>
</ul>
<h3>
Optional Owner and Author fields
</h3>
<ul>
<li>
owner: The name of the primary organization or person(s) that owns or provides the component.
</li>
<li>
contact: Contact information (such as an email address or physical address) for the component owner.
</li>
<li>
author and author_file: Name of the organization(s) or person(s) that authored the component, as a short text or an external file.
</li>
</ul>
<h3>
Optional Licensing fields
</h3>
<ul>
<li>
copyright and copyright_file: Copyright statement for the component, as a short text or an external file.
</li>
<li>
notice and notice_file: Legal notice or credits for the component, as a short text or an external file.
</li>
<li>
notice_url: URL to a legal notice for the component.
</li>
<li>
license_text and license_text_file: License text that applies to the component, as a short text or an external file.
For example, the name of a license file such as LICENSE or COPYING file extracted from a downloaded archive.
</li>
<li>
license_url: URL to the license text for the component.
</li>
<li>
license_spdx: The SPDX license short form identifiers for the license of this component. See
<a href="http://spdx.org/licenses/">
http://spdx.org/licenses/
</a>
for details. You can separate each identifier using " or " and " and " as defined in the
SPDX specification 1.1 to document the relationship between multiple license identifiers, such as a choice among
multiple licenses. The case of the SPDX ID is not significant, such that APACHE-1.1 and apache-1.1 are the same field value.
Tools should normalize the case of the ID to be the official case sensitive SPDX ID.
</li>
<h3>
Optional Licensing flag fields
</h3>
<ul>
<li>
redistribute: Set this flag to yes if the component license requires source code redistribution.
Defaults to no when absent.
</li>
<li>
attribute: Set this flag to yes if the component license requires publishing an attribution or credit notice.
Defaults to no when absent.
</li>
<li>
track_changes: Set this flag to yes if the component license requires tracking changes made to a the component.
Defaults to no when absent.
</li>
</ul>
<h3>
Optional Extension fields
</h3>
<p>
You can create extension fields by prefixing them with a short prefix to distinguish these from the standard
fields. You should provide documentation for these extensions and create or extend existing tools to support
these extensions. Other tools must ignore these extensions.
</p>
<h3>
Optional Extension fields to reference files stored in a version control system (VCS)
</h3>
<p>
These fields provide a simple way to reference files stored in a version control system.
There are many VCS tools such as CVS, Subversion, Git, ClearCase and GNU Arch.
Accurate addressing of a file or directory revision in each tool in a uniform way may not be possible.
Some tools may require access control via user/password or certificate and this information should not be stored in an ABOUT file.
This extension defines the "vcs_" field extension prefix and a few common fields to handle the
diversity of ways that VCS tools reference files and directories under version control:
</p>
<ul>
<li>
vcs_tool: VCS tool such as git, svn, cvs, etc.
</li>
<li>
vcs_repository: Typically a URL or some other identifier used by a VCS tool to point to a repository such as an SVN or Git repository URL.
</li>
<li>
vcs_path: Path used by a particular VCS tool to point to a file, directory or module inside a repository.
</li>
<li>
vcs_tag: tag name or path used by a particular VCS tool.
</li>
<li>
vcs_branch: branch name or path used by a particular VCS tool.
</li>
<li>
vcs_revision: revision identifier such as a revision hash or version number.
</li>
</ul>
<p>
Some examples for using the vcs_* extension fields include:
</p>
<pre>
vcs_tool: svn
vcs_repository: http://svn.code.sf.net/p/inkscape/code/inkscape_project/
vcs_path: trunk/inkscape_planet/
vcs_revision: 22886
</pre>
<p>
or
</p>
<pre>
vcs_tool: git
vcs_repository: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
vcs_path: tools/lib/traceevent
vcs_revision: b59958d90b3e75a3b66cd311661535f94f5be4d1
</pre>
<h3>
Optional Extension fields for checksums and digital signatures
</h3>
<p>
These fields support checksums (such as SHA1 and MD5) and signatures (such as GPG) commonly provided with downloaded
archives to verify their integrity. A tool can optionally use these to verify the integrity of a file documented
by an ABOUT file.
This extension defines the "checksum_" and "signature_" field extension prefixes with
suffix identifiers of the type of signature or checksum such as in "checksum_sha1".
</p>
<ul>
<li>
checksum_sha1, checksum_md5, checksum_sha256, checksum_sha512:
Checksum for the file documented by this ABOUT file in the "about_resource" field.
The suffix defines the checksum algorithm such as "_md5", "_sha1", "_sha256". The
checksum algorithms and formats are as defined in the GNU Coreutils tools md5sum, sha1sum and sha256sum commands (
<a href="http://www.gnu.org/software/coreutils/">
http://www.gnu.org/software/coreutils/
</a>
) that follow the specifications defined in the FIPS-180-2 standard (
<a href="http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf">
http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf
</a>
). Files can be referenced with the "_file" suffix such as with "checksum_sha1_file" to
reference checksums files commonly provided such as here:
<a href="http://mirrors.ibiblio.org/maven2/org/jdom/jdom/1.1.2/jdom-1.1.2-javadoc.jar.md5">
http://mirrors.ibiblio.org/maven2/org/jdom/jdom/1.1.2/jdom-1.1.2-javadoc.jar.md5
</a>
</li>
<li>
signature_gpg, signature_gpg_file, signature_pgp, signature_pgp_file:
Signature or external signature file for the file documented by this ABOUT file in the "about_resource" field.
Signature files for GPG and PGP are commonly provided to verify code archives integrity and provenance such as here:
<a href="http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.1.7.tar.sign">
http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.1.7.tar.sign
</a> or here:
<a href="http://archive.apache.org/dist/maven/plugins/maven-acr-plugin-1.0-source-release.zip.asc">
http://archive.apache.org/dist/maven/plugins/maven-acr-plugin-1.0-source-release.zip.asc
</a> or here:
</li>
</ul>
<p>
Some examples:
</p>
<pre>
signature_gpg_file: signature/linux-3.1.7.tar.sign
checksum_md5: f30b9c173b1f19cf42ffa44f78e4b96c
</pre>
<h3>
Optional Extension fields for DejaCode Enterprise
</h3>
<p>
These fields provide a reference to DejaCode Enterprise objects via a URN, key or name.
</p>
<ul>
<li>
dje_component: The DejaCode Enterprise component URN or component name for the component.
</li>
<li>
dje_license: The DejaCode Enterprise license URNs, license name or license key for the component.
</li>
<li>
dje_owner: The DejaCode Enterprise owner URN for the component.
</li>
</ul>
<h3>
Changes
</h3>
<ul>
<li>
2013.02.19: Add Changes section. Remove ability to reference files inside an archive.
</li>
<li>
2013.02.22: Multiple text clarifications throughout the specification.
</li>
<li>
2013.05.03: Renamed about_file to about_resource, and also made about_resource a mandatory field.
</li>
<li>
2013.05.13: Introduced flags and renamed organization-related fields to owner.
Use directory instead of folder consistently in the spec.
Use value instead of body consistently in the spec.
Renamed the scm extension to vcs (version control system).
Streamlined and clarified several sections of the spec.
Explained how a field and a field_file relate to each other.
</li>
<li>
2013.06.18: removed fields that are not necessary: modified, usage.
Added details on file content and line endings.
Added redistribute and attribute flags. Added author related fields.
</li>
<li>
2013.08.08: Text clarifications and fixed typos.
</li>
</ul>
<div id="disqus_thread" >
<script type="text/javascript">
var disqus_developer = 1; // developer mode is on
var disqus_shortname = 'dejacode';
/* * * DON'T EDIT BELOW THIS LINE * * */
(function() {
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js';
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
})();
</script>
<noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
<a href="http://disqus.com" class="dsq-brlink">comments powered by <span class="logo-disqus">Disqus</span></a>
</div>
</div>
<!-- End Main Content -->
<!-- Sidebar -->
<aside class="three columns">
<div class="panel">
<h5><a href="https://github.com/dejacode/about-code-tool">Download the ABOUT Project</a></h5>
<h5><a href="about_spec_v0.8.1.html">Read the ABOUT specification</a></h5>
<h5><a href="android_case_study.html">Android Compliance Case Study </a></h5>
<h5><a href="healthcare_case_study.html">Healthcare.gov Case Study </a></h5>
<h5><a href="index.html#nexb">Who are we?</a></h5>
</div>
</aside>
<!-- End Sidebar -->
</div>
<!-- End Main Content and Sidebar -->
<!-- Footer -->
<footer class="row">
<div class="twelve columns">
<hr />
<div class="row">
<div class="six columns">
<p><a href="http://www.nexb.com" target="_blank">© 2014 nexB, Inc.</a></p>
</div>
<div class="six columns">
<ul class="link-list right">
<li style="margin-left: 8px;"><a href="http://www.facebook.com/pages/nexB/113981918705301?sk=wall"><img src="images/fc-webicon-facebook-s.png" alt="nexB Facebook"/></a></li>
<li style="margin-left: 8px;"><a href="http://twitter.com/#!/dejacode"><img src="images/fc-webicon-twitter-s.png" alt="@dejacode"/></a></li>
<li style="margin-left: 8px;"><a href="http://www.linkedin.com/company/nexb"><img src="images/fc-webicon-linkedin-s.png" alt="nexB Linked In"/></a></li>
</ul>
</div>
</div>
</div>
</footer>
<!-- End Footer -->
<!-- Included JS Files (Uncompressed) -->
<!--
<script src="javascripts/jquery.js"></script>
<script src="javascripts/jquery.foundation.mediaQueryToggle.js"></script>
<script src="javascripts/jquery.foundation.forms.js"></script>
<script src="javascripts/jquery.foundation.reveal.js"></script>
<script src="javascripts/jquery.foundation.orbit.js"></script>
<script src="javascripts/jquery.foundation.navigation.js"></script>
<script src="javascripts/jquery.foundation.buttons.js"></script>
<script src="javascripts/jquery.foundation.tabs.js"></script>
<script src="javascripts/jquery.foundation.tooltips.js"></script>
<script src="javascripts/jquery.foundation.accordion.js"></script>
<script src="javascripts/jquery.placeholder.js"></script>
<script src="javascripts/jquery.foundation.alerts.js"></script>
<script src="javascripts/jquery.foundation.topbar.js"></script>
<script src="javascripts/jquery.foundation.joyride.js"></script>
<script src="javascripts/jquery.foundation.clearing.js"></script>
<script src="javascripts/jquery.foundation.magellan.js"></script>
-->
<!-- Included JS Files (Compressed) -->
<script src="javascripts/jquery.js"></script>
<script src="javascripts/foundation.min.js"></script>
<!-- Initialize JS Plugins -->
<script src="javascripts/app.js"></script>
</body>
</html>