search

levitation / aceview

Automatically exported from code.google.com/p/aceview
Other
0 stars 0 forks source link

No support for namespaces #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It is not possible to explicitly refer to e.g. foaf:Person from the FOAF
ontology, i.e. sentences like (1) are not supported.

(1) Every my:person is a foaf:Person and every foaf:Person is a my:person.

==Solution==
A simple solution would leave ACE/APE unchanged. The idea: allow prefixing
all the content words in the snippet with the namespace prefixes registered
in Protege (check which characters are allowed in a prefix), e.g. allow
snippets like:

(2) yahoo:John knows google:John.

When the snippet is parsed, the prefixes are analysed and the corresponding
lexicon entries are generated on the bases of the ACE View lexicon, e.g. if
the Protege prefix definitions are:

default: default.org
google: google.com
yahoo: yahoo.com

and the lexicon is:

google.com#John: John
yahoo.com#John: John
default.org#know: knows, know, known

Then generate a new snippet and its corresponding lexicon to be sent to APE
as follows:

`yahoo:John` knows `google:John`.

pn(sg, yahoo:John, yahoo.com#John)
pn(sg, google:John, google.com#John)
tv(sg, knows, default.org#know)

i.e. the wordform argument in the lexicon would contain the prefix unless
the word comes from the default namespace; and the lemma argument would be
a full IRI.

Original issue reported on code.google.com by kaljurand on 23 May 2010 at 2:10

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
TEST: my:John is not `my:John` and is my:John.

Original comment by kaljurand on 25 May 2010 at 1:36

GoogleCodeExporter commented 9 years ago 
solution #2

It should be possible to use optional postfix like this - Person:foaf.

This notation may be used in ACE with additional parameter for APE:
foaf="<foaf-URI>"

Original comment by alex.shkotin on 23 Nov 2010 at 5:05