glossarist 0.4.35 → 0.4.37

package/src/models/generic-member.js

@@ -1,82 +0,0 @@
-// GenericMember — one member of a GenericHyperedge.
-//
-// Per ISO 704:2022 §5.5.4.2.1 (Generic relations and general concepts):
-//
-//   "In a generic relation, the intension of the subordinate concept
-//    includes the intension of the superordinate concept plus at least
-//    one additional delimiting characteristic."
-//
-// In hyperedge terms: when a GenericHyperedge has comprehensive=computer mouse
-// and criterion=means of movement detection, each member (mechanical mouse,
-// optomechanical mouse, optical mouse) carries a delimitingCharacteristic —
-// the value of the criterion for that specific concept:
-//
-//   mechanical mouse     → 'detecting movement by means of rollers'
-//   optomechanical mouse → 'detecting movement by means of rollers and light sensors'
-//   optical mouse        → 'detecting movement by means of light sensors'
-//
-// Multidimensionality (§5.6.3): the same comprehensive can be the
-// '1' side of multiple generic hyperedges simultaneously, each by a
-// different criterion. computer mouse is also comprehensive of
-// {wired mouse, wireless mouse} under criterion=computer connection.
-// That second hyperedge's members carry their own delimitingCharacteristic
-// values ('using a corded electrical connection', 'using a cordless
-// light or sound connection').
-//
-// delimitingCharacteristic is REQUIRED on GenericMember. Without it,
-// the member is just a coordinate concept with no semantic content
-// tying it to the criterion — ISO 704 says the relation is meaningless
-// without the delimiting characteristic.
-//
-// LocalizedString shape (mirrors criterion on the parent hyperedge):
-//   { eng: 'detecting movement by means of light sensors' }
-//   { eng: '...', fra: '...' }   — multiple languages supported
-
-import { HyperedgeMember } from './hyperedge-member.js';
-
-export class GenericMember extends HyperedgeMember {
-  constructor(data = {}) {
-    super(data);
-    this.delimitingCharacteristic = _resolveDelimitingCharacteristic(data.delimitingCharacteristic);
-  }
-
-  toJSON() {
-    const base = super.toJSON();
-    base.delimitingCharacteristic = { ...this.delimitingCharacteristic };
-    return base;
-  }
-}
-
-function _resolveDelimitingCharacteristic(value) {
-  if (value == null) {
-    throw new Error(
-      'GenericMember.delimitingCharacteristic is required per ISO 704:2022 §5.5.4.2.1 ' +
-      '(the intension of a subordinate concept must include at least one additional ' +
-      'delimiting characteristic beyond the superordinate).',
-    );
-  }
-  if (typeof value === 'string') {
-    if (value.length === 0) {
-      throw new Error(
-        'GenericMember.delimitingCharacteristic cannot be empty (ISO 704:2022 §5.5.4.2.1)',
-      );
-    }
-    return { default: value };
-  }
-  if (typeof value === 'object') {
-    const entries = Object.entries(value).filter(([, v]) => typeof v === 'string' && v.length > 0);
-    if (entries.length === 0) {
-      throw new Error(
-        'GenericMember.delimitingCharacteristic must have at least one non-empty string ' +
-        'value (ISO 704:2022 §5.5.4.2.1)',
-      );
-    }
-    return Object.fromEntries(entries);
-  }
-  throw new Error(
-    `GenericMember.delimitingCharacteristic must be a string or a language-keyed object; ` +
-    `got ${typeof value}`,
-  );
-}
-
-export default GenericMember;

package/src/models/partitive-enumeration.js

@@ -1,23 +0,0 @@
-// PartitiveEnumeration — allowed values for PartitiveHyperedge#enumeration.
-//
-//   closed — the encoded parts are ALL the parts of the comprehensive.
-//            Adding or removing a part would change the relationship.
-//   open   — the encoded parts are SOME of the parts; others may exist
-//            but are not encoded.
-//
-// See concept-model/TODO.hyperedge/00-design-overview.md for the design
-// rationale and the open/closed distinction.
-
-export const PARTITIVE_ENUMERATION = Object.freeze({
-  CLOSED: 'closed',
-  OPEN: 'open',
-});
-
-export const PARTITIVE_ENUMERATION_VALUES = Object.freeze([
-  PARTITIVE_ENUMERATION.CLOSED,
-  PARTITIVE_ENUMERATION.OPEN,
-]);
-
-export function isValidPartitiveEnumeration(value) {
-  return PARTITIVE_ENUMERATION_VALUES.includes(value);
-}

package/src/models/partitive-hyperedge.js

