Skip to content
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 configure to not display the IRI for each thing in the exported ontology? #677

Open
Rcaschultz opened this issue Feb 2, 2024 · 4 comments

Comments

@Rcaschultz
Copy link

Do not want to display the IRI for each item in the export.

image

Regards,

@dgarijo
Copy link
Owner

dgarijo commented Feb 2, 2024

@Rcaschultz, no I don't think it's possible to hide the IRIs at the moment, sorry.

@vChavezB
Copy link
Contributor

vChavezB commented Feb 3, 2024

The IRI generation from the xsl transformation sheet is exactly here

<xsl:template name="get.ontology.url">

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:

<xsl:if test="exists((@*:about|@*:ID)[normalize-space() != ''])">

@vChavezB
Copy link
Contributor

vChavezB commented Feb 3, 2024

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>

@dgarijo
Copy link
Owner

dgarijo commented Feb 4, 2024

Thanks @vChavezB. The only thing I am a little hesitant is that your ontology ends up with Widoco configuration parameters.
We can do something similar under the hood: accept a parameter for the tool, then annotate the ontology and use the xslt.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants