@memoarchitect/ontology 0.12.1 → 0.15.0

package/extensions/cloud/src/methodology/cloud_methodology.sysml

@@ -1,19 +0,0 @@
-package memo_extension_cloud_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part cloudExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-CLOUD-001"; }
-        attribute :>> name = "CloudRuntimeExtension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "networked services and managed data stores";
-        attribute :>> description = "Adds service and data-store runtime families with their contracts, discovery, and retention.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "memo_extension_cloud";
-    }
-}

package/extensions/container/src/methodology/container_methodology.sysml

@@ -1,19 +0,0 @@
-package memo_extension_container_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part containerExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-CONTAINER-001"; }
-        attribute :>> name = "ContainerDeploymentExtension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "containerized deployment";
-        attribute :>> description = "Adds OCI container images and container runtimes as deployment content.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "memo_extension_container";
-    }
-}

package/extensions/messaging/src/methodology/messaging_methodology.sysml

@@ -1,19 +0,0 @@
-package memo_extension_messaging_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part messagingExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-MESSAGING-001"; }
-        attribute :>> name = "MessagingExtension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "publish/subscribe messaging";
-        attribute :>> description = "Adds message items, publisher/subscriber ports, topic interfaces, brokers, and delivery semantics.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "memo_extension_messaging";
-    }
-}

package/extensions/ros/src/methodology/ros_methodology.sysml

@@ -1,27 +0,0 @@
-package memo_extension_ros_methodology {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-    private import memo_core_enumerations::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    // An extension that builds on other extensions names them all here.
-    // `baseMethodology` is [0..1] — single inheritance, deliberate — but
-    // `includedModule` is [0..*], so this is how a dependency between
-    // extensions is expressed. There is no chaining and no second base.
-    part rosExtensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-ROS-001"; }
-        attribute :>> name = "Ros2Extension";
-        attribute :>> version = "0.7.0";
-        attribute :>> domain = "ROS 2 robotics middleware";
-        attribute :>> description = "Adds ROS 2 nodes, messages, directional ports, topic/service/action interfaces, QoS, and containerized deployment.";
-        ref :>> baseMethodology = mdDefaultDefinition;
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = (
-            "memo_extension_messaging",
-            "memo_extension_container",
-            "memo_extension_ros"
-        );
-    }
-}

package/extensions/template/src/extension.sysml

@@ -1,39 +0,0 @@
-// Skeleton for a new MEMO extension. Copy the directory, rename the packages,
-// and replace the prefix.
-//
-// Two conventions this file follows and every extension must (extensions/README.md):
-//
-//   1. Every definition an extension declares is prefixed with the PascalCase
-//      form of the extension's directory name — `template/` gives `Template`.
-//      Extension names share one flat namespace with the base and with each
-//      other, so the prefix is what keeps two independent extensions from both
-//      declaring `Node`.
-//   2. A relation an extension declares specializes a base relation. It never
-//      roots independently.
-//
-// This package used to bind `baseMethodName = "MedicalDeviceLightDefault"` — a
-// pre-flip spelling that resolves to nothing. It went unnoticed for as long as
-// extensions lived under `examples/`, where the build did not check them; the
-// build checks `extensions/` now, and reported it on the first run.
-package memo_extension_template {
-    private import ScalarValues::*;
-    private import memo_core_enumerations::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part extensionMethod : MethodologyDefinition {
-        @MemoIdentity { :>> providedId = "EXT-METH-001"; }
-        attribute :>> name = "ExtensionMethod";
-        attribute :>> version = "0.1.0";
-        attribute :>> domain = "project extension";
-        attribute :>> description = "Adds a project or domain package to the selected MEMO methodology.";
-        // The base is a typed SysML reference, not a name held in sync by hand.
-        ref :>> baseMethodology = mdDefaultDefinition;
-        // An extension adds its own module to whatever its base selected;
-        // saying so explicitly is required now that an empty list means empty.
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-        attribute :>> includedModule = "replace_with_extension_package";
-    }
-}

package/templates/connected-device/memo.package.yaml