@@ -1,91 +0,0 @@
-// PartitiveHyperedge — an ISO 704:2022 / ISO 1087-1 / ISO 12620
-// partitive relation connecting a comprehensive concept
-// (superordinate concept partitive) to two or more partitive
-// concepts (subordinate concepts partitive) which fitted together
-// constitute the comprehensive.
-//
-// Extends AbstractHyperedge; the leaf-specific concern is the
-// PartitiveMember type for `members`. The wire-level field name
-// stays `partitives` for v1/v2 backward compat.
-//
-// ISO 704:2022 rake diagram semantics:
-//
-//   comprehensive concept
-//   ─────────────────────
-//   │ partitive (one or more) with per-member multiplicity + optional delimiting
-//   ─────────────────────
-//
-// All partitives within one relation are coordinate concepts
-// (ISO 12620): they share the comprehensive AND share the
-// criterion of subdivision.
-//
-// "Delimiting" parts (bold/3x-width line in source diagrams) behave
-// like delimiting characteristics — they distinguish the comprehensive
-// from coordinate concepts. Whether a part is delimiting depends on
-// the concept system, the coordinate concepts, the inheritance
-// principle, and the criterion of subdivision used
-// (ISO 704:2022 §5.5.4.2.1).
-//
-// Distinguished from binary `has_part` / `is_part_of` edges, which
-// express pairwise part-of assertions without completeness,
-// multiplicity, or criterion claims. A single partitive should be
-// expressed as a binary edge, not a PartitiveHyperedge (ISO requires
-// "two or more").
-
-import { AbstractHyperedge } from './abstract-hyperedge.js';
-import { PartitiveMember } from './partitive-member.js';
-import { HyperedgeRegistry } from './hyperedge-registry.js';
-
-export class PartitiveHyperedge extends AbstractHyperedge {
-  // Per-class metadata block — the OCP contract. External systems
-  // (parser, serializer, diff, RDF emitter, validators) read from
-  // these statics and the HyperedgeRegistry. Adding a new hyperedge
-  // type = declaring these fields on a new subclass + registering
-  // it. Nothing else in the codebase changes.
-  static wireKey     = 'partitive_relations';
-  static typeTag     = 'partitive_relation';
-  static rdfType     = 'gloss:PartitiveRelation';
-  static memberClass = PartitiveMember;
-  static v1WireKeys  = ['partitive_hyperedges'];
-  static kindLabel   = 'PART';
-
-  constructor(data = {}) {
-    const members = data?.members ?? data?.partitives;
-    super({ ...data, members });
-    this.members = members == null
-      ? this.members
-      : (Array.isArray(members)
-          ? members.map(m =>
-              m instanceof PartitiveMember ? m : new PartitiveMember(m))
-          : this.members);
-  }
-
-  get partitives() { return this.members; }
-
-  toJSON() {
-    const base = super.toJSON();
-    const { members, ...rest } = base;
-    return { ...rest, partitives: members };
-  }
-
-  static identityOf(value) {
-    const v = value ?? {};
-    const c = v.comprehensive ?? {};
-    const partKeys = Array.isArray(v.partitives ?? v.members)
-      ? (v.partitives ?? v.members).map(p => {
-          const r = p?.ref ?? p ?? {};
-          return `${r.source ?? ''}:${r.id ?? ''}`;
-        }).sort()
-      : [];
-    return `${c.source ?? ''}:${c.id ?? ''}|${partKeys.join('|')}`;
-  }
-
-  static fromJSON(data) {
-    const normalized = { ...(data ?? {}), members: data?.partitives ?? data?.members };
-    return new PartitiveHyperedge(normalized);
-  }
-}
-
-export default PartitiveHyperedge;
-
-HyperedgeRegistry.register(PartitiveHyperedge);

package/src/models/sequential-hyperedge.js

@@ -1,56 +0,0 @@
-// SequentialHyperedge — an ISO 12620 A.6.3 / ISO 704:2022 §5.5.5
-// sequential relation connecting a comprehensive concept to two or
-// more subordinate concepts in an ORDERED sequence (temporal,
-// spatial, causal, developmental).
-//
-// Mirror of PartitiveHyperedge and GenericHyperedge. Member array
-// order IS significant — reversing the array reverses the sequence.
-// Use cases: manufacturing process steps, biological life cycles,
-// software release lifecycles, supply chain stages, geological eras.
-//
-// See docs/design/abstract-nary-relation.md (concept-model repo).
-
-import { AbstractHyperedge } from './abstract-hyperedge.js';
-import { SequentialMember } from './sequential-member.js';
-import { HyperedgeRegistry } from './hyperedge-registry.js';
-
-export class SequentialHyperedge extends AbstractHyperedge {
-  // Per-class metadata block — the OCP contract.
-  static wireKey     = 'sequential_relations';
-  static typeTag     = 'sequential_relation';
-  static rdfType     = 'gloss:SequentialRelation';
-  static memberClass = SequentialMember;
-  static v1WireKeys  = [];
-  static kindLabel   = 'SEQ';
-
-  constructor(data = {}) {
-    super(data);
-    this.members = data?.members == null
-      ? this.members
-      : (Array.isArray(data.members)
-          ? data.members.map(m =>
-              m instanceof SequentialMember ? m : new SequentialMember(m))
-          : this.members);
-  }
-
-  static identityOf(value) {
-    const v = value ?? {};
-    const c = v.comprehensive ?? {};
-    // For sequential, member order IS significant — do NOT sort.
-    const memberKeys = Array.isArray(v.members)
-      ? v.members.map(m => {
-          const r = m?.ref ?? m ?? {};
-          return `${r.source ?? ''}:${r.id ?? ''}`;
-        })
-      : [];
-    return `${c.source ?? ''}:${c.id ?? ''}|${memberKeys.join('|')}`;
-  }
-
-  static fromJSON(data) {
-    return new SequentialHyperedge(data);
-  }
-}
-
-export default SequentialHyperedge;
-
-HyperedgeRegistry.register(SequentialHyperedge);