update all compliance thts docs

* add/sanitize all compliance thts documents
* add/sanitize all compliance versions
* use specification layout as base for compliance layout

Signed-off-by: Toshaan Bharvani <toshaan@vantosh.com>
remotes/1693381142243034077/jamesk-patch-1
Toshaan Bharvani 3 years ago
parent 7902a5d781
commit b8905dc651

@ -0,0 +1,30 @@
---
title: 64-bit ELF v2 ABI Compliance TH/TS Specification for OpenPOWER Architecture
group: compliance
publicreview: false
tags:
- specifications
- systemsoftware
- abi
- toolchain
- compliler
- testsuite
- testharness
date: 2017-06-27
draft: false
---

This document provides requirements on a test implementation targeting the Application Binary Interface (ABI) for OpenPOWER.
Currently, this test implementation is shipped with the gcc sources, and so forms part of the official gcc build and test process.

The OpenPOWER ELFv2 Application Binary Interface (ABI) Compliance Test Harness and Test Suite (TH/TS) Specification provides
the test suite requirements to demonstrate compliance with the OpenPOWER 64-bit ELFv2 ABI Specification.
It describes the tests required in the test suite and a test harness needed to execute the test suite.
It also describes the successful execution of the test suite, including what it means for an optional feature to fail.

This document is a Standard Track, Work Group Specification work product owned by the Compliance Workgroup and
handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
It was created using the Master Template Guide version 1.0.0.

Comments, questions, etc. can be submitted to the public mailing list for this document at
<openpower-elfv2abi-thts@mailinglist.openpowerfoundation.org>.

@ -0,0 +1,9 @@
---
title: "Compliance Specifications"
date: 2022-01-06
outputs:
- html
- json
- rss
draft: false
---

@ -0,0 +1,41 @@
---
title: Advanced Accelerator Adapter 25Gbps I/O Compliance Test Harness and Test Suite Specification
group: accelerator
publicreview: false
tags:
- specification
- compliance
- testharness
- testsuite
- 25gbps
- 25gio
- advancedacceleratoradapter
- accelerator
- capi30
- opencapi
date: 2018-11-05
draft: false
---

The purpose of the OpenPOWER Advanced Accelerator Adapter Compliance 25Gbps I/O Test Harness and Test Suite specification is
to provide the test suite requirements to demonstrate OpenPOWER Advanced Accelerator Adapter 25G I/O compliance for POWER9™ systems.

The input to this specification is the following specification :
OpenPOWER Advanced Accelerator Adapter Electro-Mechanical Specification
which describes electro-mechanical specification for advanced accelerator adapters within the OpenPOWER ecosystem supported by IBM POWER9.

There are two accelerator approaches for the 25Gbit/sec interface and
the compliance for each approach is defined in this document.
The first approach is a Mezzanine Adapter Card which is attached to the system planar via two connectors.
The Mezzanine Adapter Card for OpenPOWER systems based on the POWER9 processor attaches to the 25Gbit/sec interface native to
the POWER9 and plugs into the mezzanine card connectors.

The second approach is a Cabled Interface Extension to an adapter card.
It uses a PCIe card as an example but the cabled extension does not require the adapter card be PCIe.
POWER9 platforms support the optional cabling of the 25Gbit/sec Advanced Accelerator Interface to
the advanced accelerator adapter in a riser card plugged into a PCIe slot in the same system.
In addition, the adapter could be located in different drawer of the rack.

This document is a Standard Track, Work Group Specification work product owned by the Compliance Workgroup and
handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
Comments, questions, etc. can be submitted to the public mailing list for this document at <openpower-25gio-thts@mailinglist.openpowerfoundation.org>.

@ -0,0 +1,28 @@
---
title: OpenPOWER Architecture Compliance Definition
group: compliance
publicreview: false
tags:
- compliance
- architecture
- power8
- power9
date: 2019-07-23
draft: false
---

The purpose of the OpenPOWER Architecture Compliance Definition document is to give a consistent approach
to compliance under the guidance of the Compliance Work Group.

It contains the following :
- Document the OpenPOWER specifications that contain the interfaces that are required to be OpenPOWER compliant
- Document an overview of the Compliance Test Harness and Test Suite Specifications that have been developed in the Compliance Work Group,
and an outline of the contents expected in each specification
- Document procedures on how to measure and document compliance and where to submit the report for compliance

