<img>A diagram showing a class "MilitaryHistory" with attributes "MilitaryHistoryType" and "@Attributes". It also
shows a relationship to "hr:MilitaryHistoryID" and "MilitaryService".</img>
Element
Description
Cardinality
Rule
Examples
MilitaryHistory
Information about the person's military service
0..1
N/A
N/A
Sub-elements
Element
Description
Cardinality
Rule
Examples
MilitaryHistoryID
Identifier of military history
0..1
N/A
"MIL-1234", "344", etc.
MilitaryService
Description of military service
0..n
N/A
N/A
See section /CandidateProfile/MilitaryHistory/MilitaryService for more information
<img>A diagram showing a class "MilitaryHistoryType" with attributes "validFrom" and "validTo". It also shows a
relationship to "MilitaryHistory" which represents military history records.</img>
Attributes
Description
Card.
Rule
validFrom
Validity start date for this entity's information
0..1
BR-COM-06: Compulsory Date Format is: YYYY-MM-DD, YYYY-MM, YYYY or YYYY-MM-DDThh:mm:ss.
validTo
Validity end date for this entity's information
0..1
BR-COM-06: Compulsory Date Format is: YYYY-MM-DD, YYYY-MM, YYYY or YYYY-MM-DDThh:mm:ss.
MilitaryHistoryID attributes
Attributes
Description
Card.
Rule
Refer to IdentifierType Attributes section for additional attributes.
MilitaryService attributes
Attributes
Description
Card.
Rule
See section /CandidateProfile/MilitaryHistory/MilitaryService for more information
graph TD
subgraph " "
A[hr:MilitaryServiceID]
B[CountryCode]
C[hr:MilitaryBranch]
D[hr:MilitaryDivision]
E[eures:ServicePeriod]
F[hr:StartingRank]
G[hr:CurrentOrEndingRank]
end
subgraph " "
H[MilitaryServiceType]
I[MilitaryServiceBaseType (extension base)]
J[Attributes]
end
subgraph " "
K[MilitaryService]
end
A --> H
B --> H
C --> H
D --> H
E --> H
F --> H
G --> H
H --> I
I --> J
J --> K
style A fill:#fff,stroke:#333,stroke-width:2px
style B fill:#fff,stroke:#333,stroke-width:2px
style C fill:#fff,stroke:#333,stroke-width:2px
style D fill:#fff,stroke:#333,stroke-width:2px
style E fill:#fff,stroke:#333,stroke-width:2px
style F fill:#fff,stroke:#333,stroke-width:2px
style G fill:#fff,stroke:#333,stroke-width:2px
style H fill:#e0e0e0,stroke:#333,stroke-width:2px
style I fill:#e0e0e0,stroke:#333,stroke-width:2px
style J fill:#fff,stroke:#333,stroke-width:2px
style K fill:#e0e0e0,stroke:#333,stroke-width:2px
Element
Description
Cardinality
Rule
Examples
MilitaryService
Description of military service
0..n
N/A
N/A
Sub-elements
MilitaryServiceID
Identifier of military service
0..1
N/A
"MS-291", "MS-121", etc.
CountryCode
A code specifying the country where the candidate did/does military service
0..1
Compulsory use of CountriesAndNationalities [ECV02], AuxCountriesAndNationalities [ECV10] code list.
The military office or department in which the person served
0..1
N/A
"Army", "Navy", etc.
MilitaryDivision
A portion of an army or fleet, consisting of a definite number
0..1
N/A
"Air assault", "Armoured", "Infantry", etc.
erDiagram
MilitaryService ||--o{ MilitaryServiceType : "It contains description of military service."
MilitaryServiceBaseType ||--|{ Attributes : "Attributes"
Attributes ||--|{ hr:EffectiveDateAttributeGroup : "HR-XML's 3.0 architecture makes a distinction between effective-date
meta data and effective dating that is an integral..."
BR-COM-05: If not specified, the “validFrom” date will default to “assigned by EURES on
reception”. BR-COM-06: Compulsory Date Format is: YYYY-MM-DD, YYYY-MM, YYYY or
YYYY-MM-DDThh:mm:ss.
validTo
Validity end date for this entity’s information
0..1
BR-COM-07: If not specified, the “validTo” date will be decided by EURES depending on the
transaction context. BR-COM-06: Compulsory Date Format is: YYYY-MM-DD, YYYY-MM, YYYY or
YYYY-MM-DDThh:mm:ss.
MilitaryServiceID attributes
Attributes
Description
Card.
Rule
Refer to IdentifierType Attributes section for additional attributes.
ServicePeriod attributes
See section /CandidateProfile/MilitaryHistory/MilitaryService/ServicePeriod for more information
CountryCode attributes
Attributes
Description
Card.
Rule
validFrom
Validity start date for this entity’s information
0..1
BR-COM-05: If not specified, the “validFrom” date will default to “assigned by EURES on
reception”.
BR-COM-06: Compulsory Date Format is: YYYY-MM-DD, YYYY-MM, YYYY or YYYY-MM-DDThh:mm:ss.
validTo
Validity end date for this entity's information
0..1
BR-COM-07: If not specified, the "validTo" date will be decided by EURES depending on the transaction
context. BR-COM-06: Compulsory Date Format is: YYYY-MM-DD, YYYY-MM, YYYY or YYYY-MM-DDThh:mm:ss.
Refer to CodeListAttributeGroup Attributes section for additional attributes.