Closed FredsoNerd closed 2 years ago
Hey @FredsoNerd! It was built that way to not declare the type of a node inside his own context, but in the latest discussions we had about it we decided that it wasn't a problem. Fixed it in cadf3434e34f2dc6733a4053a095a4c58a7b9581
It is not a problem, there are many rooms for interpretations in RDF semantics.. But I agree that it is easier for now to have the type defined inside the same named graph:
Current code produces:
S <http://wordnet.princeton.edu/pwn30/01002055-a-1>
P <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
O <http://www.delph-in.net/schema/dmrs#DMRS>
C <http://wordnet.princeton.edu/pwn30/01002055-a-1> .
I will open a new issue for starting a related discussion.
Hello. While working in https://github.ibm.com/alexrad/extended-glosstag we had a problem in finding a DRMS by type. After that, I noticed that the DMRS node type definition was made using another context than that from the rest of the DMRS analisys.
In the following example we got a piece of an output in n-quads of a single DMRS annotation, for the sentence 'capable of reproducing; '. Notice the first line is defined in the context
_:Nd959b4e2979f439abb3775916655aaae
and the rest in the context<http://wordnet.princeton.edu/pwn30/01001689-a-1>
.It look like you're defining in a BlankNode context, and occur in all the cases:
Did you guys get this problem?