AOAC SPADA VNGS - Final

4 VNGS Requirements

95

( a ) VNGS Identifier Scheme

96

97

(1) VNGS Universal Resource Identifier (URI). —The VNGS shall be considered fit for purpose if it

possesses a specific namespace and context. The VNGS URI shall be in the form: 98

99

scheme: //hierarchical namespace qualifier(s)/name

where the ASCII character set is used, except where ASCII characters are not used then UCS characters 100

101

shall be used.

The VNGS URI can be represented in any scheme, e.g., http: urn (www.iana.org ). 102

All metadata connected to a VNGS URI shall be capturable and shall be kept over the whole lifetime of 103

the data. A VNGS URI shall be persistent and remain independent of its mapping on a server, and its 104

notation. The VNGS URI should not attempt to infer from properties of the biothreat next generation 105

sequence data and metadata including raw data, base quality metadata, metadata, alignments, variants, 106

107

features, etc.

A VNGS URI shall identify a single biothreat agent VNGS and each VNGS shall be assigned to only one URI 108

109

(17).

110

a. Using the same VNGS URI to identify more than one biothreat agent VNGS is discouraged:

111

existing server conventions for NGS and VNGS should be considered to avoid URI collision.

112

b. The responsible party shall avoid the assignment of equivalent VNGS URIs to multiple

113

biothreat agent VNGS.

114

c. It shall be the responsibility of reference sequence providers to manage the assignment of

115

VNGS URIs.

The VNGS URI shall be opaque and shall not contain: the author’s name, the status, the access, the file 116

name extension, the software mechanism, the disk name, or the domain name. 117

118

(2) All aspects of data and metadata for the VNGS shall be version controlled.

AOAC Draft Standard – Version 09282022; Public Comment Revisions

5