@@ -1,13 +0,0 @@
-# Application/distribution descriptor for this MEMO package.
-#
-# Identity and location only. It records what this package is called, what
-# version it is, and where its SysML source sits so a resolver can find it.
-# It does not select model content: the project's native SysML imports and its
-# ProjectMethodBinding decide what is in the model. Semantic fields
-# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
-# removed at the native semantic flip and are now rejected if present.
-name: '{{name}}'
-entrypoint: model/catalog/project.sysml
-include: [model]
-version: 0.1.0
-description: MEMO connected device model

package/templates/connected-device/model/catalog/architecture/system.sysml

@@ -1,5 +0,0 @@
-package connected_device_architecture {
-    private import memo::*;
-
-    part connectedDevice : PhysicalAssembly;
-}

package/templates/connected-device/model/catalog/artifacts/catalog.sysml

@@ -1,5 +0,0 @@
-package connected_device_artifacts {
-    private import memo::*;
-
-    // Add project artifact usages here.
-}

package/templates/connected-device/model/catalog/assurance/requirements.sysml

@@ -1,7 +0,0 @@
-package connected_device_assurance {
-    private import memo::*;
-
-    requirement connectivityRequirement : Requirement {
-        attribute redefines statement = "Define connectivity and cybersecurity boundaries";
-    }
-}

package/templates/connected-device/model/catalog/project.sysml

@@ -1,30 +0,0 @@
-// Project identity and method binding — the project's native entrypoint.
-//
-// The imports below name the reusable packages this project resolves, and the
-// binding names its methodology with a typed SysML reference. Nothing outside
-// SysML selects model content: delete every YAML file beside this one and the
-// model still means exactly what it means now.
-package connected_device_catalog {
-    private import ScalarValues::*;
-
-    private import memo_core_enumerations::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-
-    private import connected_device_architecture::*;
-    private import connected_device_assurance::*;
-    private import connected_device_artifacts::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part projectMethodBinding : ProjectMethodBinding {
-        @MemoIdentity { :>> providedId = "PMB-001"; }
-        attribute :>> name = "{{name}}ProjectMethodBinding";
-        attribute :>> projectName = "{{name}}";
-        ref :>> selectedMethodology = mdDefaultDefinition;
-        // The project adds no modules of its own yet. Under `explicit` an
-        // empty additive list means exactly that — no additions — rather than
-        // being read as "everything".
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-    }
-}

package/templates/connected-device/package.json

@@ -1,8 +0,0 @@
-{
-  "name": "{{npmName}}",
-  "version": "0.1.0",
-  "private": true,
-  "dependencies": {
-    "@memoarchitect/ontology": "{{ontologyVersion}}"
-  }
-}

package/templates/connected-device/syside.toml

@@ -1,13 +0,0 @@
-#:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
-
-include = [
-    "model",
-    "node_modules/@memoarchitect/ontology/src",
-]
-
-exclude = [
-    ".memo",
-    ".sysand",
-    "dist",
-    "output",
-]

package/templates/infusion-pump/memo.package.yaml

@@ -1,13 +0,0 @@
-# Application/distribution descriptor for this MEMO package.
-#
-# Identity and location only. It records what this package is called, what
-# version it is, and where its SysML source sits so a resolver can find it.
-# It does not select model content: the project's native SysML imports and its
-# ProjectMethodBinding decide what is in the model. Semantic fields
-# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
-# removed at the native semantic flip and are now rejected if present.
-name: '{{name}}'
-entrypoint: model/catalog/project.sysml
-include: [model]
-version: 0.1.0
-description: MEMO infusion pump model

package/templates/infusion-pump/model/catalog/architecture/system.sysml

@@ -1,5 +0,0 @@
-package infusion_pump_architecture {
-    private import memo::*;
-
-    part infusionPump : PhysicalAssembly;
-}

package/templates/infusion-pump/model/catalog/artifacts/catalog.sysml

@@ -1,5 +0,0 @@
-package infusion_pump_artifacts {
-    private import memo::*;
-
-    // Add project artifact usages here.
-}

package/templates/infusion-pump/model/catalog/assurance/requirements.sysml

