Skip to content

IDTA-02035-1 : Digital Battery Passport – Part 4 Technical Data v1.0.1: Clarification on 20% and 80% SoC requirements for OriginalPowerCapability #321

Description

@aditya-work-dev

Background:
For OriginalPowerCapability, the specification states that power capability measurements for EV and industrial batteries must include measurements at both 80% and 20% state of charge

Image

The corresponding PowerCapabilityAt element has cardinality [1..*], allowing one or more measurements. However, its description says that a reference condition can be, for example, 80% or 20% SoC.

Image

Finally, the atSoc property again states that measurements must include 80% and 20% SoC for EV and industrial batteries, while the provided JSON example contains only the value 80.

Image Image

Observation:

There appear to be two ambiguities:

1. AND vs OR
OriginalPowerCapability and atSoc state that measurements must include 80% AND 20% while the description of PowerCapabilityAt refers to: 80% OR 20%

2. Cardinality for PowerCapabilityAt currently has [1..*]
If both 20% and 80% measurements are mandatory for EV and industrial batteries, at least two entries would be needed:
For Example:
OriginalPowerCapability
├── PowerCapabilityAt
│ └── atSoc = 20
└── PowerCapabilityAt
│ └── atSoc = 80

Should the cardinality therefore be changed to accept the above scenario or remain [1..*] and the requirement for 20% and 80% be expressed as a conditional validation rule for EV and industrial batteries?

Possible clarification:

  1. If both measurements are intended to be mandatory, it may be helpful to make the AND requirement consistent across the descriptions.
  2. Updating the example to contain both atSoc = 20 and atSoc = 80, if the decision is made to make those two values compulsory.
  3. Considering the perspective of validation, how this conditional requirement should be represented and validated?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions