AOAC SPADA VNGS - Final

119

(3) Formats shall permit machine readability and can permit human readability (18).

120

a. JSON, XML and RDF are permitted.

121

(4) VNGS data and metadata that are not open and do not protect semantic interoperability during

processing or transferring shall be made machine readable subject to: security considerations; cost(s) 122

and benefit(s); legal liabilities; intellectual property right(s); confidential business information; contract 123

124

restriction(s); or other binding written agreement(s).

125

(5) Knowledge representations shall use VNGS web ontology, preferably in OWL (web ontology

126

language).

127

( b ) VNGS Technical and Organizational Requirements

128

129

(1) The reference sequence provider is responsible for establishment, maintenance, and potential

changes in the ownership of the VNGS URI format including the format description, version, structure, 130

and data representation. VNGS format description and contact information shall be documented. 131

132

(2) The sequence provider is responsible for the delegation of user requests.

133

(3) AOAC takes responsibility for VNGS Standard Requirement updates and error corrections in the

134

specification.

135

( c ) Documentation

136

137

The sequence provider will provide a stable and identifiable source for the VNGS format where data

on the provenance, maintenance, format structure, data items, data formatting and features of the 138

format are maintained and updated. Data types and metadata shall be documented. The exact format 139

140

version will be documented according to a change control schedule.

141

( d ) Compatibility, extensibility, and compression

142

AOAC Draft Standard – Version 09282022; Public Comment Revisions

6