-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Can WIDOCO be configured to not display the IRI for each thing in the exported ontology? #677
Comments
@Rcaschultz, no I don't think it's possible to hide the IRIs at the moment, sorry. |
The IRI generation from the xsl transformation sheet is exactly here Widoco/src/main/resources/lode/extraction.xsl Line 1575 in 5b9b1de
It could be enhanced and add a Widoco ontology data property widoco:DoNotDisplayIRI with value xsd:boolean. Then in the xsl transformation just adding a second condition and looking if this data property is true or false here: Widoco/src/main/resources/lode/extraction.xsl Line 1576 in 5b9b1de
|
As I am not an xsl transformation expert I asked our overlord AI Chatgpt and this is something that could be tested to check if works <xsl:template name="get.ontology.url">
<xsl:if test="exists((@*:about|@*:ID)[normalize-space() != '']) and not(exists(//widoco:DoNotDisplayIRI[text()='true']))">
<dl>
<dt>IRI:</dt>
<dd>
<xsl:value-of select="@*:about|@*:ID"/>
</dd>
<xsl:if test="exists(owl:versionIRI)">
<dt>Version IRI:</dt>
<dd>
<xsl:value-of select="owl:versionIRI/@*:resource"/>
</dd>
</xsl:if>
</dl>
</xsl:if>
</xsl:template> |
Thanks @vChavezB. The only thing I am a little hesitant is that your ontology ends up with Widoco configuration parameters. But I don't understand very well why would you want to remove the class URI from the documentation, since that's kind of the main thing to know which property you are dealing with. For example, 2 properties/Classes could have the same label. How would you distinguish theM |
Do not want to display the IRI for each item in the export.
Regards,
The text was updated successfully, but these errors were encountered: