Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • CIMpy CIMpy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ACS
  • Public
  • CIM
  • CIMpyCIMpy
  • Issues
  • #33
Closed
Open
Issue created Nov 30, 2020 by Jonathan Klimt@jonathan.klimtDeveloper

Automatically determine Profile and store profiles in metadata

According to https://docstore.entsoe.eu/Documents/CIM_documents/Grid_Model_CIM/CGMES_v2.4.14_FileHeaderGuidelines_v1.0.0.pdf the profile of an xml is contained in the key <md:Model.profile>.

One to many URN/URI describing the profiles that governs this model. It uniquely identifies the profiles and its version.

For the IEC standardized Profiles, this should be something like:

  • http://iec.ch/TC57/61970-453/DiagramLayout/2
  • But there seem to exist other profiles (probably pre-IEC Standard).
    • http://entsoe.eu/CIM/EquipmentCore/3/1

However, I think it is feasible to automatically determine the profile from that xml key.

  • Check the IEC standard if this is still valid
  • Get all the profile strings supported by cimpy (I think it is only the IEC ones)|
  • Write a function which matches the profile
    • either define a set of supported strings (e.g. IEC) or match if the string contains e.g. Equipment and not Topology
  • Store the profile in the cimpy metadata
  • Remove the profile list requirement from generate_xml and cim_export (maybe make it optional)
  • Profit
Assignee
Assign to
Time tracking