This ontology has been created in the context of a collaboration between the Ontology Engineering Group and Huawei Research Ireland
This is a place holder text for the introduction. The introduction should briefly describe the ontology, its motivation, state of the art and goals.
devopscert | <http://w3id.org/devops-infra/certificate> |
core | <http://w3id.org/devops-infra/core> |
owl | <http://www.w3.org/2002/07/owl> |
rdf | <http://www.w3.org/1999/02/22-rdf-syntax-ns> |
terms | <http://purl.org/dc/terms> |
xsd | <http://www.w3.org/2001/XMLSchema> |
skos | <http://www.w3.org/2004/02/skos/core> |
devops-infra | <http://w3id.org/devops-infra> |
rdfs | <http://www.w3.org/2000/01/rdf-schema> |
vann | <http://purl.org/vocab/vann> |
dc | <http://purl.org/dc/elements/1.1> |
This ontology has the following classes and properties.
This ontology is focused on the description of aspects related to the management of digital certificates (including DigitalCertificate as well as DigitalCertificateBundle, DigitalCertificateDeployment and DigitalCertificateSigningRequest). All the data properties defined in this ontology are focused on describing the main characteristics of such certificates, as commonly understood in existing standards.
IRI: http://w3id.org/devops-infra/certificate#CertificateSigningRequest
IRI: http://w3id.org/devops-infra/certificate#CFCACertificate
CFCA is a national Authority safety Certification organization which is established by the people's bank of China. CFCA certificates are issued by this organisation
IRI: http://w3id.org/devops-infra/certificate#DigitalCertificate
Digital Certificates are electronic credentials that bind the identity of the certificate owner to a pair of electronic encryption keys, (one public and one private), that can be used to encrypt and sign information digitally.
IRI: http://w3id.org/devops-infra/certificate#DigitalCertificateBundle
A digital certificate bundle is a file that contains root and intermediate certificates.
IRI: http://w3id.org/devops-infra/certificate#DigitalCertificateDeployment
A Digital Certificate Deployment is the result of deploying a digital certificate in a specific domain and for a specific service on a site.
IRI: http://w3id.org/devops-infra/certificate#SSLCertificate
An SSL certificate is a data file hosted in a website's origin server. SSL certificates make SSL/TLS encryption possible, and they contain the website's public key and the website's identity, along with related information. Devices attempting to communicate with the origin server will reference this file to obtain the public key and verify the server's identity. The private key is kept secret and secure.
IRI: http://w3id.org/devops-infra/certificate#containsCertificate
A Digital Certificate Bundle contains several Digital Certificates
IRI: http://w3id.org/devops-infra/certificate#hasCertificateDeployment
A digital certificate can be deployed somewhere, and this is registered as a Digital Certificate Deployment
IRI: http://w3id.org/devops-infra/certificate#hasCertificateSigningRequest
A Digital Certificate is obtained after a Certificate Signing Request
IRI: http://w3id.org/devops-infra/certificate#usesDigitalCertificate
Different types of entities (domains, servers, etc.) make use of one or several digital certificates
IRI: http://w3id.org/devops-infra/certificate#certApplyPerson
The person in charge of the certificate application
IRI: http://w3id.org/devops-infra/certificate#certificateContent
The content of the certificate
IRI: http://w3id.org/devops-infra/certificate#certDeployPerson
The person in charge of the certificate deployment
IRI: http://w3id.org/devops-infra/certificate#certDeployRegion
The region for the certificate deployment
IRI: http://w3id.org/devops-infra/certificate#certPurchaseNumber
The purchase number of the certificate
IRI: http://w3id.org/devops-infra/certificate#certType
The type of certificate
IRI: http://w3id.org/devops-infra/certificate#domain
Also referred to as common name (CN). It is the fully qualified domain name for the certificate, the deployment of the certificate, or the certificate signing request. For example, *.example.org
IRI: http://w3id.org/devops-infra/certificate#expiryDate
The expiry date of the certificate
IRI: http://w3id.org/devops-infra/certificate#issuer
The issuer of the certificate, also known as issuer common name
IRI: http://w3id.org/devops-infra/certificate#issuerOrganisation
The organisation that issues the certificate
IRI: http://w3id.org/devops-infra/certificate#issuerOrganisationUnit
The organisational unit that issues the certificate
IRI: http://w3id.org/devops-infra/certificate#privateKey
The private key of the certificate or the certificate signing request
IRI: http://w3id.org/devops-infra/certificate#publicKey
The public key of the certificate signing request
IRI: http://w3id.org/devops-infra/certificate#realSerialNumber
The real serial number of the certificate
IRI: http://w3id.org/devops-infra/certificate#region
The region for the certificate, the deployment of the certificate, etc.
IRI: http://w3id.org/devops-infra/certificate#serialNumber
The serial number of the certificate
IRI: http://w3id.org/devops-infra/certificate#service
The service for which the Digital Certificate is deployed
IRI: http://w3id.org/devops-infra/certificate#site
The site for which the Digital Certificate is deployed
IRI: http://w3id.org/devops-infra/certificate#startDate
The start date of the certificate
IRI: http://w3id.org/devops-infra/certificate#user
The user of the certificate or certificate signing request, also known as user common name
IRI: http://w3id.org/devops-infra/certificate#userOrganisation
Also known as Organization Name (O). It is usually the legal name of a company or entity that is using the certificate, or has made the certificate signing request, and should commonly include any suffixes such as Ltd., Inc., or Corp. For example, Example Organisation, Ltd
IRI: http://w3id.org/devops-infra/certificate#userOrganisationCountry
Also referred to as country (C). The two-letter ISO code for the country of the organisation that uses the Digital Certificate or has made the Certificate Signing Request. For instance, ES
IRI: http://w3id.org/devops-infra/certificate#userOrganisationEmail
Also referred to as email address (EMAIL). The email contact (usually the certificate administrator or IT department) for the country of the organisation that uses the Digital Certificate or has made the Certificate Signing Request. For instance, info@example.org
IRI: http://w3id.org/devops-infra/certificate#userOrganisationLocality
Also referred to as locality (L). The name of the locality (town, city, village, etc.) of the organisation that uses the Digital Certificate or has made the Certificate Signing Request. For instance, Boadilla del Monte
IRI: http://w3id.org/devops-infra/certificate#userOrganisationState
Also referred to as state (S). The name of the locality (province, region, county or state) of the organisation that uses the Digital Certificate or has made the Certificate Signing Requestte or Certificate Signing Request. For instance, Comunidad de Madrid
IRI: http://w3id.org/devops-infra/certificate#userOrganisationUnit
Also known as Organizational Unit (OU). It is the organisational unit of the user of the certificate or certificate signing request. It is an internal department/division name. For example, IT Support
IRI: http://w3id.org/devops-infra/certificate#valid
It determines whether the certificate is valid
IRI: http://w3id.org/devops-infra/certificate#vendor
The vendor for the certificate
Add your references here. It is recommended to have them as a list.
The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.
A Certificate Signing Request (also known as CSR or certification request) is a message sent from an applicant to a registration authority of the public key infrastructure in order to apply for a digital identity certificate. It usually contains the public key for which the certificate should be issued, identifying information (such as a domain name) and integrity protection (e.g., a digital signature). The most common format for CSRs is the PKCS #10 specification; another is the Signed Public Key and Challenge SPKAC format generated by some web browsers.