2024 Release Candidate

[jmccrae]

When this branch is merged, it will be tagged as the 2024 release

[jmccrae]

@1313ou @fcbond @goodmami

2024 Release Candidate is ready. Please let me know of any issues by the end of the week.

[goodmami]

@jmccrae I generated the xml file with scripts/from_yaml.py. First, I noticed that the generated file uses the WN-LMF-relaxed-1.3.dtd schema instead of WN-LMF-1.3.dtd because of the second True argument in this line:

english-wordnet/scripts/from_yaml.py

Line 372 in a513594

wn.to_xml(outp, True)

thus, part=True here:

english-wordnet/scripts/wordnet.py

Lines 105 to 112 in a513594

	def to_xml(self, xml_file, part=False):
	xml_file.write("""<?xml version="1.0" encoding="UTF-8"?>\n""")
	if part:
	xml_file.write(
	"""<!DOCTYPE LexicalResource SYSTEM "http://globalwordnet.github.io/schemas/WN-LMF-relaxed-1.3.dtd">\n""")
	else:
	xml_file.write(
	"""<!DOCTYPE LexicalResource SYSTEM "http://globalwordnet.github.io/schemas/WN-LMF-1.3.dtd">\n""")

Is there a reason to use the -relaxed schema, or should it be the normal one?

And, tangentially, it looks like the -relaxed schema may not be updated as it does not have the xml:space attribute?

Once I stopped Wn from rejecting the relaxed schema in the doctype declaration, I didn't have any issues adding it to the database and running some simple queries. I haven't yet done more extensive testing beyond that. So, for now, the main issue is with the doctype schema.

[jmccrae]

The 'relaxed' scheme was used to allow multiple small XML files, which would be merged later. This was how we worked with the wordnet before we adopted YAML in #664, it should not be generated anymore.