Context
For the moment, the aliases are built ONLY based on the Work and Locator. See Odyssey 1.5:
Odyssey 1.5
In context
Work: Odyssey
Citation system: Homeric book-line
Locator: 1.5
Aliases (1)
https://textrefs.org/cite/homer.odyssey/1.5/
Obviously, this would cause problems when different citation systems are used for the same passage. However, adding the Citation system in the aliases goes against most of the usecases, where users don't mention the Citation system.
Options considered
One option considered would be to simply add the citation system in the aliases. But as mentioned above, this would solve the problem, but might complexify 90% of the usage of the passages, as it is often implied which system is used.
Recommendation
My proposition would be ot introduce a Preferred Citation System. An alias using the preferred system (most of the usage) will remain simple and understandable:
homer.odyssey/1.5
If a user prefer to use a non-preferred system, then the alias will mention the system:
homer.odyssey/non-pref-sys/x.y
The community will decide which system is the preferred.
Expected consequences
This means changing the system behind, but I'm not sure what will be the technical consequences.
Another consequences is to have consensus on what is the preferred system. One of the metric is the frequency a system is used in a community.
Context
For the moment, the aliases are built ONLY based on the Work and Locator. See Odyssey 1.5:
Obviously, this would cause problems when different citation systems are used for the same passage. However, adding the Citation system in the aliases goes against most of the usecases, where users don't mention the Citation system.
Options considered
One option considered would be to simply add the citation system in the aliases. But as mentioned above, this would solve the problem, but might complexify 90% of the usage of the passages, as it is often implied which system is used.
Recommendation
My proposition would be ot introduce a Preferred Citation System. An alias using the preferred system (most of the usage) will remain simple and understandable:
If a user prefer to use a non-preferred system, then the alias will mention the system:
The community will decide which system is the preferred.
Expected consequences
This means changing the system behind, but I'm not sure what will be the technical consequences.
Another consequences is to have consensus on what is the preferred system. One of the metric is the frequency a system is used in a community.