From: Lady <redacted>
Date: Fri, 13 Sep 2024 03:36:33 +0000 (-0400)
Subject: Remove the range restriction on dc11:language
X-Git-Url: https://git.ladys.computer/Vocab/commitdiff_plain/6133fce53d8432cb6a79cf40f120b2afbe85fb73?hp=795c962df1df941a81b9a8072ba096c502506008

Remove the range restriction on dc11:language

awol:lang can now be used generally when a value restricted to
xsd:language is desired.
---

diff --git "a/data/datatype_properties/dc11\302\246language" "b/data/datatype_properties/dc11\302\246language"
index 1dda15f..20ae3b0 100644
--- "a/data/datatype_properties/dc11\302\246language"
+++ "b/data/datatype_properties/dc11\302\246language"
@@ -14,16 +14,12 @@ SPDX-License-Identifier: CC0-1.0
 			<ptr target="(DCMI)"/> recommends the use of a « IETF Best Current Practice 47 [<ref target="https://tools.ietf.org/html/bcp47">IETF-BCP47</ref>] language tag ».
 		</p>
 		<p>
-			<ptr target="(ANNO)"/> constrains the range of this property to <resource name="xsd:string"/>, but further stipulates in prose that it match the format of <resource name="xsd:language"/>.
-			These datatypes share a value space, so this ontology just restricts it to the latter.
+			<ptr target="(ANNO)"/> effectively constrains the range of this property to <resource name="xsd:language"/>, but this ontology does not recognize this constraint.
 		</p>
 	</comment>
 	<isDefinedBy>
 		<SpecificResource source="(DCMI)" fragment="http://purl.org/dc/elements/1.1/language"/>
 	</isDefinedBy>
-	<isDefinedBy>
-		<SpecificResource source="(ANNO)" fragment="dc-language"/>
-	</isDefinedBy>
 	<range>
 		<resource name="xsd:language"/>
 	</range>