| ITI41 | ITI41-1 | reviewed | Testable |
2
|
1
| | A Provide and Register Document Set-b transaction shall carry within metadata, one XDSDocumentEntry object per document | 156 | Section 3.41.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-11 | reviewed | Testable |
3
|
1
| | A Document Repository shall forward the metadata to the Document Registry using the Register Document Set-b transaction [ITI-42] | 159 | Section 3.41.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-12 | reviewed | Testable |
3
|
1
| | Each document within the message shall be stored into the Document Repository as an octet stream with an associated MIME type. | 159 | Section 3.41.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-13 | reviewed | Testable |
3
|
1
| | The Document Repository shall modify the received document metadata before initiating the Register Document Set-b transaction to the Document Registry by adding/replacing:
The repositoryUniqueId for this Document Repository to allow for the Document Consumer to correctly identify the proper Document Repository for each document (XDSDocumentEntry.repositoryUniqueId).
A hash value (XDSDocumentEntry.hash)
A size (XDSDocumentEntry.size). | 159 | Section 3.41.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-16 | reviewed | Testable |
1
|
1
| | If the Document Repository or Document Recipient detects a failure it shall return an error message to the Document Source or Metadata-Limited Document Source thus terminating this transaction. | 159 | Section 3.41.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-17 | reviewed | Testable |
3
|
1
| | The Document Repository or Document Recipient shall send a Provide and Register Document Set-b Response when the processing of a Provide and Register Document Set-b Request is complete | 161 | Section 3.41.4.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-18 | reviewed | Testable |
3
|
1
| | The document(s) received by the Document Recipient shall be available for further processing according to the capabilities of the system | 161 | Section 3.41.4.2.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-19 | reviewed | Testable |
3
|
1
| | The metadata added to the registry shall be available for discovery via Registry Stored Query transactions | 161 | Section 3.41.4.2.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-2 | reviewed | Testable |
1
|
1
| | A Provide and Register Document Set-b transaction shall carry XDS Submission Set definition along with the linkage to new documents and references to existing documents | 156 | Section 3.41.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-20 | reviewed | Testable |
2
|
1
| | An implementation of the Document Source or Metadata-Limited Document Source Actor shall be capable of Submit one or more documents | 166 | Section 3.41.6.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-22 | reviewed | Testable |
2
|
1
| | A Document Repository or Document Recipient shall be capable of accepting submissions containing multiple documents | 167 | Section 3.41.6.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-23 | reviewed | Testable |
3
|
1
| | A Document Repository shall validate the following metadata element received as part of a Provide and Register transaction: XDSDocumentEntry.uniqueId, XDSSubmissionSet.sourceId, XDSDocumentEntry.hash, XDSDocumentEntry.size | 167 | Section 3.41.6.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-24 | reviewed | Testable |
1
|
1
| | A submission shall be rejected if not unique within the repository and the hashes of the two documents do not match. If the hashes of the documents match, the Document Repository shall accept the duplicate document | 167 | Section 3.41.6.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-25 | reviewed | Testable |
1
|
1
| | a submission shall be rejected if the hash is included in the submission and its value does not match the hash for the received document (ignoring case), as calculated by the Document Repository or Document Recipient; an XDSRepositoryMetadataError shall be returned on mismatch | 167 | Section 3.41.6.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-26 | reviewed | Testable |
1
|
1
| | a submission shall be rejected if the size is included in the submission and its value does not match the size of the received document, as computed by the Document Repository or Document Recipient; an XDSRepositoryMetadataError shall be returned on mismatch | 167 | Section 3.41.6.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-3 | reviewed | Testable |
1
|
1
| | The Document Repository shall, upon receipt of a Provide and Register Document Set-b [ITI-41] transaction send a corresponding Register Document Set-b [ITI-42] transaction to the Document Registry Actor | 158 | Section 3.41.4.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-4 | reviewed | Testable |
3
|
1
| | The Document Repository Actor shall create and insert the XDSDocumentEntry.repositoryUniqueId, XDSDocumentEntry.size, and XDSDocumentEntry.hash attributes for each document received from the Provide and Register Document Set-b [ITI-41] transaction into the resulting Register Document Set-b [ITI-42] transaction metadata | 158 | Section 3.41.4.1 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-5 | reviewed | Testable |
2
|
1
| | The Provide and Register Document Set-b message shall include the metadata attributes as defined in ITI TF-3: 4.3.1.2.1 and ITI TF-3: Table 4.3.1.1-3 | 159 | Section 3.41.4.1.2 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-6 | reviewed | Testable |
3
|
1
| | The Document Recipient may validate the metadata as described in ITI TF-3: Table 4.3.1.1-3 | 159 | Section 3.41.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|
| ITI41 | ITI41-7 | reviewed | Testable |
1
|
1
| | If the Document Recipient declares the Accepts Limited Metadata Option it shall not reflect an error because the limitedMetadata attribute is present | 159 | Section 3.41.4.1.3 | 2/5/16 12:27:23 PM by aboufahj |
|