@@ -1,7 +0,0 @@
-package infusion_pump_assurance {
-    private import memo::*;
-
-    requirement deliveryRequirement : Requirement {
-        attribute redefines statement = "Define safe therapy delivery behavior";
-    }
-}

package/templates/infusion-pump/model/catalog/project.sysml

@@ -1,30 +0,0 @@
-// Project identity and method binding — the project's native entrypoint.
-//
-// The imports below name the reusable packages this project resolves, and the
-// binding names its methodology with a typed SysML reference. Nothing outside
-// SysML selects model content: delete every YAML file beside this one and the
-// model still means exactly what it means now.
-package infusion_pump_catalog {
-    private import ScalarValues::*;
-
-    private import memo_core_enumerations::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-
-    private import infusion_pump_architecture::*;
-    private import infusion_pump_assurance::*;
-    private import infusion_pump_artifacts::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part projectMethodBinding : ProjectMethodBinding {
-        @MemoIdentity { :>> providedId = "PMB-001"; }
-        attribute :>> name = "{{name}}ProjectMethodBinding";
-        attribute :>> projectName = "{{name}}";
-        ref :>> selectedMethodology = mdDefaultDefinition;
-        // The project adds no modules of its own yet. Under `explicit` an
-        // empty additive list means exactly that — no additions — rather than
-        // being read as "everything".
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-    }
-}

package/templates/infusion-pump/package.json

@@ -1,8 +0,0 @@
-{
-  "name": "{{npmName}}",
-  "version": "0.1.0",
-  "private": true,
-  "dependencies": {
-    "@memoarchitect/ontology": "{{ontologyVersion}}"
-  }
-}

package/templates/infusion-pump/syside.toml

@@ -1,13 +0,0 @@
-#:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
-
-include = [
-    "model",
-    "node_modules/@memoarchitect/ontology/src",
-]
-
-exclude = [
-    ".memo",
-    ".sysand",
-    "dist",
-    "output",
-]

package/templates/monitoring-device/memo.package.yaml

@@ -1,13 +0,0 @@
-# Application/distribution descriptor for this MEMO package.
-#
-# Identity and location only. It records what this package is called, what
-# version it is, and where its SysML source sits so a resolver can find it.
-# It does not select model content: the project's native SysML imports and its
-# ProjectMethodBinding decide what is in the model. Semantic fields
-# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
-# removed at the native semantic flip and are now rejected if present.
-name: '{{name}}'
-entrypoint: model/catalog/project.sysml
-include: [model]
-version: 0.1.0
-description: MEMO monitoring device model

package/templates/monitoring-device/model/catalog/architecture/system.sysml

@@ -1,5 +0,0 @@
-package monitoring_device_architecture {
-    private import memo::*;
-
-    part monitoringDevice : PhysicalAssembly;
-}

package/templates/monitoring-device/model/catalog/artifacts/catalog.sysml

@@ -1,5 +0,0 @@
-package monitoring_device_artifacts {
-    private import memo::*;
-
-    // Add project artifact usages here.
-}

package/templates/monitoring-device/model/catalog/assurance/requirements.sysml

@@ -1,7 +0,0 @@
-package monitoring_device_assurance {
-    private import memo::*;
-
-    requirement monitoringRequirement : Requirement {
-        attribute redefines statement = "Define the monitored physiological parameter";
-    }
-}

package/templates/monitoring-device/model/catalog/project.sysml

@@ -1,30 +0,0 @@
-// Project identity and method binding — the project's native entrypoint.
-//
-// The imports below name the reusable packages this project resolves, and the
-// binding names its methodology with a typed SysML reference. Nothing outside
-// SysML selects model content: delete every YAML file beside this one and the
-// model still means exactly what it means now.
-package monitoring_device_catalog {
-    private import ScalarValues::*;
-
-    private import memo_core_enumerations::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-
-    private import monitoring_device_architecture::*;
-    private import monitoring_device_assurance::*;
-    private import monitoring_device_artifacts::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part projectMethodBinding : ProjectMethodBinding {
-        @MemoIdentity { :>> providedId = "PMB-001"; }
-        attribute :>> name = "{{name}}ProjectMethodBinding";
-        attribute :>> projectName = "{{name}}";
-        ref :>> selectedMethodology = mdDefaultDefinition;
-        // The project adds no modules of its own yet. Under `explicit` an
-        // empty additive list means exactly that — no additions — rather than
-        // being read as "everything".
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-    }
-}

