This issue is intended to raise and track the question of whether a set of component-focused .json test files would be a useful addition to the current group of test files:

• purl-spec/tests/spec/, which contains a single file atm, specification-test.json (19 test objects)
• purl-spec/tests/types/, which contains 34 type-specific .json test files atm (varying numbers of test objects)

The "specification" test file has a cross-section of tests without any strong pattern. I think this is meant to be tests that are common to all types, while the tests/types are for each PURL type.

@jkowalleck recently opened PR 738 (#738) comprising a set of tests focused on the qualifiers component, which seems like a useful way to group tests. This PR raises some important questions:

• Does it make sense to create a separate file in tests/spec for each component?
• What tests belong in tests/spec/specification-test.json if we have component-level spec tests?

A broader open question is: What is the relationship between specification and type tests? Based on the current set of type tests, most are a combination of:

• Tests where the input is type-specific
• Tests for PURL type rules such as: no namespace allowed or type-specific qualifiers