Version 1.1.0 of the document is based on the POWER8™ systems and the POWER9™ systems and
reflects work by the Compliance Work Group to improve the document.

The OpenPOWER Architecture Compliance Definition document is a Standards Track, Work Group Specification owned by the Compliance Workgroup and
handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
Comments about this document may be submitted to the Compliance Workgroup by emailing to <openpower-arch-comp-def@mailinglist.openpowerfoundation.org>

@ -0,0 +1,28 @@
---
title: CAPI Accelerator Compliance Test Specification
group: compliance
publicreview: false
tags:
- compliance
- caia
- capi
- testsuite
- testharness
date: 2018-02-15
draft: false
---

The purpose of the OpenPOWER CAPI Accelerator Compliance Test Specification is
to provide the test suite requirements to demonstrate OpenPOWER CAPI Accelerator solution compliance for POWER™ systems.
The input to this specification are the following specifications which define the hardware interfaces which are the subject of
this OpenPOWER CAPI Accelerator Compliance document:

- OpenPOWER Power Service Layer (PSL) to Accelerator Function Unit (AFU) Interface CAPI Specification,
which describes the interface to communicate to the acceleration logic running on the FPGA.
- OpenPOWER Coherent Accelerator Interface Architecture Version (CAIA) Specification
which describes a coherent accelerator interface structure for coherently attaching accelerators to the POWER systems using a standard PCIe bus.

This document is a Standard Track, Work Group Specification work product owned by the Compliance Workgroup and
handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
Comments, questions, etc. can be submitted to the public mailing list for this document at <capi_accelerator@mailinglist.openpowerfoundation.org>.

@ -0,0 +1,26 @@
---
title: FSI Compliance Specification TS/TH
group: compliance
publicreview: false
tags:
- specification
- compliance
- testsuite
- testharness
- openfsi
- fsi
- fru
- hardware
date: 2018-02-15
draft: false
---

The purpose of the OpenPOWER FSI Compliance Test Harness and Test Suite (TH/TS) Specification is
to provide the test suite requirements to be able to demonstrate OpenPOWER FSI compliance for POWER™ systems.
The input to this specification is the following specification:
Field Replaceable Unit (FRU) Service Interface (FSI) OpenFSI Specification which describes the FSI Protocol in detail,
including the timing and electrical specification.

This document is a Standard Track, Work Group Specification work product owned by the Compliance Workgroup and
handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
Comments, questions, etc. can be submitted to the public mailing list for this document at <openpower-fsithts@mailinglist.openpowerfoundation.org>.

@ -0,0 +1,38 @@
---
title: I/O Design Architecture Compliance Test Harness and Test Suite
group: compliance
publicreview: false
tags:
- ioda
- power8
- power9
date: 2020-11-10
draft: false
---

This is the OpenPOWER I/O Design Architecture (IODA) Compliance Test Harness and Test Suite (TH/TS) specification.

The purpose of the OpenPOWER I/O Design Architecture (IODA) Compliance Test Harness and Test Suite (TH/TS) specification is
to provide the test suite requirements to be able to demonstrate OpenPOWER I/O Design Architecture, compliance for POWER(TM) systems.
It describes the tests required in the test suite and a test harness needed to execute the test suite.
It also describes the successful execution of the test suite, including what it means for an optional feature to fail.

The input to this specification is the OpenPOWER I/O Design Architecture (IODA) Specification
which describes the chip architecture for key aspects of PCI Express® (PCIe)-based host bridge (PHB) designs for POWER systems.

This specification defines the PHB hardware and firmware requirements for these functions:
1. MMIO Partitionable-Endpoint Number Determination,
1. DMA and MSI Partitionable-Endpoint Number Determination,
1. Partitionable-Endpoint State and Enhanced Error Handling,
1. Error-Injection,
1. DMA with No Page Migration,
1. DMA with Page Migration,
1. DMA with Multilevel TCE Tables,
1. DMA Read Sync Register,
1. Message-Signalled Interrupt,
1. PCIe Configura- tion Space, and
1. Partitionable-Endpoint State Table.

This document is proposed as a Standard Track, Work Group Specification work product owned by the Compliance Workgroup and
handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
Comments, questions, etc. can be submitted to the public mailing list for this document at openpower-ioda-thts@mailinglist.openpowerfoundation.org.

@ -0,0 +1,32 @@
---
title: Instruction Set Architecture Compliance Definition
group: compliance
publicreview: false
tags:
- instructionsetarchitecture
- isa
- powerisa
- cores
- power8
- power9
date: 2020-05-07
draft: false
---

The OpenPOWER ISA Compliance Definition defines the test suite requirements to demonstrate OpenPOWER ISA Profile compliance for POWER systems.
The purpose of the OpenPOWER ISA Profile Compliance Test Harness and Test Suite (TH/TS) Specification,
is to provide the test suite requirements to be able to demonstrate OpenPOWER ISA Profile compliance for POWER based systems.

The input to this specification is the IBM POWER ISA, implementation of all of the ISA is required, there are no optional sections.

The testing of a processor implementations compliance against the Power ISA OpenPOWER Profile ensures
that software shown to execute properly on one compliant processor implementation will execute properly on
a different also compliant processor implementation.
The testing is not intended to show that the processor implementation under test is robust
under all possible operating conditions, inputs, or event time interactions.
It is intend to show that the processor implementation under test implemented the ISA
as specified and the ISA specification was interpreted by the processor developers as intended by the ISA specification author.

This document is a Standard Track, Work Group Specification work product owned by the Compliance Workgroup and
handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
Comments, questions, etc. can be submitted to the public mailing list for this document at openpower-isa-thts@mailinglist.openpowerfoundation.org.

@ -0,0 +1,43 @@
---
title: OpenPOWER Ready Definition and Criteria
group: compliance
tags:
- ready
- criteria
date: 2018-01-18
draft: false
---

The OpenPOWER Foundation set up the OpenPOWER Ready™ program in 2016.
Within the program, developers identify products for use by members of the OpenPOWER ecosystem.
The OpenPOWER Ready mark indicates that a product should work with other OpenPOWER Ready products.
Because of this the OpenPOWER Foundation is suggesting that entities providing such products join the foundation.

Companies and other entities can make a strong statement about their support of the OpenPOWER technology
as an alternative to other computing solutions by becoming a member of the OpenPOWER Foundation membership.

The OpenPOWER Ready Definition and Criteria document describes the details of the program.
Since there are several types of products categorized in the document they are listed below.
Because of the differences between the categories of products the criteria varies between them.
Developers will find the categories and criteria described in the document.

OpenPOWER Ready Product Categories :

- Systems
- System Support Components
- IO Adapters
- Storage controllers
- Network controllers
- Graphics controllers
- ...
- CAPI Accelerators : Heterogeneous accelerator attached via a CAPI enabled PCIe Adapter
- OpenCAPI™ 3.0 Adapters
- Software
- Operating Systems
- Applications
- Tool Chains
- ...

This document is a Standard Track, Work Group Specification work product owned by
the OpenPOWER Ready Workgroup and handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
Comments, questions, etc. can be submitted to the public mailing list for this document.

@ -0,0 +1,29 @@
---
title: "Vector Intrinsic Programming Reference Compliance Specification"
group: compliance
reviewdraft: false
tags:
- pvipr
date: 2021-03-22
draft: false
---

This document provides requirements for a compiler to demonstrate compliance with the Power Vector Intrinsics Programming Reference, version 1.0.

The input to this specification is the following specification which describes the vector intrinsics expected to be provided
by compilers targeting PowerISA 2.07 and 3.0B or later, as implemented on POWER8 and POWER9 systems.

Power Vector Intrinsics Programming Reference (PVIPR) which is published on the resource catalog:
https://openpowerfoundation.org/?resource_lib=power-vector-intrinsic-programming-reference

The PVIPR document is organized into the following chapters:
1. Introduction to Vector Programming on Power
2. The Power Bi-Endian Vector Programming Model
3. Vector Programming Techniques
4. Vector Intrinsic Reference
5. Instruction/Intrinsic Cross-Reference

This document is a Standard Track, Workgroup Specification work product owned by the Compliance Workgroup
and handled in compliance with the requirements outlined in the OpenPOWER Foundation Work Group (WG) Process document.
Comments, questions, etc. can be submitted to the public mailing list for the parent specification at
<openpower-pvipr-thts@mailinglist.openpowerfoundation.org>.

@ -0,0 +1,11 @@
versions:
- number: 2.0.71
date: 2017-01-10
- number: 2.0.72
date: 2017-01-27
- number: 2.0.90
date: 2017-01-30
- number: 2.1.0
date: 2017-06-27
- number: 2.1.5
date: 2021-03-28

@ -0,0 +1,23 @@
versions:
- number: "0.2"
date: 2018-04-25
description: Initial content draft
- number: "0.3"
date: 2018-05-23
description: Updates discussed at 4/26/2018 Compliance Work Group meeting
- number: "0.4"
date: 2018-06-22
description: Updates to fill in missing content
- number: "0.5"
date: 2018-08-22
description: Updates identified at the June 28, 2018 Compliance Work Group meeting
- number: "0.9"
date: 2018-09-19
description: public review draft
- number: "0.91"
date: 2019-01-03
description: workgroup specification
- number: "1.0"
date: 2019-01-04
description: update abstract and intro to be consistent
download: https://files.openpower.foundation/s/8oykwyapQcYfDdK

@ -0,0 +1,66 @@
versions:
- number: "0.8.0"
date: 2015-02-04
description: Initial Draft
- number: "0.9.0"
date: 2015-09-04
description: Conversion to approved template and release for public review
- number: "0.9.1"
date: 2015-09-09
description: Correction of identified conversion errors
- number: "0.9.2"
date: 2015-09-11
description: Public Review
- number: "0.9.3"
date: 2015-11-04
description: Updated with comments from Public Review
- number: "1.0.0"
date: 2016-01-12
description: Work Group Specification
download:
- number: "1.0.1"
date: 2018-09-18
description: Beginning updating Chapters 1 and 2
- number: "1.0.2"
date: 2018-09-18
description: Updated Chapters 1 and 2 with some additional changes
- number: "1.0.3"
date: 2018-09-20
description: Updated Chapters 1, 2, and 3
- number: "1.0.4"
date: 2018-10-11
description: Updates from Oct 11, 2018 Compliance Work Group meeting
- number: "1.0.5"
date: 2018-10-16
description: Added ISA Profile Rev 2 and IODA3 in Chapters 1, 2, 3; added FSI Spec in Chapter 2; other cleanup
- number: "1.0.6"
date: 2018-11-02
description: Updates from Oct 30, 2018 Compliance TWG meeting
- number: "1.0.7"
date: 2018-11-14
description: Updates from Nov 7, 2018 Compliance TWG meeting
- number: "1.0.8"
date: 2018-11-28
description: Minor updates including update to revision 1.1.0
- number: "1.0.9"
date: 2018-11-29
description: Updated pom file to revision 1.1.0
- number: "1.0.10"
date: 2018-11-30
description: Removed the mark-ups agreed at Nov 29, 2018 Compliance TWG meeting
- number: "1.0.10.1"
date: 2018-12-10
description: Architecture Compliance Definition Rev 1.1.0 - Public Review Draft
- number: "1.0.11"
date: 2019-04-02
description: Added abstract and pulled in updated Docs-Master with corrected links
- number: "1.0.12"
date: 2019-04-05
description: Updates for POWER8 & POWER9 systems
- number: "1.0.13"
date: 2019-04-11
description: Public Review Draft for second review
- number: "1.1.0"
date: 2019-07-08
description: Work Group
download: https://files.openpower.foundation/s/yqq8AtkdRQkiyCa

@ -0,0 +1,25 @@
versions:
- number: 0.30
date: 2016-03-10
description: conversion to OPF docbook
- number: 0.90
date: 2016-05-04
description: public review draft
- number: 0.91
date: 2016-08-04
description: add privileged mode app and supporting afu
- number: 1.0
date: 2016-10-07
description: workgroup specification
download:
- number: 1.1
date: 2017-08-22
description: initial update for capi2
- number: 1.2
date: 2017-09-25
- number: 1.9
date: 2017-10-25
- number: 2.0
date: 2018-01-30
description: work group specification
download:

