Skip to content

Reference Systems subclass of Directive vs Descriptive Information Entity? #147

Description

@alanruttenberg

Reference Systems are currently a subclass of Descriptive Information Content Entity. I am speculating that they are really a subclass of Directive Information Content Entity under the interpretation that a reference system provides a recipe for creating Designative Information Content Entities. I'm specifically interested in spatial and temporal reference systems at the moment. For example, a spatial coordinate system tells us how to create a set of coordinates (a kind of name/identifier) of a site.

There are three subclasses of Reference System, currently. I've thought about the spatial and temporal reference systems but not as much as the third subclass, a priority scale.

Activity

  1. nklsbckmnn commented on Apr 10, 2022

    @nklsbckmnn

    I am speculating that they are really a subclass of Directive Information Content Entity under the interpretation that a reference system provides a recipe for creating Designative Information Content Entities.

    I agree that Directive Information Content Entity seems to be a better choice of genus for reference systems.

    At first sight, reference systems also seem to be able to be understood as specifications of types of a concrete reference. E. g. "12 am" seems to be an instance of "Twelve-Hour Clock Time System reference" and "Twelve-Hour Clock Time System" could be understood as a specification of that type. And, if I understand correctly, we have at least one other example where something like a type specification has been represented as a Directive Information Content Entity, namely Artifact Model: "A Directive Information Content Entity that prescribes a common set of Functions and Qualities to inhere in a set of artifact instances."

  2. added this to the milestone on Aug 19, 2024
  3. added
    for 2.1 releaseThese are changes we would like to see addressed under the 2.1 release
    and removed on Oct 19, 2024
  4. modified the milestones: , 2.1 Release on Nov 3, 2024
  5. added
    for 2.2 releaseThese are changes we would like to see addressed under the 2.2 release
    and removed
    for 2.1 releaseThese are changes we would like to see addressed under the 2.1 release
    on Mar 26, 2026
  6. removed this from the 2.1 Release milestone on Mar 26, 2026
  7. added theissue type on Mar 26, 2026
  8. added and removed
    for 2.2 releaseThese are changes we would like to see addressed under the 2.2 release
    on Jun 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions