Closed DiellzaElshani closed 2 years ago
We can of course still introduce a prefix, but that would avoid the need for an URI. A triple consists of a Subject Predicate Object . In essence, when the object refers to a new individual, we need a URI to identify it.
If we define a new prefix at the beginning, like:
@prefix example: <www.uni-stuttgart.de/> .
we can use something like this:
example:9fe1f23b-26e9-46b9-b7de-552e3e3e8bd0 bhom:BH.oM.Architecture.Elements.Room.Perimeter example:38028790.
However, currently we follow a similar convection with the following, so I'd suggest to conitnute with it:
<www.uni-stuttgart.de/9fe1f23b-26e9-46b9-b7de-552e3e3e8bd0> bhom:BH.oM.Architecture.Elements.Room.Perimeter <www.uni-stuttgart.de/38028790>
Description:
When adding a new property which is also idividual to an indivusual (e.g. Room has location Point), we need to use the URI of the individuals to create triples, (not only the ID- basically the RDF identifier which is a URI).
Our current code looks like:
Expected behaviour:
It should look like:
Test file(s):