@ -0,0 +1,14 @@
versions:
- number: "0.3"
date: 2016-11-26
description: template draft ported from MS doc
- number: "0.4"
date: 2016-08-30
description: converted skeletonversion from .doc to docbook format
- number: "0.5"
date: 2017-10-24
description: public review draft
- number: "1.0"
date: 2018-01-30
description: work group specification
download: https://files.openpower.foundation/s/GcfrazYq6TSN3kN

@ -0,0 +1,20 @@
versions:
- number: 3.0.1
date: 2020-02-14
description: initial draft
- number: 3.0.2
date: 2020-02-17
description: fixed typos and changed formatting
- number: 3.0.3
date: 2020-03-06
description: updated Abstract, defined acronyms on first use, and other minor changes
- number: 3.0.4
date: 2020-03-17
description: added glossary to define the acronyms
- number: 3.0.5
date: 2020-03-25
description: Workgroup Approved Public Review Draft
- number: 3.1.0
date: 2020-06-23
description: Workgroup Approved Specification
download: https://files.openpower.foundation/s/c5qsTMB58beysqo

@ -0,0 +1,51 @@
versions:
- number: 0.1
date: 2016-09-30
description: First porting from word to docbook
- number: 0.2
date: 2017-08-09
description: Updates per WG Review
- number: 0.3
date: 2017-08-29
description: Minor corrections per Sandy Woodward
- number: 1.0.0
date: 2018-01-10
description: Approved specification
dwonload: https://files.openpower.foundation/s/2EKs2zpwPQxYNZm
- number: 2.0.1
date: 2019-05-13
description: Updated for ISA 3.0b through end of Part I
- number: 2.0.2
date: 2019-05-28
description: Updated for ISA 3.0b through end of Part II
- number: 2.0.3
date: 2019-06-27
description: Updated for ISA 3.0b through end of Part III 18.6 Storage Protection section
- number: 2.0.4
date: 2019-07-26
description: Updated for ISA 3.0b through end of Part III Section 18
- number: 2.0.5
date: 2019-08-26
description: Updated for ISA 3.0b through end of Part III Section 19.2.19.2
- number: 2.0.6
date: 2019-08-30
description: Fixes to sections 9.4.2, 12, and 19.2.5.1 through 19.2.19.2
- number: 2.0.7
date: 2019-09-06
description: Fixes to sections 19.2.19.1 and 19.2.19.2, and changes to 19.2.20 through the end of the document for ISA 3.0b
- number: 2.0.8
date: 2019-10-11
description: Updates for changes identified at the October 2, 2019, Compliance TWG meeting and minor changes in part 1
- number: 2.0.9
date: 2019-10-27
description: Updates change doubleword[0], doubleword[2], and doubleword[3] to be word[0], word[2], word[3] respectively for I-7.4.1.VE0.37 xscvqpswz test results and for I-7.4.1.VE0.39 xscvqpuwz test results
- number: 2.0.10
date: 2019-10-24
description: Updates changes to section 18.2. Radix Tree Translation
- number: 2.0.11
date: 2019-10-29
description: Updates for changes identified at the October 29, 2019, Compliance TWG meeting
- number: 2.1.0
date: 2020-04-07
description: Approved Specification
download: https://files.openpower.foundation/s/TkLmPi2mpywijNA

@ -0,0 +1,66 @@
versions:
- number: "0.1"
date: 2015-10-03
description: Initial draft based on input from OPIO and DEVPLAT Workgroup
- number: "0.2"
date: 2015-12-08
description: Added more details on intent and process
- number: "0.3"
date: 2016-01-15
description: Added SW, CAPI, IO chapter
- number: "0.4"
date: 2016-01-20
description: Added OpenPOWER Ready Graphics
- number: "0.5"
date: 2016-01-27
description: Many changes from review of 0.0.5 by WGs and BOD
- number: "0.6"
date: 2016-02-02
description: Many changes from review of 0.0.6
- number: "0.7"
date: 2016-03-03
description: Change title to 2016
- number: "0.8"
date: 2016-03-04
description: Add trademark symbols
- number: "0.9"
date: 2016-03-05
description: Updated system OS criteria
- number: "0.10"
date: 2016-03-06
description: Updated intro to encourage broad participation.
- number: "0.11"
date: 2016-03-22
description: Added link to TMLA text
- number: "0.12"
date: 2016-03-23
description: Added links to request document templates and modified section 1.6 Scope
- number: "1.0"
date: 2016-03-15
description: Approval version - Cleaned URLs
download: https://files.openpower.foundation/s/zqHSbSMY5wCBWFQ
- number: "1.1"
date: 2017-06-06
description: Updated Intro to reflect changes to submission process via web automation
- number: "1.2"
date: 2017-08-17
description: Updating sections to include Power 9 criteria
- number: "1.3"
date: 2017-11-10
description: Added Section for CAPI SNAP
- number: "1.4"
date: 2017-11-11
description: Added Section for OPEN CAPI
- number: "1.5"
date: 2017-11-12
description: Added PCIe G4 compatibility statement
- number: "1.6"
date: 2017-11-13
description: Replaced most of OPR Trusted Boot and Secure Boot section
- number: "1.9"
date: 2018-01-13
description: public review draft
- number: "2.0"
date: 2018-04-19
description: workgroup specification
download: https://files.openpower.foundation/s/d5MjKE4kc39Xxcf

