Skip to content
Snippets Groups Projects
Commit ac7ad717 authored by canterburym's avatar canterburym Committed by canterburym
Browse files

Changes to revision 2, including new Auth status values

parent 6e7724ab
No related branches found
No related tags found
1 merge request!58TS 103 120 CR039 - Multiple Endpoint Workflow Profile
Pipeline #14100 passed
......@@ -90,6 +90,14 @@
<Value>Invalid</Value>
<Meaning>The Authorisation is not active due to a problem with the current information populated in the Authorisation Object.</Meaning>
</DictionaryEntry>
<DictionaryEntry>
<Value>CreatingForCSP</Value>
<Meaning>The LEA is in the process of creating the Authorisation with the CSP (i.e. in the process of uploading the relevant components). For example, it could be used as described in H.3.3</Meaning>
</DictionaryEntry>
<DictionaryEntry>
<Value>SubmittedToCSP</Value>
<Meaning>The LEA has now uploaded all the relevant objects for this Authorisation to the CSP e.g. it could be used as described in H.3.3. This is intended to convey that the LEA has submitted all the relevant to this Authorisation and the CSP can now proceed</Meaning>
</DictionaryEntry>
</DictionaryEntries>
</Dictionary>
<Dictionary> <!--AuthorisationDesiredStatus: see Clause 7.2.6 Table 7.7 -->
......@@ -124,6 +132,14 @@
<Value>Expired</Value>
<Meaning>The expiry date for this Authorisation has passed, meaning that the Authorisation has lapsed.</Meaning>
</DictionaryEntry>
<DictionaryEntry>
<Value>CreatingForCSP</Value>
<Meaning>The LEA is in the process of creating the Authorisation with the CSP (i.e. in the process of uploading the relevant components). For example, it could be used as described in H.3.3</Meaning>
</DictionaryEntry>
<DictionaryEntry>
<Value>SubmittedToCSP</Value>
<Meaning>The LEA has now uploaded all the relevant objects for this Authorisation to the CSP e.g. it could be used as described in H.3.3. This is intended to convey that the LEA has submitted all the relevant to this Authorisation and the CSP can now proceed</Meaning>
</DictionaryEntry>
</DictionaryEntries>
</Dictionary>
<Dictionary> <!--AuthorisationFlags: see Clause 7.2.5 Table 7.6 -->
......
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:etsi="http://uri.etsi.org/03280/common/2017/07"
xmlns:common="http://uri.etsi.org/03120/common/2016/02/Common"
xmlns:core="http://uri.etsi.org/03120/common/2019/10/Core"
xmlns="http://uri.etsi.org/03120/common/2023/01/Submission"
targetNamespace="http://uri.etsi.org/03120/common/2023/01/Submission"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://uri.etsi.org/03120/common/2016/02/Common" />
<xs:import namespace="http://uri.etsi.org/03120/common/2019/10/Core" />
<xs:import namespace="http://uri.etsi.org/03280/common/2017/07"/>
<xs:complexType name="SubmissionObject">
<xs:complexContent>
<xs:extension base="core:HI1Object">
<xs:sequence>
<xs:element name="SubmissionStatus" type="common:DictionaryEntry" minOccurs="0"></xs:element>
<xs:element name="SubmissionDesiredStatus" type="common:DictionaryEntry" minOccurs="0"></xs:element>
<xs:element name="SubmissionInvalidReason" type="core:ActionUnsuccesfulInformation" minOccurs="0"></xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:schema>
......@@ -39,7 +39,6 @@
"103120/schema/ts_103120_Notification.xsd",
"103120/schema/ts_103120_Task.xsd",
"103120/schema/ts_103120_TrafficPolicy.xsd",
"103120/schema/ts_103120_Submission.xsd",
"103280/TS_103_280.xsd",
"testing/deps/xmldsig/xmldsig-core-schema.xsd",
"103120/examples/FooServiceSchema.xsd"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment