Improve sentences

[PhillipTommerholt]

There are two sentences in 6.1.1 What is a Content Information Type Specification which might be improved:

"For example, the ERMS Content Information Type Specification does specific a method for referencing data (i.e. computer files) from descriptive metadata in ERMS format, to ensure the integrity of data and metadata."

"does a method" sounds odd - is this correct English?

"Stating these requirements in a general specification allows archival institutions receiving SIPs including ERMS extracts or whole systems to understand and validate potentially complex information packages."

" allows receiving" -> allows to receive?

[carlwilson]

I'll take these in reverse order (I'd have asked if that was OK but then I'd have to wait for a reply ;) ):

I think that the second issue is OK, to me this reads that the "allows" refers to "understand and validate...." later in the sentence, i.e. (to re-order & paraphrase) "the general specification allows institutions to understand complex SIPs they receive". It might be better written in that more direct form (with use of original terms)?

Regarding the first issue, I agree and am suggesting this patch which I'll PR and pull you in for review:

@@ -12,11 +12,11 @@ Content Information Types can be regarded as categories of Content Information,
 The following elements should be at the core of a Content Information Type Specification:

 - Required file formats for content data;
-- Specification of information package structure, i.e. specific sub-folders under the "Data" folder for particular categories of content data;
+- Specification of information package structure, i.e. specific sub-folders under the "data" folder for particular categories of content data;
 - Requirements for specific representation metadata that should be available in PREMIS for understanding and rendering the Content Data Object;
 - Details of specific (binary) documentation or other components (e.g. software, emulators, etc.) which must be available for rendering and understanding the Content Data Object.

-Pragmatically it may not be sufficient to deal only with the Information Object. For complex Content Information Types or large IPs it may be necessary to provide explicit requirements for other metadata (descriptive, administrative) relevant to the specific content type. For example, the ERMS Content Information Type Specification does specific a method for referencing data (i.e. computer files) from descriptive metadata in ERMS format, to ensure the integrity of data and metadata. Stating these requirements in a general specification allows archival institutions receiving SIPs including ERMS extracts or whole systems to understand and validate potentially complex information packages.
+Pragmatically it may not be sufficient to deal only with the Information Object. For complex Content Information Types or large IPs it may be necessary to provide explicit requirements for other metadata relevant to the specific content type. For example, the ERMS Content Information Type Specification prescribes a method for referencing data (i.e. computer files) from descriptive metadata in ERMS format, ensuring package integrity. Stating these requirements in a general specification allows archival institutions receiving SIPs including ERMS extracts or whole systems to understand and validate potentially complex information packages.

[carlwilson]

Done and ready to close