Current version: 1.1.0 (2017-05-10). Maintained by Mark Jordan and Nick Ruest.
Current version: 1.2.0 (2018-12-03). Maintained by Mark Jordan and Nick Ruest.
Original draft created by members of the Access 2012 Hackfest group: Meghan Currie, Krista Godfrey, Mark Jordan, Nick Ruest, William Wueppelmann, and Dan Chudnov.
@@ -55,7 +55,26 @@ The following fields make up a BagIt profile. Each field is a top-level JSON key
1.`BagIt-Profile-Info`:
A list of tags that describes the profile itself. The following tags are required in this section: "Source-Organization", "External-Description", "Version", and "BagIt-Profile-Identifier". The first two of these tags are taken from the reserved tags defined in the BagIt spec. The value of "Version" contains the version of the profile; the value of "BagIt-Profile-Identifier" is the URI where the profile file is available, and will have the same value as the "BagIt-Profile-Identifier" tag in bag-info.txt (see below). Inclusion of "Contact-Name," "Contact-Phone" and "Contact-Email," as defined in the BagIt spec, is not required but is encouraged.
A list of tags that describes the profile itself. The following tags are
required in this section: `Source-Organization`, `External-Description`,
`Version`, and `BagIt-Profile-Identifier`. Starting with version [`v1.2.0`],
`BagIt-Profile-Version` is also required.
The `Source-Organization` and `External-Description` tags are taken from the
[reserved tags defined in the BagIt spec](https://tools.ietf.org/html/rfc8493#page-10).
The value of `Version` contains the version of the profile; the value of
`BagIt-Profile-Identifier` is the URI where the profile file is available, and
will have the same value as the `BagIt-Profile-Identifier` tag in bag-info.txt
(see below).
The value of `BagIt-Profile-Version` contains the version of this specification the
profile.conforms to. Since the tag was introduced after version [`v1.1.0`], any
profile not explicitly defining `BagIt-Profile-Version` should be treated as
conforming to version [`1.1.0`] of this specification.
Inclusion of `Contact-Name,``Contact-Phone` and `Contact-Email,`
as [defined in the BagIt spec](https://tools.ietf.org/html/rfc8493#page-10), is not required but is encouraged.
2.`Bag-Info`:
@@ -93,13 +112,28 @@ the complete filename), e.g. `["sha1", "md5"]`.
9.`Tag-Files-Required`: LIST
A list of a tag files that must be included in a conformant Bag. Entries are full path names relative to the Bag base directory. As per the [BagIt Spec](http://tools.ietf.org/html/draft-kunze-bagit-08), these tag files need not be listed in tag manifiest files. `Tag-Files-Required` SHOULD NOT include `bag-info.txt` (which is always required), nor any required manifest files, which instead are required by `Manifests-Required` and `Tag-Manifests-Required`.
A list of a tag files that must be included in a conformant Bag. Entries are full path names relative to the Bag base directory. As per the [BagIt Spec](https://tools.ietf.org/html/rfc8493), these tag files need not be listed in tag manifest files. `Tag-Files-Required` SHOULD NOT include `bag-info.txt` (which is always required), nor any required manifest files, which instead are required by `Manifests-Required` and `Tag-Manifests-Required`.
Every file in `Tag-Files-Required` must also be present in `Tag-Files-Allowed`.
10.`Tag-Files-Allowed`: LIST
*(Added in [`v1.2.0`])*
A list of tag files that may be included in a conformant Bag. Entries are either full path names relative to the bag base directory or path name patterns in which asterisks can represent zero or more characters (c.f. [glob(7)](http://man7.org/linux/man-pages/man7/glob.7.html)).
If `Tag-Files-Allowed` is not provided, its value is assumed to be `['*']`, i.e. all tag files are allowed.
As per the [BagIt Spec](https://tools.ietf.org/html/rfc8493), these tag files need not be listed in tag manifest files. `Tag-Files-Required` SHOULD NOT include `bag-info.txt` (which is always required), nor any required manifest files, which instead are required by `Manifests-Required` and `Tag-Manifests-Required`.
At least all the tag files listed in `Tag-Files-Required` must be in included in `Tag-Files-Allowed`.
0 comments on commit
aaace1b