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

Improve ontology documentation #5

Open
jimkont opened this issue Mar 5, 2015 · 4 comments
Open

Improve ontology documentation #5

jimkont opened this issue Mar 5, 2015 · 4 comments

Comments

@jimkont
Copy link
Member

jimkont commented Mar 5, 2015

We should improve the ontology documentation where possible with additional links to external definitions.

@pfps suggested we link the related Wikipedia pages which is an obvious choice.
Is rdfs:seeAlso sufficient? e.g.
dbo:Person rdfs:seeAlso <https://en.wikipedia.org/wiki/Person>

@kurzum
Copy link
Member

kurzum commented Mar 5, 2015

should be something more specific that rdfs:seeAlso, we can also use our own vocab. An initial mapping can be found here:
https://code.google.com/p/lexo/source/browse/trunk/lexo2/data/dbpedia_ontology_mapping.txt

@pfps
Copy link

pfps commented Mar 5, 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

rdfs:seeAlso has such a weak name.

I think that rdfs;isDefinedBy would be better, or something new.

The benefit of rdfs:isDefinedBy is that it might be possible in the future
to serve up real definitions.

peter

On 03/05/2015 06:32 AM, Dimitris Kontokostas wrote:

We should improve the ontology documentation where possible with
additional links to external definitions.

@pfps https://github.com/pfps suggested we link the related Wikipedia
pages which is an obvious choice. Is |rdfs:seeAlso| sufficient? e.g.
|dbo:Person rdfs:seeAlso https://en.wikipedia.org/wiki/Person|

— Reply to this email directly or view it on GitHub
#5.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU+IGSAAoJECjN6+QThfjzo0EH/AsO9YYldWRutnpvU6q+Jxge
w/CP3eq1bm1W3G1IZdgOgeainXNOE+R89C+YotZtM6amL2MTMh2lC1IbBCVKOsLB
9WPap2bfclHS8yGRYo/s6083SgEPItCKDAEYoC7tv5KBvfSNPAFAwvXmQMzH7iqz
1lAvEZmPbouA+D704j8RDufL7tpC/Y/eHWnRnfocdaLdCWkPT8B2dSK8uYv8q5Lp
ZqDwpIzing41TG4rNoFZAa4GSbp1eFW5ejPQ7NezIUTY6/y1Ds/fXe+j6hAo+QTG
5fl9+RgVsj6Xmx2UOM3tgX2WXtY6DKtPUhE3enKdPfvpbHmn4kUpgta2dDwcKmA=
=VuiZ
-----END PGP SIGNATURE-----

@jimkont
Copy link
Member Author

jimkont commented Mar 6, 2015

what about dbo:classDocumentation as an object property that links to other definition resources. For text descriptions we can use the existing label & comments.

@jimkont
Copy link
Member Author

jimkont commented Mar 6, 2015

@kurzum are these definitions manually curated?
@alexandrutodor would it be easy to import them with your script? (when there is no English comment in an existing class)

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

No branches or pull requests

3 participants