At present the reference data includes subclasses of Version_identification_code for each and every possible type which can have a version identifier. However, the most commonly used template OASIS:Part does not make use of the Part_version_identification_code but just uses Version_identification_code to constraint the version_id.
The current reference data seems to make use of PLCS more complex than it needs to be. Most users just view a version id as a string, making it an object that has to be classified as a specific type of version id from a long list of possible classifiers just seems overly complex and can cause PLCS to be seen to be non-implementable.
This issue was first raised under http://sourceforge.net/p/plcslib/plcs-templates/362/ but I think we need wider discussion on how to proceed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At present the reference data includes subclasses of Version_identification_code for each and every possible type which can have a version identifier. However, the most commonly used template OASIS:Part does not make use of the Part_version_identification_code but just uses Version_identification_code to constraint the version_id.
The current reference data seems to make use of PLCS more complex than it needs to be. Most users just view a version id as a string, making it an object that has to be classified as a specific type of version id from a long list of possible classifiers just seems overly complex and can cause PLCS to be seen to be non-implementable.
This issue was first raised under http://sourceforge.net/p/plcslib/plcs-templates/362/ but I think we need wider discussion on how to proceed.