Using the Jena RDF library, how do I return the property of a URI resource? -

-

I have a Jena URI resource ( resource is the reference of an object where isURIResource () returns correct). An example resource URI is:

If you open it in a web browser, you might be given HTML rendering of the data:

You can change the .html extension with .rdf :

This RDF model is formatted as XML. The property I need to retrieve is: 

  & lt; C: symbol & gt; MSFT.OQ & lt; / C: Symbols & gt;

In summary, I am looking for a way to use my Jena Yuri resource to return the value of c: symbol , which in my example MSFT.OQ

I know that I can take this URI, getting the representation of RDF through some HTTP client, then load the model as a load and inquiry I am already doing what I believe, though, that Jena is doing this recurring task. Provides a more elegant solution.

I do not think there is 'streaming' API for Jena like stax api for xml. Can help: Last year I wrote an simple streaming parser for RDF: it does not handle full RDF device, but you can get some ideas.


Comments

Post a Comment

Popular posts from this blog

MySql variables and php -

-
I am getting an error with php in order to format mysql_query () in php to format this string What is the right way? SELECT SELECT SELECT (*) Agents @AgentCount; User_Agent_English, User_Angent_Oursal, US.___Gent_Aginal, COUNT (User_Agent_Percade) ACC, COUNT (*) / (AgentCount) Percentage by agents user_agent_preser order DEC limit limit 50; In PHP, how am i setting $ query $ query = "SELECT count (*) agents @ agentcount; SELECT user_agent_parsed, User_agent_original , COUNT (user_agent_parsed) ascount, COUNT (*) / (@AgentCount) as a percentage by user_agent_parced by URI date DESC limit 50 "; This exact query will work properly if I put it in MySQL directly through a command line session. Do I need to release two separate php calls from mysql_query () and store the results first? I get the following error: There is an error in your SQL syntax; Instead of using a sub-selection and instead of using the 'SELECT user_agent_parsed, user_agent_original, ne...
Read more

php - Laravel - Overriding a resource route into a different route filter group -

-
Does Laravel's routing work as expected? What I think, if I want to override a route, then I just have to give the expected route before each other. I have something like this: root :: group (array ('first' = & gt; 'defaultLoads' =); function () {root :: post 'Newsletter', 'newsletter controller @ store'); root: group (array ('(newsletter', 'newsletter controller');}}); That if I post this route, only http://domain.com/newsletter should run only the default loads route filter. However, when I call php Runs artisan routes , I get this: | | POST newsletter | newsletter.store | newslettercontroller@ store | default loads | login | | though it reads the route correctly (PHP artisan loads which The correct path is to the right place) but the file of the resource path even if it is not in the filter group, the path is affected. Then my question: How does it work Laravel? If so, do I post this -> Newsle...
Read more

url rewriting - How to implement the returnurl like SO in PHP? -

-
This URL should work even after the rewrite. Is this possible? Otherwise, I can only hardcoded everything If you are trying to create a login system with redirection You need to use the HTTP_REFERER header to find out where the user came from so that you can send it back there. The best way to do this is to use something like this in your login form: // - Login php & Lt; Input type = "password" name = "password" /> & Lt; Input type = "hidden" name = "returnrelale" value = "& lt ;? php echo $ redirectURL ;? & gt;" / & Gt; & Lt; / Form & gt; Please note that some ISP, browser or proxy will delete the referrer header, so you can not rely on each user to work fully. If you use a statement, to check whether the header exists or not, you can send those users back to the homepage or whatever. Edit If you are looking to use $ _SERVER ['REQUEST_URI'], if you are running Apache It sho...
Read more