Skip to content

Commit b516274

Browse files
fix: typo [0..1]
1 parent 5a847a3 commit b516274

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

specs/index.bs

+17-17
Original file line numberDiff line numberDiff line change
@@ -170,40 +170,40 @@ They are the context from which supporting data transactions ([[#txns]]) are def
170170

171171
The following business cases shall be supported by this specification:
172172

173-
: <dfn>Business Case #1</dfn>: Quantify Avoided Emissions
173+
: <dfn>Business Case #1</dfn>: Quantify Avoided Emissions
174174
::
175-
A [=Transport Service User=] requests their service provider ([=Transport Service Organizer=] or ([=Transport Operator=])) to share GHG emissions at the TCE level, to enable accurate emissions accounting based on primary data.
176-
This allows the Transport Service User to compare the logistics emissions reduction resulting of the introduction of specific operational changes with the emissions without the intervention.
175+
A [=Transport Service User=] requests their service provider ([=Transport Service Organizer=] or ([=Transport Operator=])) to share GHG emissions at the TCE level, to enable accurate emissions accounting based on primary data.
176+
This allows the Transport Service User to compare the logistics emissions reduction resulting of the introduction of specific operational changes with the emissions without the intervention.
177177
This is enabled through [[#txn1]].
178178

179179
: Business Case #2: Procurement of carbon-efficient services
180180
::
181-
A [=Transport Service Organizer=] requests their service provider ([=Transport Operator=]) to share GHG emissions at the TOC or HOC level.
181+
A [=Transport Service Organizer=] requests their service provider ([=Transport Operator=]) to share GHG emissions at the TOC or HOC level.
182182
By incorporating emission intensities (HOCs or TOCs) in procurement processes, the Transport Service Organizer is enabled to choose services that are offer carbon-efficiency advantages.
183183
This is enabled through [[#txn2]].
184-
185-
: Business Case #3: Enable Emissions Calculations from Activity Data
184+
185+
: Business Case #3: Enable Emissions Calculations from Activity Data
186186
::
187-
A [=Transport Service Organizer=] requests their service provider ([=Transport Operator=]) to share [=Transport Activity=] data to enable the estimation of emissions from the contracted services.
187+
A [=Transport Service Organizer=] requests their service provider ([=Transport Operator=]) to share [=Transport Activity=] data to enable the estimation of emissions from the contracted services.
188188
This is enabled through [[#txn3]].
189-
ISSUE: I would argue this is not a business case, but just a data transaction.
189+
ISSUE: I would argue this is not a business case, but just a data transaction.
190190

191-
: Business Case #4: Disclose Logistics Emissions as Part of PCFs
191+
: Business Case #4: Disclose Logistics Emissions as Part of PCFs
192192
::
193193
A [=Transport Service User=] is requested by their customers to disclose logistics emissions as part of a [=PCF=].
194194
This is enabled through the usage of the Pathfinder Technical Specification
195195
and disclosing through so-called Data Model Extensions based on the iLEAP
196-
Data Model ([[#data-model]]) . See the Pathfinder [[!DATA-MODEL-EXTENSIONS]] specification.
196+
Data Model ([[#data-model]]) . See the Pathfinder [[!DATA-MODEL-EXTENSIONS]] specification.
197197

198198
## Potential additional Business Cases ## {#txns-appendix}
199199

200-
: Business Case #a1: Forecasting
201-
:: A [=Transport Service User=] requests their service provider ([=Transport Service Organizer=] or [=Transport Operator=]) to share GHG emissions at the TOC or HOC level. This enables the Transport Service User to forecast emissions related to specific activities or services, before these take place.
200+
: Business Case #a1: Forecasting
201+
:: A [=Transport Service User=] requests their service provider ([=Transport Service Organizer=] or [=Transport Operator=]) to share GHG emissions at the TOC or HOC level. This enables the Transport Service User to forecast emissions related to specific activities or services, before these take place.
202202

203203
: Business Case #a2: Book & Claim
204-
:: A [=Transport Service Organizer=] requests their service provider ([=Transport Operator=]) to share with them emissions attributes according to a book & claim scheme.
205-
206-
Note: This business case is currently out of scope. It might be supported in the future, as book & claim methodologies and related variables are considered in scope of these technical specifications.
204+
:: A [=Transport Service Organizer=] requests their service provider ([=Transport Operator=]) to share with them emissions attributes according to a book & claim scheme.
205+
206+
Note: This business case is currently out of scope. It might be supported in the future, as book & claim methodologies and related variables are considered in scope of these technical specifications.
207207

208208

209209
# Data Transactions # {#txns}
@@ -1453,10 +1453,10 @@ The following properties are defined for data type <dfn element>Feedstock</dfn>:
14531453
<td>O
14541454
<td>Percentage of the feedstock in the total composition of energy carrier.
14551455
<tr>
1456-
<td><dfn>regionProvenance</dfn> : [0..1]
1456+
<td><dfn>regionProvenance</dfn>
14571457
<td>String
14581458
<td>O
1459-
<td>Country or region of provenance of the feedstock.
1459+
<td>Country or region of provenance of the feedstock.
14601460
</table>
14611461
</figure>
14621462

0 commit comments

Comments
 (0)