You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{class mpsId} is the Model Processing Service (MPS) id for the class. It looks like "org.1edtech.ob.v3p0.achievementsubject.class".
{title} is either a custom title for the section provided by the spec author, or the class name. In either case, Respec generates an id for the <h3> element from the contents of the header (which is either the custom title or the class name) by applying the lowerCase() function to the contents. That leads to id="achievement" for example.
As you can see, no id is currently provided for the individual properties. If an anchor id were generated, it could not be the property name because the same property name are used in so many classes.
I hope this information informs the discussion about improving the way data models are rendered.
Is this so the context file naturally expands IRI to URLs pointing to a definition of a term? I was wrong to suggest using the data model as the target. The context only defines a term once, while the data model defines it every time it appears.
It's not required for there to be anchor links but it's recommended to make classes and properties more efficiently accessible.
Recommendation: update/add anchor links for all properties and update anchors for class names to match case.
The text was updated successfully, but these errors were encountered: