See this documentation - there is a class Conceptual Model and a property conceptual model - this is a quite common situation. However, it generates the same anchor name conceptual-model, creating a conflict.
I suggest keeping case in the anchor ids.
Actually, the anchor IDs should be the local names (ends of IRIs) of the classes and properties (class profiles, property profiles), so that e.g. https://w3id.org/dsv-dap#ConceptualModel works correctly also with human generated spec.
See this documentation - there is a class
Conceptual Modeland a propertyconceptual model- this is a quite common situation. However, it generates the same anchor nameconceptual-model, creating a conflict.I suggest keeping case in the anchor ids.
Actually, the anchor IDs should be the local names (ends of IRIs) of the classes and properties (class profiles, property profiles), so that e.g. https://w3id.org/dsv-dap#ConceptualModel works correctly also with human generated spec.