OCDS schema v1.1: Item <aditionalClassification>.
OCDS schema v1.1: Organization .
OCDS schema v1.1: Tender, Award, Contract <amendments>.
OCDS schema v1.1: Award <contractPeriod>.
OCDS schema v1.1: Item <classification>.
OCDS schema v1.1: Organization <contactPoint>.
OCDS schema v1.1: Contract <implementation>.
OCDS schema v1.1: Plan, Tender, Award, Contract, Implementation <documents>.
OCDS schema v1.1: Tender <enquiryPeriod>.
OCDS schema v1.1: Tender <contractPeriod>.
OCDS schema v1.1: Plan, Tender, Contract, Implementation <milestones>.
OCDS schema v1.1: Contract <relatedProcesses>.
OCDS schema v1.1: Tender <tenderPeriod>.
OCDS schema v1.1: Implementation <transactions>.
OCDS schema v1.1: Tender <procuringEntity>.
Use in OCDS ontology: Organization, Budget, Transaction.
Similar to https://www.w3.org/TR/vocab-org/#org:identifier
The particular identifier scheme should be indicated by the datatype of the identifier value. Using datatypes to distinguish the notation scheme used is consistent with recommended best practice for skos:notation of which this property is a specialization.
OCDS schema v1.1: Parties <additionalIdentifier>, i.e., Additional identifier.
OCDS schema v1.1: Item <additionalClassification>.
OCDS schema v1.1: Tender <additionalProcurementCategories>.
OCDS schema v1.1: Amendment <rationale>.
OCDS schema v1.1: Tender <awardCriteria>.
OCDS schema v1.1: Tender <awardCriteriaDetails>.
OCDS schema v1.1: Contract <dateSigned>.
OCDS schema v1.1: Document <dateModified>.
OCDS schema v1.1: Document <datePublished>.
OCDS schema v1.1: Tender <eligibilityCriteria>.
OCDS schema v1.1: Tender <hasEnquiries>.
OCDS schema v1.1: Identifier <legalName>.
OCDS schema v1.1: Tender <mainProcurementCategory>.
OCDS schema v1.1: Milestone <dateModified>.
OCDS schema v1.1: Tender <numberOfTenderers>.
OCDS schema v1.1: Period <durationInDays>.
OCDS schema v1.1: Period <maxExtentDate>.
OCDS schema v1.1: Tender <procurementMethod>.
OCDS schema v1.1: Tender <procurementMethodDetails>.
OCDS schema v1.1: Tender <procurementMethodRationale>.
OCDS schema v1.1: Tender <submissionMethod>.
OCDS schema v1.1: Tender <submissionMethodDetails>.
Use in OCDS ontology: Budget, Tender, Award, Contract, Amendment, Document, Item, Milestone.
Use in OCDS ontology: Project, Tender, Award, Contract, Document, Milestone.
Use in OCDS ontology: ContactPoint, Document.
OCDS schema v1.1: Address <countryName>.
OCDS schema v1.1: ContactPoint <faxNumber>.
Use in OCDS ontology: Organization, ContactPoint.
OCDS schema v1.1: Address <streetAddress>.
OCDS schema v1.1: ContactPoint <telephone>.
Many different national and international identifier schemes are available from other vocabularies. The ORG ontology is neutral to which schemes are used. The particular identifier scheme should be indicated by the datatype of the identifier value. Using datatypes to distinguish the notation scheme used is consistent with recommended best practice for skos:notation of which this property is a specialization.
OCDS schema v1.1: Parties <identifier>, i.e., Primary identifier.
Uses also the following data type properties: addressCountry, addressLocality, postalCode, streeAddress, region.
Uses also the following data type properties: description.
Uses also the following data type properties: title, description.
Uses also the following data type properties: description, URI.
Uses also the following data type properties: faxNumber, telephone, email, addressCountry, postalCode, addressLocality, streetAddress, name, url.
Uses also the following data type properties: language, format, title, description, url.
Uses also following data properties: quantity, unit, description.
Uses also the following data type properties: legalName, name, URI.
Uses also the following data type properties: title.
Uses also the following data type properties: URI.