HAPI FAQ – Publications API
Where is the Publications API documented?
-
Common XSD : https://bitbucket.org/sdo-hapi/data-models/src/master/schema/xsd/common/harmonized-commons.xsd
-
XSD : https://bitbucket.org/sdo-hapi/data-models/src/master/schema/xsd/projects/harmonized-projects.xsd
-
OpenAPI YAML: https://bitbucket.org/sdo-hapi/api-specifications/src/master/openapi-v3/iec-projects-publications-openapi3.yaml
-
OpenAPI: IEC API Portal – https://api-portal.iec.ch/ (developer account required)
Why do some publications have no project?
|
Category |
How to recognize |
Example |
|---|---|---|
|
Joint ISO/IEC standards published by ISO |
|
|
|
Old joint standards originated by IEC, published by ISO (all revised/replaced/withdrawn) |
|
|
|
Database standards |
|
|
|
Packages |
|
|
|
Series (marketing products) |
|
|
|
Other publications (Guides, White Papers, Trend Reports…) |
|
|
|
Commented versions |
|
– |
|
Other |
|
– |
How do I identify Database (DB) publications?
There is no dedicated publicationType for DBs. Identify them by releaseItem/format = ONLINE (no project, no downloadable file). The five DB standards are: iec:pub:474, iec:pub:980, iec:pub:2098, iec:pub:2723, iec:pub:7514.
What publication statuses exist?
|
Status |
Meaning |
|---|---|
|
|
Current and valid |
|
|
A new edition or amendment was published (same |
|
|
Replaced by one or more standards with a different |
|
|
No longer maintained. Still available. |
dateOfWithdrawal = date the publication stopped being valid (revised, replaced or withdrawn).
What happens to projects when a publication changes status?
-
New edition/amendment → previous edition and all its amendments, CSV, CMV become
REVISED; project stage becomesDELPUB. -
Replaced by a different standard →
REPLACED; project stage becomesDELPUB. -
No longer maintained →
WITHDRAWN; project stage becomesWPUB.
Why is "Withdrawn" different between the API and the Webstore?
The Webstore shows "Withdrawn" (in red) for any publication no longer valid, with history available. The API uses the precise IEC statuses above (REVISED / REPLACED / WITHDRAWN).
Example – IEC 61107:
|
Project |
Stage |
Publication |
Reference |
Status |
Superseded by |
|---|---|---|---|---|---|
|
|
DELPUB |
|
IEC 61107:1992 ED1 |
REVISED |
|
|
|
DELPUB |
|
IEC 61107:1996 ED2 |
REPLACED |
|
|
|
PPUB |
|
IEC 62056-21:2002 ED1 |
PUBLISHED |
– |
Why does dateOfWithdrawal differ from the WPUB date in the Projects API?
-
dateOfWithdrawal(Publications API, Webstore) = actual withdrawal date. -
effectiveDateof stageWPUB(Projects API) = announcement date of the withdrawal.
Why are relations missing on corrigenda of consolidated versions?
A corrigendum can correct a consolidated version (e.g. IEC 60529:1989+AMD1:1999 CSV/COR1:2003). Consolidated versions have no own project (they link to the base project), and the Publications API has no publication-to-publication relations. CORRECTS/CORRECTED_BY cannot be provided today. This is a known limitation.
Which languages are available?
|
Language |
|
|
|---|---|---|
|
EN-FR |
|
true |
|
EN |
|
false |
|
ES |
|
false |
|
FR |
|
false |
|
RU |
|
false |
Publication languages can differ from the project's languageSettings (e.g. a project developed in English, translated later: iec:proj:8383 / iec:pub:5972).
Why do downloads fail for some language versions?
Language versions other than English and French require a contract with IEC Sales. Exception: trilingual EN/FR/RU publications.