Discussions on chris2
Start a New Discussion
-
-
Should Constitution have a property for amendments, too?
-
Good idea!
*some experimenting later* Iiiks, I´d never said yes, if I´d known more about amendments to the US constitution ;-) There are too many of them, and even more unratified ones. Someone at Wikipedia has even created a non-existing amendment , as sort of a human-friendly error note...
Now here´s a problem: First thing I tried was simply add ratified amendments as properties to the US constitution. Then I stumbled over the unratified ones, and put them into a new property "Unratified Amendments". The result looked nice on the US Constitution page, but obviously was lacking beauty and simplicity.
So I stopped, and set up a type "Constitutional Amendments", to put them all in instead. With a property "Ratification completed on". According to logics, it should be possible to filter all Amendments into the ratified and unratified ones now, to create the lists on the "US Constitution" page automatically - the first group has an entry in this "Ratification completed on" property, the second hasn´t. Or maybe there´s another data type that can be used to set a yes/no flag for ratified/unratified. But I can´t figure out how to do such filtering... is it possible?-
So as I understand it your first method was to have a property for Ratified Ammendments, and another for Proposed Amendments. I like that solution, since people are generally searching for one or the other, but not both. Also, as you point out, it is easy for humans to read and edit.
Your second solution would be better if people mostly want to search for them together. It does have the problem, as you point out, that MQL doesn't yet have a Not. Also, I can imagine if I know that amendment is ratified but don't know when it was.
All taken together, I am inclined to go with your first method. Does that make sense to you?
-
