@prefix rdfs: . @prefix rdf: . rdf:type rdfs:label "type" . rdf:Property rdfs:label "Property" . rdfs:label rdfs:label "label" . rdfs:domain rdfs:label "domain" . rdfs:isDefinedBy rdfs:label "isDefinedBy" . rdfs:comment rdfs:label "comment" . @prefix ns2: . ns2:locn rdfs:label "ISA Programme Location Core Vocabulary"@en . @prefix mdr: . mdr:hasURI rdfs:label "has URI" . @prefix ns4: . ns4:adminUnitL1 rdfs:label "admin unit level 1"@en . @prefix locn: . ns4:adminUnitL1 mdr:hasURI locn:adminUnitL1 . locn:Address rdfs:label "Address"@en . @prefix dcterms: . dcterms:identifier rdfs:label "Identifier"@en . locn:adminUnitL1 rdf:type rdf:Property ; rdfs:label "admin unit level 1"@en ; rdfs:domain locn:Address ; rdfs:isDefinedBy ns2:locn ; rdfs:comment "The uppermost administrative unit for the address, almost always a country. The domain of locn:adminUnitL1 is locn:Address and the range is a literal, conceptually defined by the INSPIRE Geographical Name data type."@en . @prefix ns7: . locn:adminUnitL1 ns7:term_status "testing"@en . @prefix ns8: . locn:adminUnitL1 ns8:usageNote "Best practice is to use the ISO 3166-1 code but if this is inappropriate for the context, country names should be provided in a consistent manner to reduce ambiguity. For example, either write 'United Kingdom' or 'UK' consistently throughout the data set and avoid mixing the two."@en . @prefix xsd: . locn:adminUnitL1 dcterms:identifier "locn:adminUnitL1"^^xsd:string .