lutaml-uml 0.4.3 → 0.5.2

data/config/package_metadata.example.yml

@@ -0,0 +1,58 @@
+# Package Metadata Configuration Example
+#
+# This file demonstrates how to configure package metadata for use with
+# LutaML's PackageMetadata system.
+#
+# Package metadata enables external configuration of:
+# - XSD generation: xmlns, targetNamespace, schemaLocation
+# - Documentation: Package descriptions
+# - Styling: Package-specific styling rules
+# - Validation: Package constraints
+#
+# Format: YAML with "packages" root key
+
+packages:
+  # Exact package path match
+  "ModelRoot::i-UR::Urban Planning ADE 3.2::uro":
+    xmlns: "http://www.kantei.go.jp/jp/singi/tiiki/toshisaisei/itoshisaisei/iur/uro/2.0"
+    targetNamespace: "http://www.kantei.go.jp/jp/singi/tiiki/toshisaisei/itoshisaisei/iur/uro/2.0"
+    schemaLocation: "../../schemas/uro/2.0/urbanObject.xsd"
+    prefix: "uro"
+    documentation: |
+      Urban Object package containing classes for urban planning and
+      infrastructure modeling in PLATEAU i-UR standard.
+    version: "2.0"
+
+  # Another exact match
+  "ModelRoot::CityGML2.0::Core":
+    xmlns: "http://www.opengis.net/citygml/2.0"
+    targetNamespace: "http://www.opengis.net/citygml/2.0/core"
+    schemaLocation: "http://schemas.opengis.net/citygml/2.0/cityGMLBase.xsd"
+    prefix: "core"
+    documentation: "CityGML 2.0 Core module - fundamental city model classes"
+
+  # Wildcard pattern: matches any direct child of ModelRoot::CityGML2.0
+  "ModelRoot::CityGML2.0::*":
+    xmlns: "http://www.opengis.net/citygml/2.0"
+    prefix: "citygml"
+    documentation: "Default CityGML 2.0 namespace"
+
+  # Multi-level wildcard: matches ModelRoot::<anything>::Common
+  "ModelRoot::*::Common":
+    documentation: "Common elements package"
+    category: "utilities"
+
+  # Package with custom metadata
+  "ModelRoot::CustomPackage":
+    xmlns: "http://example.com/custom/1.0"
+    prefix: "custom"
+    author: "Your Organization"
+    license: "Apache-2.0"
+    contact: "info@example.com"
+
+# Notes:
+# 1. Exact matches take precedence over wildcard patterns
+# 2. Multiple wildcards can match the same package path
+# 3. Metadata from all matches is merged (exact match wins)
+# 4. Any custom keys are supported beyond the standard ones
+# 5. Package paths use "::" as separator (UML qualified name format)

data/config/static_site.yml

@@ -0,0 +1,166 @@
+# LutaML Static Site Generator Configuration
+# External configuration following YAGNI and separation of concerns
+
+version: "1.0"
+description: "Configuration for LutaML UML Browser SPA Generator"
+
+# Output Configuration
+output:
+  modes:
+    single_file:
+      enabled: true
+      default_filename: "browser.html"
+      embed_data: true
+      embed_styles: true
+      embed_scripts: true
+      minify: false
+    multi_file:
+      enabled: true
+      default_directory: "dist"
+      data_directory: "data"
+      assets_directory: "assets"
+      minify: false
+
+# Template Configuration
+templates:
+  base_path: "templates/static_site"
+  layouts:
+    single_file: "single_file.liquid"
+    multi_file: "multi_file.liquid"
+  components:
+    - header
+    - sidebar
+    - tree_node
+    - content
+    - package_details
+    - class_details
+
+# Data Transformation Configuration
+data_transformation:
+  include_diagrams: true
+  format_definitions: true
+  max_definition_length: null
+  normalize_paths: true
+  generate_statistics: true
+
+# Search Index Configuration
+search:
+  enabled: true
+  fields:
+    - name: "name"
+      boost: 10
+      searchable: true
+    - name: "qualifiedName"
+      boost: 5
+      searchable: true
+    - name: "type"
+      boost: 3
+      searchable: true
+    - name: "package"
+      boost: 2
+      searchable: true
+    - name: "content"
+      boost: 1
+      searchable: true
+  document_types:
+    - type: "class"
+      boost: 1.5
+      enabled: true
+    - type: "attribute"
+      boost: 1.0
+      enabled: true
+    - type: "association"
+      boost: 0.8
+      enabled: true
+    - type: "package"
+      boost: 1.2
+      enabled: true
+  stop_words:
+    - "the"
+    - "a"
+    - "an"
+    - "and"
+    - "or"
+    - "but"
+    - "in"
+    - "on"
+    - "at"
+    - "to"
+    - "for"
+    - "of"
+    - "with"
+    - "from"
+    - "by"
+  pipeline:
+    - "stemmer"
+    - "stopWordFilter"
+
+# Asset Configuration
+assets:
+  styles:
+    - "00-variables.css"
+    - "01-reset.css"
+    - "02-base.css"
+    - "03-layout.css"
+    - "04-components.css"
+    - "05-utilities.css"
+  scripts:
+    - "core/utils.js"
+    - "core/state.js"
+    - "ui/sidebar.js"
+    - "ui/search.js"
+    - "ui/details.js"
+    - "app.js"
+  cdn:
+    alpinejs: "https://cdn.jsdelivr.net/npm/alpinejs@3.13.3/dist/cdn.min.js"
+    lunrjs: "https://cdn.jsdelivr.net/npm/lunr@2.3.9/lunr.min.js"
+
+# UI Configuration
+ui:
+  title: "UML Model Browser"
+  description: "Interactive browser for UML models"
+  theme:
+    default: "light"
+    allow_toggle: true
+  sidebar:
+    width: "320px"
+    collapsible: true
+    default_expanded: false
+  breadcrumb:
+    enabled: true
+    separator: "/"
+  statistics:
+    enabled: true
+    display_on_welcome: true
+
+# Feature Flags
+features:
+  search: true
+  dark_mode: true
+  keyboard_shortcuts: true
+  breadcrumbs: true
+  statistics: true
+  diagrams: true
+  export: false  # Future feature
+  print: false   # Future feature
+
+# Plugin System
+plugins:
+  serializers: []  # Custom serializers can be registered
+  transformers: [] # Custom transformers can be registered
+  filters: []      # Custom Liquid filters
+
+# Performance Configuration
+performance:
+  lazy_loading: false
+  virtual_scrolling: false
+  chunk_size: 1000
+  cache_enabled: true
+
+# Accessibility Configuration
+accessibility:
+  wcag_level: "AA"
+  keyboard_nav: true
+  aria_labels: true
+  focus_indicators: true
+  reduced_motion: true

