Almost identical concepts (lowercase and uppercase)

[floresbakker]

Hi there ReSpec community!

I am trying to create a specification document that identifies two concepts that have almost identical names. One is for a OWL class called ex:Example and one is for an OWL object property called ex:example. In the RDF/OWL world, it is custom to write classes with a name starting with a upper case letter, while properties are written with a name starting with a lower case letter. The two concepts are semantically different from eachother, hence I want to show this in the ReSpec document. However, the ReSpec validation shows that the two concepts are seen as one, and it warns me that there is a duplicate definition of ex:example.

<section>
  <h2>Start your spec!</h2>
  <dfn>[=ex:Example=]</dfn>
  This is a class.      
  <dfn>[=ex:example=]</dfn>
  This is a property.
</section>

I tried using scoped concepts as described in https://respec.org/docs/#scoped-concepts:

<section>
  <h2>Start your spec!</h2>
  <dfn>[=class/ex:Example=]</dfn>
  This is a class.      
  <dfn>[=property/ex:example=]</dfn>
  This is a property.
</section>

Still I get a duplicate definition warning.

Even an example that I took from https://respec.org/docs/#scoped-concepts results in a warning:

<section>
  <h2>Start your spec!</h2>
  <dfn>[=list/for each=]</dfn>
  This is a function for lists.      
  <dfn>[=map/for each=]</dfn>
  This is a function for maps.
</section>

What am I doing wrong here?

[floresbakker]

See here: #4821