Skip to content

Fix some typos (found by codespell) #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
stweil wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix some typos (found by codespell) #14

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion METS2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -398,7 +398,7 @@ Note in this case the `<fileGrp>` elements are preserved, and the multiple `<str

## METS Profiles

For METS 1 one important feature has been [METS profiles](https://www.loc.gov/standards/mets/mets-profiles.html). These allow implementors to describe a class of METS documents in sufficient detail to provide both document authors and programmers the guidance they require to create and process METS documents conforming with a particular profile. Profiles describe what METS elements are expected to be present and how they will be used in a particular application. Implementors may register the profile for purposes around re-use or interoperability, or may use profiles primarily for internal documentation.
For METS 1 one important feature has been [METS profiles](https://www.loc.gov/standards/mets/mets-profiles.html). These allow implementers to describe a class of METS documents in sufficient detail to provide both document authors and programmers the guidance they require to create and process METS documents conforming with a particular profile. Profiles describe what METS elements are expected to be present and how they will be used in a particular application. Implementers may register the profile for purposes around reuse or interoperability, or may use profiles primarily for internal documentation.

### METS Profiles for METS 2

Expand Down
2 changes: 1 addition & 1 deletion v2/mets2.xsd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -325,7 +325,7 @@ A &lt;fileGrp&gt; may contain zero or more &lt;file&gt; elements.
<xsd:complexType name="mdSecType">
<xsd:annotation>
<xsd:documentation xml:lang="en">mdSecType: Complex Type for Metadata Sections
The metadata section consists of elements that can contain any kind of metdata, included but not limited to technical metadata technical metadata for text/image/audio/video files, intellectual property rights metadata, analog/digital source metadata, and digital provenance metadata, that is, the history of migrations/translations performed on a digital library object from it's original digital capture/encoding.
The metadata section consists of elements that can contain any kind of metadata, included but not limited to technical metadata technical metadata for text/image/audio/video files, intellectual property rights metadata, analog/digital source metadata, and digital provenance metadata, that is, the history of migrations/translations performed on a digital library object from it's original digital capture/encoding.
</xsd:documentation>
</xsd:annotation>
<xsd:choice>
Expand Down
6 changes: 3 additions & 3 deletions version112/mets.xsd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ mptr and area elements for mapping MPEG21 DII Identifier values
3. Add an MDTYPEVERSION attribute as a companion to the MDTYPE attribute in the mdRef and mdWrap elements.
4. ID and STRUCTID attributes on the behavior element made optional. Depending on whether the behavior applies to a transformFile element or div elements in the structMap, only one or the other of the attributes would pertain.
5. Documentation aligned with the METS Primer, and corrected.
6. xml:lang="en" atttribute value added to every <documentation> element
6. xml:lang="en" attribute value added to every <documentation> element
7. xlink:extendedLink support added to the <structLink> element by means of a new <smLinkGrp> element, and its child <smLocatorLink> and <smArcLink> elements.
-->
<!--February 2010: Version 1.9-->
Expand Down Expand Up @@ -840,7 +840,7 @@ to clarify the differences between the ORDER, ORDERLABEL, and LABEL attributes f
</xsd:attribute>
<xsd:attribute name="SHAPE" use="optional">
<xsd:annotation>
<xsd:documentation xml:lang="en">SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the &lt;area&gt; element. Typically this would be used with image content (still image or video frame) when only a portion of an integal image map pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML4 &lt;area&gt; element. SHAPE must contain one of the following values:
<xsd:documentation xml:lang="en">SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the &lt;area&gt; element. Typically this would be used with image content (still image or video frame) when only a portion of an integral image map pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML4 &lt;area&gt; element. SHAPE must contain one of the following values:
RECT
CIRCLE
POLY
Expand Down Expand Up @@ -1636,7 +1636,7 @@ DDI: Data Documentation Initiative
FGDC: Federal Geographic Data Committee metadata
LOM: Learning Object Model
PREMIS: PREservation Metadata: Implementation Strategies
PREMIS:OBJECT: PREMIS Object entiry
PREMIS:OBJECT: PREMIS Object entity
PREMIS:AGENT: PREMIS Agent entity
PREMIS:RIGHTS: PREMIS Rights entity
PREMIS:EVENT: PREMIS Event entity
Expand Down
6 changes: 3 additions & 3 deletions version1121/mets.xsd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@
3. Add an MDTYPEVERSION attribute as a companion to the MDTYPE attribute in the mdRef and mdWrap elements.
4. ID and STRUCTID attributes on the behavior element made optional. Depending on whether the behavior applies to a transformFile element or div elements in the structMap, only one or the other of the attributes would pertain.
5. Documentation aligned with the METS Primer, and corrected.
6. xml:lang="en" atttribute value added to every &lt;documentation&gt; element
6. xml:lang="en" attribute value added to every &lt;documentation&gt; element
7. xlink:extendedLink support added to the &lt;structLink&gt; element by means of a new &lt;smLinkGrp&gt; element, and its child &lt;smLocatorLink&gt; and &lt;smArcLink&gt; elements.
</xsd:documentation>

Expand Down Expand Up @@ -914,7 +914,7 @@ to clarify the differences between the ORDER, ORDERLABEL, and LABEL attributes f
</xsd:attribute>
<xsd:attribute name="SHAPE" use="optional">
<xsd:annotation>
<xsd:documentation xml:lang="en">SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the &lt;area&gt; element. Typically this would be used with image content (still image or video frame) when only a portion of an integal image map pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML4 &lt;area&gt; element. SHAPE must contain one of the following values:
<xsd:documentation xml:lang="en">SHAPE (string/O): An attribute that can be used as in HTML to define the shape of the relevant area within the content file pointed to by the &lt;area&gt; element. Typically this would be used with image content (still image or video frame) when only a portion of an integral image map pertains. If SHAPE is specified then COORDS must also be present. SHAPE should be used in conjunction with COORDS in the manner defined for the shape and coords attributes on an HTML4 &lt;area&gt; element. SHAPE must contain one of the following values:
RECT
CIRCLE
POLY
Expand Down Expand Up @@ -1710,7 +1710,7 @@ DDI: Data Documentation Initiative
FGDC: Federal Geographic Data Committee metadata
LOM: Learning Object Model
PREMIS: PREservation Metadata: Implementation Strategies
PREMIS:OBJECT: PREMIS Object entiry
PREMIS:OBJECT: PREMIS Object entity
PREMIS:AGENT: PREMIS Agent entity
PREMIS:RIGHTS: PREMIS Rights entity
PREMIS:EVENT: PREMIS Event entity
Expand Down