dotnetrdf-support — User Help and Support

[dotNetRDF-Support] hi nice to meet you

[Anita S. <sia...@ya...>]

Hello dear.



How are you today 
hope everything is well with you, as my name is Anita is my pleasure to 
contact you after viewing your profile today  which really interest me 
in having communication with you if you have the desire with me so we 
can get to know each other better and see what was happening in the 
future. I will be very happy if you can write me back on my personal 
email for easiest communication and to know more about each other.i will
 send you my picture when I receive your response, I'll be waiting to 
hear from you and I wish you all the best for your day . new friend   
(ANI...@YA...)

Anita

Re: [dotNetRDF-Support] UriNode Encoding / Escaping

[Rob V. <rv...@do...>]

Hi


It wasn't intentionally by design and neither is it really a bug in the strictest sense.  I added a unit test and the URIs round trip correctly whether they have the escapes included in them or not (at least for simple escapes like this) i.e. they can be serialized and deserialized and still the same URI.


Looking at the specifications again I see that technically it should do this so I have raised bug CORE-136 [1] and this should very shortly be fixed as it requires trivial code changes.  I'll drop you another email when this is fixed.


Thanks for reporting this,


Rob Vesse


[1]: http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=136

----------------------------------------

From: "Øystein Isaksen" <oys...@bo...>

Sent: 18 October 2011 13:38

To: "dot...@li..." <dot...@li...>

Subject: [dotNetRDF-Support] UriNode Encoding / Escaping

Hi.
 
Big fan of your framework, and we use it in a project of ours. We have a little problem though, and it has to do with Uri encoding. We send in an escaped Uri like the example code shows:
 
var name =
"http://psi.hafslund.no/sesam/ifs/employee/escaped%20psi";
g.Assert(new Triple(dotNetRDF, says, (INode)g.CreateUriNode(new Uri(name))));
 
 
RdfXmlWriter rdfxmlwriter =
new RdfXmlWriter();
rdfxmlwriter.Save(g,
"HelloWorld.xml");
 
Ends up unescaped again in the xml file:
 
<rdf:RDF
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:public360="http://psi.hafslund.no/sesam/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
 
<rdf:Description
rdf:about="http://www.dotnetrdf.org/">
    <ns0:says
xmlns:ns0="http://example.org/"
rdf:resource="http://psi.hafslund.no/sesam/ifs/employee/escaped psi" />
 
</rdf:Description>
</rdf:RDF>
 
Is this by design, or is this a bug? 
J
 
I've also tried to use qname parameter in the CreateUriNode, but get the same result. Hence, it does not seem to be an Uri problem, but something that happens in the RdfXmlWriter.
 
When using the NTriplesWriter, it works as expected.
 
NTriplesWriter ntwriter =
new NTriplesWriter();
ntwriter.Save(g,
"HelloWorld.nt");
 
<http://www.dotnetrdf.org/>
<http://example.org/says>
<http://psi.hafslund.no/sesam/ifs/employee/escaped%20psi> .
 
Best regards
Øystein Isaksen

[dotNetRDF-Support] UriNode Encoding / Escaping

[Øystein I. <oys...@bo...>]

Hi.

Big fan of your framework, and we use it in a project of ours. We have a little problem though, and it has to do with Uri encoding. We send in an escaped Uri like the example code shows:

var name = "http://psi.hafslund.no/sesam/ifs/employee/escaped%20psi";
g.Assert(new Triple(dotNetRDF, says, (INode)g.CreateUriNode(new Uri(name))));


RdfXmlWriter rdfxmlwriter = new RdfXmlWriter();
rdfxmlwriter.Save(g, "HelloWorld.xml");

Ends up unescaped again in the xml file:

<rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:public360="http://psi.hafslund.no/sesam/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
  <rdf:Description rdf:about="http://www.dotnetrdf.org/">
    <ns0:says xmlns:ns0="http://example.org/" rdf:resource="http://psi.hafslund.no/sesam/ifs/employee/escaped psi" />
  </rdf:Description>
</rdf:RDF>

Is this by design, or is this a bug? :)

I've also tried to use qname parameter in the CreateUriNode, but get the same result. Hence, it does not seem to be an Uri problem, but something that happens in the RdfXmlWriter.

When using the NTriplesWriter, it works as expected.

NTriplesWriter ntwriter = new NTriplesWriter();
ntwriter.Save(g, "HelloWorld.nt");

<http://www.dotnetrdf.org/> <http://example.org/says> <http://psi.hafslund.no/sesam/ifs/employee/escaped%20psi> .

Best regards
Øystein Isaksen

Re: [dotNetRDF-Support] Sparql Update Help

[Rob V. <rv...@do...>]

Hi Marco
I believe this was already fixed for the 0.5.0 release which came out just over a week ago, can you test your code with the latest release and let me know if that solves your issue?
As a minor comment on your code I notice that you have ?doc and ?worker variables but then restrict these with a FILTER to just a single value for each.  In that case it would make more sense just to make these parameters and substitute in the values with the SetUri() method as you've already done for the @Tagging parameter
Regards,
Rob Vesse

----------------------------------------
From: "Marco Cepparulo CRMPA" <cep...@mo...>
Sent: 19 September 2011 15:56
To: dot...@li..., dot...@li...
Subject: [dotNetRDF-Support] Sparql Update Help 