data/docs/adr/0001-repository-facade-stays-large.md

@@ -0,0 +1,43 @@
+# ADR-0001: Repository Facade Stays Large for API Stability
+
+Date: 2026-07-14
+
+## Context
+
+`Lutaml::UmlRepository::Repository` is 689 LOC with 30+ public
+methods, each a one-line forwarder to one of six query services
+(`ClassQuery`, `InheritanceQuery`, `AssociationQuery`,
+`PackageQuery`, `SearchQuery`, `DiagramQuery`).
+
+Architecture review flagged this as a shallow facade — the
+deletion test (deleting Repository would not concentrate
+complexity, the query services already own it) suggested it's a
+pass-through.
+
+## Decision
+
+**Keep the facade as-is.** The Repository's 30+ methods are the
+gem's primary public surface. The ergonomics (`repo.find_class`
+vs `repo.class_query.find`) win over file-size aesthetics.
+
+## Consequences
+
+- The file stays over the 300-LOC guideline. Per-line complexity
+  is extremely low (mostly one-line delegations).
+- New query methods still get added to Repository as one-line
+  forwarders — the API growth is intentional.
+- The query services (`ClassQuery`, `InheritanceQuery`, etc.)
+  are also exposed via reader methods (`repo.class_query`,
+  `repo.inheritance_query`) for callers who want composition.
+
+## Alternatives considered
+
+1. **`method_missing` forwarding** — rejected: loses explicit
+   API surface, breaks IDE autocomplete and YARD docs.
+2. **Expose query objects as the public API** — rejected:
+   breaks every existing caller across `ea`, `lutaml-lml`, and
+   the `lutaml` meta-bundle.
+
+## References
+
+- TODO.refactor/01-repository-facade-pruning.md

data/docs/adr/0002-spa-shape-implicit-until-volatile.md

@@ -0,0 +1,45 @@
+# ADR-0002: SPA Document Shape Stays Implicit Until Volatile
+
+Date: 2026-07-14
+
+## Context
+
+The SPA generation pipeline (Generator → DataTransformer → 6
+serializers → 19 SPA model files → Vue templates) has no single
+declared contract for the shape of `SpaDocument`. Adding a
+field today requires touching the model file, the serializer,
+and the Vue template.
+
+Architecture review suggested introducing a typed `SpaSchema`
+as the single contract.
+
+## Decision
+
+**Defer.** The shape is currently stable (the Vue IIFE is
+checked into `frontend/dist/`, indicating the format is baked).
+A typed schema on the Ruby side cannot enforce the Vue
+(JavaScript) side contract directly — it would only constrain
+the serializer half. The implicit contract is currently
+enforced by the SPA generator's round-trip specs.
+
+## Consequences
+
+- The 19 SPA model files + 6 serializers continue to be the
+  implicit shape declaration.
+- Future shape changes ripple across model + serializer + Vue
+  template. This is acceptable while changes are rare.
+- When shape volatility emerges (multiple new fields per
+  release), revisit and introduce the typed schema.
+
+## Alternatives considered
+
+1. **Introduce `SpaSchema` now** — rejected: duplicates the
+   round-trip specs and adds a layer to keep in sync without
+   enforcing the Vue side.
+2. **Move to TypeScript on the Vue side with shared schema** —
+   out of scope for this gem; would require a separate
+   codegen step.
+
+## References
+
+- TODO.refactor/02-spa-pipeline-typed-schema.md