@ -0,0 +1,14 @@
versions:
- number: "0.1"
date: 2020-09-27
description: original draft
- number: "0.2"
date: 2020-09-29
description: incorporate workgroup comments
- number: "0.3"
date: 2020-10-26
description: workgroup approved public review draft
- number: "1.0"
date: 2021-03-28
description: workgroup approved specification
download: https://files.openpower.foundation/s/9qzp2KxAsxcgcL3

@ -0,0 +1,57 @@
{{ partial "header.html" . }}
{{ partial "navbar.html" . }}
<main id="main">
<section id="specifications">
<div id="specifications" class="container-fluid">
<div class="section-header">
<div class="row">
<div class="col-lg-12 text-center">
<h1 class="section-title text-center">{{ .Title }}</h1>
</div>
</div>
<div class="row">
<span class="section-divider"></span>
</div>
<div class="row">
<div class="col-lg-2">&nbsp;</div>
<div class="col-lg-8 text-center">
<script src="{{ "/lib/search//jquery-3.3.1.min.js" | relURL }}"></script>
<script src="{{ "/lib/search/fuse-3.2.0.min.js" | relURL }}"></script>
<script src="{{ "/lib/search/jquery.mark-8.11.1.min.js" | relURL }}"></script>
<script>var jsonfile = "{{ .RelPermalink }}/index.json"</script>
{{ $searchjavascript := resources.Get "js/search.js" }}
{{ $searchjs := $searchjavascript | resources.Minify }}
<script src="{{ $searchjs.RelPermalink }}"></script>
<div class="my-auto" >
<form action="{{ .RelPermalink }}" onkeyup="executeInlineSearch()">
<input id="search-query" placeholder="Search..." name="s" autocomplete="off" search autofocus/>
</form>
<div id="search-results"><h3 class="search-results-title">Matching items</h3></div>
</div>
<script id="search-result-template" type="text/x-js-template">
<div class="search-results-summary" id="summary-${key}">
<h4><a class="search-item" href="${link}">${title}</a></h4>
${ isset tags }<p>${tags}</p>${ end }
${ isset categories }<p>Categories: ${categories}</p>${ end }
</div>
</script>
</div>
<div class="col-lg-2">&nbsp;</div>
</div>
<div class="row">
<span class="section-divider"></span>
</div>
</div>
<div class="row pb-4 text-center">
{{ range .Data.Pages.ByTitle }}
<div class="col-lg-2">&nbsp;</div>
<div class="col-lg-8">
<a class="mb-4" href="{{ .Permalink }}">{{ .Title }}</a>
</div>
<div class="col-lg-2">&nbsp;</div>
{{ end }}
</div>
</div>
</section>
</main>
{{ partial "footer.html" . }}

@ -0,0 +1,5 @@
{{- $.Scratch.Add "index" slice -}}
{{- range .Data.Pages -}}
{{- $.Scratch.Add "index" (dict "title" .Title "permalink" .Permalink "contents" .Plain "tags" .Params.tags) }}
{{- end -}}
{{- $.Scratch.Get "index" | jsonify -}}

