Menu
▾
▴
dotnetrdf-develop
|
From: Rob V. <rv...@do...> - 2012-11-09 19:07:37
|
Hey All Would anyone object if I went ahead and made the 0.8.0 release sometime next week? There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 compliance and general improvements to SPARQL implementation plus significant fixes and updates to the Query.FullText library. I had originally thought that we might get the Fluent Query API in this release but looking at what Tom's got so far (which is great btw) it's clearly a much bigger lift than I first thought. I'd rather push that to unscheduled and have it be merged in as and when Tom thinks it's ready rather than holding back a useful (and primarily bug fix) release. Any other thoughts/objections? Rob |
|
From: Tomasz P. <tom...@gm...> - 2012-11-11 17:53:53
|
I don't mind an earlier release. Regarding the Fluent API I think we could get it out in 8.1 or so. At this point maybe it will be good to define some kind of a road map internally. SPARQL has many features and it is possible to implement some in the first go and add more later on. I would be good to decide what should be delivered at first. As we all know time is limited and I'm working hard to get the code thoroughly tested. Especially in the arithmetic and logical operators where there is a multitude of possible combinations and each one needs a operator overload for the API to be complete and most user-friendly. If you haven't noticed, I am maintaining a documentation of the API's features on a wiki [1]. If you guys could find some spare time to have a look at it and maybe offer suggestions that would be great. Thanks, Tom [1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/ On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote: > Hey All > > Would anyone object if I went ahead and made the 0.8.0 release sometime next > week? > > There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 > compliance and general improvements to SPARQL implementation plus > significant fixes and updates to the Query.FullText library. > > I had originally thought that we might get the Fluent Query API in this > release but looking at what Tom's got so far (which is great btw) it's > clearly a much bigger lift than I first thought. I'd rather push that to > unscheduled and have it be merged in as and when Tom thinks it's ready > rather than holding back a useful (and primarily bug fix) release. > > Any other thoughts/objections? > > Rob > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_nov > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2012-11-15 00:51:12
|
May have spoken too soon on the 0.8.0 release, the proposed recommendations for SPARQL 1.1 just came out so I'm going to try and get some final compatibility and bug fixing for this done before the next release. On the fluent query front maybe it would be sufficient to have a partial API in place for 0.8.0. By partial I mean something that supported the major constructs of the language (WHERE, OPTIONAL, GRAPH, UNION, SERVICE, FILTER etc) with a limited set of expressions supported. Something that just covered the SPARQL 1.0 operators would be sufficient and we can flesh out to the full SPARQL 1.1 set in later releases. How does this sound? Rob On 11/11/12 9:53 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >I don't mind an earlier release. > >Regarding the Fluent API I think we could get it out in 8.1 or so. At >this point maybe it will be good to define some kind of a road map >internally. SPARQL has many features and it is possible to implement >some in the first go and add more later on. I would be good to decide >what should be delivered at first. As we all know time is limited and >I'm working hard to get the code thoroughly tested. Especially in the >arithmetic and logical operators where there is a multitude of >possible combinations and each one needs a operator overload for the >API to be complete and most user-friendly. > >If you haven't noticed, I am maintaining a documentation of the API's >features on a wiki [1]. If you guys could find some spare time to have >a look at it and maybe offer suggestions that would be great. > >Thanks, >Tom > >[1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/ > >On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote: >> Hey All >> >> Would anyone object if I went ahead and made the 0.8.0 release sometime >>next >> week? >> >> There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 >> compliance and general improvements to SPARQL implementation plus >> significant fixes and updates to the Query.FullText library. >> >> I had originally thought that we might get the Fluent Query API in this >> release but looking at what Tom's got so far (which is great btw) it's >> clearly a much bigger lift than I first thought. I'd rather push that >>to >> unscheduled and have it be merged in as and when Tom thinks it's ready >> rather than holding back a useful (and primarily bug fix) release. >> >> Any other thoughts/objections? >> >> Rob >> >> >>------------------------------------------------------------------------- >>----- >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_nov >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_d2d_nov >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2012-11-15 10:39:57
|
Can do. Can you point me to a concise comparison between SPARQL 1.0 and 1.1. Or maybe you could quickly draft what you think should come first and what cant wait? Thanks, Tom On Thu, Nov 15, 2012 at 1:50 AM, Rob Vesse <rv...@do...> wrote: > May have spoken too soon on the 0.8.0 release, the proposed > recommendations for SPARQL 1.1 just came out so I'm going to try and get > some final compatibility and bug fixing for this done before the next > release. > > On the fluent query front maybe it would be sufficient to have a partial > API in place for 0.8.0. By partial I mean something that supported the > major constructs of the language (WHERE, OPTIONAL, GRAPH, UNION, SERVICE, > FILTER etc) with a limited set of expressions supported. Something that > just covered the SPARQL 1.0 operators would be sufficient and we can flesh > out to the full SPARQL 1.1 set in later releases. > > How does this sound? > > Rob > > On 11/11/12 9:53 AM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>I don't mind an earlier release. >> >>Regarding the Fluent API I think we could get it out in 8.1 or so. At >>this point maybe it will be good to define some kind of a road map >>internally. SPARQL has many features and it is possible to implement >>some in the first go and add more later on. I would be good to decide >>what should be delivered at first. As we all know time is limited and >>I'm working hard to get the code thoroughly tested. Especially in the >>arithmetic and logical operators where there is a multitude of >>possible combinations and each one needs a operator overload for the >>API to be complete and most user-friendly. >> >>If you haven't noticed, I am maintaining a documentation of the API's >>features on a wiki [1]. If you guys could find some spare time to have >>a look at it and maybe offer suggestions that would be great. >> >>Thanks, >>Tom >> >>[1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/ >> >>On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote: >>> Hey All >>> >>> Would anyone object if I went ahead and made the 0.8.0 release sometime >>>next >>> week? >>> >>> There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 >>> compliance and general improvements to SPARQL implementation plus >>> significant fixes and updates to the Query.FullText library. >>> >>> I had originally thought that we might get the Fluent Query API in this >>> release but looking at what Tom's got so far (which is great btw) it's >>> clearly a much bigger lift than I first thought. I'd rather push that >>>to >>> unscheduled and have it be merged in as and when Tom thinks it's ready >>> rather than holding back a useful (and primarily bug fix) release. >>> >>> Any other thoughts/objections? >>> >>> Rob >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_d2d_nov >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >>-------------------------------------------------------------------------- >>---- >>Everyone hates slow websites. So do we. >>Make your web apps faster with AppDynamics >>Download AppDynamics Lite for free today: >>http://p.sf.net/sfu/appdyn_d2d_nov >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2012-11-16 23:19:17
|
Here's a quick guide SPARQL 1.0 - Graph Patterns - OPTIONAL, GRAPH, UNION - FILTER - Expressions - BOUND, ISIRI, ISBLANK, ISLITERAL, STR, LANG, DATATYPE, ||, &&, =, SAMETERM, LANGMATCHES, REGEX, >, >=, <, <=, XPath constructors (xsd:boolean, xsd:integer etc) - Solution Modifiers - ORDER BY, LIMIT, OFFSET SPARQL 1.1 - As SPARQL 1.0 plus the following - Graph Patterns - Sub-SELECT, MINUS, SERVICE, VALUES, EXISTS and NOT EXISTS (these last two are in FILTER only) - Expressions - IF, COALESCE, NOT EXISTS, EXISTS, IN, NOT IN, ISNUMERIC, IRI, BNODE, STRDT, STRLANG, UUID, STRUUID, STRLEN, SUBSTR, UCASE, LCASE, STRSTARTS, STRENDS, CONTAINS, STRBEFORE, STRAFTER, ENCODE_FOR_URI, CONCAT, REPLACE, ABS, ROUND, CEIL, FLOOR, RAND, NOW, YEAR, MONTH, DAY, HOURS, MINUTES, SECONDS, TIMEZONE, TZ, MD5, SHA1, SHA256, SHA384, SHA512 - Solution Modifiers - GROUP BY, HAVING, VALUES - Aggregate Expressions - AVG, COUNT, GROUP_CONCAT, MAX, MIN, SAMPLE So clearly SPARQL 1.0 is much smaller Hope this helps, Rob On 11/15/12 2:39 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Can do. Can you point me to a concise comparison between SPARQL 1.0 and >1.1. > >Or maybe you could quickly draft what you think should come first and >what cant wait? > >Thanks, >Tom > >On Thu, Nov 15, 2012 at 1:50 AM, Rob Vesse <rv...@do...> wrote: >> May have spoken too soon on the 0.8.0 release, the proposed >> recommendations for SPARQL 1.1 just came out so I'm going to try and get >> some final compatibility and bug fixing for this done before the next >> release. >> >> On the fluent query front maybe it would be sufficient to have a partial >> API in place for 0.8.0. By partial I mean something that supported the >> major constructs of the language (WHERE, OPTIONAL, GRAPH, UNION, >>SERVICE, >> FILTER etc) with a limited set of expressions supported. Something that >> just covered the SPARQL 1.0 operators would be sufficient and we can >>flesh >> out to the full SPARQL 1.1 set in later releases. >> >> How does this sound? >> >> Rob >> >> On 11/11/12 9:53 AM, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>I don't mind an earlier release. >>> >>>Regarding the Fluent API I think we could get it out in 8.1 or so. At >>>this point maybe it will be good to define some kind of a road map >>>internally. SPARQL has many features and it is possible to implement >>>some in the first go and add more later on. I would be good to decide >>>what should be delivered at first. As we all know time is limited and >>>I'm working hard to get the code thoroughly tested. Especially in the >>>arithmetic and logical operators where there is a multitude of >>>possible combinations and each one needs a operator overload for the >>>API to be complete and most user-friendly. >>> >>>If you haven't noticed, I am maintaining a documentation of the API's >>>features on a wiki [1]. If you guys could find some spare time to have >>>a look at it and maybe offer suggestions that would be great. >>> >>>Thanks, >>>Tom >>> >>>[1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/ >>> >>>On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote: >>>> Hey All >>>> >>>> Would anyone object if I went ahead and made the 0.8.0 release >>>>sometime >>>>next >>>> week? >>>> >>>> There's a whole bunch of bug fixes in there, updates to SPARQL 1.1 >>>> compliance and general improvements to SPARQL implementation plus >>>> significant fixes and updates to the Query.FullText library. >>>> >>>> I had originally thought that we might get the Fluent Query API in >>>>this >>>> release but looking at what Tom's got so far (which is great btw) it's >>>> clearly a much bigger lift than I first thought. I'd rather push that >>>>to >>>> unscheduled and have it be merged in as and when Tom thinks it's ready >>>> rather than holding back a useful (and primarily bug fix) release. >>>> >>>> Any other thoughts/objections? >>>> >>>> Rob >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>----- >>>> Everyone hates slow websites. So do we. >>>> Make your web apps faster with AppDynamics >>>> Download AppDynamics Lite for free today: >>>> http://p.sf.net/sfu/appdyn_d2d_nov >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Everyone hates slow websites. So do we. >>>Make your web apps faster with AppDynamics >>>Download AppDynamics Lite for free today: >>>http://p.sf.net/sfu/appdyn_d2d_nov >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Monitor your physical, virtual and cloud infrastructure from a single >web console. Get in-depth insight into apps, servers, databases, vmware, >SAP, cloud infrastructure, etc. Download 30-day Free Trial. >Pricing starts from $795 for 25 servers or applications! >http://p.sf.net/sfu/zoho_dev2dev_nov >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2012-11-19 21:24:02
|
Thanks Rob
1. It seems that I have most of SPARQL 1.0 already and a portion of
SPARQL 1.1 in place. Out of what you have listed I'm currently missing
REGEX, ORDER BY and constructors.
2. I have just thought that maybe we could split the methods over two
namespaces so that it is possible to choose which syntax a user wants.
For example the current namespace VDS.RDF.Query.Builder will contain
only SPARQL 1.0 and to get the SPARQL 1.1 one would include
VDS.RDF.Query.Builder.Sparql11. Or maybe this isn't necessary?
3. I'm also struggling with the expression types for string methods.
Until recently it seems to have worked fine but the problem is with
string/simple/plain literals. Today I have decided to remove the
SimpleLiteralExpression class because it doesn't play well with the
typed string expression. Instead I use simpy LiteralExpression which
is also base for other typed literals. This means that it will be
possible to call for example
Builder.LangMatches( Builder.Constant(10), "fr")
which doesn't make sense but I can't figure a good way to make the API
strict enough but not too complicated. The expression builder is
already quite grown.
4. Another thing I have been considering the API change for some
expression type, most notably for string functions. With the exception
of IN function all methods are static extensions of ExpressionBuilder
class. IN on the other hand is invoked on any other expression.
However I wonder whether it would be more user-friendly if more of the
functions would be built in context of expressions and not expression
builder (which is unused in implementation in most of the cases
anyway). Examples could be LANG or STRLEN. So instead of
Builder.Lang(variable) or Buidler.StrLen(variable)
the user would call simply
variable.GetLang() or variable.GetStrLen()
What do you think?
5. Also I'm not sure is for the best are quite numerous overloads
especially for string functions. I didn't have an issue with that
until I implemented SUBSTR some time last week, which has two or three
parameters. The first can be variable or string expression, and the
second and third can be variable, int expression or simply integers.
This gives a total of 18 overloads and I start to think it's a code
smell. Should remove the ones which take int parameters?
6. Lastly the I would like to ask you about constants. How much does
it matter in SPARQL whether a literal is typed or not. I mean "str" vs
"str"^^xsd:string or 5 vs "5"^^xsd:int. In any what is you opinion,
which should be created by the expression builder? When user calls
Builder.Constant("str"), Builder.Constant(5) or
Builder.Constant(DateTime.Now)?
On Sat, Nov 17, 2012 at 12:18 AM, Rob Vesse <rv...@do...> wrote:
> Here's a quick guide
>
> SPARQL 1.0
> - Graph Patterns - OPTIONAL, GRAPH, UNION
> - FILTER
> - Expressions - BOUND, ISIRI, ISBLANK, ISLITERAL, STR, LANG, DATATYPE, ||,
> &&, =, SAMETERM, LANGMATCHES, REGEX, >, >=, <, <=, XPath constructors
> (xsd:boolean, xsd:integer etc)
> - Solution Modifiers - ORDER BY, LIMIT, OFFSET
>
> SPARQL 1.1 - As SPARQL 1.0 plus the following
> - Graph Patterns - Sub-SELECT, MINUS, SERVICE, VALUES, EXISTS and NOT
> EXISTS (these last two are in FILTER only)
> - Expressions - IF, COALESCE, NOT EXISTS, EXISTS, IN, NOT IN, ISNUMERIC,
> IRI, BNODE, STRDT, STRLANG, UUID, STRUUID, STRLEN, SUBSTR, UCASE, LCASE,
> STRSTARTS, STRENDS, CONTAINS, STRBEFORE, STRAFTER, ENCODE_FOR_URI, CONCAT,
> REPLACE, ABS, ROUND, CEIL, FLOOR, RAND, NOW, YEAR, MONTH, DAY, HOURS,
> MINUTES, SECONDS, TIMEZONE, TZ, MD5, SHA1, SHA256, SHA384, SHA512
> - Solution Modifiers - GROUP BY, HAVING, VALUES
> - Aggregate Expressions - AVG, COUNT, GROUP_CONCAT, MAX, MIN, SAMPLE
>
> So clearly SPARQL 1.0 is much smaller
>
> Hope this helps,
>
> Rob
>
> On 11/15/12 2:39 AM, "Tomasz Pluskiewicz" <tom...@gm...>
> wrote:
>
>>Can do. Can you point me to a concise comparison between SPARQL 1.0 and
>>1.1.
>>
>>Or maybe you could quickly draft what you think should come first and
>>what cant wait?
>>
>>Thanks,
>>Tom
>>
>>On Thu, Nov 15, 2012 at 1:50 AM, Rob Vesse <rv...@do...> wrote:
>>> May have spoken too soon on the 0.8.0 release, the proposed
>>> recommendations for SPARQL 1.1 just came out so I'm going to try and get
>>> some final compatibility and bug fixing for this done before the next
>>> release.
>>>
>>> On the fluent query front maybe it would be sufficient to have a partial
>>> API in place for 0.8.0. By partial I mean something that supported the
>>> major constructs of the language (WHERE, OPTIONAL, GRAPH, UNION,
>>>SERVICE,
>>> FILTER etc) with a limited set of expressions supported. Something that
>>> just covered the SPARQL 1.0 operators would be sufficient and we can
>>>flesh
>>> out to the full SPARQL 1.1 set in later releases.
>>>
>>> How does this sound?
>>>
>>> Rob
>>>
>>> On 11/11/12 9:53 AM, "Tomasz Pluskiewicz" <tom...@gm...>
>>> wrote:
>>>
>>>>I don't mind an earlier release.
>>>>
>>>>Regarding the Fluent API I think we could get it out in 8.1 or so. At
>>>>this point maybe it will be good to define some kind of a road map
>>>>internally. SPARQL has many features and it is possible to implement
>>>>some in the first go and add more later on. I would be good to decide
>>>>what should be delivered at first. As we all know time is limited and
>>>>I'm working hard to get the code thoroughly tested. Especially in the
>>>>arithmetic and logical operators where there is a multitude of
>>>>possible combinations and each one needs a operator overload for the
>>>>API to be complete and most user-friendly.
>>>>
>>>>If you haven't noticed, I am maintaining a documentation of the API's
>>>>features on a wiki [1]. If you guys could find some spare time to have
>>>>a look at it and maybe offer suggestions that would be great.
>>>>
>>>>Thanks,
>>>>Tom
>>>>
>>>>[1] https://bitbucket.org/romanticweb/dotnetrdf/wiki/
>>>>
>>>>On Fri, Nov 9, 2012 at 8:06 PM, Rob Vesse <rv...@do...> wrote:
>>>>> Hey All
>>>>>
>>>>> Would anyone object if I went ahead and made the 0.8.0 release
>>>>>sometime
>>>>>next
>>>>> week?
>>>>>
>>>>> There's a whole bunch of bug fixes in there, updates to SPARQL 1.1
>>>>> compliance and general improvements to SPARQL implementation plus
>>>>> significant fixes and updates to the Query.FullText library.
>>>>>
>>>>> I had originally thought that we might get the Fluent Query API in
>>>>>this
>>>>> release but looking at what Tom's got so far (which is great btw) it's
>>>>> clearly a much bigger lift than I first thought. I'd rather push that
>>>>>to
>>>>> unscheduled and have it be merged in as and when Tom thinks it's ready
>>>>> rather than holding back a useful (and primarily bug fix) release.
>>>>>
>>>>> Any other thoughts/objections?
>>>>>
>>>>> Rob
>>>>>
>>>>>
>>>>>-----------------------------------------------------------------------
>>>>>--
>>>>>-----
>>>>> Everyone hates slow websites. So do we.
>>>>> Make your web apps faster with AppDynamics
>>>>> Download AppDynamics Lite for free today:
>>>>> http://p.sf.net/sfu/appdyn_d2d_nov
>>>>> _______________________________________________
>>>>> dotNetRDF-develop mailing list
>>>>> dot...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>>>
>>>>
>>>>------------------------------------------------------------------------
>>>>--
>>>>----
>>>>Everyone hates slow websites. So do we.
>>>>Make your web apps faster with AppDynamics
>>>>Download AppDynamics Lite for free today:
>>>>http://p.sf.net/sfu/appdyn_d2d_nov
>>>>_______________________________________________
>>>>dotNetRDF-develop mailing list
>>>>dot...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>>
>>>
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------------------------
>>>-----
>>> Monitor your physical, virtual and cloud infrastructure from a single
>>> web console. Get in-depth insight into apps, servers, databases, vmware,
>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>> Pricing starts from $795 for 25 servers or applications!
>>> http://p.sf.net/sfu/zoho_dev2dev_nov
>>> _______________________________________________
>>> dotNetRDF-develop mailing list
>>> dot...@li...
>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>
>>--------------------------------------------------------------------------
>>----
>>Monitor your physical, virtual and cloud infrastructure from a single
>>web console. Get in-depth insight into apps, servers, databases, vmware,
>>SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>>Pricing starts from $795 for 25 servers or applications!
>>http://p.sf.net/sfu/zoho_dev2dev_nov
>>_______________________________________________
>>dotNetRDF-develop mailing list
>>dot...@li...
>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
>
>
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X