Relationships

Nodes within SpecAtlas maintain a number of relationships.

HAS_CHILD_ORG

Describes a subordinate relationship between organizations.

(<SourceNode>) -[ HAS_CHILD_ORG ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Parent OrgChild Org
1ControllingOrgControllingOrg

HAS_AFFILIATE_ORG

Describes a relationship between organizations with a specified affiliation.

(<SourceNode>) -[ HAS_AFFILIATE_ORG {affiliation} ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Originator OrgAffiliate Org
1ControllingOrgControllingOrg

affiliation values include, but are not limited to:

  • accredits - In the case of formal national standards bodies, a national standards body (source) may accredit an affiliate (target) to support specific subjects.

  • sponsors - An example would be a commercial organization (source) providing financial, technical, or administrative assistance to a standards making body (target).

  • national representative - A national standards body (source) provides national representation to a broader international standards body (target).

  • national technical advisor - A nationally-accredited standards group (source) provides technical participation in the international standards making process (target).

  • operates - A technical organization (source) provides technical services on behalf of another organization (target).

PREVIOUSLY_KNOWN_AS

Describes the continuity of an organization across name changes. May also be used to describe the direct succession of an organization with minimal organizational change.

(<SourceNode>) -[ PREVIOUSLY_KNOWN_AS ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Instant OrgPrevious Org
1ControllingOrgControllingOrg

SUCCEEDED_ORG

Describes the continuity of organizations across significant change. This is often due to significant reorganization or combining organizations.

(<SourceNode>) -[ SUCCEEDED_ORG ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Instant OrgPrevious Org
1ControllingOrgControllingOrg

CONTROLS

Describes the relationship between a standards making organization and an artifact (e.g., Authority, AuthorityGroup, etc.). This relationship should only be used for documents under some level of standards development.

(<SourceNode>) -[ CONTROLS ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Document ControllerDocument or Collection
1ControllingOrgAuthority
2ControllingOrgAuthorityGroup
3ControllingOrgAuthorityDraft

MEMBER_OF

Describes groups of artifacts.

(<SourceNode>) -[ MEMBER_OF ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Collection MemberCollection
1AuthorityAuthorityGroup
2AuthorityGroupAuthorityGroup

DEPRECATES

One artifact notifies users to discontinue use of the Authority. The target may be a group of documents to accommodate amended Authorities. See the Deprecated Authority status.

(<SourceNode>) -[ DEPRECATES ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Notification DocumentOriginal Document
1AuthorityAuthority
2AuthorityAuthorityGroup
3AuthorityAuthorityDraft

OBSOLETES

One artifact replaces another without being in a common series. The target may be a group of documents to accommodate amended Authorities. One artifact may obsolete multiple other documents; an artifact may be obsoleted by multiple other documents. See the Obsoleted Authority status.

(<SourceNode>) -[ OBSOLETES ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Replacement DocumentOriginal Document
1AuthorityAuthority
2AuthorityAuthorityGroup
3AuthorityDraftRevisionAuthorityDraftRevision

SUPERSEDES

One artifact in a series directly replaces a prior document in the series. The target may be a group of documents to accommodate amended Authorities. The SUPERSEDES relationship should be a one-to-one relationship, granted the target is an AuthorityGroup.

(<SourceNode>) -[ SUPERSEDES ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Replacement DocumentOriginal Document
1AuthorityAuthority
2AuthorityAuthorityGroup

UPDATES

One artifact substantively updates another. See the Updated Authority status.

(<SourceNode>) -[ UPDATES ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Document with UpdatesSource Document
1AuthorityAuthority

CORRECTS

One artifact corrects another, either technically or editorially. See the Errata Authority status.

(<SourceNode>) -[ CORRECTS ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Document with CorrectionsSource Document
1AuthorityAuthority

HAS_RELATED_AUTHORITY

Describes a relationship between two Authorities, given a relationship.

(<SourceNode>) -[ HAS_RELATED_AUTHORITY {relationship} ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Source DocumentTarget Document
1AuthorityAuthority
2AuthorityAuthorityGroup
3AuthorityAuthorityDraftRevision
4AuthorityGroupAuthority
5AuthorityGroupAuthorityGroup

relationship values include, but are not limited to:

  • influenced - One Authority provided a basis for the development of another.

  • partially equivalent - Elements of an Authority, but not the entirety, are technically equivalent to another. Equivalent elements should be noted in the notes field.

  • technically equivalent - Two Authorities have the same technical meaning, although the text is not identical.

  • textually equivalent - Two Authorities maintain the exact text. The Authorities are published from two different controlling organizations.

  • republication - One Authority is a direct republication of a prior Authority, such as due to a renumbering or reauthorization.

REFERENCES

Describes one Authority's reference of another, given an optional referenceType.

(<SourceNode>) -[ REFERENCES {referenceType} ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Referencing DocumentReferenced Document
1AuthorityAuthority
2AuthorityAuthorityGroup
3AuthorityAuthorityDraftRevision

referenceType values include, but are not limited to:

  • normative - Understanding the referenced document is critical to understand or implement the technology presented in the referencing document.

  • informative - The referenced document provides contextual or additional information not critical to understand or implement the technology in the referencing document.

DRAFTED_BY

An authority has been drafted by a group of draft revisions.

(<SourceNode>) -[ DRAFTED_BY ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Defining DocumentObject
1AuthorityAuthorityDraft

ADOPTED_AS

An authority draft revision has been adopted as a published authority.

(<SourceNode>) -[ ADOPTED_AS ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Defining DocumentObject
1AuthorityDraftRevisionAuthority

DEFINES

An authority provides the definition of a format.

(<SourceNode>) -[ DEFINES ]-> (<TargetNode>)

Source Node TypeTarget Node Type
Defining DocumentObject
1AuthorityArtifact
2AuthorityGroupArtifact