E.11.DSG:4.1 - Keep the Reference product series, each edition, and Suite belonging distinct

A DPF Suite Reference product series is a continuing collection of Reference edition epistemes under its reader-use, content-selection, admission, reidentification, later-review, and retirement rules. It begins when a product-constitution decision under E.4:4.2 admits the first Reference edition. A separate publication occurrence may make that edition available. A maintaining System, maintenance commitment, revision duty, another edition, or continued availability requires a separate claim. A title, date, language tag, file, carrier, or publication alone does not create the series.

A later Reference edition belongs to that series only after its source-edition relation and the Reference admission rule pass and an admission decision takes effect. Supersession, unavailability, non-currentness, or edition retirement does not end that occurrence while the same Reference product series continues. If the series ends, current belonging ends with it. If its identity rule identifies another series, belonging to the old series ends when that reidentification takes effect. The past fact remains, and another Reference product series needs its own admission and occurrence. A fork, translation, retargeting, or reconstruction is not admitted by title or provenance alone. A changed-scheme derivative may remain in the same Reference product series only when it also qualifies as an edition and the shared reader, access, warning, later-review, and retirement conditions still hold.

The Reference product series belongs to its DPF Suite only after a separate Suite-inclusion decision takes effect. Belonging remains current only while the same Reference product series and Suite continue and no removal decision has taken effect. If either collection ends, current belonging ends with it. If its identity rule identifies another collection, belonging to the old collection ends when that reidentification takes effect. Neither case requires a prior removal decision, and the new Reference product series or Suite needs a new inclusion. The Reference product series, its Suite belonging, Reference availability, and Reference use are different claims. The Suite may exist before the Reference series is included, and a Reference may be temporarily unusable without ending the Suite or other belonging occurrences. This claim establishes no parthood or holonhood; any such claim needs the complete A.1 test and its own part relation.

One exact DPF Suite Reference edition is identified under C.2.1 as:

<claim content = J_g, EntityOfConcern = G, effective ReferenceScheme = R_g>

G is that Reference edition. J_g states its intended readers and use, the Suite collection, selected problem-led entries, the resource and blocker claims those entries make, and only the product-series or edition state, source, warning, availability, and currentness claims that change those entries. R_g resolves the Reference edition, Suite collection, cited product series and editions, results, adjacent products, direct sources, and relation words used in the entries.

The Reference product has its own intended readers and use, edition-admission and reidentification rule, access, later-review, and retirement conditions. A publication occurrence may make an edition available. A maintaining System, maintenance relation, commitment, or future maintenance Work exists only when its direct evidence establishes it; authorship, constitution, publication, a locator, or the word maintained establishes none of them. Suite maintenance does not supply Reference maintenance, and Reference maintenance does not supply maintenance of the DPF product series that belong to the Suite.