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
Should one simply be a reference to another (e.g., <dfn data-cite=".RDF12-CONCEPETS#dfn-entailment">entails</dfn>)?
If parallel definition is appropriate, they should probably cross-reference each other and note subtlties.
As it is now, both specs will export these terms making them show up in xref to allow automatic resolution. Existing identifiers can be preserved in documents without exporting them (e.g., <span id="..></span>, or <dfn class="no export"></dfn>.
Probably at some point we should automate finding parallel term definitions in different specs which should be unified.
The text was updated successfully, but these errors were encountered:
There are two notes in the RDF Concepts drafts on Entailment and Equivalence that they are similar to the terms entails and equivalent in semantics.
Which is the appropriate primary definition?
Should one simply be a reference to another (e.g.,
<dfn data-cite=".RDF12-CONCEPETS#dfn-entailment">entails</dfn>
)?If parallel definition is appropriate, they should probably cross-reference each other and note subtlties.
As it is now, both specs will export these terms making them show up in xref to allow automatic resolution. Existing identifiers can be preserved in documents without exporting them (e.g.,
<span id="..></span>
, or<dfn class="no export"></dfn>
.Probably at some point we should automate finding parallel term definitions in different specs which should be unified.
The text was updated successfully, but these errors were encountered: