xavierxc14 / jenabean

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

OWL or RDF #4

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hello,

First, I'd like to thank you for a brilliant idea of JenaBean. This is what
we are exactly looking for. Here are I one question:

Is there any particular reason classes are defined in OWL (as instances of
owl:Class) and properties in pure RDFS (as instances of rdf:Property, not
as owl:ObjectProperty or owl:DatatypeProperty) ?

> What is the expected output? What do you see instead?

For example you may see the following N3 output of Sensor2 class and
timestamp property.

<http://unimore.ecosystem.zombie.sensor/Sensor2>
      a       owl:Class ;
      <http://thewebsemantic.com/javaclass>
              "unimore.ecosystem.zombie.sensor.Sensor2" .

<http://ecosystem.it#timeStamp>
      a       <http://www.w3.org/1999/02/22-rdf-syntax-ns#Property> .

> What version of the product are you using? On what operating system?

The fresh checkout from SVN repository.

Best,

Maciej

Original issue reported on code.google.com by mgawine...@gmail.com on 19 May 2008 at 4:37

GoogleCodeExporter commented 8 years ago
Suggestion:

Refactor the method in thewebsemantic.Base.java:

protected Resource ontClass(String uri) {
  return m.getResource(uri).addProperty(RDF.type, OWL.Class);
}

into: 

protected Resource rdfsClass(String uri) {
  return m.getResource(uri).addProperty(RDF.type, RDFS.Class);
}

Naming of the method is -- of course -- not important.

What do you think about that?

Best,
Maciej

Original comment by mgawine...@gmail.com on 22 May 2008 at 3:17

GoogleCodeExporter commented 8 years ago
I like it!  you know I haven't been checking these bugs, they don't get mailed 
to me.
 I think somebody else, or myself, has made this change so I'm closing it.

Original comment by thewebse...@gmail.com on 6 Nov 2008 at 4:24