Menu
▾
▴
dotnetrdf-develop — Developer Discussion and Feature Request
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(11) |
Mar
(17) |
Apr
(12) |
May
(2) |
Jun
(20) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
|
Jul
(12) |
Aug
(4) |
Sep
(5) |
Oct
(1) |
Nov
(38) |
Dec
(27) |
| 2012 |
Jan
(46) |
Feb
(182) |
Mar
(83) |
Apr
(22) |
May
(68) |
Jun
(47) |
Jul
(135) |
Aug
(84) |
Sep
(57) |
Oct
(45) |
Nov
(27) |
Dec
(61) |
| 2013 |
Jan
(59) |
Feb
(78) |
Mar
(66) |
Apr
(107) |
May
(27) |
Jun
(56) |
Jul
(53) |
Aug
(3) |
Sep
(19) |
Oct
(41) |
Nov
(44) |
Dec
(54) |
| 2014 |
Jan
(49) |
Feb
(72) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(27) |
Jul
(45) |
Aug
(12) |
Sep
(3) |
Oct
(8) |
Nov
(27) |
Dec
(16) |
| 2015 |
Jan
(3) |
Feb
(20) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(16) |
May
(9) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tr...@do...> - 2014-02-27 16:51:17
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NTriples</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-02-27 04:49 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Parsing support has been added with all test cases passing</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-02-27 16:34:32
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NTriples</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Progress changed from "0 %" to "50 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <dot...@li...> - 2014-02-27 16:32:26
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: 24 new changesets (Bitbucket) 2. commit/dotnetrdf: 7 new changesets (Bitbucket) 3. commit/dotnetrdf: 4 new changesets (Bitbucket) 4. commit/dotnetrdf: rvesse: Align .wixproject compiler options for Release config with Debug config (TOOLS-360) (Bitbucket) 5. commit/dotnetrdf: rvesse: Fix a couple of regressions introduced by SPIN work merge (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) 7. commit/dotnetrdf: 10 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Thu, 20 Feb 2014 17:09:01 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 24 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 24 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3a08d9c72a95/ Changeset: 3a08d9c72a95 User: magicmoux Date: 2013-07-01 15:57:19 Summary: Added a Virtual Count Property to queries and multiset to return nulber of results it would return without any limit clause Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4dea4644433d/ Changeset: 4dea4644433d User: magicmoux Date: 2013-07-04 21:25:28 Summary: Reassert separation between the native TripleStore and Graphs implementations Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/212df3cbdeac/ Changeset: 212df3cbdeac User: magicmoux Date: 2013-07-04 21:32:25 Summary: Reassert separation between the native TripleStore and Graphs implementations Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8aa166dd9bfe/ Changeset: 8aa166dd9bfe User: magicmoux Date: 2013-07-06 00:14:50 Summary: Corrected 2 more incorrect method indirection missing the graphUris filter parameter Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/09497f481b7c/ Changeset: 09497f481b7c User: magicmoux Date: 2013-07-06 00:18:11 Summary: Merged dotnetrdf/dotnetrdf into default Affected #: 53 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ba1ebfcaa920/ Changeset: ba1ebfcaa920 User: magicmoux Date: 2013-07-09 23:08:48 Summary: Merged dotnetrdf/dotnetrdf into default Affected #: 42 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/df7c582924e3/ Changeset: df7c582924e3 User: magicmoux Date: 2013-07-12 11:49:43 Summary: Merged dotnetrdf/dotnetrdf into default Affected #: 11 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f8746757aa2b/ Changeset: f8746757aa2b User: magicmoux Date: 2013-07-16 21:59:34 Summary: Merged dotnetrdf/dotnetrdf into default Affected #: 43 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b705907284d8/ Changeset: b705907284d8 User: magicmoux Date: 2013-08-12 07:55:58 Summary: Merged dotnetrdf/dotnetrdf into default Affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a16c602873c5/ Changeset: a16c602873c5 User: magicmoux Date: 2013-09-16 10:32:06 Summary: Merged dotnetrdf/dotnetrdf into default Affected #: 173 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/de7486f7a28c/ Changeset: de7486f7a28c User: magicmoux Date: 2013-09-18 08:03:23 Summary: Merged dotnetrdf/dotnetrdf into default Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/256686f522fb/ Changeset: 256686f522fb User: magicmoux Date: 2013-10-04 08:15:46 Summary: Merged dotnetrdf/dotnetrdf into default Affected #: 24 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cf87929933f5/ Changeset: cf87929933f5 User: magicmoux Date: 2013-10-05 10:56:43 Summary: Update to the latest SPIN SPARQL Syntax version Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c4de63104d29/ Changeset: c4de63104d29 User: magicmoux Date: 2014-01-16 11:33:05 Summary: Forced the copy of the nodes to the graph while waiting for v2 Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3043a3d4be94/ Changeset: 3043a3d4be94 User: magicmoux Date: 2014-01-16 11:35:21 Summary: Changed the virtualCount handling Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d96e9bc1c43b/ Changeset: d96e9bc1c43b User: magicmoux Date: 2014-01-16 11:36:22 Summary: Added RdfsResource definition Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c9004b72d92d/ Changeset: c9004b72d92d User: magicmoux Date: 2014-01-16 12:07:58 Summary: A first (if still skecthy and not functional) implementation of SPIN for dotNetRDF. It is based and evolves from the SPIN java implementation for Jena. The goal of this implementation is to provide SPIN capabilities over any SPIN-unaware storage engine while relying as much as possible on the storage engine SPARQL processing power. A special implementation of the ISparqlDataset interface is provided so clients may still work with the original dataset whitout being polluted by pending updates that should be first checked aginst the dataset's SPIN configuration before being flushed. The SpinWrappedDataset will wrap queries and updates through a SpinProcessor class that rewrites SPIN-interpreted SPARQL command patterns at runtime depending on the underlying dataset state (ie. dataset changes, pending graphs updates...) and its configuration (magic properties...) a first example of this can be found in the current org.topbraid.spin.model.impl.NamedGraphImpl class. The current commit addresses mainly the SpinWrappedDataset implementation and its runtime features. Real SPIN processing is not yet supported with this version and should come next but SPIN constraints checking was already tested in a first prototype. Affected #: 232 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fccb6903899e/ Changeset: fccb6903899e User: magicmoux Date: 2014-01-16 12:18:55 Summary: Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e2efe52dcef2/ Changeset: e2efe52dcef2 User: magicmoux Date: 2014-01-16 12:23:45 Summary: File conflict correction Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ce53f0328d96/ Changeset: ce53f0328d96 User: magicmoux Date: 2014-01-16 12:39:36 Summary: File conflict correction Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/39d104c5fb43/ Changeset: 39d104c5fb43 User: magicmoux Date: 2014-01-17 10:24:43 Summary: Refactored RDF Dataset management on AddGraph and RemoveGraph calls Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d585c79676cc/ Changeset: d585c79676cc User: magicmoux Date: 2014-01-17 13:38:30 Summary: Renamed missed vocabulary Nodes to conform to the Class... Property... naming chart Implemented SpinWrappedDataset.Flush and .Discard methods Affected #: 27 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0813b7e97d01/ Changeset: 0813b7e97d01 User: magicmoux Date: 2014-01-29 09:27:05 Summary: Implemented the IEqualityComparer<Triple> interface on class BaseTripleComparer Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6a1ba3b1c080/ Changeset: 6a1ba3b1c080 User: magicmoux Date: 2014-01-31 14:55:30 Summary: Massive refactoring for simplification and consistency Cleanup before pullrequest Affected #: 262 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Fri, 21 Feb 2014 12:58:08 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 7 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 7 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8d99815f2a71/ Changeset: 8d99815f2a71 Branch: 1.9 User: rvesse Date: 2014-02-21 12:35:49 Summary: Merge latest changes from default onto 1.9 branch Affected #: 228 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a2a03079e77b/ Changeset: a2a03079e77b Branch: 1.9 User: rvesse Date: 2014-02-21 12:40:59 Summary: Manually port CORE-401 fix onto 1.9 branch Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d82cab7f50c2/ Changeset: d82cab7f50c2 Branch: 1.9 User: rvesse Date: 2014-02-21 12:59:17 Summary: Implicitly type literals when RDF 1.1 mode is enabled (CORE-329) Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3e9f3c6fd15d/ Changeset: 3e9f3c6fd15d Branch: 1.9 User: rvesse Date: 2014-02-21 13:14:52 Summary: Clean up LiteralNode constructors to fully implement RDF 1.1 implicit typing Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b4429a94bb29/ Changeset: b4429a94bb29 Branch: 1.9 User: rvesse Date: 2014-02-21 13:22:31 Summary: Start adding multiple target .Net profiles for IO.Core library Affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6835d127f57b/ Changeset: 6835d127f57b Branch: 1.9 User: rvesse Date: 2014-02-21 13:45:15 Summary: Work towards getting the IO.Html library building Affected #: 25 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d546aa83219d/ Changeset: d546aa83219d Branch: 1.9 User: rvesse Date: 2014-02-21 13:56:24 Summary: Work towards getting the IO.Html library building Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Fri, 21 Feb 2014 16:16:26 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 4 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a44a648b3384/ Changeset: a44a648b3384 Branch: 1.9 User: rvesse Date: 2014-02-21 16:23:53 Summary: Work on fleshing out 2.0 module structure (CORE-315) Affected #: 20 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6cd2f25bf5bf/ Changeset: 6cd2f25bf5bf Branch: 1.9 User: rvesse Date: 2014-02-21 16:36:52 Summary: Work on fleshing out 2.0 module structure (CORE-315) Affected #: 149 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0cf92aa754c8/ Changeset: 0cf92aa754c8 Branch: 1.9 User: rvesse Date: 2014-02-21 16:57:41 Summary: Continuing fleshing out 2.0 module structure (CORE-315) Affected #: 31 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6898e37d4030/ Changeset: 6898e37d4030 Branch: 1.9 User: rvesse Date: 2014-02-21 17:16:07 Summary: Mostly fix up Configuration Core (CORE-315) Affected #: 17 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Mon, 24 Feb 2014 14:36:46 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Align .wixproject compiler options for Release config with Debug config (TOOLS-360) To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9efb6f9664d1/ Changeset: 9efb6f9664d1 User: rvesse Date: 2014-02-24 15:36:22 Summary: Align .wixproject compiler options for Release config with Debug config (TOOLS-360) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 5 Date: Tue, 25 Feb 2014 10:02:26 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Fix a couple of regressions introduced by SPIN work merge To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c93c901b40dc/ Changeset: c93c901b40dc User: rvesse Date: 2014-02-25 11:02:03 Summary: Fix a couple of regressions introduced by SPIN work merge Affected #: 5 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Thu, 27 Feb 2014 15:31:28 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/19a2f39281b7/ Changeset: 19a2f39281b7 Branch: ntuples11 User: rvesse Date: 2014-02-27 16:14:57 Summary: Add official test suite for NTriples 1.1 (CORE-355) Affected #: 72 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/aa49f1286118/ Changeset: aa49f1286118 Branch: ntuples11 User: rvesse Date: 2014-02-27 16:28:12 Summary: Infrastructure to support configurable syntax modes for NTriples (CORE-355) Affected #: 13 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Thu, 27 Feb 2014 16:32:17 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 10 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 10 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/87cb376d947e/ Changeset: 87cb376d947e Branch: ntuples11 User: rvesse Date: 2014-02-27 16:44:35 Summary: Start working to fix failing NTriples 1.1 test cases (CORE-355) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2515c721f58e/ Changeset: 2515c721f58e Branch: ntuples11 User: rvesse Date: 2014-02-27 16:51:34 Summary: Open files differently depending on which syntax we are using (CORE-355) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/044384358dd8/ Changeset: 044384358dd8 Branch: ntuples11 User: rvesse Date: 2014-02-27 16:55:15 Summary: Fix for one of the NTriples 1.1 test failures, only 1 failure remaining (CORE-355) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8f69c3ae87f1/ Changeset: 8f69c3ae87f1 Branch: ntuples11 User: rvesse Date: 2014-02-27 16:57:02 Summary: Fix the other remaining NTriples 1.1 test failure (CORE-355) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9e93bf5978cf/ Changeset: 9e93bf5978cf Branch: ntuples11 User: rvesse Date: 2014-02-27 17:03:40 Summary: Add test cases for RDF NQuads 1.1 (CORE-356) Affected #: 90 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/669e0cf2bd68/ Changeset: 669e0cf2bd68 Branch: ntuples11 User: rvesse Date: 2014-02-27 17:07:01 Summary: Unit test to run RDF NQuads 1.1 test cases (CORE-356) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9a275bf546de/ Changeset: 9a275bf546de Branch: ntuples11 User: rvesse Date: 2014-02-27 17:20:45 Summary: Work towards getting more of the RDF 1.1 NQuads tests passing (CORE-356) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7f87272c3af2/ Changeset: 7f87272c3af2 Branch: ntuples11 User: rvesse Date: 2014-02-27 17:25:26 Summary: Parse the RDF 1.1 NQuads manifest correctly (CORE-356) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4d3fded780ed/ Changeset: 4d3fded780ed Branch: ntuples11 User: rvesse Date: 2014-02-27 17:28:18 Summary: Fix remaining RDF 1.1 NQuads test failures (CORE-356) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a6c9df983815/ Changeset: a6c9df983815 Branch: ntuples11 User: rvesse Date: 2014-02-27 17:31:51 Summary: Open files in correct encodings and check for appropriate encodings dependent on NQuads syntax mode (CORE-356) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 16, Issue 3 ************************************************ |
|
From: <tr...@do...> - 2014-02-27 15:15:41
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NTriples</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Priority changed from "Low" to "Normal"
</li>
<li>Status changed from "Planned" to "In Progress"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-02-25 10:45:36
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NQuads</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Milestone changed from "Unscheduled" to "1.0.4"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-02-25 10:45:03
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NTriples</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-02-25 10:14 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The W3C ended up turning this into a recommendation so we should definitely add support for it - http://www.w3.org/TR/n-triples/</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-02-25 10:44:38
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NTriples</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Milestone changed from "Unscheduled" to "1.0.4"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Rob V. <rv...@do...> - 2014-02-25 10:23:14
|
Tom Yes the original NTriples and NQuads specifications only allow ASCII, this was by design to make those formats canonical (since with UTF-8 you can potentially encode complex characters in multiple ways) and facilitate reliable data exchange across systems that didn't necessarily support non-ASCII data. Btw the reader only enforces ASCII encoding if you pass a filename (I.e. when it deals with opening the file stream), if you pass in a pre-opened StreamReader that is in a different encoding (I.e. UTF-8) it may still parse successfully though exact behaviour is hard to know in advance. It will issue a warning about incorrect encoding (via the Warning event) and it may error out on some native UTF-8 data since the tokeniser is not written to expect native UTF-8. The RDF 1.1 working group have published proposed recommendations which standardise NQuads & NTriples and part of the standardization is to change the encoding to UTF-8 but I haven't had chance to update dotNetRDF to support the updated specs yet. Since this is a breaking change to spec and current API behaviour the existing tokenizers and parsers would need to be modified so that they can support either the new/old specification. An approach similar to how we updated Turtle support where we implement the new specifications and the parsers default to the new spec mode and the writers implement the new spec but default to producing the old spec as output would be ideal. This is Postel's law in action if you're wondering why this is done. There are issues filed for these upgrades but I haven't had time to implement them yet, I was considering trying to get these into the next release anyway and I have some time to start on this at the end of the week unless you want to attempt this yourself. See CORE-356 (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356) for NQuads and CORE-355 (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=355) for NTriples which include links to the updated specifications, see the comments for the most up to date spec links. Hope this clarifies things, Cheers, Rob On 25/02/2014 10:06, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Rob > >A colleague of mine has just discovered that the NQuadsParser reads >file with ASCII encoding while all other use UTF-8. > >I understand that this is as described in the specification but why is >that exactly? > >And what do you think about adding a option to the parsers so that >alternative encodings can be used for reading dataset files? > >Cheers, >Tom > >-------------------------------------------------------------------------- >---- >Flow-based real-time traffic analytics software. Cisco certified tool. >Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >Customize your own dashboards, set traffic alerts and generate reports. >Network behavioral analysis & security monitoring. All-in-one tool. >http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >rk >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <tr...@do...> - 2014-02-25 10:13:54
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add support for new variant of NQuads</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-02-25 10:12 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The note ended up getting turned into a recommendation - http://www.w3.org/TR/n-quads/</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=356</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Tomasz P. <tom...@gm...> - 2014-02-25 10:07:00
|
Hi Rob A colleague of mine has just discovered that the NQuadsParser reads file with ASCII encoding while all other use UTF-8. I understand that this is as described in the specification but why is that exactly? And what do you think about adding a option to the parsers so that alternative encodings can be used for reading dataset files? Cheers, Tom |
|
From: Rob V. <rv...@do...> - 2014-02-25 09:29:46
|
Yes I had great fun figuring out which SDK to install myself locally Thanks for sorting this out Cheers, Rob On 24/02/2014 20:53, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Weird Microsoft. It turns out that this bootstrapper is only installed >with Visual Studio and not SDK. Which I totally don't understand. Why >is it necessary to install VS on a build server? I simply copied the >files as suggested na SO. > >Anyway, it's working now :) > >Regards, >Tom > >On Mon, Feb 24, 2014 at 4:58 PM, Rob Vesse <rv...@do...> wrote: >> I went ahead and fixed the compiler options property but I now get the >> following error: >> >> >>C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstall >>er.wixproj(79, >> 5): error MSB3147: Could not find required file 'setup.bin' in >>'C:\Program >> Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Engine' >> >> Looks like we also need the Windows 7 SDK installed. >> >> Cheers, >> >> Rob >> >> From: Kal Ahmed <ka...@ne...> >> Reply-To: dotNetRDF Developer Discussion and Feature Request >> <dot...@li...> >> Date: Saturday, 22 February 2014 21:03 >> To: dotNetRDF Developer Discussion and Feature Request >> <dot...@li...> >> Subject: Re: [dotNetRDF-Develop] WiX Toolset for CI Server? >> >> It probably means that there is a missing option in the >> CompilerAdditionalOptions property in the .wixproj file (-d >> InfoFiles=..\SomeDirectory). It looks like it is missing an option to >>define >> the path to the directory where some files to be included in the >>installer >> can be found. I'm not at a machine to check right now, but hopefully >>that >> gives you a bit of a clue to track things down. You may find that >> CompilerAdditionalOptions is defined separately for both Debug and >>Release - >> check if there are differences between the two. FWIW with BrightstarDB, >>I >> ended up editing the .wixproj to move the definition of the property so >>that >> there is one definition for all configurations - makes it easier to >>change >> later. >> >> Cheers >> >> Kal >> >> >> On Sat, Feb 22, 2014 at 8:52 PM, Tomasz Pluskiewicz >> <tom...@gm...> wrote: >>> >>> Hi Rob, Kal >>> >>> I installed the WiX toolset and now the build failed with message as >>> follows. >>> >>> C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\Info.wxs(9, >>> 0): error CNDL0150: Undefined preprocessor variable '$(var.infoFiles)' >>> >>> Know what this means? >>> >>> Regards, >>> Tom >>> >>> On Fri, Feb 21, 2014 at 12:20 PM, Tomasz Pluskiewicz >>> <tom...@gm...> wrote: >>> > Hi Rob >>> > >>> > Shouldn't be a problem. I'll get it done later today. >>> > >>> > Tom >>> > >>> > On Fri, Feb 21, 2014 at 12:00 PM, Rob Vesse <rv...@do...> >>> > wrote: >>> >> Tom >>> >> >>> >> I've noticed that since I merged TOOLS-360 which was Kal's work to >>>move >>> >> to >>> >> using a WiX based installer that the builds are now failing on the >>> >> TeamCity >>> >> server with an error like the following: >>> >> >>> >> [18:12:42][Build\ToolkitInstaller\ToolkitInstaller.wixproj] >>> >> >>> >> >>>C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstal >>>ler.wixproj(41, >>> >> 3): error MSB4019: The imported project "C:\Program Files >>> >> (x86)\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm >>> >> that >>> >> the path in the <Import> declaration is correct, and that the file >>> >> exists on >>> >> disk. >>> >> >>> >> This looks like we just need the WiX Toolset installed on the >>>server, >>> >> any >>> >> chance you could do that? >>> >> >>> >> Cheers, >>> >> >>> >> Rob >>> >> >>> >> >>> >> >>>------------------------------------------------------------------------ >>>------ >>> >> Managing the Performance of Cloud-Based Applications >>> >> Take advantage of what the Cloud has to offer - Avoid Common >>>Pitfalls. >>> >> Read the Whitepaper. >>> >> >>> >> >>>http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.cl >>>ktrk >>> >> _______________________________________________ >>> >> dotNetRDF-develop mailing list >>> >> dot...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >>> >>> >>> >>>------------------------------------------------------------------------ >>>------ >>> Managing the Performance of Cloud-Based Applications >>> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >>> Read the Whitepaper. >>> >>> >>>http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.cl >>>ktrk >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> -- >> Kal Ahmed >> Director, Networked Planet Limited >> e: kal...@ne... >> w: www.networkedplanet.com >> >>------------------------------------------------------------------------- >>----- >> Managing the Performance of Cloud-Based Applications Take advantage of >>what >> the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. >> >>http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clk >>trk_______________________________________________ >> dotNetRDF-develop mailing list dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >>------------------------------------------------------------------------- >>----- >> Flow-based real-time traffic analytics software. Cisco certified tool. >> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >> Customize your own dashboards, set traffic alerts and generate reports. >> Network behavioral analysis & security monitoring. All-in-one tool. >> >>http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clk >>trk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Flow-based real-time traffic analytics software. Cisco certified tool. >Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer >Customize your own dashboards, set traffic alerts and generate reports. >Network behavioral analysis & security monitoring. All-in-one tool. >http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clkt >rk >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2014-02-24 20:54:16
|
Weird Microsoft. It turns out that this bootstrapper is only installed with Visual Studio and not SDK. Which I totally don't understand. Why is it necessary to install VS on a build server? I simply copied the files as suggested na SO. Anyway, it's working now :) Regards, Tom On Mon, Feb 24, 2014 at 4:58 PM, Rob Vesse <rv...@do...> wrote: > I went ahead and fixed the compiler options property but I now get the > following error: > > C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstaller.wixproj(79, > 5): error MSB3147: Could not find required file 'setup.bin' in 'C:\Program > Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Engine' > > Looks like we also need the Windows 7 SDK installed. > > Cheers, > > Rob > > From: Kal Ahmed <ka...@ne...> > Reply-To: dotNetRDF Developer Discussion and Feature Request > <dot...@li...> > Date: Saturday, 22 February 2014 21:03 > To: dotNetRDF Developer Discussion and Feature Request > <dot...@li...> > Subject: Re: [dotNetRDF-Develop] WiX Toolset for CI Server? > > It probably means that there is a missing option in the > CompilerAdditionalOptions property in the .wixproj file (-d > InfoFiles=..\SomeDirectory). It looks like it is missing an option to define > the path to the directory where some files to be included in the installer > can be found. I'm not at a machine to check right now, but hopefully that > gives you a bit of a clue to track things down. You may find that > CompilerAdditionalOptions is defined separately for both Debug and Release - > check if there are differences between the two. FWIW with BrightstarDB, I > ended up editing the .wixproj to move the definition of the property so that > there is one definition for all configurations - makes it easier to change > later. > > Cheers > > Kal > > > On Sat, Feb 22, 2014 at 8:52 PM, Tomasz Pluskiewicz > <tom...@gm...> wrote: >> >> Hi Rob, Kal >> >> I installed the WiX toolset and now the build failed with message as >> follows. >> >> C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\Info.wxs(9, >> 0): error CNDL0150: Undefined preprocessor variable '$(var.infoFiles)' >> >> Know what this means? >> >> Regards, >> Tom >> >> On Fri, Feb 21, 2014 at 12:20 PM, Tomasz Pluskiewicz >> <tom...@gm...> wrote: >> > Hi Rob >> > >> > Shouldn't be a problem. I'll get it done later today. >> > >> > Tom >> > >> > On Fri, Feb 21, 2014 at 12:00 PM, Rob Vesse <rv...@do...> >> > wrote: >> >> Tom >> >> >> >> I've noticed that since I merged TOOLS-360 which was Kal's work to move >> >> to >> >> using a WiX based installer that the builds are now failing on the >> >> TeamCity >> >> server with an error like the following: >> >> >> >> [18:12:42][Build\ToolkitInstaller\ToolkitInstaller.wixproj] >> >> >> >> C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstaller.wixproj(41, >> >> 3): error MSB4019: The imported project "C:\Program Files >> >> (x86)\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm >> >> that >> >> the path in the <Import> declaration is correct, and that the file >> >> exists on >> >> disk. >> >> >> >> This looks like we just need the WiX Toolset installed on the server, >> >> any >> >> chance you could do that? >> >> >> >> Cheers, >> >> >> >> Rob >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Managing the Performance of Cloud-Based Applications >> >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >> >> Read the Whitepaper. >> >> >> >> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk >> >> _______________________________________________ >> >> dotNetRDF-develop mailing list >> >> dot...@li... >> >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> ------------------------------------------------------------------------------ >> Managing the Performance of Cloud-Based Applications >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >> Read the Whitepaper. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications Take advantage of what > the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk_______________________________________________ > dotNetRDF-develop mailing list dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2014-02-24 15:59:59
|
I went ahead and fixed the compiler options property but I now get the following error: C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstaller. wixproj(79, 5): error MSB3147: Could not find required file 'setup.bin' in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Engine' Looks like we also need the Windows 7 SDK installed. Cheers, Rob From: Kal Ahmed <ka...@ne...> Reply-To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Date: Saturday, 22 February 2014 21:03 To: dotNetRDF Developer Discussion and Feature Request <dot...@li...> Subject: Re: [dotNetRDF-Develop] WiX Toolset for CI Server? > It probably means that there is a missing option in the > CompilerAdditionalOptions property in the .wixproj file (-d > InfoFiles=..\SomeDirectory). It looks like it is missing an option to define > the path to the directory where some files to be included in the installer can > be found. I'm not at a machine to check right now, but hopefully that gives > you a bit of a clue to track things down. You may find that > CompilerAdditionalOptions is defined separately for both Debug and Release - > check if there are differences between the two. FWIW with BrightstarDB, I > ended up editing the .wixproj to move the definition of the property so that > there is one definition for all configurations - makes it easier to change > later. > > Cheers > > Kal > > > On Sat, Feb 22, 2014 at 8:52 PM, Tomasz Pluskiewicz > <tom...@gm...> wrote: >> Hi Rob, Kal >> >> I installed the WiX toolset and now the build failed with message as follows. >> >> C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\Info.wxs(9, >> 0): error CNDL0150: Undefined preprocessor variable '$(var.infoFiles)' >> >> Know what this means? >> >> Regards, >> Tom >> >> On Fri, Feb 21, 2014 at 12:20 PM, Tomasz Pluskiewicz >> <tom...@gm...> wrote: >>> > Hi Rob >>> > >>> > Shouldn't be a problem. I'll get it done later today. >>> > >>> > Tom >>> > >>> > On Fri, Feb 21, 2014 at 12:00 PM, Rob Vesse <rv...@do...> wrote: >>>> >> Tom >>>> >> >>>> >> I've noticed that since I merged TOOLS-360 which was Kal's work to move to >>>> >> using a WiX based installer that the builds are now failing on the >>>> TeamCity >>>> >> server with an error like the following: >>>> >> >>>> >> [18:12:42][Build\ToolkitInstaller\ToolkitInstaller.wixproj] >>>> >> >>>> C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstaller >>>> .wixproj(41, >>>> >> 3): error MSB4019: The imported project "C:\Program Files >>>> >> (x86)\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm >>>> that >>>> >> the path in the <Import> declaration is correct, and that the file >>>> exists on >>>> >> disk. >>>> >> >>>> >> This looks like we just need the WiX Toolset installed on the server, >>>> any >>>> >> chance you could do that? >>>> >> >>>> >> Cheers, >>>> >> >>>> >> Rob >>>> >> >>>> >> >>>> --------------------------------------------------------------------------->>>> --- >>>> >> Managing the Performance of Cloud-Based Applications >>>> >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >>>> >> Read the Whitepaper. >>>> >> >>>> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk >>>> >> _______________________________________________ >>>> >> dotNetRDF-develop mailing list >>>> >> dot...@li... >>>> >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >> >> >> ----------------------------------------------------------------------------->> - >> Managing the Performance of Cloud-Based Applications >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >> Read the Whitepaper. >> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com <http://www.networkedplanet.com> > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications Take advantage of what > the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk__ > _____________________________________________ dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Khalil A. <ka...@ne...> - 2014-02-22 21:03:45
|
It probably means that there is a missing option in the CompilerAdditionalOptions property in the .wixproj file (-d InfoFiles=..\SomeDirectory). It looks like it is missing an option to define the path to the directory where some files to be included in the installer can be found. I'm not at a machine to check right now, but hopefully that gives you a bit of a clue to track things down. You may find that CompilerAdditionalOptions is defined separately for both Debug and Release - check if there are differences between the two. FWIW with BrightstarDB, I ended up editing the .wixproj to move the definition of the property so that there is one definition for all configurations - makes it easier to change later. Cheers Kal On Sat, Feb 22, 2014 at 8:52 PM, Tomasz Pluskiewicz < tom...@gm...> wrote: > Hi Rob, Kal > > I installed the WiX toolset and now the build failed with message as > follows. > > C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\Info.wxs(9, > 0): error CNDL0150: Undefined preprocessor variable '$(var.infoFiles)' > > Know what this means? > > Regards, > Tom > > On Fri, Feb 21, 2014 at 12:20 PM, Tomasz Pluskiewicz > <tom...@gm...> wrote: > > Hi Rob > > > > Shouldn't be a problem. I'll get it done later today. > > > > Tom > > > > On Fri, Feb 21, 2014 at 12:00 PM, Rob Vesse <rv...@do...> > wrote: > >> Tom > >> > >> I've noticed that since I merged TOOLS-360 which was Kal's work to move > to > >> using a WiX based installer that the builds are now failing on the > TeamCity > >> server with an error like the following: > >> > >> [18:12:42][Build\ToolkitInstaller\ToolkitInstaller.wixproj] > >> > C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstaller.wixproj(41, > >> 3): error MSB4019: The imported project "C:\Program Files > >> (x86)\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm > that > >> the path in the <Import> declaration is correct, and that the file > exists on > >> disk. > >> > >> This looks like we just need the WiX Toolset installed on the server, > any > >> chance you could do that? > >> > >> Cheers, > >> > >> Rob > >> > >> > ------------------------------------------------------------------------------ > >> Managing the Performance of Cloud-Based Applications > >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > >> Read the Whitepaper. > >> > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > >> _______________________________________________ > >> dotNetRDF-develop mailing list > >> dot...@li... > >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >> > > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > -- Kal Ahmed Director, Networked Planet Limited e: kal...@ne... w: www.networkedplanet.com |
|
From: Tomasz P. <tom...@gm...> - 2014-02-22 20:53:14
|
Hi Rob, Kal I installed the WiX toolset and now the build failed with message as follows. C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\Info.wxs(9, 0): error CNDL0150: Undefined preprocessor variable '$(var.infoFiles)' Know what this means? Regards, Tom On Fri, Feb 21, 2014 at 12:20 PM, Tomasz Pluskiewicz <tom...@gm...> wrote: > Hi Rob > > Shouldn't be a problem. I'll get it done later today. > > Tom > > On Fri, Feb 21, 2014 at 12:00 PM, Rob Vesse <rv...@do...> wrote: >> Tom >> >> I've noticed that since I merged TOOLS-360 which was Kal's work to move to >> using a WiX based installer that the builds are now failing on the TeamCity >> server with an error like the following: >> >> [18:12:42][Build\ToolkitInstaller\ToolkitInstaller.wixproj] >> C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstaller.wixproj(41, >> 3): error MSB4019: The imported project "C:\Program Files >> (x86)\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm that >> the path in the <Import> declaration is correct, and that the file exists on >> disk. >> >> This looks like we just need the WiX Toolset installed on the server, any >> chance you could do that? >> >> Cheers, >> >> Rob >> >> ------------------------------------------------------------------------------ >> Managing the Performance of Cloud-Based Applications >> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. >> Read the Whitepaper. >> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> |
|
From: Tomasz P. <tom...@gm...> - 2014-02-21 11:21:22
|
Hi Rob Shouldn't be a problem. I'll get it done later today. Tom On Fri, Feb 21, 2014 at 12:00 PM, Rob Vesse <rv...@do...> wrote: > Tom > > I've noticed that since I merged TOOLS-360 which was Kal's work to move to > using a WiX based installer that the builds are now failing on the TeamCity > server with an error like the following: > > [18:12:42][Build\ToolkitInstaller\ToolkitInstaller.wixproj] > C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstaller.wixproj(41, > 3): error MSB4019: The imported project "C:\Program Files > (x86)\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm that > the path in the <Import> declaration is correct, and that the file exists on > disk. > > This looks like we just need the WiX Toolset installed on the server, any > chance you could do that? > > Cheers, > > Rob > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2014-02-21 11:01:18
|
Tom I've noticed that since I merged TOOLS-360 which was Kal's work to move to using a WiX based installer that the builds are now failing on the TeamCity server with an error like the following: [18:12:42][Build\ToolkitInstaller\ToolkitInstaller.wixproj] C:\BuildAgent\work\f65accef49585896\Build\ToolkitInstaller\ToolkitInstaller. wixproj(41, 3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. This looks like we just need the WiX Toolset installed on the server, any chance you could do that? Cheers, Rob |
|
From: <tr...@do...> - 2014-02-20 17:02:34
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Literal with uppercase sub language tag can not be matched properly.</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-02-20 05:01 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This has been fixed and will be included in the next release. The library now consistently normalizes all language tags to lower case internally. This means your first two queries will now behave correctly.</p>
<p>
Note that your last example query will now fail because language tags are now all lower case internally so in your example lang(?o) would always return "en-us" regardless of whether the data started off as "en-US" or not</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=401" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=401</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-02-20 17:00:30
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Literal with uppercase sub language tag can not be matched properly.</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "0 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=401" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=401</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <dot...@li...> - 2014-02-20 16:57:11
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: 2 new changesets (Bitbucket) 2. commit/dotnetrdf: 2 new changesets (Bitbucket) 3. commit/dotnetrdf: rvesse: Add TODO for customizing dialogues (TOOLS-360) (Bitbucket) 4. commit/dotnetrdf: 2 new changesets (Bitbucket) 5. commit/dotnetrdf: 2 new changesets (Bitbucket) 6. commit/dotnetrdf: rvesse: Fix overly greedly tokenization when tokenizing prefix declarations in Turtle, N3 and SPARQL (Bitbucket) 7. commit/dotnetrdf: rvesse: Update Change Log (Bitbucket) 8. commit/dotnetrdf: 5 new changesets (Bitbucket) 9. commit/dotnetrdf: 6 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Thu, 13 Feb 2014 11:40:49 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2b56b40dd4cd/ Changeset: 2b56b40dd4cd Branch: TOOLS-360 User: rvesse Date: 2014-02-13 12:14:19 Summary: Merge latest changes from default Affected #: 297 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/72de20d9f1a5/ Changeset: 72de20d9f1a5 Branch: TOOLS-360 User: rvesse Date: 2014-02-13 12:38:21 Summary: Hard code SDK path to workaround build issue (TOOLS-360) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Thu, 13 Feb 2014 12:50:48 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d3c64c8d0601/ Changeset: d3c64c8d0601 Branch: TOOLS-360 User: rvesse Date: 2014-02-13 13:25:59 Summary: Work towards making components indepdently installable (TOOLS-360) Affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ae7ea61d9cfd/ Changeset: ae7ea61d9cfd Branch: TOOLS-360 User: rvesse Date: 2014-02-13 13:50:33 Summary: Work towards making individual tools installable (TOOLS-360) Affected #: 6 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Thu, 13 Feb 2014 13:01:14 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Add TODO for customizing dialogues (TOOLS-360) To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3187f9f47d47/ Changeset: 3187f9f47d47 Branch: TOOLS-360 User: rvesse Date: 2014-02-13 14:00:49 Summary: Add TODO for customizing dialogues (TOOLS-360) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Fri, 14 Feb 2014 10:11:04 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2c36fe748ad0/ Changeset: 2c36fe748ad0 Branch: TOOLS-360 User: rvesse Date: 2014-02-14 11:04:50 Summary: Get all features included in Installer (TOOLS-360) Affected #: 13 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/af7aba4049f1/ Changeset: af7aba4049f1 Branch: TOOLS-360 User: rvesse Date: 2014-02-14 11:10:16 Summary: Finish features Affected #: 15 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 5 Date: Fri, 14 Feb 2014 10:37:59 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/403a932043ae/ Changeset: 403a932043ae Branch: TOOLS-360 User: rvesse Date: 2014-02-14 11:37:06 Summary: Build new installer with NAnt (TOOLS-360) Affected #: 11 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/95a2f1cf0401/ Changeset: 95a2f1cf0401 User: rvesse Date: 2014-02-14 11:37:39 Summary: Merge TOOLS-360 installer refactoring into default Affected #: 18 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Fri, 14 Feb 2014 12:18:25 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Fix overly greedly tokenization when tokenizing prefix declarations in Turtle, N3 and SPARQL To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6ec85a44f67f/ Changeset: 6ec85a44f67f User: rvesse Date: 2014-02-14 13:18:08 Summary: Fix overly greedly tokenization when tokenizing prefix declarations in Turtle, N3 and SPARQL Affected #: 4 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Fri, 14 Feb 2014 12:19:16 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Update Change Log To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2c3453a976c9/ Changeset: 2c3453a976c9 User: rvesse Date: 2014-02-14 13:19:02 Summary: Update Change Log Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Thu, 20 Feb 2014 16:22:32 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 5 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 5 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b7248a2536bc/ Changeset: b7248a2536bc Branch: CORE-400 User: rvesse Date: 2014-02-20 17:08:53 Summary: Add Timeout property to BaseHttpConnector so all HTTP based stores receive configurable timeout support (CORE-400) Affected #: 14 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d5193b302b76/ Changeset: d5193b302b76 Branch: CORE-400 User: rvesse Date: 2014-02-20 17:19:53 Summary: Verify that all HTTP based storage providers are calling the appropriate helper method that enforces the timeout, some minor refactoring (CORE-400) Affected #: 20 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/069cbd97e020/ Changeset: 069cbd97e020 Branch: CORE-400 User: rvesse Date: 2014-02-20 17:20:42 Summary: Fix Portable build Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ca8f279fa5b0/ Changeset: ca8f279fa5b0 Branch: CORE-400 User: rvesse Date: 2014-02-20 17:21:49 Summary: Close CORE-400 branch Affected #: 10 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c586944d2d83/ Changeset: c586944d2d83 User: rvesse Date: 2014-02-20 17:22:12 Summary: Merge CORE-400 improvements to default Affected #: 31 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 9 Date: Thu, 20 Feb 2014 16:57:01 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 6 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4a43dc042a00/ Changeset: 4a43dc042a00 Branch: CORE-401 User: rvesse Date: 2014-02-20 17:35:30 Summary: Add unit tests to demonstrate CORE-401 bug Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/deb31eb6a613/ Changeset: deb31eb6a613 Branch: CORE-401 User: rvesse Date: 2014-02-20 17:38:38 Summary: Improve CORE-401 test case Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/7e215a09d755/ Changeset: 7e215a09d755 Branch: CORE-401 User: rvesse Date: 2014-02-20 17:39:22 Summary: Normalize all language specifiers to lower case (CORE-401) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/46f3b0009e61/ Changeset: 46f3b0009e61 Branch: CORE-401 User: rvesse Date: 2014-02-20 17:50:46 Summary: Bunch more tests for CORE-401 based on SPARQL in bug report Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3b4c679c5e08/ Changeset: 3b4c679c5e08 Branch: CORE-401 User: rvesse Date: 2014-02-20 17:56:05 Summary: Note CORE-401 fix in Change Log Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2e5199086969/ Changeset: 2e5199086969 User: rvesse Date: 2014-02-20 17:56:43 Summary: Merge CORE-401 fixes to default Affected #: 5 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 16, Issue 2 ************************************************ |
|
From: <tr...@do...> - 2014-02-20 16:46:02
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Literal with uppercase sub language tag can not be matched properly.</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "New" to "In Progress"
</li>
<li>Milestone changed from "Unassigned" to "1.0.4"
</li>
<li>Assigned to changed from "Unassigned" to "Rob Vesse"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=401" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=401</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-02-20 15:53:53
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Timeouts for HTTP Storage Providers are not configurable</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Title changed from "Cannot increase query timeout more than default HttpWebRequest 100 seconds for SPARQL Update on Stardog" to "Timeouts for HTTP Storage Providers are not configurable"
</li>
<li>Priority changed from "Unassigned" to "High"
</li>
<li>Status changed from "Unassigned" to "In Progress"
</li>
<li>Milestone changed from "Unassigned" to "1.0.4"
</li>
<li>Assigned to changed from "Unassigned" to "Rob Vesse"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=400" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=400</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-02-20 15:50:54
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Cannot increase query timeout more than default HttpWebRequest 100 seconds for SPARQL Update on Stardog</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2014-02-20 03:50 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I don't believe we currently provide any mechanism for controlling the HTTP timeouts for Storage Providers. Options.QueryExecutionTimeout both refer specifically to in-memory execution though could be used as a default value for HTTP timeouts once added.</p>
<p>
This should be relatively easy to implement and I will get this into the next release</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=400" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=400</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2014-02-20 12:29:28
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Literal with uppercase sub language tag can not be matched properly.</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>i_liang_chen</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Core API</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
When using TripleStroe.LoadFromFile to import triples file, if it contains literal with uppercase sub language tag, a query cannot match the literal.</p>
<p>
The following case gets empty result.</p>
<p>
File:</p>
<p>
_:a <urn:p> <a href="mailto:"test"@en-US">"test"@en-US</a>.</p>
<p>
Sparql:</p>
<p>
select * where { ?s ?p <a href="mailto:"test"@en-US">"test"@en-US</a>. }</p>
<p>
or</p>
<p>
select * where { ?s ?p <a href="mailto:"test"@en-us">"test"@en-us</a>. }</p>
<p>
or</p>
<p>
select * where { ?s ?p ?o. filter (str(?o)="test"&&lang(?o)="en-us") }</p>
<p>
but following query can work properly.</p>
<p>
select * where { ?s ?p ?o. filter (str(?o)="test"&&lang(?o)="en-US") }</p>
<p>
</p>
<p>
If the triples are inserted by sparql update, the above queries can work properly.</p>
<p>
I guess the sparql engine normalizes the language tag to lowercase but imports way does not.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=401" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=401</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Miloš C. <cha...@ho...> - 2014-02-17 12:04:46
|
Hi, Thank you for your replies and your suggestions. I hope that it will be possible to implement the storage without changes in the dotnetrdf or r2rml libraries. I will start with a standalone library with nuget references to r2rml and dotnetrdf and I will see if it is sufficient till the final implementation. As soon as I will have some work done, I will notify you. Regards, Miloš -----Original Message----- From: plo...@gm... [mailto:plo...@gm...] On Behalf Of Tomasz Pluskiewicz Sent: Thursday, February 13, 2014 2:34 PM To: dotNetRDF Developer Discussion and Feature Request Cc: Miloš Chaloupka Subject: Re: [dotNetRDF-Develop] DotNetRDF Hi Miloš, Yes I did get your email! Thank you and sorry for late reply. I have been thinking long ago about using the R2RML mapping to translate SPARQL into SQL. Unfortunately there is always little time and more pressing issues and eventually I haven't even finished R2RML.net in 100%. However I will be happy to help with your project shall you desire to use the R2RML.net mapping as input and dotNetRDF as the query processor. As Rob said in his response, you could implement the existing interfaces to read through an input SQL query and transform it to SPARQL. There you will need the mappings. Most difficult is probably the actual algorithm for converting one query into another. Other than that of course you will need a way to process the SPARQL query. dotNetRDF parses it into a nice abstract model so you should be fine. Lastly you will eventually need a way to produce SQL queries for different DBMS flavours. On the mapping side you would have to make sure that R2RML.net exposes all the required mapping data. If you need any changes I encourage you to fork my repository and we'll try to adjust it to your needs. Regards, Tom PS There's also a blog posts which briefly discusses a way to do what you try to achive: http://antoniogarrote.wordpress.com/2011/01/10/translating-sparql-queries-into-sql-using-r2rml/ On Thu, Feb 13, 2014 at 12:09 PM, Rob Vesse <rv...@do...> wrote: > Hi Milos > > To be honest we've moved away from SQL backed storage because in the > past it hasn't proven that performant. However providing a R2RML > adaptor layer does make a lot more sense and provides a better > solution than what we've tried in the past (which was based on storing triples natively in a SQL database). > > I would suggest looking at implementing a IStorageProvider which also > implements IQueryableStorage if you are intending to support SPARQL. > Since this likely involves some sort of dependency upon Tom's existing > R2RML library then this would be best implemented as a separate > library in a similar way to the existing Data.Virtuoso library because > we want to mimize dependencies in the core library. I'd suggest > reading up on the Storage API > (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/UserGuide/Storage%20AP > I) if you haven't already and taking a look at the implementations of > existing IStorageProviders. > > Contribution wise I would suggest you create your own fork, work in > there and then submit pull request(s) as and when you have something > you thing is sufficiently stable for inclusion in the main project. > Please take a look at our Code Style guidelines > (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Code%20 > Style) > and Test Environment > (https://bitbucket.org/dotnetrdf/dotnetrdf/wiki/DeveloperGuide/Test%20 > Environment) documentation. Any substantial feature contribution like > this will need to be accompanied by appropriate tests which I > appreciate can be tricky for testing that requires on external > resources I.e. SQL servers but you can use the approach we use for > existing storage to provide developer configurable settings for test > setup and skip tests where the test system is unavailable. > > And of course if you have questions about anything then please ask on > the developer list which I've CC'd on this response, this is a > subscription based list which you will need to subscribe to via > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > Best Regards, > > Rob Vesse > > From: Miloš Chaloupka <cha...@ho...> > Date: Monday, 10 February 2014 09:18 > To: Rob Vesse <rv...@do...> > Subject: DotNetRDF > > Hi Rob, > > > > I have found you as an author of DotNetRDF so I hope I am contacting > the right person. I have already written to Tomasz Pluskiewicz, but > got no response yet, so I am not really sure, whether he even got the message. > > > > I am currently writing my master thesis "Querying RDF graphs stored in > a relational database using SPARQL and R2RML" and I am choosing how I > will write the implementation. I don't want to write a solution that > will end as an academic work with no chance of real use so I think, > that it would be nice to make it as a "part" of dotNetRDF. I want to > implement it as a store, that will be queryable using SPARQL according > to R2RML mapping. I can see that you have already listed several > libraries and that is in fact the only thing I want. Maybe you want to > ask why I am asking before I am starting the implementation, it is > because my supervisor wants to make the implementation as a part of > something bigger so I want to know whether it is possible. Are you > interested in such storage implementation? And if so, do you have any demands? > > > > Thank you for your reply, > > best regards, > > Miloš Chaloupka > > > ---------------------------------------------------------------------- > -------- > Android apps run on BlackBerry 10 > Introducing the new BlackBerry 10.2.1 Runtime for Android apps. > Now with support for Jelly Bean, Bluetooth, Mapview and more. > Get your Android app in front of a whole new audience. Start now. > http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg. > clktrk _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
48 messages has been excluded from this view by a project administrator.