package/templates/monitoring-device/package.json

@@ -1,8 +0,0 @@
-{
-  "name": "{{npmName}}",
-  "version": "0.1.0",
-  "private": true,
-  "dependencies": {
-    "@memoarchitect/ontology": "{{ontologyVersion}}"
-  }
-}

package/templates/monitoring-device/syside.toml

@@ -1,13 +0,0 @@
-#:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
-
-include = [
-    "model",
-    "node_modules/@memoarchitect/ontology/src",
-]
-
-exclude = [
-    ".memo",
-    ".sysand",
-    "dist",
-    "output",
-]

package/templates/samd/memo.package.yaml

@@ -1,13 +0,0 @@
-# Application/distribution descriptor for this MEMO package.
-#
-# Identity and location only. It records what this package is called, what
-# version it is, and where its SysML source sits so a resolver can find it.
-# It does not select model content: the project's native SysML imports and its
-# ProjectMethodBinding decide what is in the model. Semantic fields
-# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
-# removed at the native semantic flip and are now rejected if present.
-name: '{{name}}'
-entrypoint: model/catalog/project.sysml
-include: [model]
-version: 0.1.0
-description: MEMO software as a medical device model

package/templates/samd/model/catalog/architecture/system.sysml

@@ -1,5 +0,0 @@
-package samd_architecture {
-    private import memo::*;
-
-    part samdDevice : SoftwareSystem;
-}

package/templates/samd/model/catalog/artifacts/catalog.sysml

@@ -1,5 +0,0 @@
-package samd_artifacts {
-    private import memo::*;
-
-    // Add project artifact usages here.
-}

package/templates/samd/model/catalog/assurance/requirements.sysml

@@ -1,7 +0,0 @@
-package samd_assurance {
-    private import memo::*;
-
-    requirement clinicalPurpose : Requirement {
-        attribute redefines statement = "Define the clinical purpose and intended user";
-    }
-}

package/templates/samd/model/catalog/project.sysml

@@ -1,30 +0,0 @@
-// Project identity and method binding — the project's native entrypoint.
-//
-// The imports below name the reusable packages this project resolves, and the
-// binding names its methodology with a typed SysML reference. Nothing outside
-// SysML selects model content: delete every YAML file beside this one and the
-// model still means exactly what it means now.
-package samd_catalog {
-    private import ScalarValues::*;
-
-    private import memo_core_enumerations::*;
-    private import memo_methodology_core::*;
-    private import memo_methodology_profiles::*;
-
-    private import samd_architecture::*;
-    private import samd_assurance::*;
-    private import samd_artifacts::*;
-
-    private import memo_core_common::*;
-    private import memo_core_common::MemoIdentity;
-    part projectMethodBinding : ProjectMethodBinding {
-        @MemoIdentity { :>> providedId = "PMB-001"; }
-        attribute :>> name = "{{name}}ProjectMethodBinding";
-        attribute :>> projectName = "{{name}}";
-        ref :>> selectedMethodology = mdDefaultDefinition;
-        // The project adds no modules of its own yet. Under `explicit` an
-        // empty additive list means exactly that — no additions — rather than
-        // being read as "everything".
-        attribute :>> scopeMode = ScopeModeKind::explicit;
-    }
-}

package/templates/samd/package.json

@@ -1,8 +0,0 @@
-{
-  "name": "{{npmName}}",
-  "version": "0.1.0",
-  "private": true,
-  "dependencies": {
-    "@memoarchitect/ontology": "{{ontologyVersion}}"
-  }
-}

package/templates/samd/syside.toml

@@ -1,13 +0,0 @@
-#:schema https://docs.sensmetry.com/schemas/latest/syside.schema.json
-
-include = [
-    "model",
-    "node_modules/@memoarchitect/ontology/src",
-]
-
-exclude = [
-    ".memo",
-    ".sysand",
-    "dist",
-    "output",
-]