Hi,i'm using dotnetrdf for a research project. I have problems with SPARQL update, especially with the DELETE operation. I'm using  Sesame2.3.3+Owlim3.5 as triplestore and dotnetrdf 0.4.1 (tested also on 0.2.1). My triples are stored in defaultGraph so there isn't any context associated to triples.The code throw an NullReferenceException in ConstructContext method GetNode case NodeType.Uri:IUriNode u = (IUriNode)n;temp = this._g.CreateUriNode(u.Uri);break;I resolve this problem changing ProcessDeleteCommand method in GenericUpdateProcessor. Dotnetrdf source uses ConstructContext context = new ConstructContext(null, s, true);I replace this code with the code below and the delete operation worksIGraph g = new Graph();g.BaseUri = cmd.GraphUri;ConstructContext context = new ConstructContext(g, s, true);I create a simple node which contain defaultGraphBelow is the code that performs the DELETE on triplestore: if (!defaultGraphUri.Equals(""))                with="with <"+defaultGraphUri+">";            SparqlUpdateParser parser = new SparqlUpdateParser();             //Generate a Command             SparqlParameterizedString cmdString = new SparqlParameterizedString();            cmdString.CommandText = "PREFIX km: <" + kmPrefix + ">";            cmdString.CommandText += "PREFIX tag: <" + tagPrefix + ">";                        cmdString.CommandText += " " + with + " delete {?tagging tag:tag ?doc. ?tagging tag:taggedBy ?worker. ?tagging tag:associatedTag ?tag. ?tagging a @Tagging}";            cmdString.CommandText += " where {?tagging tag:tag ?doc.";            cmdString.CommandText += " ?tagging tag:taggedBy ?worker.";            cmdString.CommandText += " ?tagging tag:associatedTag ?tag.";            cmdString.CommandText += " Filter(?doc=<" + docid + "> &&";            cmdString.CommandText +=  " ?worker=<" + workerid + ">) }";             cmdString.SetUri("Tagging", new Uri(tagPrefix + "RestrictedTagging"));            //Parse the command into a SparqlUpdateCommandSet            SparqlUpdateCommandSet cmds = parser.ParseFromString(cmdString);             //Connect to Sesame (which does not support SPARQL Update itself)            //and create a GenericUpdateProcessor to apply the update            SesameHttpProtocolConnector sesame = new SesameHttpProtocolConnector(server, DB);            GenericUpdateProcessor processor = new GenericUpdateProcessor(sesame);             processor.ProcessCommandSet(cmds);            The Delete command delete the relations (Tagging entity) between worker and document input.Can you help me to execute Delete command if I made a mistake on my code?Can you tell me if this is a bug, and if my change has impact on other dotnetrdf operation (i.e select)? 
 

[dotNetRDF-Support] Sparql Update Help

[Marco C. C. <cep...@mo...>]

Hi,

i'm using dotnetrdf for a research project. I have problems with SPARQL
update, especially with the DELETE operation. I'm using
Sesame2.3.3+Owlim3.5 as triplestore and dotnetrdf 0.4.1 (tested also on
0.2.1). 

My triples are stored in defaultGraph so there isn't any context associated
to triples.

The code throw an NullReferenceException in ConstructContext method GetNode 

case NodeType.Uri:

IUriNode u = (IUriNode)n;

temp = this._g.CreateUriNode(u.Uri);

break;

I resolve this problem changing ProcessDeleteCommand method in
GenericUpdateProcessor. Dotnetrdf source uses 

ConstructContext context = new ConstructContext(null, s, true);

I replace this code with the code below and the delete operation works

IGraph g = new Graph();

g.BaseUri = cmd.GraphUri;

ConstructContext context = new ConstructContext(g, s, true);

I create a simple node which contain defaultGraph

Below is the code that performs the DELETE on triplestore:

 

if (!defaultGraphUri.Equals(""))

                with="with <"+defaultGraphUri+">";

            SparqlUpdateParser parser = new SparqlUpdateParser();

 

            //Generate a Command

 

            SparqlParameterizedString cmdString = new
SparqlParameterizedString();

            cmdString.CommandText = "PREFIX km: <" + kmPrefix + ">";

            cmdString.CommandText += "PREFIX tag: <" + tagPrefix + ">";

            

            cmdString.CommandText += " " + with + " delete {?tagging tag:tag
?doc. ?tagging tag:taggedBy ?worker. ?tagging tag:associatedTag ?tag.
?tagging a @Tagging}";

            cmdString.CommandText += " where {?tagging tag:tag ?doc.";

            cmdString.CommandText += " ?tagging tag:taggedBy ?worker.";

            cmdString.CommandText += " ?tagging tag:associatedTag ?tag.";

            cmdString.CommandText += " Filter(?doc=<" + docid + "> &&";

            cmdString.CommandText +=  " ?worker=<" + workerid + ">) }";

 

            cmdString.SetUri("Tagging", new Uri(tagPrefix +
"RestrictedTagging"));

            //Parse the command into a SparqlUpdateCommandSet

            SparqlUpdateCommandSet cmds = parser.ParseFromString(cmdString);

 

            //Connect to Sesame (which does not support SPARQL Update
itself)

            //and create a GenericUpdateProcessor to apply the update

            SesameHttpProtocolConnector sesame = new
SesameHttpProtocolConnector(server, DB);

            GenericUpdateProcessor processor = new
GenericUpdateProcessor(sesame);

 

            processor.ProcessCommandSet(cmds);

            

The Delete command delete the relations (Tagging entity) between worker and
document input.

Can you help me to execute Delete command if I made a mistake on my code?

Can you tell me if this is a bug, and if my change has impact on other
dotnetrdf operation (i.e select)?

 

[dotNetRDF-Support] Migrating Legacy SQL Stores

[Rob V. <rv...@do...>]

Hi All
Those of you who have been using our legacy SQL store will be aware that we 
have been working to deprecate and replace it for a while now and our 0.5.0 
release marks the introduction of our new ADO Store.
This new store provides many advantages including better abstraction 
between code and database schema, improved security settings, SQL Azure 
support and much more memory efficient SPARQL Query over SQL databases.  
This new store is provided in a separate library dotNetRDF.Data.Sql.dll 
which you will find under the Data/Sql/ directory in the latest download 
packages.
We've now added some basic documentation on using the store and how to 
migrate existing stores, please see [1] and [2] for details.  We hope the 
migration process should be relatively simple and easy, if you encounter 
any problems please drop us an email and we'll work to address this ASAP.  
If you have any questions, requests for additional documentation etc. 
please let us know.
Best Regards,
Rob Vesse
[1]: http://www.dotnetrdf.org/blogitem.asp?blogID=52[2]: 
http://www.dotnetrdf.org/content.asp?pageID=rdfSqlStorage

 

[dotNetRDF-Support] dotNetRDF 0.5.0 Beta and dotNetRDF Toolkit 0.3.0 Alpha Released

[Rob V. <rv...@do...>]

Hi All
We are please to announce that dotNetRDF 0.5.0 Beta has been released as 
well as the 0.3.0 Alpha release of the associated dotNetRDF Toolkit.  You 
can get the latest library from [1] and latest toolkit from [2]
The latest release of the library brings the following new features and 
improvements:Bug fixes for various issues including major crash fixes for 
Silverlight/Windows Phone 7Basic .Net serialization support for some core 
classes e.g. INode, IGraph, SparqlResultSetNew asynchronous callback based 
APIs for various features to provide better Silverlight/Windows Phone 7 
support and to make it easier to write async RDF/SPARQL based 
applicationsNew features in the Configuration API and our ASP.Net 
integration to provide detailed control of writer behaviour with regards to 
things like compression, pretty printing, DTD usage etc - see [3] for 
detailsAdded a new ExplainQueryProcessor that can be used to explain the 
evaluation of queries using our Leviathan engineRefactored the 
LeviathanQueryProcessor to make it much easier to extendSupport for some 
experimental advanced algebra optimisations such as parallelised union 
evaluation (disabled by default)Expanded the Handlers API so that you can 
use it to stream process RDF and SPARQL Results from a wider variety of 
data sources including SPARQL endpoints, any IGenericIOManager instance and 
SPARQL Queries in general.This release also marks the introduction of a new 
packaging model where some features are incorporated into separate DLLs 
from the core library.  As of this release as well as the Core library 
(dotNetRDF.dll) - which now comes in 4 different versions: .Net 3.5, .Net 
3.5 Client Profile, Silverlight 4 and Silverlight 4 for Windows Phone 7 - 
you will also find two data providers - Data.Virtuoso and Data.Sql
Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll) contains the OpenLink Virtuoso 
functionality previously found in the core library thus allowing us to 
remove OpenLink.Data.Virtuoso.dll as a dependency from the core library so 
users who don't need this feature have a smaller dependency footprint.
Data.Sql (dotNetRDF.Data.Sql.dll) contains our new SQL backend called the 
ADO store which currently supports Microsoft SQL Server and SQL Azure only. 
 This backend replaces the legacy SQL store from the core library and we'll 
be providing documentation and tooling for migrating from the old format to 
the new format in the next few days so please keep an eye on the mailing 
list.
Note - As another dependency change dotNetRDF now uses 
Newtonsoft.Json.Net35.dll since the main Json.Net build is now targeted at 
.Net 4.0, we plan to move to .Net 4.0 as the primary build next year though 
we will continue to provide a .Net 3.5 build
All of these libraries are now also available via NuGet for those using 
VS2010 and the NuGet plugin.
The latest release of the Toolkit incorporates the following 
changes:Support for our new SQL backend in Store ManagerNamespace 
declarations from queries are now used to format SELECT results in 
StoreManager and SparqlGUIQuery Explanation features in SparqlGUISupport 
for configuring advanced options when using the Save With functionality in 
rdfEditorFaster and more memory efficient syntax validation in rdfEditorNew 
rdfSqlStorage tool for managing our new SQL backendAs always we aim to 
ensure that the library and toolkit continues to stabilise and improve over 
time, if you have any suggestions, feedback, bug reports, patches etc 
please let us know via the mailing lists.
Finally we'd like to thank the following people who've contributed to this 
release:Graham Moore and Khalil Ahmed for input on the query engine 
refactoringDaniel Bittencourt, Rodrigo de Castro Reis, Rafael Dias Araujo 
and Guillherme Alcantra Dias for input on the .Net serialization 
supportKoos Strydoom, Robert P DeCarlo for input on the new SQL backendKoos 
Strydoom and Rahul Patil for input on the new advanced writer configuration 
for ASP.Net featuresJim Rhyne for input on Store Manager and SparqlGUI 
improvements regarding formatting of SELECT resultsSid John and Steve S for 
feedback and debugging help with Silverlight/Windows Phone 7 issuesPaul 
Hermans for input on the improved Save With functionality in rdfEditorCsaba 
GoncziMike GroveApologies to anyone I've unintentionally missed off this 
list, thanks again for all your contributions
Best Regards,
Rob Vesse
[1]: http://www.dotnetrdf.org/content.asp?pageID=Download%20dotNetRDF[2]: 
http://www.dotnetrdf.org/content.asp?pageID=Download%20dotNetRDF%20Toolkit%2
0for%20Windows[3]: 
http://www.dotnetrdf.org/content.asp?pageID=Configuration%20API%20-%20HTTP%2
0Handlers#OutputSettings 

Re: [dotNetRDF-Support] rdfEditor

[Rob V. <rv...@do...>]

Apologies for this, was due to a bug in my build and deployment scripts, the download should now include rdfEditor
Let me know if it still is missing
Rob Vesse

----------------------------------------
From: "Thierry Cot" <Thi...@fa...>
Sent: 09 September 2011 19:12
To: "dot...@li..." <dot...@li...>
Subject: [dotNetRDF-Support] rdfEditor 





Hello,
 
 
I have just downloaded tools package on you web site (http://www.dotnetrdf.org/content.asp?pageID=Tools).
In this release ( 030_alpha),  rdtEditor application is missing.
 
Is this the good link ?
 
Regards
 
 
 






	 
Thierry Cot
	 
Facteur K inc.
	 
Fondateur, Associé
	 
Tél. : 418 266-7840 ext: 102
	 
Thi...@Fa...
	 
www.FacteurK.com
	 
	 
	 
Solutions en gestion de l'information
	 
P 
Merci de considérer l'impact sur l'environnement avant d'imprimer ce courriel
	 



 
 




__________ Information from ESET NOD32 Antivirus, version of virus signature database 6450 (20110909) __________


The message was checked by ESET NOD32 Antivirus.


http://www.eset.com

 

[dotNetRDF-Support] subscribe

[evan chua-y. <sem...@gm...>]

subscribe

[dotNetRDF-Support] New Issue Tracker

[Rob V. <rv...@do...>]

Hi all

 

In addition to our email support we will now formally track issues through
an online tracker at http://www.dotnetrdf.org/tracker/

 

You can report bugs and/or request features there directly if you so wish
and we will be using it to track the progress of our work on all future
releases

 

Regards,

 

Rob Vesse

dotNetRDF Lead Developer

================================================================

Developer Discussion & Feature Request -
dot...@li...

Bug Reports - dot...@li...

User Help & Support - dot...@li...

 

Website: http://www.dotnetrdf.org

User Guide: http://www.dotnetrdf.org/content.asp?pageID=User%20Guide

API: http://www.dotnetrdf.org/api/

================================================================

 

 

 

Re: [dotNetRDF-Support] problem with virtuoso opensource

[Rob V. <rv...@do...>]

Hi Csaba

I think this is due to dotNetRDF though I wouldn't be surprised if using Virtuoso directly produced the same behaviour.  You are not doing anything wrong and this is not a bug, it is by design.

The host portion of a URI is case-insensitive (see Section 3.2.2 of RFC 3986 [1]).  dotNetRDF uses the standard .Net Uri class to represent URIs which automatically normalizes appropriate sections of a URI to lower case.

If you have further questions please let me know

Regards,

Rob Vesse

[1]: http://www.ietf.org/rfc/rfc3986.txt

----------------------------------------
From: "Csaba Gönczi" <cs...@gm...>
Sent: 16 July 2011 18:06
To: rv...@do...
Subject: problem with virtuoso opensource 

Hi Rob,

I just found this bug, but I'm not sure if it is connected to dotNetRDF or this problem is caused by Virtuoso's ADO.Net provider.

I have this SPARQL query and I'm expecting ?x to be http://testAuthor.com.

PREFIX j.0:   <http://xmlns.com/foaf/0.1/>
SELECT DISTINCT ?x { {<http://test.com> <http://audio.com#author> ?x. ?x j.0:name ?y.} UNION {<http://test.com> <http://audio.com#author> ?x. FILTER isLiteral(?x)} }

My code looks like this:
SparqlResultSet obj = manager.Query( p_query ) as SparqlResultSet; (p_query is the query above and manager is the VirtuosoManager instance)

The query executes just fine but ?x is http://testauthor.com. The same as I expected but in lower case.

Is there a workaround to solve this or am I doing something wrong?

Regards,
CssaBee

[dotNetRDF-Support] [ANN] dotNetRDF 0.4.1 Beta Released

[Rob V. <ra...@ec...>]

Hi All 

We are pleased to announce a new release of dotNetRDF. dotNetRDF
is a free and open source (GPL/LGPL/MIT license) RDF/Semantic Web library
written in C# for .Net 3.5 and higher. 

The new version is 0.4.1 Beta.
Below is a quick summary of new features, you can read more online at [1]
or see the full Change Log in the download package. Downloads are available
via our website [2] or via SourceForge [3]

Key New Features/Improvements


 	* Full SPARQL 1.1 Query and Update Support (passes the entire official
test suite as it currently stands)
 	* Significantly improved parser
subsystem
 	* Various bug fixes for 0.4.0 issues

We'd like to acknowledge
the following people whose bug reports, patches and suggestions have helped
shape this release: 

 	* Graham Moore
 	* Laurent Lefort
 	* Felipe
Santos
 	* Sergey Novikov
 	* Adonis Damian
 	* Bob Morris

Regards, 

Rob
Vesse 

[1] http://www.dotnetrdf.org/blogitem.asp?blogID=44
[2]
http://www.dotnetrdf.org/content.asp?pageID=Download%20dotNetRDF
[3]
https://sourceforge.net/projects/dotnetrdf/files/Library/0.4.1%20Beta/dotNetRDF_library_041_beta.zip/download

[dotNetRDF-Support] Advance Notice of Breaking API Changes in Upcoming 0.4.1 Release

[Rob V. <rv...@do...>]

Hi All

Please take a look at our latest blog post - 
http://www.dotnetrdf.org/blogitem.asp?blogID=43 - which describes some 
breaking API changes we have made for the forthcoming release based on user 
feedback to address a key limitation of the API.

As stated in the blog post all your code should be easily fixable using a 
simple find and replace so while the change is fundamental in some respects 
from a code perspective it is relatively minor.

Apologies in advance for breaking your code when the new release comes out 
late next week.

Best Regards,

Rob Vesse

 

Re: [dotNetRDF-Support] website suggestion to aid tool users

[Rob V. <rv...@do...>]

Good point, have added a note about this to both the Tools page and the
homepage

Thanks again,

Rob Vesse

> -----Original Message-----
> From: Bob Morris [mailto:mor...@gm...]
> Sent: 12 May 2011 13:13
> To: Rob Vesse
> Subject: Re: [dotNetRDF-Support] website suggestion to aid tool users
> 
> One more small suggestion:
> 
> on http://www.dotnetrdf.org/content.asp?pageID=Tools in the
> requirements section, remark that Windows 7 has .Net 3.5 already
> installed, but that other versions of Windows will require a .Net
> installation.
> 
> 
> 
> On Thu, May 12, 2011 at 6:16 AM, Rob Vesse <rv...@do...>
> wrote:
> > Hi Bob
> >
> > Thanks for the suggestions, hopefully the difference between the two
> kinds
> > of download are now clear on the homepage.
> >
> > I have also added a download link to the page for each individual
> tool so a
> > person arriving at one of those pages can quickly get to the Tools
> download.
> >
> > Regards,
> >
> > Rob Vesse
> >
> >> -----Original Message-----
> >> From: Bob Morris [mailto:mor...@gm...]
> >> Sent: 12 May 2011 03:32
> >> To: dot...@li...
> >> Subject: [dotNetRDF-Support] website suggestion to aid tool users
> >>
> >> Based on your answer in
> >> http://answers.semanticweb.com/questions/510/are-there-such-things-
> as-
> >> rdf-editors,
> >> I recently suggested to a biologist who is fairly sophisticated
> about
> >> RDF and OWL that he look at rdfEditor to see if it would ease his
> pain
> >> arising from trying to use Protege to edit individuals as examples
> for
> >> his ontology development. Alas, instead of your link to the tool
> page,
> >> he ended up on your main web page home
> >> http://www.dotnetrdf.org/default.asp. There, due to not
> understanding
> >> the difference between the tools and the api, he stubbed his toe on
> >> the wrong download. That is a likely scenario for the rising number
> of
> >> domain scientists beginning to learn about rdf.
> >>
> >> On http://www.dotnetrdf.org/default.asp  you could help avoid that
> >> with a little more prominent mention of the tools in or near the
> >> section on downloading and/or perhaps have a separate section on
> >> tools, rather than relegate it only to the links at the page header.
> >> For example, you might say
> >>
> >> TOOLS
> >> If you only want the standalone tools such as rdfEditor, you can
> find
> >> links to them completely packaged [here]. By contrast, if you follow
> >> download links on this page, you will get distributions mainly of
> >> interest to programmers.
> >>
> >>
> >> Just a thought
> >> Bob Morris
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Robert A. Morris
> >>
> >> Emeritus Professor  of Computer Science
> >> UMASS-Boston
> >> 100 Morrissey Blvd
> >> Boston, MA 02125-3390
> >> IT Staff
> >> Filtered Push Project
> >> Department of Organismal and Evolutionary Biology
> >> Harvard University
> >>
> >>
> >> email: mor...@gm...
> >> web: http://efg.cs.umb.edu/
> >> web: http://etaxonomy.org/mw/FilteredPush
> >> http://www.cs.umb.edu/~ram
> >> phone (+1) 857 222 7992 (mobile)
> >>
> >> --------------------------------------------------------------------
> ---
> >> -------
> >> Achieve unprecedented app performance and reliability
> >> What every C/C++ and Fortran developer should know.
> >> Learn how Intel has extended the reach of its next-generation tools
> >> to help boost performance applications - inlcuding clusters.
> >> http://p.sf.net/sfu/intel-dev2devmay
> >> _______________________________________________
> >> dotNetRDF-Support mailing list
> >> dot...@li...
> >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support
> >
> >
> >
> >
> 
> 
> 
> --
> Robert A. Morris
> 
> Emeritus Professor  of Computer Science
> UMASS-Boston
> 100 Morrissey Blvd
> Boston, MA 02125-3390
> IT Staff
> Filtered Push Project
> Department of Organismal and Evolutionary Biology
> Harvard University
> 
> 
> email: mor...@gm...
> web: http://efg.cs.umb.edu/
> web: http://etaxonomy.org/mw/FilteredPush
> http://www.cs.umb.edu/~ram
> phone (+1) 857 222 7992 (mobile)

Re: [dotNetRDF-Support] website suggestion to aid tool users

[Rob V. <rv...@do...>]

Hi Lee

> -----Original Message-----
> From: Lee Fisher [mailto:bl...@gm...]
> Sent: 12 May 2011 06:00
> To: dotNetRDF User Help and Support
> Subject: Re: [dotNetRDF-Support] website suggestion to aid tool users
> 
> On 5/11/11 7:31 PM, Bob Morris wrote:
> > Based on your answer in
> > http://answers.semanticweb.com/questions/510/are-there-such-things-
> as-rdf-editors,
> 
> Hmm, nobody mentioned Morla on the stackoverflow thread...
> 
> http://www.morlardf.net/about.php

I guess that is because no one is really aware of it for whatever reason.

As a moderator and active member of the answers.sematicweb.com community I
would encourage you to join (if you haven't already) and add the link
yourself so other people can find Morla in future as it looks interesting.

Best Regards,

Rob Vesse

Re: [dotNetRDF-Support] website suggestion to aid tool users

[Rob V. <rv...@do...>]

Hi Bob

Thanks for the suggestions, hopefully the difference between the two kinds
of download are now clear on the homepage.

I have also added a download link to the page for each individual tool so a
person arriving at one of those pages can quickly get to the Tools download.

Regards,

Rob Vesse

> -----Original Message-----
> From: Bob Morris [mailto:mor...@gm...]
> Sent: 12 May 2011 03:32
> To: dot...@li...
> Subject: [dotNetRDF-Support] website suggestion to aid tool users
> 
> Based on your answer in
> http://answers.semanticweb.com/questions/510/are-there-such-things-as-
> rdf-editors,
> I recently suggested to a biologist who is fairly sophisticated about
> RDF and OWL that he look at rdfEditor to see if it would ease his pain
> arising from trying to use Protege to edit individuals as examples for
> his ontology development. Alas, instead of your link to the tool page,
> he ended up on your main web page home
> http://www.dotnetrdf.org/default.asp. There, due to not understanding
> the difference between the tools and the api, he stubbed his toe on
> the wrong download. That is a likely scenario for the rising number of
> domain scientists beginning to learn about rdf.
> 
> On http://www.dotnetrdf.org/default.asp  you could help avoid that
> with a little more prominent mention of the tools in or near the
> section on downloading and/or perhaps have a separate section on
> tools, rather than relegate it only to the links at the page header.
> For example, you might say
> 
> TOOLS
> If you only want the standalone tools such as rdfEditor, you can find
> links to them completely packaged [here]. By contrast, if you follow
> download links on this page, you will get distributions mainly of
> interest to programmers.
> 
> 
> Just a thought
> Bob Morris
> 
> 
> 
> 
> 
> --
> Robert A. Morris
> 
> Emeritus Professor  of Computer Science
> UMASS-Boston
> 100 Morrissey Blvd
> Boston, MA 02125-3390
> IT Staff
> Filtered Push Project
> Department of Organismal and Evolutionary Biology
> Harvard University
> 
> 
> email: mor...@gm...
> web: http://efg.cs.umb.edu/
> web: http://etaxonomy.org/mw/FilteredPush
> http://www.cs.umb.edu/~ram
> phone (+1) 857 222 7992 (mobile)
> 
> -----------------------------------------------------------------------
> -------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> dotNetRDF-Support mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-support

Re: [dotNetRDF-Support] website suggestion to aid tool users

[Lee F. <bl...@gm...>]

On 5/11/11 7:31 PM, Bob Morris wrote:
> Based on your answer in
> http://answers.semanticweb.com/questions/510/are-there-such-things-as-rdf-editors,

Hmm, nobody mentioned Morla on the stackoverflow thread...

http://www.morlardf.net/about.php

[dotNetRDF-Support] website suggestion to aid tool users

[Bob M. <mor...@gm...>]

Based on your answer in
http://answers.semanticweb.com/questions/510/are-there-such-things-as-rdf-editors,
I recently suggested to a biologist who is fairly sophisticated about
RDF and OWL that he look at rdfEditor to see if it would ease his pain
arising from trying to use Protege to edit individuals as examples for
his ontology development. Alas, instead of your link to the tool page,
he ended up on your main web page home
http://www.dotnetrdf.org/default.asp. There, due to not understanding
the difference between the tools and the api, he stubbed his toe on
the wrong download. That is a likely scenario for the rising number of
domain scientists beginning to learn about rdf.

On http://www.dotnetrdf.org/default.asp  you could help avoid that
with a little more prominent mention of the tools in or near the
section on downloading and/or perhaps have a separate section on
tools, rather than relegate it only to the links at the page header.
For example, you might say

TOOLS
If you only want the standalone tools such as rdfEditor, you can find
links to them completely packaged [here]. By contrast, if you follow
download links on this page, you will get distributions mainly of
interest to programmers.


Just a thought
Bob Morris





-- 
Robert A. Morris

Emeritus Professor  of Computer Science
UMASS-Boston
100 Morrissey Blvd
Boston, MA 02125-3390
IT Staff
Filtered Push Project
Department of Organismal and Evolutionary Biology
Harvard University


email: mor...@gm...
web: http://efg.cs.umb.edu/
web: http://etaxonomy.org/mw/FilteredPush
http://www.cs.umb.edu/~ram
phone (+1) 857 222 7992 (mobile)

Re: [dotNetRDF-Support] NamespaceMap on parsetime

[Rob V. <rv...@vd...>]

Hi Jens

Just noticed an error in my reply.  The following line:

queryString.Namespaces.AddNamespace("rdf", new 
Uri(RdfSpecsHelper.RdfType));  

Should actually have been:

queryString.Namespaces.AddNamespace("rdf", new Uri(NamespaceMapper.RDF));  


Regards,

Rob Vesse

----------------------------------------
From: "Rob Vesse" <rv...@vd...>
Sent: 10 May 2011 11:08
To: "dotNetRDF User Help and Support" 
<dot...@li...>
Subject: re: [dotNetRDF-Support] NamespaceMap on parsetime 

Hi Jens

There is no way to add a Namespace to the parser, it must be defined in the 
query but you can do this without lots of nasty string concatenation by 
using the SparqlParameterizedString class.  Essentially this has a 
Namespaces property that can be used to build a namespace map and 
automatically inserts the appropriate prefix declarations into the 
querystring when it is passed to the parser.

SparqlParameterizedString queryString = new SparqlParameterizedString();

 //Define as many namespaces as you want - note that the Namespace Map for 
a Parameterized

//String will be empty by default so you typically need to define rdf 
namespace as well 
queryString.Namespaces.AddNamespace("rdf", new 
Uri(RdfSpecsHelper.RdfType));
queryString.Namespaces.AddNamespace("foaf", new 
Uri("http://xmlns.com/foaf/0.1/"));

//Use CommandText to set the actual query text
queryString.CommandText = "SELECT ?image WHERE 
{?image rdf:type foaf:Image}";

//Then parse the query from a string as usual
SparqlQueryParser parser = new SparqlQueryParser();
SparqlQuery query = parser.ParseFromString(queryString);

//Finally go ahead and process the query however you wish 

Hope this helps, if you have any further questions please let me know

Regards,

Rob Vesse

----------------------------------------
From: "Jens Panneel" <jen...@gm...>
Sent: 10 May 2011 10:52
To: dot...@li...
Subject: SPAM-LOW:  [dotNetRDF-Support] NamespaceMap on parsetime 



Hi
 
I am doing the folowing: 
 
http://pastebin.com/rfTC0fZu
 
/* 
* Getting an error from ParseFromString, saying:
* The Namespace URI for the given Prefix 'foaf' is not known by the 
in-scope NamespaceMapper
* 
* My question how can i add a Namespace before the parsing?
* I don't like the idea of manualy concatenating a lot of prefix strings to 

build my queries. 
*
*/ 
 
ISparqlQueryProcessor processor = new RemoteQueryProcessor(new 
SparqlRemoteEndpoint(new Uri("http://localhost:11025/sparql/query")));
SparqlQueryParser sparqlparser = new SparqlQueryParser();
SparqlQuery query = sparqlparser.ParseFromString("SELECT ?image WHERE 
{?image rdf:type foaf:Image}");
query.NamespaceMap.AddNamespace("foaf", new 
Uri("http://xmlns.com/foaf/0.1/"));
Object results = processor.ProcessQuery(query);
 
So is there a way to add a namespace to the parser?
 
Thanks 
 
JPanneel

 

Re: [dotNetRDF-Support] NamespaceMap on parsetime

[Rob V. <rv...@vd...>]

Hi Jens

There is no way to add a Namespace to the parser, it must be defined in the 
query but you can do this without lots of nasty string concatenation by 
using the SparqlParameterizedString class.  Essentially this has a 
Namespaces property that can be used to build a namespace map and 
automatically inserts the appropriate prefix declarations into the 
querystring when it is passed to the parser.

SparqlParameterizedString queryString = new SparqlParameterizedString();

 //Define as many namespaces as you want - note that the Namespace Map for 
a Parameterized

//String will be empty by default so you typically need to define rdf 
namespace as well 
queryString.Namespaces.AddNamespace("rdf", new 
Uri(RdfSpecsHelper.RdfType));
queryString.Namespaces.AddNamespace("foaf", new 
Uri("http://xmlns.com/foaf/0.1/"));

//Use CommandText to set the actual query text
queryString.CommandText = "SELECT ?image WHERE 
{?image rdf:type foaf:Image}";

//Then parse the query from a string as usual
SparqlQueryParser parser = new SparqlQueryParser();
SparqlQuery query = parser.ParseFromString(queryString);

//Finally go ahead and process the query however you wish 

Hope this helps, if you have any further questions please let me know

Regards,

Rob Vesse

----------------------------------------
From: "Jens Panneel" <jen...@gm...>
Sent: 10 May 2011 10:52
To: dot...@li...
Subject: SPAM-LOW:  [dotNetRDF-Support] NamespaceMap on parsetime 



Hi
 
I am doing the folowing: 
 
http://pastebin.com/rfTC0fZu
 
/* 
* Getting an error from ParseFromString, saying:
* The Namespace URI for the given Prefix 'foaf' is not known by the 
in-scope NamespaceMapper
* 
* My question how can i add a Namespace before the parsing?
* I don't like the idea of manualy concatenating a lot of prefix strings to 

build my queries. 
*
*/ 
 
ISparqlQueryProcessor processor = new RemoteQueryProcessor(new 
SparqlRemoteEndpoint(new Uri("http://localhost:11025/sparql/query")));
SparqlQueryParser sparqlparser = new SparqlQueryParser();
SparqlQuery query = sparqlparser.ParseFromString("SELECT ?image WHERE 
{?image rdf:type foaf:Image}");
query.NamespaceMap.AddNamespace("foaf", new 
Uri("http://xmlns.com/foaf/0.1/"));
Object results = processor.ProcessQuery(query);
 
So is there a way to add a namespace to the parser?
 
Thanks 
 
JPanneel
 

[dotNetRDF-Support] NamespaceMap on parsetime

[Jens P. <jen...@gm...>]

Hi

I am doing the folowing: 

http://pastebin.com/rfTC0fZu

/* 
* Getting an error from ParseFromString, saying:
* The Namespace URI for the given Prefix 'foaf' is not known by the in-scope NamespaceMapper
* 
* My question how can i add a Namespace before the parsing?
* I don't like the idea of manualy concatenating a lot of prefix strings to build my queries. 
*
*/ 

ISparqlQueryProcessor processor = new RemoteQueryProcessor(new SparqlRemoteEndpoint(new Uri("http://localhost:11025/sparql/query")));
SparqlQueryParser sparqlparser = new SparqlQueryParser();
SparqlQuery query = sparqlparser.ParseFromString("SELECT ?image WHERE {?image rdf:type foaf:Image}");
query.NamespaceMap.AddNamespace("foaf", new Uri("http://xmlns.com/foaf/0.1/"));
Object results = processor.ProcessQuery(query);

So is there a way to add a namespace to the parser?

Thanks 

JPanneel

Re: [dotNetRDF-Support] dotNetRDF API SPARQL CONSTRUCT issue

[Andrew A. <sti...@gm...>]

Hi Rob

Thank you for the quick and complete answer. I read documentation again and
I found answer just after sending my question to you. Where was my eyes
before? :)
I changed the scope of triples subjects from the blank nodes to separated
namespace. It is the right way not only for SPARQL, but to whole RDF
concepts. As I understand, the triple's subject better be an identifier
(URI) than a blank node.

Thank you again. I'll investigate your proposals. In some scenarios the
creation of the reflections by the CONSTRUCT query produce too complex
queries. Perhaps, the separation of logic into a SELECT query and the
subsequent processing will be more effective solution.

WBR
Andrew Abramov AKA Stinger


On Fri, May 6, 2011 at 14:36, Rob Vesse <rv...@do...> wrote:

> Hi Andrew
>
>
>
> Thanks for the feedback
>
>
>
> Firstly with regards to your issue I would point you to the SPARQL
> Specification section on Blank Node Labels in Query Results (
> http://www.w3.org/TR/rdf-sparql-query/#BlankNodesInResults) which states
> the following:
>
>
>
> “Blank node labels are scoped to a result set (as defined in "SPARQL Query
> Results XML Format <http://www.w3.org/TR/rdf-sparql-XMLres/>") or, for the
> CONSTRUCT query form, the result graph. Use of the same label within a
> result set indicates the same blank node.”
>
>
>
> For SELECT queries the library will return the original Blank Node labels
> but for CONSTRUCT/DESCRIBE queries it is necessary to rewrite the labels to
> avoid any collisions between Blank Nodes that originate from different
> Graphs.  Blank Node labels are just a convenient way of distinguishing
> between nodes in a particular serialization, they should not really be
> relied upon for identifying nodes wherever possible.
>
>
>
> The additional parts in the names you see are actually hash codes of the
> originating graph of the node, if you really wanted to you could use this to
> determine the graph the node originated from but I wouldn’t recommend this
> approach.  There is no way to turn off this behaviour as doing so would
> break the implementation of CONSTRUCT and DESCRIBE.
>
>
>
> What I would suggest is that you use a SELECT query to find the blank nodes
> you are interested in and then use the results to issue GetTriplesWithX()
> calls against your graphs to do further searches.
>
>
>
> You can also use the special syntax <_:id> in SPARQL queries to search for
> nodes with specific IDs but this is a non-standard SPARQL feature so again I
> would not rely on it.  This needs you to have enable Extended syntax for the
> SparqlQueryParser instance you use to parse your queries.
>
>
>
> If you have further questions or issues please let me know
>
>
>
> Regards,
>
>
>
> Rob Vesse
>
>
>
> *From:* Andrew Abramov [mailto:sti...@gm...]
> *Sent:* 05 May 2011 15:19
> *To:* rv...@do...
> *Subject:* dotNetRDF API SPARQL CONSTRUCT issue
>
>
>
> Hi, Rob!
>
>
>
> Let me say many thanks for your amazing library dotNetRDF. It's the great
> product!
>
> This library is my pass to the world of RDF.
>
>
>
> But I still have some misunderstandings. One of these is the construction
> of new graphs by the SPARQL CONSTRUCT query.
>
> It works. But the blank nodes created by this query have additional part in
> they names. These parts seems like the timestamp, separated from the
> original name by the minus sign.
>
>
>
> In my tasks will be better to avoid such additions. Because I construct the
> really new graphs - they are just the "reflections" of the original graph.
> And the changes of the node names makes me trouble to search orignal data on
> original graph.
>
> Maybe this approach (search data by the name of the node ) isn't "clear RDF
> way", but it makes the code and logic more clearly.
>
>
>
> Thus, I have a question. Can I avoid add-ons in the blank node names when
> creating new graph by the CONSTRUCT query?
>
>
>
> Thanks in advance
>
>
> WBR
> Andrew Abramov AKA Stinger
>

Re: [dotNetRDF-Support] dotNetRDF API SPARQL CONSTRUCT issue

[Rob V. <rv...@do...>]

Hi Andrew

 

Thanks for the feedback

 

Firstly with regards to your issue I would point you to the SPARQL
Specification section on Blank Node Labels in Query Results
(http://www.w3.org/TR/rdf-sparql-query/#BlankNodesInResults) which states
the following:

 

"Blank node labels are scoped to a result set (as defined in "SPARQL Query
Results XML Format <http://www.w3.org/TR/rdf-sparql-XMLres/> ") or, for the
CONSTRUCT query form, the result graph. Use of the same label within a
result set indicates the same blank node."

 

For SELECT queries the library will return the original Blank Node labels
but for CONSTRUCT/DESCRIBE queries it is necessary to rewrite the labels to
avoid any collisions between Blank Nodes that originate from different
Graphs.  Blank Node labels are just a convenient way of distinguishing
between nodes in a particular serialization, they should not really be
relied upon for identifying nodes wherever possible.

 

The additional parts in the names you see are actually hash codes of the
originating graph of the node, if you really wanted to you could use this to
determine the graph the node originated from but I wouldn't recommend this
approach.  There is no way to turn off this behaviour as doing so would
break the implementation of CONSTRUCT and DESCRIBE.

 

What I would suggest is that you use a SELECT query to find the blank nodes
you are interested in and then use the results to issue GetTriplesWithX()
calls against your graphs to do further searches.

 

You can also use the special syntax <_:id> in SPARQL queries to search for
nodes with specific IDs but this is a non-standard SPARQL feature so again I
would not rely on it.  This needs you to have enable Extended syntax for the
SparqlQueryParser instance you use to parse your queries.

 

If you have further questions or issues please let me know

 

Regards,

 

Rob Vesse

 

From: Andrew Abramov [mailto:sti...@gm...] 
Sent: 05 May 2011 15:19
To: rv...@do...
Subject: dotNetRDF API SPARQL CONSTRUCT issue

 

Hi, Rob!

 

Let me say many thanks for your amazing library dotNetRDF. It's the great
product!

This library is my pass to the world of RDF.

 

But I still have some misunderstandings. One of these is the construction of
new graphs by the SPARQL CONSTRUCT query.

It works. But the blank nodes created by this query have additional part in
they names. These parts seems like the timestamp, separated from the
original name by the minus sign.

 

In my tasks will be better to avoid such additions. Because I construct the
really new graphs - they are just the "reflections" of the original graph.
And the changes of the node names makes me trouble to search orignal data on
original graph.

Maybe this approach (search data by the name of the node ) isn't "clear RDF
way", but it makes the code and logic more clearly.

 

Thus, I have a question. Can I avoid add-ons in the blank node names when
creating new graph by the CONSTRUCT query?

 

Thanks in advance


WBR
Andrew Abramov AKA Stinger

Re: [dotNetRDF-Support] Bug

[Rob V. <rv...@do...>]

Hi Felipe

 

Thanks for reporting this, now fixed in SVN as of revision 1559 and will be
in the next release which should be available around the end of next week

 

Thanks,

 

Rob Vesse

 

From: Felipe Guimarães Santos [mailto:fel...@in...] 
Sent: 02 May 2011 13:22
To: dot...@li...
Subject: [dotNetRDF-Support] Bug

 

Hi,

 

I was seeing this class IndexedTripleCollection and this method:

 

private void UnIndex(Triple t)

        {

            this._subjIndex.Remove(t.Subject, t);

            this._predIndex.Remove(t.Predicate, t);

            this._objIndex.Add(t.Object, t);

 

The last line is correct?

 

 

Thanks

[dotNetRDF-Support] Bug

[Felipe G. S. <fel...@in...>]

Hi,

I was seeing this class IndexedTripleCollection and this method:

private void UnIndex(Triple t)
        {
            this._subjIndex.Remove(t.Subject, t);
            this._predIndex.Remove(t.Predicate, t);
            this._objIndex.Add(t.Object, t);

The last line is correct?


Thanks