@ -0,0 +1,107 @@
{{ partial "header.html" . }}
{{ partial "navbar.html" . }}
{{ $filename := .File.BaseFileName }}
{{ $datafile := index $.Site.Data.compliance $filename }}
{{ $specificationfile := printf "%s/%s" "specifications" $filename }}
<main id="main" class="specifications-single">
<section id="page" class="section-bg">
<div class="row">
<div class="section-header my-3 my-md5 pb-2 pb-md3 text-center">
<h2 class="section-title text-center">{{ .Title }}</h2>
<p class="section-description"></p>
</div>
<div class="row">
<div class="col-lg-3"></div>
<div class="col-lg-6">
{{ if $datafile.versions }}
{{ range last 1 $datafile.versions }}
<a href="{{ .download }}"><i class="far fa-file-pdf mr-2"></i>&nbsp;Download version {{.number }}</a>
<span class="changetime-wrapper"><span class="changetime">{{ .date }}</span></span>
{{ end }}
{{ end }}
</div>
<div class="col-lg-3"></div>
</div>
{{ if .Param "publicreview" }}
{{ $reviewenddate := .Date.AddDate 0 0 30 }}
{{ if lt now $reviewenddate }}
<div class="row">
<div class="col-lg-3"></div>
<div class="col-lg-6">
<b>The Public Review for this document completes at close-of-business on {{ $reviewenddate.Format "Monday 2 January 2006" }}.</b>
</div>
<div class="col-lg-3"></div>
</div>
{{ end }}
{{ end }}
<div class="row">
<div class="col-lg-3"></div>
<div class="col-lg-6 content wow fadeInTop">
<p>{{ .Content }}</p>
</div>
<div class="col-lg-3">
{{ if .Param "group" }}
{{ $group := printf "%s/%s" "groups" (.Param "group") }}
{{ with $.Site.GetPage $group }}
Owned by : <a href="{{ .Permalink }}">{{ .Title }}</a><br>
{{ end }}
{{ end }}
{{ with $.Site.GetPage $specificationfile }}
Specification File : <a href="{{ .Permalink }}">{{ $filename }}</a><br>
{{ end }}
{{ if $datafile.versions }}
<ul class="changelogtimeline">
{{ range sort $datafile.versions "date" "desc" }}
<li>
<div class="direction-r">
<div class="changeflag-wrapper">
<span class="changeflag">version {{ .number }}</span>
<span class="changetime-wrapper"><span class="changetime">{{ .date }}</span></span>
</div>
<div class="desc">{{ .description }}</div>
{{ if .download }}
<div class="desc"><a href="{{ .download }}">download</a></div>
{{ end }}
</div>
</li>
{{ end }}
</ul>
{{ end }}
</div>
</div>
{{ if .Params.tags }}
{{ $tags := .Params.tags }}
<div class="row">
<div class="col-lg-3"></div>
<div class="col-lg-6 text-center">
{{ if not (eq (len $.Site.Taxonomies.tags) 0) }}
{{ $fontUnit := "rem" }}
{{ $largestFontSize := 3.5 }}
{{ $smallestFontSize := 0.5 }}
{{ $fontSpread := sub $largestFontSize $smallestFontSize }}
{{ $max := add (len (index $.Site.Taxonomies.tags.ByCount 0).Pages) 1 }}
{{ $min := len (index $.Site.Taxonomies.tags.ByCount.Reverse 0).Pages }}
{{ $spread := sub $max $min }}
{{ $fontStep := div $fontSpread $spread }}
{{ range $name, $taxonomy := $.Site.Taxonomies.tags }}
{{ $currentTagCount := len $taxonomy.Pages }}
{{ $currentFontSize := (add $smallestFontSize (mul (sub $currentTagCount $min) $fontStep) ) }}
{{ $count := len $taxonomy.Pages }}
{{ $weigth := div (sub (math.Log $count) (math.Log $min)) (sub (math.Log $max) (math.Log $min)) }}
{{ $currentFontSize := (add $smallestFontSize (mul (sub $largestFontSize $smallestFontSize) $weigth) ) }}
{{ range $tags }}
{{ if eq $name . }}
&nbsp;
<span style="font-size: {{ $currentFontSize }}{{ $fontUnit }}">{{ $name }}</span>
&nbsp;
{{ end }}
{{ end }}
{{ end }}
</div>
<div class="col-lg-3"></div>
{{ end }}
</div>
{{ end }}
</section>
</main>
{{ partial "footer.html" . }}
Loading…
Cancel
Save