Closed PriyankaNanjappa closed 5 years ago
One of the most important things we are doing is integrating information. At this level, we are doing this manually but we should be capable to describe the process in a way that it can be easily automated. Having two instances would help us to better describe the domain and do the integration, since if in only one example, the standards are named differently or only with IEC or ISO, then we would need the two instances.
As far as I researched on the internet, they are always referred to as ISO/IEC ........ and so on. A web search "ISO 11404" produces results for ISO/IEC 11404 and none of the results show IEC 11404 or ISO 11404. That was the concern. If it makes sense to have them separately for some reason and does not hurt the semantics, then I guess we can let it be.
The point is which resource the refer to. While we are usually talking/thinking about e.g. ISO/IEC 11404, the informtation resource (=the document providing/containing the resource) is actually either ISO 11404 or IEC 11404. So, they are different entities and therefore have to be treated differently. The main question is whether we want to mix the resource (ISO/IEC 11404) and it's information carrier. In my view, we should not.
Have a look at this resource - https://www.tititudorancea.com/z/iso_11404.htm
As @sebbader says and the example above confirms, they are equivalent but treated differently in different places. Thus, we should keep them separate.
Alright then. We will maintain the same format of representation. Thanks for the clarification!
Issue can be closed.
Can we name the ISO/IEC standards as is in the resources rather than creating 2 different instances as in example . Since in resources in official resources IEC and ISO both specify it as ISO/IEC 11404 rather than 2 instances ISO 11404 and IEC 11404 which are then specified to be same.