On Tue, Aug 13, 2013 at 3:18 PM, Márcio Vinicius
<[email protected]> wrote:
> Currently ContextServer I developed an application that receives requests
> from a client and responds. The ContextServer consists of two basic methods:
>
> 1 - storeModel public String (String sourceModelXML) - method that takes
> models as XML and add to the database
>
> 2 - public String [] queryModel (querySPARQL String, String [] Parans) -
> method that takes a query and the parameters that you want to return.
>
> These methods I believe are right.
>
> My question is how I'm organizing the information.
>
> The application is for Monitoring Vital Signs and currently my database goes
> as follows:
>
> exemplo_banco_em_triplas.rtf - attached

This list doesn't accept attachments.  You'll need to post the
document somewhere online (e.g., pastebin), and link to it, if it's
important for us to see it.

> It is as it should be willing in the bank? Property + id?
>
> Example:
> <http://www.semanticweb.org/ontologies/2013/1/Ontology1361391792831.owl#valueSystolic01>

It's not really clear what you're asking here.  It's very common to
define an ontology IRI and then define properties whose IRIs are the
concatenation <ontologyIRI> + "#" + <propertyName>.

> Another question I have is regarding the schemagem:
>
> When I use the schmeagem from a file. Owl for a java class it generates
> these resources which in my opinion I should add them to the software,
> example:
>
> My class is sired by schmeagem (MonitorSinalVital.java - attached) on line
> 152 of this file is the resource "axiliary_fossa01", the correct would I
> delete it from this class and when I add a fossa_auxiliary in my application
> I add fossa_auxiliary + id ?

Usually the classes generated by schemagen ('...n', not '...m') are
used as classes containing symbolic constants.  For instance, your
class might be something like

class MonitorSinalVital {
  public static Resource axiliary_fossa01 = ...;
}

The way you'd typically use that, if that's a property is like this,
in another class somewhere:

Model model = ...;
Resource subject = ...;
RDFNode object = ...;
model.add( subject, MonitorSinalVital.axiliary_fossa01, object );

Another good example might be the RDF class [1] that comes with Jena,
or the OWL class [2], or any of the other classes in the vocabulary
package [3].  For instance, you can do:

Resource someThing = ...;
someThing.addProperty( RDF.type, OWL.Thing );

[1] 
http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/RDF.html
[2] 
http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/OWL.html
[3] 
http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/package-summary.html

-- 
Joshua Taylor, http://www.cs.rpi.edu/~tayloj/

Reply via email to