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: song x. <son...@gm...> - 2014-07-04 06:49:06
|
Tom, Thank you very much, and sorry for not clearing myself I forgot typing <hasMyClass02>, so the complete one will like this —————————————————— <rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns# xmlns:KB="http://protege.stanford.edu/kb#"> <KB:MyClass01 rdf:about="MyClass01Id"> <hasProperty01>the value of this property</hasProperty01> <hasMyClass02> <KB:MyClass02 rdf:about="MyClass02Id"> <hasProperty02 >the value of this property</hasProperty02> </KB:MyClass02> </hasMyClass02> </KB:MyClass01> </rdf:RDF> —————————————————— (I think this is the correct format of —————————————————— <MyClass01Id> <hasProperty01> "the value of this property". <MyClass01Id> <hasMyClass02> <MyClass02Id> . <MyClass02Id> <hasProperty02> "the value of this property". —————————————————— , right? ) You see, I cannot create that “<KB:MyClass01…” thing but only “<rdf:Description…”, because I think the target system also might need to know “MyClass01Id” is an instance of type “MyClass01” (as well as “MyClass02Id” is an instance of type “MyClass02”) maybe I just cannot do like this? I will contact the guys working in target system to look how to solve. Thank you for the information! I should have read them more carefully. 在 3 Jul 2014，19:57，Tomasz Pluskiewicz <tom...@gm...> 写道： > First, your example is not a valid RDF/XML. AFAIK text nodes are > valid, when they are a value of a literal property. Such as Bob is 20 > years old. In NTriples: > > <Bob> <age> 20 . > > could be written as > > <rdf:Description rdf:about="Bob> > <age>20</age> > </rdf:Description> > > or it could use XML attribute > > <rdf:Description rdf:about="Bob age="20" /> > > Your example is missing one part of the triple. Either predicate or > object. The subject is MyClass01ID but what is xxx? A full statement > about MyClass01ID requires that there is a verb (predicate/property) > and the value (object). > > I must stress again, that a RDF-aware system cannot require any > specific formatting of a RDF/XML document. I understand that maybe > other RDF formats aren't supported but in the end it is the data that > s important and it can be written in various ways without chaging the > meaning. > > I could also suggest that you read some introductory documents about > RDF like [1] and maybe RDF/XML documentation [2], since you are > working with that format. Though by using dotNetRDF or any other > library you shouldn't be at all concerned with it. It is the graph > that matters and you should never really have to manipulate raw > RDF/XML document save maybe for debugging. > > Tom > > [1] http://www.w3.org/TR/rdf11-primer/ > [2] http://www.w3.org/TR/rdf-syntax-grammar/ > > On Thu, Jul 3, 2014 at 5:39 PM, son...@gm... > <son...@gm...> wrote: >> Thank you for the help >> >> but I am sorry that I still not very clear how to do >> the target system requires this format: >> >> ------------------------------------ >> <MyClass01 rdf:about="MyClass01ID"> >> xxx >> </MyClass01> >> ------------------------------------ >> How can i create this (not rdf:Description xxx)? >> >> Best Wishes >> >> ________________________________ >> son...@gm... >> >> From: Tomasz Pluskiewicz >> Date: 2014-07-03 15:21 >> To: dotNetRDF Developer Discussion and Feature Request >> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format >> In RDF this is a relation like any other. You state exactly what you >> described, that a resource is of a given type. And you declare that >> statement with a triple like any other fact about your resources. >> >> You use the predicate rdf:type [1]. There is a handy class called >> VDS.RDF.Parsing.RdfSpecsHelper, which contains the correct Uri of the >> rdf namespace. >> >> On Thu, Jul 3, 2014 at 4:03 PM, son...@gm... >> <son...@gm...> wrote: >>> Thank you so much Tom! >>> >>> there only just one question left: >>> Since the target system need to know the class type, i.e., >>> ==> MyClass01Id is a MyClass01 >>> How can I express this in dotnetrdf? >>> >>> >>> ________________________________ >>> son...@gm... >>> >>> From: Tomasz Pluskiewicz >>> Date: 2014-07-01 21:53 >>> To: dotNetRDF Developer Discussion and Feature Request >>> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format >>> On Tue, Jul 1, 2014 at 12:23 PM, son...@gm... >>> <son...@gm...> wrote: >>>> Thank you Tom! >>>> >>>> You are right, basically what I am trying to do is converting following >>>> class: >>>> ------------------------------------- >>>> class MyClass01 { >>>> public string Property01 {get; set;} >>>> public MyClass02 myClass02 {get; set;} >>>> } >>>> //the instance of class has its own unique id >>>> >>> >>> I strongly suggest that you think in terms of triples or graphs and >>> not their serializaitions. So given an instance of MyClass01 you could >>> have the following data >>> >>> <MyClass01Id> <hasProperty01> "the value of this property". >>> <MyClass01Id> <hasMyClass02> <MyClass02Id> . >>> >>> This is all you need. These two triples would be stored the way you >>> used in the earlier email (remember to use proper URIs). I know >>> nothing about MyClass02 at this point, just the hypothetical id. It >>> would add further similar triples >>> >>> Notice how this notation (NTriples/Turtle) removes any unnecessary >>> syntactic clutter and leaves only the subjects, predicates and >>> objects. >>> >>>> >>>> ------------------------------------- >>>> to this kind of text >>>> ------------------------------------- >>>> <rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns# >>>> xmlns:KB="http://protege.stanford.edu/kb#"> >>>> <KB:MyClass01 rdf:about="that unique id"> >>>> <hasProperty01 >the value of this property</hasProperty01> >>>> <MyClass02 rdf:about="the unique id"> >>>> //MyClass02's content >>>> </MyClass02> >>>> </KB:EndToEndBlueprintRoot> >>>> </rdf:RDF> >>>> ------------------------------------- >>>> >>> >>> You must keep in mind that with RDF/XML there are multiple ways to >>> write the same document. It means that the structure can change, while >>> the actual data doesn't. >>> >>>> >>>> Also I have to use this kind of format because it is the input of another >>>> system I have to use... >>>> >>> >>> In memory you keep the data (triples) and dotNetRDF helps you save it >>> in one of the RDF formats. If the other system requires that you use >>> RDF/XML, that's fine but you could save it as Turtle or Notation3. >>> >>>> >>>> Thank you again! >>>> >>>> ________________________________ >>>> son...@gm... >>>> >>>> From: Tomasz Pluskiewicz >>>> Date: 2014-07-01 10:13 >>>> To: dotNetRDF Developer Discussion and Feature Request >>>> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format >>>> On Tue, Jul 1, 2014 at 7:44 AM, son...@gm... >>>> <son...@gm...> wrote: >>>>> Hi, all >>>>> >>>>> I am trying to write a RDF/XML like follows: >>>>> ------------------------------------------------------- >>>>> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" >>>>> xmlns:KB="http://protege.stanford.edu/kb#"> >>>>> <KB:EndToEndBlueprintRoot >>>>> rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001"> >>>>> xxxxx >>>>> </KB:EndToEndBlueprintRoot> >>>>> </rdf:RDF> >>>>> ------------------------------------------------------- >>>>> >>>> >>>> First of all this document is not a valid RDF/XML. >>>> >>>>> Here is my code >>>>> ------------------------------------------------------- >>>>> INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot"); >>>>> INode p = g.CreateUriNode("rdf:about"); >>>>> INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001"); >>>>> >>>>> g.Assert(new Triple(s,p,o)); >>>>> >>>>> RdfXmlWriter rxw = new RdfXmlWriter(); >>>>> string res = VDS.RDF.Writing.StringWriter.Write(g, rxw); >>>>> ------------------------------------------------------- >>>>> >>>> >>>> Secondly, the rdf:about is just a RDF/XML syntax feature and not a >>>> predicate. It denotes that part of an RDF/XML document is grouped with >>>> a common subject. Please read [1]. >>>> >>>> You should think in terms of triples, which define a relation >>>> (predicate) between two objects (subjects and objects). That is much >>>> like in natural language. >>>> >>>>> >>>>> But only got this >>>>> ------------------------------------------------------- >>>>> <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" >>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema#" >>>>> xmlns="http://example.org/" >>>>> xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#" >>>>> xmlns:kb="http://protege.stanford.edu/kb#" >>>>> xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#" >>>>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> >>>>> <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot"> >>>>> xxx >>>>> <ns3:about xmlns:ns3="http://protege.stanford.edu/system#" >>>>> rdf:resource="&kb;DemoRootImagineID001" /> >>>>> </rdf:Description> >>>>> </rdf:RDF> >>>>> ------------------------------------------------------- >>>>> >>>>> Is my usage correct? or how can I output the format that I want? >>>>> What is the appropriate writing of "rdf:about"? >>>>> >>>> >>>> You probably mean kb:DemoRootImagineID001 as you subject, that is the >>>> thing you want to describe in your document. Is that right? >>>> >>>> Please describe what kind of data you want your document to contain. >>>> >>>>> >>>>> Any suggestion will be appreciated! >>>>> >>>>> ________________________________ >>>>> son...@gm... >>>>> >>>> >>>> Regards, >>>> Tom >>>> >>>> [1] >>>> >>>> >>>> http://stackoverflow.com/questions/7118326/differences-between-rdfresource-rdfabout-and-rdfid >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Open source business process management suite built on Java and Eclipse >>>> Turn processes into business applications with Bonita BPM Community >>>> Edition >>>> Quickly connect people, data, and systems into organized workflows >>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>>> http://p.sf.net/sfu/Bonitasoft >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Open source business process management suite built on Java and Eclipse >>>> Turn processes into business applications with Bonita BPM Community >>>> Edition >>>> Quickly connect people, data, and systems into organized workflows >>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>>> http://p.sf.net/sfu/Bonitasoft >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>> Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> ------------------------------------------------------------------------------ >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>> Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >> ------------------------------------------------------------------------------ >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> ------------------------------------------------------------------------------ >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2014-07-03 18:58:37
|
First, your example is not a valid RDF/XML. AFAIK text nodes are valid, when they are a value of a literal property. Such as Bob is 20 years old. In NTriples: <Bob> <age> 20 . could be written as <rdf:Description rdf:about="Bob> <age>20</age> </rdf:Description> or it could use XML attribute <rdf:Description rdf:about="Bob age="20" /> Your example is missing one part of the triple. Either predicate or object. The subject is MyClass01ID but what is xxx? A full statement about MyClass01ID requires that there is a verb (predicate/property) and the value (object). I must stress again, that a RDF-aware system cannot require any specific formatting of a RDF/XML document. I understand that maybe other RDF formats aren't supported but in the end it is the data that s important and it can be written in various ways without chaging the meaning. I could also suggest that you read some introductory documents about RDF like [1] and maybe RDF/XML documentation [2], since you are working with that format. Though by using dotNetRDF or any other library you shouldn't be at all concerned with it. It is the graph that matters and you should never really have to manipulate raw RDF/XML document save maybe for debugging. Tom [1] http://www.w3.org/TR/rdf11-primer/ [2] http://www.w3.org/TR/rdf-syntax-grammar/ On Thu, Jul 3, 2014 at 5:39 PM, son...@gm... <son...@gm...> wrote: > Thank you for the help > > but I am sorry that I still not very clear how to do > the target system requires this format: > > ------------------------------------ > <MyClass01 rdf:about="MyClass01ID"> > xxx > </MyClass01> > ------------------------------------ > How can i create this (not rdf:Description xxx)? > > Best Wishes > > ________________________________ > son...@gm... > > From: Tomasz Pluskiewicz > Date: 2014-07-03 15:21 > To: dotNetRDF Developer Discussion and Feature Request > Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format > In RDF this is a relation like any other. You state exactly what you > described, that a resource is of a given type. And you declare that > statement with a triple like any other fact about your resources. > > You use the predicate rdf:type [1]. There is a handy class called > VDS.RDF.Parsing.RdfSpecsHelper, which contains the correct Uri of the > rdf namespace. > > On Thu, Jul 3, 2014 at 4:03 PM, son...@gm... > <son...@gm...> wrote: >> Thank you so much Tom! >> >> there only just one question left: >> Since the target system need to know the class type, i.e., >> ==> MyClass01Id is a MyClass01 >> How can I express this in dotnetrdf? >> >> >> ________________________________ >> son...@gm... >> >> From: Tomasz Pluskiewicz >> Date: 2014-07-01 21:53 >> To: dotNetRDF Developer Discussion and Feature Request >> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format >> On Tue, Jul 1, 2014 at 12:23 PM, son...@gm... >> <son...@gm...> wrote: >>> Thank you Tom! >>> >>> You are right, basically what I am trying to do is converting following >>> class: >>> ------------------------------------- >>> class MyClass01 { >>> public string Property01 {get; set;} >>> public MyClass02 myClass02 {get; set;} >>> } >>> //the instance of class has its own unique id >>> >> >> I strongly suggest that you think in terms of triples or graphs and >> not their serializaitions. So given an instance of MyClass01 you could >> have the following data >> >> <MyClass01Id> <hasProperty01> "the value of this property". >> <MyClass01Id> <hasMyClass02> <MyClass02Id> . >> >> This is all you need. These two triples would be stored the way you >> used in the earlier email (remember to use proper URIs). I know >> nothing about MyClass02 at this point, just the hypothetical id. It >> would add further similar triples >> >> Notice how this notation (NTriples/Turtle) removes any unnecessary >> syntactic clutter and leaves only the subjects, predicates and >> objects. >> >>> >>> ------------------------------------- >>> to this kind of text >>> ------------------------------------- >>> <rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns# >>> xmlns:KB="http://protege.stanford.edu/kb#"> >>> <KB:MyClass01 rdf:about="that unique id"> >>> <hasProperty01 >the value of this property</hasProperty01> >>> <MyClass02 rdf:about="the unique id"> >>> //MyClass02's content >>> </MyClass02> >>> </KB:EndToEndBlueprintRoot> >>> </rdf:RDF> >>> ------------------------------------- >>> >> >> You must keep in mind that with RDF/XML there are multiple ways to >> write the same document. It means that the structure can change, while >> the actual data doesn't. >> >>> >>> Also I have to use this kind of format because it is the input of another >>> system I have to use... >>> >> >> In memory you keep the data (triples) and dotNetRDF helps you save it >> in one of the RDF formats. If the other system requires that you use >> RDF/XML, that's fine but you could save it as Turtle or Notation3. >> >>> >>> Thank you again! >>> >>> ________________________________ >>> son...@gm... >>> >>> From: Tomasz Pluskiewicz >>> Date: 2014-07-01 10:13 >>> To: dotNetRDF Developer Discussion and Feature Request >>> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format >>> On Tue, Jul 1, 2014 at 7:44 AM, son...@gm... >>> <son...@gm...> wrote: >>>> Hi, all >>>> >>>> I am trying to write a RDF/XML like follows: >>>> ------------------------------------------------------- >>>> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" >>>> xmlns:KB="http://protege.stanford.edu/kb#"> >>>> <KB:EndToEndBlueprintRoot >>>> rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001"> >>>> xxxxx >>>> </KB:EndToEndBlueprintRoot> >>>> </rdf:RDF> >>>> ------------------------------------------------------- >>>> >>> >>> First of all this document is not a valid RDF/XML. >>> >>>> Here is my code >>>> ------------------------------------------------------- >>>> INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot"); >>>> INode p = g.CreateUriNode("rdf:about"); >>>> INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001"); >>>> >>>> g.Assert(new Triple(s,p,o)); >>>> >>>> RdfXmlWriter rxw = new RdfXmlWriter(); >>>> string res = VDS.RDF.Writing.StringWriter.Write(g, rxw); >>>> ------------------------------------------------------- >>>> >>> >>> Secondly, the rdf:about is just a RDF/XML syntax feature and not a >>> predicate. It denotes that part of an RDF/XML document is grouped with >>> a common subject. Please read [1]. >>> >>> You should think in terms of triples, which define a relation >>> (predicate) between two objects (subjects and objects). That is much >>> like in natural language. >>> >>>> >>>> But only got this >>>> ------------------------------------------------------- >>>> <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema#" >>>> xmlns="http://example.org/" >>>> xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#" >>>> xmlns:kb="http://protege.stanford.edu/kb#" >>>> xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#" >>>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> >>>> <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot"> >>>> xxx >>>> <ns3:about xmlns:ns3="http://protege.stanford.edu/system#" >>>> rdf:resource="&kb;DemoRootImagineID001" /> >>>> </rdf:Description> >>>> </rdf:RDF> >>>> ------------------------------------------------------- >>>> >>>> Is my usage correct? or how can I output the format that I want? >>>> What is the appropriate writing of "rdf:about"? >>>> >>> >>> You probably mean kb:DemoRootImagineID001 as you subject, that is the >>> thing you want to describe in your document. Is that right? >>> >>> Please describe what kind of data you want your document to contain. >>> >>>> >>>> Any suggestion will be appreciated! >>>> >>>> ________________________________ >>>> son...@gm... >>>> >>> >>> Regards, >>> Tom >>> >>> [1] >>> >>> >>> http://stackoverflow.com/questions/7118326/differences-between-rdfresource-rdfabout-and-rdfid >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>> Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>> Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >> >> ------------------------------------------------------------------------------ >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >> Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> ------------------------------------------------------------------------------ >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >> Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: <son...@gm...> - 2014-07-03 15:40:02
|
Thank you for the help
but I am sorry that I still not very clear how to do
the target system requires this format:
------------------------------------
<MyClass01 rdf:about="MyClass01ID">
xxx
</MyClass01>
------------------------------------
How can i create this (not rdf:Description xxx)?
Best Wishes
son...@gm...
From: Tomasz Pluskiewicz
Date: 2014-07-03 15:21
To: dotNetRDF Developer Discussion and Feature Request
Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
In RDF this is a relation like any other. You state exactly what you
described, that a resource is of a given type. And you declare that
statement with a triple like any other fact about your resources.
You use the predicate rdf:type [1]. There is a handy class called
VDS.RDF.Parsing.RdfSpecsHelper, which contains the correct Uri of the
rdf namespace.
On Thu, Jul 3, 2014 at 4:03 PM, son...@gm...
<son...@gm...> wrote:
> Thank you so much Tom!
>
> there only just one question left:
> Since the target system need to know the class type, i.e.,
> ==> MyClass01Id is a MyClass01
> How can I express this in dotnetrdf?
>
>
> ________________________________
> son...@gm...
>
> From: Tomasz Pluskiewicz
> Date: 2014-07-01 21:53
> To: dotNetRDF Developer Discussion and Feature Request
> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
> On Tue, Jul 1, 2014 at 12:23 PM, son...@gm...
> <son...@gm...> wrote:
>> Thank you Tom!
>>
>> You are right, basically what I am trying to do is converting following
>> class:
>> -------------------------------------
>> class MyClass01 {
>> public string Property01 {get; set;}
>> public MyClass02 myClass02 {get; set;}
>> }
>> //the instance of class has its own unique id
>>
>
> I strongly suggest that you think in terms of triples or graphs and
> not their serializaitions. So given an instance of MyClass01 you could
> have the following data
>
> <MyClass01Id> <hasProperty01> "the value of this property".
> <MyClass01Id> <hasMyClass02> <MyClass02Id> .
>
> This is all you need. These two triples would be stored the way you
> used in the earlier email (remember to use proper URIs). I know
> nothing about MyClass02 at this point, just the hypothetical id. It
> would add further similar triples
>
> Notice how this notation (NTriples/Turtle) removes any unnecessary
> syntactic clutter and leaves only the subjects, predicates and
> objects.
>
>>
>> -------------------------------------
>> to this kind of text
>> -------------------------------------
>> <rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#
>> xmlns:KB="http://protege.stanford.edu/kb#">
>> <KB:MyClass01 rdf:about="that unique id">
>> <hasProperty01 >the value of this property</hasProperty01>
>> <MyClass02 rdf:about="the unique id">
>> //MyClass02's content
>> </MyClass02>
>> </KB:EndToEndBlueprintRoot>
>> </rdf:RDF>
>> -------------------------------------
>>
>
> You must keep in mind that with RDF/XML there are multiple ways to
> write the same document. It means that the structure can change, while
> the actual data doesn't.
>
>>
>> Also I have to use this kind of format because it is the input of another
>> system I have to use...
>>
>
> In memory you keep the data (triples) and dotNetRDF helps you save it
> in one of the RDF formats. If the other system requires that you use
> RDF/XML, that's fine but you could save it as Turtle or Notation3.
>
>>
>> Thank you again!
>>
>> ________________________________
>> son...@gm...
>>
>> From: Tomasz Pluskiewicz
>> Date: 2014-07-01 10:13
>> To: dotNetRDF Developer Discussion and Feature Request
>> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
>> On Tue, Jul 1, 2014 at 7:44 AM, son...@gm...
>> <son...@gm...> wrote:
>>> Hi, all
>>>
>>> I am trying to write a RDF/XML like follows:
>>> -------------------------------------------------------
>>> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>>> xmlns:KB="http://protege.stanford.edu/kb#">
>>> <KB:EndToEndBlueprintRoot
>>> rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001">
>>> xxxxx
>>> </KB:EndToEndBlueprintRoot>
>>> </rdf:RDF>
>>> -------------------------------------------------------
>>>
>>
>> First of all this document is not a valid RDF/XML.
>>
>>> Here is my code
>>> -------------------------------------------------------
>>> INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot");
>>> INode p = g.CreateUriNode("rdf:about");
>>> INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001");
>>>
>>> g.Assert(new Triple(s,p,o));
>>>
>>> RdfXmlWriter rxw = new RdfXmlWriter();
>>> string res = VDS.RDF.Writing.StringWriter.Write(g, rxw);
>>> -------------------------------------------------------
>>>
>>
>> Secondly, the rdf:about is just a RDF/XML syntax feature and not a
>> predicate. It denotes that part of an RDF/XML document is grouped with
>> a common subject. Please read [1].
>>
>> You should think in terms of triples, which define a relation
>> (predicate) between two objects (subjects and objects). That is much
>> like in natural language.
>>
>>>
>>> But only got this
>>> -------------------------------------------------------
>>> <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://example.org/"
>>> xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>>> xmlns:kb="http://protege.stanford.edu/kb#"
>>> xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
>>> <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot">
>>> xxx
>>> <ns3:about xmlns:ns3="http://protege.stanford.edu/system#"
>>> rdf:resource="&kb;DemoRootImagineID001" />
>>> </rdf:Description>
>>> </rdf:RDF>
>>> -------------------------------------------------------
>>>
>>> Is my usage correct? or how can I output the format that I want?
>>> What is the appropriate writing of "rdf:about"?
>>>
>>
>> You probably mean kb:DemoRootImagineID001 as you subject, that is the
>> thing you want to describe in your document. Is that right?
>>
>> Please describe what kind of data you want your document to contain.
>>
>>>
>>> Any suggestion will be appreciated!
>>>
>>> ________________________________
>>> son...@gm...
>>>
>>
>> Regards,
>> Tom
>>
>> [1]
>>
>> http://stackoverflow.com/questions/7118326/differences-between-rdfresource-rdfabout-and-rdfid
>>
>>
>> ------------------------------------------------------------------------------
>> Open source business process management suite built on Java and Eclipse
>> Turn processes into business applications with Bonita BPM Community
>> Edition
>> Quickly connect people, data, and systems into organized workflows
>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>> http://p.sf.net/sfu/Bonitasoft
>> _______________________________________________
>> dotNetRDF-develop mailing list
>> dot...@li...
>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>
>>
>> ------------------------------------------------------------------------------
>> Open source business process management suite built on Java and Eclipse
>> Turn processes into business applications with Bonita BPM Community
>> Edition
>> Quickly connect people, data, and systems into organized workflows
>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>> http://p.sf.net/sfu/Bonitasoft
>> _______________________________________________
>> dotNetRDF-develop mailing list
>> dot...@li...
>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
dotNetRDF-develop mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2014-07-03 14:22:25
|
In RDF this is a relation like any other. You state exactly what you
described, that a resource is of a given type. And you declare that
statement with a triple like any other fact about your resources.
You use the predicate rdf:type [1]. There is a handy class called
VDS.RDF.Parsing.RdfSpecsHelper, which contains the correct Uri of the
rdf namespace.
On Thu, Jul 3, 2014 at 4:03 PM, son...@gm...
<son...@gm...> wrote:
> Thank you so much Tom!
>
> there only just one question left:
> Since the target system need to know the class type, i.e.,
> ==> MyClass01Id is a MyClass01
> How can I express this in dotnetrdf?
>
>
> ________________________________
> son...@gm...
>
> From: Tomasz Pluskiewicz
> Date: 2014-07-01 21:53
> To: dotNetRDF Developer Discussion and Feature Request
> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
> On Tue, Jul 1, 2014 at 12:23 PM, son...@gm...
> <son...@gm...> wrote:
>> Thank you Tom!
>>
>> You are right, basically what I am trying to do is converting following
>> class:
>> -------------------------------------
>> class MyClass01 {
>> public string Property01 {get; set;}
>> public MyClass02 myClass02 {get; set;}
>> }
>> //the instance of class has its own unique id
>>
>
> I strongly suggest that you think in terms of triples or graphs and
> not their serializaitions. So given an instance of MyClass01 you could
> have the following data
>
> <MyClass01Id> <hasProperty01> "the value of this property".
> <MyClass01Id> <hasMyClass02> <MyClass02Id> .
>
> This is all you need. These two triples would be stored the way you
> used in the earlier email (remember to use proper URIs). I know
> nothing about MyClass02 at this point, just the hypothetical id. It
> would add further similar triples
>
> Notice how this notation (NTriples/Turtle) removes any unnecessary
> syntactic clutter and leaves only the subjects, predicates and
> objects.
>
>>
>> -------------------------------------
>> to this kind of text
>> -------------------------------------
>> <rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#
>> xmlns:KB="http://protege.stanford.edu/kb#">
>> <KB:MyClass01 rdf:about="that unique id">
>> <hasProperty01 >the value of this property</hasProperty01>
>> <MyClass02 rdf:about="the unique id">
>> //MyClass02's content
>> </MyClass02>
>> </KB:EndToEndBlueprintRoot>
>> </rdf:RDF>
>> -------------------------------------
>>
>
> You must keep in mind that with RDF/XML there are multiple ways to
> write the same document. It means that the structure can change, while
> the actual data doesn't.
>
>>
>> Also I have to use this kind of format because it is the input of another
>> system I have to use...
>>
>
> In memory you keep the data (triples) and dotNetRDF helps you save it
> in one of the RDF formats. If the other system requires that you use
> RDF/XML, that's fine but you could save it as Turtle or Notation3.
>
>>
>> Thank you again!
>>
>> ________________________________
>> son...@gm...
>>
>> From: Tomasz Pluskiewicz
>> Date: 2014-07-01 10:13
>> To: dotNetRDF Developer Discussion and Feature Request
>> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
>> On Tue, Jul 1, 2014 at 7:44 AM, son...@gm...
>> <son...@gm...> wrote:
>>> Hi, all
>>>
>>> I am trying to write a RDF/XML like follows:
>>> -------------------------------------------------------
>>> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>>> xmlns:KB="http://protege.stanford.edu/kb#">
>>> <KB:EndToEndBlueprintRoot
>>> rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001">
>>> xxxxx
>>> </KB:EndToEndBlueprintRoot>
>>> </rdf:RDF>
>>> -------------------------------------------------------
>>>
>>
>> First of all this document is not a valid RDF/XML.
>>
>>> Here is my code
>>> -------------------------------------------------------
>>> INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot");
>>> INode p = g.CreateUriNode("rdf:about");
>>> INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001");
>>>
>>> g.Assert(new Triple(s,p,o));
>>>
>>> RdfXmlWriter rxw = new RdfXmlWriter();
>>> string res = VDS.RDF.Writing.StringWriter.Write(g, rxw);
>>> -------------------------------------------------------
>>>
>>
>> Secondly, the rdf:about is just a RDF/XML syntax feature and not a
>> predicate. It denotes that part of an RDF/XML document is grouped with
>> a common subject. Please read [1].
>>
>> You should think in terms of triples, which define a relation
>> (predicate) between two objects (subjects and objects). That is much
>> like in natural language.
>>
>>>
>>> But only got this
>>> -------------------------------------------------------
>>> <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://example.org/"
>>> xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>>> xmlns:kb="http://protege.stanford.edu/kb#"
>>> xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
>>> <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot">
>>> xxx
>>> <ns3:about xmlns:ns3="http://protege.stanford.edu/system#"
>>> rdf:resource="&kb;DemoRootImagineID001" />
>>> </rdf:Description>
>>> </rdf:RDF>
>>> -------------------------------------------------------
>>>
>>> Is my usage correct? or how can I output the format that I want?
>>> What is the appropriate writing of "rdf:about"?
>>>
>>
>> You probably mean kb:DemoRootImagineID001 as you subject, that is the
>> thing you want to describe in your document. Is that right?
>>
>> Please describe what kind of data you want your document to contain.
>>
>>>
>>> Any suggestion will be appreciated!
>>>
>>> ________________________________
>>> son...@gm...
>>>
>>
>> Regards,
>> Tom
>>
>> [1]
>>
>> http://stackoverflow.com/questions/7118326/differences-between-rdfresource-rdfabout-and-rdfid
>>
>>
>> ------------------------------------------------------------------------------
>> Open source business process management suite built on Java and Eclipse
>> Turn processes into business applications with Bonita BPM Community
>> Edition
>> Quickly connect people, data, and systems into organized workflows
>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>> http://p.sf.net/sfu/Bonitasoft
>> _______________________________________________
>> dotNetRDF-develop mailing list
>> dot...@li...
>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>
>>
>> ------------------------------------------------------------------------------
>> Open source business process management suite built on Java and Eclipse
>> Turn processes into business applications with Bonita BPM Community
>> Edition
>> Quickly connect people, data, and systems into organized workflows
>> Winner of BOSSIE, CODIE, OW2 and Gartner awards
>> http://p.sf.net/sfu/Bonitasoft
>> _______________________________________________
>> dotNetRDF-develop mailing list
>> dot...@li...
>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
|
|
From: <son...@gm...> - 2014-07-03 14:04:14
|
Thank you so much Tom!
there only just one question left:
Since the target system need to know the class type, i.e.,
==> MyClass01Id is a MyClass01
How can I express this in dotnetrdf?
son...@gm...
From: Tomasz Pluskiewicz
Date: 2014-07-01 21:53
To: dotNetRDF Developer Discussion and Feature Request
Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
On Tue, Jul 1, 2014 at 12:23 PM, son...@gm...
<son...@gm...> wrote:
> Thank you Tom!
>
> You are right, basically what I am trying to do is converting following
> class:
> -------------------------------------
> class MyClass01 {
> public string Property01 {get; set;}
> public MyClass02 myClass02 {get; set;}
> }
> //the instance of class has its own unique id
>
I strongly suggest that you think in terms of triples or graphs and
not their serializaitions. So given an instance of MyClass01 you could
have the following data
<MyClass01Id> <hasProperty01> "the value of this property".
<MyClass01Id> <hasMyClass02> <MyClass02Id> .
This is all you need. These two triples would be stored the way you
used in the earlier email (remember to use proper URIs). I know
nothing about MyClass02 at this point, just the hypothetical id. It
would add further similar triples
Notice how this notation (NTriples/Turtle) removes any unnecessary
syntactic clutter and leaves only the subjects, predicates and
objects.
>
> -------------------------------------
> to this kind of text
> -------------------------------------
> <rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#
> xmlns:KB="http://protege.stanford.edu/kb#">
> <KB:MyClass01 rdf:about="that unique id">
> <hasProperty01 >the value of this property</hasProperty01>
> <MyClass02 rdf:about="the unique id">
> //MyClass02's content
> </MyClass02>
> </KB:EndToEndBlueprintRoot>
> </rdf:RDF>
> -------------------------------------
>
You must keep in mind that with RDF/XML there are multiple ways to
write the same document. It means that the structure can change, while
the actual data doesn't.
>
> Also I have to use this kind of format because it is the input of another
> system I have to use...
>
In memory you keep the data (triples) and dotNetRDF helps you save it
in one of the RDF formats. If the other system requires that you use
RDF/XML, that's fine but you could save it as Turtle or Notation3.
>
> Thank you again!
>
> ________________________________
> son...@gm...
>
> From: Tomasz Pluskiewicz
> Date: 2014-07-01 10:13
> To: dotNetRDF Developer Discussion and Feature Request
> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
> On Tue, Jul 1, 2014 at 7:44 AM, son...@gm...
> <son...@gm...> wrote:
>> Hi, all
>>
>> I am trying to write a RDF/XML like follows:
>> -------------------------------------------------------
>> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>> xmlns:KB="http://protege.stanford.edu/kb#">
>> <KB:EndToEndBlueprintRoot
>> rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001">
>> xxxxx
>> </KB:EndToEndBlueprintRoot>
>> </rdf:RDF>
>> -------------------------------------------------------
>>
>
> First of all this document is not a valid RDF/XML.
>
>> Here is my code
>> -------------------------------------------------------
>> INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot");
>> INode p = g.CreateUriNode("rdf:about");
>> INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001");
>>
>> g.Assert(new Triple(s,p,o));
>>
>> RdfXmlWriter rxw = new RdfXmlWriter();
>> string res = VDS.RDF.Writing.StringWriter.Write(g, rxw);
>> -------------------------------------------------------
>>
>
> Secondly, the rdf:about is just a RDF/XML syntax feature and not a
> predicate. It denotes that part of an RDF/XML document is grouped with
> a common subject. Please read [1].
>
> You should think in terms of triples, which define a relation
> (predicate) between two objects (subjects and objects). That is much
> like in natural language.
>
>>
>> But only got this
>> -------------------------------------------------------
>> <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://example.org/"
>> xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>> xmlns:kb="http://protege.stanford.edu/kb#"
>> xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
>> <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot">
>> xxx
>> <ns3:about xmlns:ns3="http://protege.stanford.edu/system#"
>> rdf:resource="&kb;DemoRootImagineID001" />
>> </rdf:Description>
>> </rdf:RDF>
>> -------------------------------------------------------
>>
>> Is my usage correct? or how can I output the format that I want?
>> What is the appropriate writing of "rdf:about"?
>>
>
> You probably mean kb:DemoRootImagineID001 as you subject, that is the
> thing you want to describe in your document. Is that right?
>
> Please describe what kind of data you want your document to contain.
>
>>
>> Any suggestion will be appreciated!
>>
>> ________________________________
>> son...@gm...
>>
>
> Regards,
> Tom
>
> [1]
> http://stackoverflow.com/questions/7118326/differences-between-rdfresource-rdfabout-and-rdfid
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
dotNetRDF-develop mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2014-07-03 09:09:39
|
Thanks Tom Now failing with different errors but I think that is just because I need to IFDEF out some of the new tests I added based on your recent NQuadsWriter bug for the PCL tests because they rely on LoadFromFile() which isn't available in the PCL builds Rob On 03/07/2014 10:00, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >I tried some more with intalling Phone SDK 8.0, which allegedly >contains the missing profile, but the setup package fails every time. > >I copied the folder. Running build now. > >Tom > >On Thu, Jul 3, 2014 at 10:13 AM, Rob Vesse <rv...@do...> wrote: >> That sounds about right, not the first thing I've run into where copy >>from >> working machine to non-working machine was the solution >> >> Rob >> >> On 02/07/2014 13:03, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>I wouldn't worry about the warning per se, because the build fails >>>anyway. >>> >>>I tried reinstalling the PCL Tools but Profile136 is stil missing. >>>Actually it's a problem people have and some suggest simply copying >>>the profile folder from dev machine. Gotta love Microsoft right? >>> >>>On Wed, Jul 2, 2014 at 11:37 AM, Rob Vesse <rv...@do...> wrote: >>>> Hmmm, turns out you can't have the MSBuild warning treated as an error >>>> because the WarningsAsError functionality only applies to compiler >>>>warnings >>>> not MSBuild warnings >>>> >>>> When I tried to mark the relevant MSBuild warnings MSB3644 and MSB3245 >>>>as >>>> errors they still just print as warnings and now the compiler >>>>complains >>>>that >>>> they aren't valid warning numbers: >>>> >>>> [11:24:47][Libraries\core\portable\dotNetRDF.Portable.csproj] >>>> GetReferenceAssemblyPaths >>>> [11:24:47][GetReferenceAssemblyPaths] GetReferenceAssemblyPaths >>>> [11:24:47][GetReferenceAssemblyPaths] >>>> >>>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets( >>>>84 >>>>7, >>>> 9): warning MSB3644: The reference assemblies for framework >>>> ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To >>>>resolve >>>> this, install the SDK or Targeting Pack for this framework version or >>>> retarget your application to a version of the framework for which you >>>>have >>>> the SDK or Targeting Pack installed. Note that assemblies will be >>>>resolved >>>> from the Global Assembly Cache (GAC) and will be used in place of >>>>reference >>>> assemblies. Therefore your assembly may not be correctly targeted for >>>>the >>>> framework you intend. >>>> [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] >>>> ResolveAssemblyReferences >>>> [11:24:48][ResolveAssemblyReferences] ResolveAssemblyReference >>>> [11:24:48][ResolveAssemblyReference] >>>> >>>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets( >>>>13 >>>>60, >>>> 9): warning MSB3245: Could not resolve this reference. Could not >>>>locate >>>>the >>>> assembly "System". Check to make sure the assembly exists on disk. If >>>>this >>>> reference is required by your code, you may get compilation errors. >>>> [11:24:48][ResolveAssemblyReference] >>>> >>>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets( >>>>13 >>>>60, >>>> 9): warning MSB3245: Could not resolve this reference. Could not >>>>locate >>>>the >>>> assembly "System.Net". Check to make sure the assembly exists on disk. >>>>If >>>> this reference is required by your code, you may get compilation >>>>errors. >>>> [11:24:48][ResolveAssemblyReference] >>>> >>>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets( >>>>13 >>>>60, >>>> 9): warning MSB3245: Could not resolve this reference. Could not >>>>locate >>>>the >>>> assembly "System.Xml". Check to make sure the assembly exists on disk. >>>>If >>>> this reference is required by your code, you may get compilation >>>>errors. >>>> [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] >>>>CoreCompile >>>> (3s) >>>> [11:24:48][CoreCompile] Csc (3s) >>>> [11:24:49][Csc] CSC warning CS1691: '3245' is not a valid warning >>>>number >>>> [11:24:49][Csc] CSC warning CS1691: '3644' is not a valid warning >>>>number >>>> >>>> >>>> So we still need to figure out what is missing on the TeamCity server >>>>that >>>> prevents the PCL build from building and we'll still get the unhelpful >>>> compilation errors hiding the true error message >>>> >>>> Rob >>>> >>>> On 02/07/2014 10:16, "Rob Vesse" <rv...@do...> wrote: >>>> >>>> If you dig into the tree view build log you will still see the same >>>>error >>>> message - >>>> >>>>http://ci.dotnetrdf.org/viewLog.html?buildId=1009&buildTypeId=bt2&tab=b >>>>ui >>>>ld >>>> Log#_focus=4578 >>>> >>>> Profile 136 is described as the following - .NET Portable Subset (.NET >>>> Framework 4, Silverlight 5, Windows 8, Windows Phone Silverlight 8) - >>>>so >>>> it may be that Silverlight 5, Windows 8 and Windows Phone Silverlight >>>>8 >>>> SDKs are also required >>>> >>>> Annonying the "error" I mention is only a warning by default, I will >>>>look >>>> at editing that project to make it an error so the true error shows up >>>>in >>>> the log overview rather than having to dig through the tree view log >>>>to >>>> find it >>>> >>>> Rob >>>> >>>> On 01/07/2014 20:02, "Tomasz Pluskiewicz" >>>><tom...@gm...> >>>> wrote: >>>> >>>> Hi Rob >>>> >>>> I installed the PCL update but now TeamCity fails with a swath of >>>> missing types and anmespaces including System.Uri and System.Xml. Is >>>> there something I must install or reconfigure? >>>> >>>> Tom >>>> >>>> On Tue, Jul 1, 2014 at 4:56 PM, Rob Vesse <rv...@do...> >>>>wrote: >>>> >>>> Tom >>>> >>>> I've noticed that with the 1.0.5 changes to our PCL targets the PCL >>>> libraries no longer build and the following warning is given in the >>>> build >>>> logs: >>>> >>>> [GetReferenceAssemblyPaths] >>>> >>>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets( >>>>84 >>>> 7, >>>> 9): warning MSB3644: The reference assemblies for framework >>>> ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To >>>> resolve >>>> this, install the SDK or Targeting Pack for this framework version or >>>> retarget your application to a version of the framework for which you >>>> have >>>> the SDK or Targeting Pack installed. Note that assemblies will be >>>> resolved >>>> from the Global Assembly Cache (GAC) and will be used in place of >>>> reference >>>> assemblies. Therefore your assembly may not be correctly targeted for >>>> the >>>> framework you intend. >>>> >>>> Can you please install the necessary PCL targeting pack so we can get >>>> things >>>> building on TeamCity again? >>>> >>>> Thanks, >>>> >>>> Rob >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>> ----- >>>> Open source business process management suite built on Java and >>>>Eclipse >>>> Turn processes into business applications with Bonita BPM Community >>>> Edition >>>> Quickly connect people, data, and systems into organized workflows >>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>>> http://p.sf.net/sfu/Bonitasoft >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>- >>>> ---- >>>> Open source business process management suite built on Java and >>>>Eclipse >>>> Turn processes into business applications with Bonita BPM Community >>>> Edition >>>> Quickly connect people, data, and systems into organized workflows >>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>>> http://p.sf.net/sfu/Bonitasoft >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>----- >>>> Open source business process management suite built on Java and >>>>Eclipse >>>> Turn processes into business applications with Bonita BPM Community >>>>Edition >>>> Quickly connect people, data, and systems into organized workflows >>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>>> http://p.sf.net/sfu/Bonitasoft >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>>> >>>> >>>>----------------------------------------------------------------------- >>>>-- >>>>----- >>>> Open source business process management suite built on Java and >>>>Eclipse >>>> Turn processes into business applications with Bonita BPM Community >>>>Edition >>>> Quickly connect people, data, and systems into organized workflows >>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>>> http://p.sf.net/sfu/Bonitasoft >>>> _______________________________________________ >>>> dotNetRDF-develop mailing list >>>> dot...@li... >>>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>>> >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Open source business process management suite built on Java and Eclipse >>>Turn processes into business applications with Bonita BPM Community >>>Edition >>>Quickly connect people, data, and systems into organized workflows >>>Winner of BOSSIE, CODIE, OW2 and Gartner awards >>>http://p.sf.net/sfu/Bonitasoft >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >>Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Open source business process management suite built on Java and Eclipse >Turn processes into business applications with Bonita BPM Community >Edition >Quickly connect people, data, and systems into organized workflows >Winner of BOSSIE, CODIE, OW2 and Gartner awards >http://p.sf.net/sfu/Bonitasoft >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2014-07-03 09:01:12
|
I tried some more with intalling Phone SDK 8.0, which allegedly contains the missing profile, but the setup package fails every time. I copied the folder. Running build now. Tom On Thu, Jul 3, 2014 at 10:13 AM, Rob Vesse <rv...@do...> wrote: > That sounds about right, not the first thing I've run into where copy from > working machine to non-working machine was the solution > > Rob > > On 02/07/2014 13:03, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>I wouldn't worry about the warning per se, because the build fails anyway. >> >>I tried reinstalling the PCL Tools but Profile136 is stil missing. >>Actually it's a problem people have and some suggest simply copying >>the profile folder from dev machine. Gotta love Microsoft right? >> >>On Wed, Jul 2, 2014 at 11:37 AM, Rob Vesse <rv...@do...> wrote: >>> Hmmm, turns out you can't have the MSBuild warning treated as an error >>> because the WarningsAsError functionality only applies to compiler >>>warnings >>> not MSBuild warnings >>> >>> When I tried to mark the relevant MSBuild warnings MSB3644 and MSB3245 >>>as >>> errors they still just print as warnings and now the compiler complains >>>that >>> they aren't valid warning numbers: >>> >>> [11:24:47][Libraries\core\portable\dotNetRDF.Portable.csproj] >>> GetReferenceAssemblyPaths >>> [11:24:47][GetReferenceAssemblyPaths] GetReferenceAssemblyPaths >>> [11:24:47][GetReferenceAssemblyPaths] >>> >>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(84 >>>7, >>> 9): warning MSB3644: The reference assemblies for framework >>> ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To >>>resolve >>> this, install the SDK or Targeting Pack for this framework version or >>> retarget your application to a version of the framework for which you >>>have >>> the SDK or Targeting Pack installed. Note that assemblies will be >>>resolved >>> from the Global Assembly Cache (GAC) and will be used in place of >>>reference >>> assemblies. Therefore your assembly may not be correctly targeted for >>>the >>> framework you intend. >>> [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] >>> ResolveAssemblyReferences >>> [11:24:48][ResolveAssemblyReferences] ResolveAssemblyReference >>> [11:24:48][ResolveAssemblyReference] >>> >>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(13 >>>60, >>> 9): warning MSB3245: Could not resolve this reference. Could not locate >>>the >>> assembly "System". Check to make sure the assembly exists on disk. If >>>this >>> reference is required by your code, you may get compilation errors. >>> [11:24:48][ResolveAssemblyReference] >>> >>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(13 >>>60, >>> 9): warning MSB3245: Could not resolve this reference. Could not locate >>>the >>> assembly "System.Net". Check to make sure the assembly exists on disk. >>>If >>> this reference is required by your code, you may get compilation errors. >>> [11:24:48][ResolveAssemblyReference] >>> >>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(13 >>>60, >>> 9): warning MSB3245: Could not resolve this reference. Could not locate >>>the >>> assembly "System.Xml". Check to make sure the assembly exists on disk. >>>If >>> this reference is required by your code, you may get compilation errors. >>> [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] >>>CoreCompile >>> (3s) >>> [11:24:48][CoreCompile] Csc (3s) >>> [11:24:49][Csc] CSC warning CS1691: '3245' is not a valid warning number >>> [11:24:49][Csc] CSC warning CS1691: '3644' is not a valid warning number >>> >>> >>> So we still need to figure out what is missing on the TeamCity server >>>that >>> prevents the PCL build from building and we'll still get the unhelpful >>> compilation errors hiding the true error message >>> >>> Rob >>> >>> On 02/07/2014 10:16, "Rob Vesse" <rv...@do...> wrote: >>> >>> If you dig into the tree view build log you will still see the same >>>error >>> message - >>> >>>http://ci.dotnetrdf.org/viewLog.html?buildId=1009&buildTypeId=bt2&tab=bui >>>ld >>> Log#_focus=4578 >>> >>> Profile 136 is described as the following - .NET Portable Subset (.NET >>> Framework 4, Silverlight 5, Windows 8, Windows Phone Silverlight 8) - so >>> it may be that Silverlight 5, Windows 8 and Windows Phone Silverlight 8 >>> SDKs are also required >>> >>> Annonying the "error" I mention is only a warning by default, I will >>>look >>> at editing that project to make it an error so the true error shows up >>>in >>> the log overview rather than having to dig through the tree view log to >>> find it >>> >>> Rob >>> >>> On 01/07/2014 20:02, "Tomasz Pluskiewicz" <tom...@gm...> >>> wrote: >>> >>> Hi Rob >>> >>> I installed the PCL update but now TeamCity fails with a swath of >>> missing types and anmespaces including System.Uri and System.Xml. Is >>> there something I must install or reconfigure? >>> >>> Tom >>> >>> On Tue, Jul 1, 2014 at 4:56 PM, Rob Vesse <rv...@do...> wrote: >>> >>> Tom >>> >>> I've noticed that with the 1.0.5 changes to our PCL targets the PCL >>> libraries no longer build and the following warning is given in the >>> build >>> logs: >>> >>> [GetReferenceAssemblyPaths] >>> >>>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(84 >>> 7, >>> 9): warning MSB3644: The reference assemblies for framework >>> ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To >>> resolve >>> this, install the SDK or Targeting Pack for this framework version or >>> retarget your application to a version of the framework for which you >>> have >>> the SDK or Targeting Pack installed. Note that assemblies will be >>> resolved >>> from the Global Assembly Cache (GAC) and will be used in place of >>> reference >>> assemblies. Therefore your assembly may not be correctly targeted for >>> the >>> framework you intend. >>> >>> Can you please install the necessary PCL targeting pack so we can get >>> things >>> building on TeamCity again? >>> >>> Thanks, >>> >>> Rob >>> >>> >>>------------------------------------------------------------------------- >>> ----- >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>> Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> >>>------------------------------------------------------------------------- >>>- >>> ---- >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>> Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> >>> >>> >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>>Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>>Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >>-------------------------------------------------------------------------- >>---- >>Open source business process management suite built on Java and Eclipse >>Turn processes into business applications with Bonita BPM Community >>Edition >>Quickly connect people, data, and systems into organized workflows >>Winner of BOSSIE, CODIE, OW2 and Gartner awards >>http://p.sf.net/sfu/Bonitasoft >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2014-07-03 08:14:16
|
That sounds about right, not the first thing I've run into where copy from working machine to non-working machine was the solution Rob On 02/07/2014 13:03, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >I wouldn't worry about the warning per se, because the build fails anyway. > >I tried reinstalling the PCL Tools but Profile136 is stil missing. >Actually it's a problem people have and some suggest simply copying >the profile folder from dev machine. Gotta love Microsoft right? > >On Wed, Jul 2, 2014 at 11:37 AM, Rob Vesse <rv...@do...> wrote: >> Hmmm, turns out you can't have the MSBuild warning treated as an error >> because the WarningsAsError functionality only applies to compiler >>warnings >> not MSBuild warnings >> >> When I tried to mark the relevant MSBuild warnings MSB3644 and MSB3245 >>as >> errors they still just print as warnings and now the compiler complains >>that >> they aren't valid warning numbers: >> >> [11:24:47][Libraries\core\portable\dotNetRDF.Portable.csproj] >> GetReferenceAssemblyPaths >> [11:24:47][GetReferenceAssemblyPaths] GetReferenceAssemblyPaths >> [11:24:47][GetReferenceAssemblyPaths] >> >>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(84 >>7, >> 9): warning MSB3644: The reference assemblies for framework >> ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To >>resolve >> this, install the SDK or Targeting Pack for this framework version or >> retarget your application to a version of the framework for which you >>have >> the SDK or Targeting Pack installed. Note that assemblies will be >>resolved >> from the Global Assembly Cache (GAC) and will be used in place of >>reference >> assemblies. Therefore your assembly may not be correctly targeted for >>the >> framework you intend. >> [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] >> ResolveAssemblyReferences >> [11:24:48][ResolveAssemblyReferences] ResolveAssemblyReference >> [11:24:48][ResolveAssemblyReference] >> >>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(13 >>60, >> 9): warning MSB3245: Could not resolve this reference. Could not locate >>the >> assembly "System". Check to make sure the assembly exists on disk. If >>this >> reference is required by your code, you may get compilation errors. >> [11:24:48][ResolveAssemblyReference] >> >>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(13 >>60, >> 9): warning MSB3245: Could not resolve this reference. Could not locate >>the >> assembly "System.Net". Check to make sure the assembly exists on disk. >>If >> this reference is required by your code, you may get compilation errors. >> [11:24:48][ResolveAssemblyReference] >> >>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(13 >>60, >> 9): warning MSB3245: Could not resolve this reference. Could not locate >>the >> assembly "System.Xml". Check to make sure the assembly exists on disk. >>If >> this reference is required by your code, you may get compilation errors. >> [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] >>CoreCompile >> (3s) >> [11:24:48][CoreCompile] Csc (3s) >> [11:24:49][Csc] CSC warning CS1691: '3245' is not a valid warning number >> [11:24:49][Csc] CSC warning CS1691: '3644' is not a valid warning number >> >> >> So we still need to figure out what is missing on the TeamCity server >>that >> prevents the PCL build from building and we'll still get the unhelpful >> compilation errors hiding the true error message >> >> Rob >> >> On 02/07/2014 10:16, "Rob Vesse" <rv...@do...> wrote: >> >> If you dig into the tree view build log you will still see the same >>error >> message - >> >>http://ci.dotnetrdf.org/viewLog.html?buildId=1009&buildTypeId=bt2&tab=bui >>ld >> Log#_focus=4578 >> >> Profile 136 is described as the following - .NET Portable Subset (.NET >> Framework 4, Silverlight 5, Windows 8, Windows Phone Silverlight 8) - so >> it may be that Silverlight 5, Windows 8 and Windows Phone Silverlight 8 >> SDKs are also required >> >> Annonying the "error" I mention is only a warning by default, I will >>look >> at editing that project to make it an error so the true error shows up >>in >> the log overview rather than having to dig through the tree view log to >> find it >> >> Rob >> >> On 01/07/2014 20:02, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >> Hi Rob >> >> I installed the PCL update but now TeamCity fails with a swath of >> missing types and anmespaces including System.Uri and System.Xml. Is >> there something I must install or reconfigure? >> >> Tom >> >> On Tue, Jul 1, 2014 at 4:56 PM, Rob Vesse <rv...@do...> wrote: >> >> Tom >> >> I've noticed that with the 1.0.5 changes to our PCL targets the PCL >> libraries no longer build and the following warning is given in the >> build >> logs: >> >> [GetReferenceAssemblyPaths] >> >>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(84 >> 7, >> 9): warning MSB3644: The reference assemblies for framework >> ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To >> resolve >> this, install the SDK or Targeting Pack for this framework version or >> retarget your application to a version of the framework for which you >> have >> the SDK or Targeting Pack installed. Note that assemblies will be >> resolved >> from the Global Assembly Cache (GAC) and will be used in place of >> reference >> assemblies. Therefore your assembly may not be correctly targeted for >> the >> framework you intend. >> >> Can you please install the necessary PCL targeting pack so we can get >> things >> building on TeamCity again? >> >> Thanks, >> >> Rob >> >> >>------------------------------------------------------------------------- >> ----- >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >> Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >>------------------------------------------------------------------------- >>- >> ---- >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >> Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >>Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >>------------------------------------------------------------------------- >>----- >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >>Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Open source business process management suite built on Java and Eclipse >Turn processes into business applications with Bonita BPM Community >Edition >Quickly connect people, data, and systems into organized workflows >Winner of BOSSIE, CODIE, OW2 and Gartner awards >http://p.sf.net/sfu/Bonitasoft >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <tr...@do...> - 2014-07-02 20:52:10
|
<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>SparqlJsonParser fails to parse results of ASK queries with atypical ordering</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>dwatts</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Parsing</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Unassigned</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 "boolean" exists before "head" in the JSON response for an ASK query, an error is thrown when attempting to parse. This is happening with the latest snapshot of the code as of 7/2/2014.</p>
<p>
For example:</p>
<p>
var data = @"{""boolean"": false, ""head"": {""link"": []}}";<br />
var results = new SparqlResultSet();<br />
using (var reader = new StringReader(data))<br />
{<br />
var parser = new SparqlJsonParser();<br />
parser.Load(results, reader);<br />
}</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=423" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=423</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-07-02 12:04:33
|
I wouldn't worry about the warning per se, because the build fails anyway. I tried reinstalling the PCL Tools but Profile136 is stil missing. Actually it's a problem people have and some suggest simply copying the profile folder from dev machine. Gotta love Microsoft right? On Wed, Jul 2, 2014 at 11:37 AM, Rob Vesse <rv...@do...> wrote: > Hmmm, turns out you can't have the MSBuild warning treated as an error > because the WarningsAsError functionality only applies to compiler warnings > not MSBuild warnings > > When I tried to mark the relevant MSBuild warnings MSB3644 and MSB3245 as > errors they still just print as warnings and now the compiler complains that > they aren't valid warning numbers: > > [11:24:47][Libraries\core\portable\dotNetRDF.Portable.csproj] > GetReferenceAssemblyPaths > [11:24:47][GetReferenceAssemblyPaths] GetReferenceAssemblyPaths > [11:24:47][GetReferenceAssemblyPaths] > C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(847, > 9): warning MSB3644: The reference assemblies for framework > ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To resolve > this, install the SDK or Targeting Pack for this framework version or > retarget your application to a version of the framework for which you have > the SDK or Targeting Pack installed. Note that assemblies will be resolved > from the Global Assembly Cache (GAC) and will be used in place of reference > assemblies. Therefore your assembly may not be correctly targeted for the > framework you intend. > [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] > ResolveAssemblyReferences > [11:24:48][ResolveAssemblyReferences] ResolveAssemblyReference > [11:24:48][ResolveAssemblyReference] > C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360, > 9): warning MSB3245: Could not resolve this reference. Could not locate the > assembly "System". Check to make sure the assembly exists on disk. If this > reference is required by your code, you may get compilation errors. > [11:24:48][ResolveAssemblyReference] > C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360, > 9): warning MSB3245: Could not resolve this reference. Could not locate the > assembly "System.Net". Check to make sure the assembly exists on disk. If > this reference is required by your code, you may get compilation errors. > [11:24:48][ResolveAssemblyReference] > C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360, > 9): warning MSB3245: Could not resolve this reference. Could not locate the > assembly "System.Xml". Check to make sure the assembly exists on disk. If > this reference is required by your code, you may get compilation errors. > [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] CoreCompile > (3s) > [11:24:48][CoreCompile] Csc (3s) > [11:24:49][Csc] CSC warning CS1691: '3245' is not a valid warning number > [11:24:49][Csc] CSC warning CS1691: '3644' is not a valid warning number > > > So we still need to figure out what is missing on the TeamCity server that > prevents the PCL build from building and we'll still get the unhelpful > compilation errors hiding the true error message > > Rob > > On 02/07/2014 10:16, "Rob Vesse" <rv...@do...> wrote: > > If you dig into the tree view build log you will still see the same error > message - > http://ci.dotnetrdf.org/viewLog.html?buildId=1009&buildTypeId=bt2&tab=build > Log#_focus=4578 > > Profile 136 is described as the following - .NET Portable Subset (.NET > Framework 4, Silverlight 5, Windows 8, Windows Phone Silverlight 8) - so > it may be that Silverlight 5, Windows 8 and Windows Phone Silverlight 8 > SDKs are also required > > Annonying the "error" I mention is only a warning by default, I will look > at editing that project to make it an error so the true error shows up in > the log overview rather than having to dig through the tree view log to > find it > > Rob > > On 01/07/2014 20:02, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > > Hi Rob > > I installed the PCL update but now TeamCity fails with a swath of > missing types and anmespaces including System.Uri and System.Xml. Is > there something I must install or reconfigure? > > Tom > > On Tue, Jul 1, 2014 at 4:56 PM, Rob Vesse <rv...@do...> wrote: > > Tom > > I've noticed that with the 1.0.5 changes to our PCL targets the PCL > libraries no longer build and the following warning is given in the > build > logs: > > [GetReferenceAssemblyPaths] > C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(84 > 7, > 9): warning MSB3644: The reference assemblies for framework > ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To > resolve > this, install the SDK or Targeting Pack for this framework version or > retarget your application to a version of the framework for which you > have > the SDK or Targeting Pack installed. Note that assemblies will be > resolved > from the Global Assembly Cache (GAC) and will be used in place of > reference > assemblies. Therefore your assembly may not be correctly targeted for > the > framework you intend. > > Can you please install the necessary PCL targeting pack so we can get > things > building on TeamCity again? > > Thanks, > > Rob > > ------------------------------------------------------------------------- > ----- > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community > Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > -------------------------------------------------------------------------- > ---- > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community > Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2014-07-02 09:38:00
|
Hmmm, turns out you can't have the MSBuild warning treated as an error because the WarningsAsError functionality only applies to compiler warnings not MSBuild warnings When I tried to mark the relevant MSBuild warnings MSB3644 and MSB3245 as errors they still just print as warnings and now the compiler complains that they aren't valid warning numbers: [11:24:47][Libraries\core\portable\dotNetRDF.Portable.csproj] GetReferenceAssemblyPaths [11:24:47][GetReferenceAssemblyPaths] GetReferenceAssemblyPaths [11:24:47][GetReferenceAssemblyPaths] C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(847, 9): warning MSB3644: The reference assemblies for framework ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] ResolveAssemblyReferences [11:24:48][ResolveAssemblyReferences] ResolveAssemblyReference [11:24:48][ResolveAssemblyReference] C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360, 9): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [11:24:48][ResolveAssemblyReference] C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360, 9): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Net". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [11:24:48][ResolveAssemblyReference] C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360, 9): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Xml". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [11:24:48][Libraries\core\portable\dotNetRDF.Portable.csproj] CoreCompile (3s) [11:24:48][CoreCompile] Csc (3s) [11:24:49][Csc] CSC warning CS1691: '3245' is not a valid warning number [11:24:49][Csc] CSC warning CS1691: '3644' is not a valid warning number So we still need to figure out what is missing on the TeamCity server that prevents the PCL build from building and we'll still get the unhelpful compilation errors hiding the true error message Rob On 02/07/2014 10:16, "Rob Vesse" <rv...@do...> wrote: > If you dig into the tree view build log you will still see the same error > message - > http://ci.dotnetrdf.org/viewLog.html?buildId=1009&buildTypeId=bt2&tab=build > Log#_focus=4578 > > Profile 136 is described as the following - .NET Portable Subset (.NET > Framework 4, Silverlight 5, Windows 8, Windows Phone Silverlight 8) - so > it may be that Silverlight 5, Windows 8 and Windows Phone Silverlight 8 > SDKs are also required > > Annonying the "error" I mention is only a warning by default, I will look > at editing that project to make it an error so the true error shows up in > the log overview rather than having to dig through the tree view log to > find it > > Rob > > On 01/07/2014 20:02, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >> Hi Rob >> >> I installed the PCL update but now TeamCity fails with a swath of >> missing types and anmespaces including System.Uri and System.Xml. Is >> there something I must install or reconfigure? >> >> Tom >> >> On Tue, Jul 1, 2014 at 4:56 PM, Rob Vesse <rv...@do...> wrote: >>> Tom >>> >>> I've noticed that with the 1.0.5 changes to our PCL targets the PCL >>> libraries no longer build and the following warning is given in the >>> build >>> logs: >>> >>> [GetReferenceAssemblyPaths] >>> >>> C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(84 >>> 7, >>> 9): warning MSB3644: The reference assemblies for framework >>> ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To >>> resolve >>> this, install the SDK or Targeting Pack for this framework version or >>> retarget your application to a version of the framework for which you >>> have >>> the SDK or Targeting Pack installed. Note that assemblies will be >>> resolved >>> from the Global Assembly Cache (GAC) and will be used in place of >>> reference >>> assemblies. Therefore your assembly may not be correctly targeted for >>> the >>> framework you intend. >>> >>> Can you please install the necessary PCL targeting pack so we can get >>> things >>> building on TeamCity again? >>> >>> Thanks, >>> >>> Rob >>> >>> >>> ------------------------------------------------------------------------- >>> ----- >>> Open source business process management suite built on Java and Eclipse >>> Turn processes into business applications with Bonita BPM Community >>> Edition >>> Quickly connect people, data, and systems into organized workflows >>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>> http://p.sf.net/sfu/Bonitasoft >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >> >> -------------------------------------------------------------------------- >> ---- >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >> Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2014-07-02 09:17:06
|
If you dig into the tree view build log you will still see the same error message - http://ci.dotnetrdf.org/viewLog.html?buildId=1009&buildTypeId=bt2&tab=build Log#_focus=4578 Profile 136 is described as the following - .NET Portable Subset (.NET Framework 4, Silverlight 5, Windows 8, Windows Phone Silverlight 8) - so it may be that Silverlight 5, Windows 8 and Windows Phone Silverlight 8 SDKs are also required Annonying the "error" I mention is only a warning by default, I will look at editing that project to make it an error so the true error shows up in the log overview rather than having to dig through the tree view log to find it Rob On 01/07/2014 20:02, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Rob > >I installed the PCL update but now TeamCity fails with a swath of >missing types and anmespaces including System.Uri and System.Xml. Is >there something I must install or reconfigure? > >Tom > >On Tue, Jul 1, 2014 at 4:56 PM, Rob Vesse <rv...@do...> wrote: >> Tom >> >> I've noticed that with the 1.0.5 changes to our PCL targets the PCL >> libraries no longer build and the following warning is given in the >>build >> logs: >> >> [GetReferenceAssemblyPaths] >> >>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(84 >>7, >> 9): warning MSB3644: The reference assemblies for framework >> ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To >>resolve >> this, install the SDK or Targeting Pack for this framework version or >> retarget your application to a version of the framework for which you >>have >> the SDK or Targeting Pack installed. Note that assemblies will be >>resolved >> from the Global Assembly Cache (GAC) and will be used in place of >>reference >> assemblies. Therefore your assembly may not be correctly targeted for >>the >> framework you intend. >> >> Can you please install the necessary PCL targeting pack so we can get >>things >> building on TeamCity again? >> >> Thanks, >> >> Rob >> >> >>------------------------------------------------------------------------- >>----- >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community >>Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> > >-------------------------------------------------------------------------- >---- >Open source business process management suite built on Java and Eclipse >Turn processes into business applications with Bonita BPM Community >Edition >Quickly connect people, data, and systems into organized workflows >Winner of BOSSIE, CODIE, OW2 and Gartner awards >http://p.sf.net/sfu/Bonitasoft >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2014-07-01 20:54:47
|
On Tue, Jul 1, 2014 at 12:23 PM, son...@gm...
<son...@gm...> wrote:
> Thank you Tom!
>
> You are right, basically what I am trying to do is converting following
> class:
> -------------------------------------
> class MyClass01 {
> public string Property01 {get; set;}
> public MyClass02 myClass02 {get; set;}
> }
> //the instance of class has its own unique id
>
I strongly suggest that you think in terms of triples or graphs and
not their serializaitions. So given an instance of MyClass01 you could
have the following data
<MyClass01Id> <hasProperty01> "the value of this property".
<MyClass01Id> <hasMyClass02> <MyClass02Id> .
This is all you need. These two triples would be stored the way you
used in the earlier email (remember to use proper URIs). I know
nothing about MyClass02 at this point, just the hypothetical id. It
would add further similar triples
Notice how this notation (NTriples/Turtle) removes any unnecessary
syntactic clutter and leaves only the subjects, predicates and
objects.
>
> -------------------------------------
> to this kind of text
> -------------------------------------
> <rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#
> xmlns:KB="http://protege.stanford.edu/kb#">
> <KB:MyClass01 rdf:about="that unique id">
> <hasProperty01 >the value of this property</hasProperty01>
> <MyClass02 rdf:about="the unique id">
> //MyClass02's content
> </MyClass02>
> </KB:EndToEndBlueprintRoot>
> </rdf:RDF>
> -------------------------------------
>
You must keep in mind that with RDF/XML there are multiple ways to
write the same document. It means that the structure can change, while
the actual data doesn't.
>
> Also I have to use this kind of format because it is the input of another
> system I have to use...
>
In memory you keep the data (triples) and dotNetRDF helps you save it
in one of the RDF formats. If the other system requires that you use
RDF/XML, that's fine but you could save it as Turtle or Notation3.
>
> Thank you again!
>
> ________________________________
> son...@gm...
>
> From: Tomasz Pluskiewicz
> Date: 2014-07-01 10:13
> To: dotNetRDF Developer Discussion and Feature Request
> Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
> On Tue, Jul 1, 2014 at 7:44 AM, son...@gm...
> <son...@gm...> wrote:
>> Hi, all
>>
>> I am trying to write a RDF/XML like follows:
>> -------------------------------------------------------
>> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>> xmlns:KB="http://protege.stanford.edu/kb#">
>> <KB:EndToEndBlueprintRoot
>> rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001">
>> xxxxx
>> </KB:EndToEndBlueprintRoot>
>> </rdf:RDF>
>> -------------------------------------------------------
>>
>
> First of all this document is not a valid RDF/XML.
>
>> Here is my code
>> -------------------------------------------------------
>> INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot");
>> INode p = g.CreateUriNode("rdf:about");
>> INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001");
>>
>> g.Assert(new Triple(s,p,o));
>>
>> RdfXmlWriter rxw = new RdfXmlWriter();
>> string res = VDS.RDF.Writing.StringWriter.Write(g, rxw);
>> -------------------------------------------------------
>>
>
> Secondly, the rdf:about is just a RDF/XML syntax feature and not a
> predicate. It denotes that part of an RDF/XML document is grouped with
> a common subject. Please read [1].
>
> You should think in terms of triples, which define a relation
> (predicate) between two objects (subjects and objects). That is much
> like in natural language.
>
>>
>> But only got this
>> -------------------------------------------------------
>> <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://example.org/"
>> xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>> xmlns:kb="http://protege.stanford.edu/kb#"
>> xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
>> <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot">
>> xxx
>> <ns3:about xmlns:ns3="http://protege.stanford.edu/system#"
>> rdf:resource="&kb;DemoRootImagineID001" />
>> </rdf:Description>
>> </rdf:RDF>
>> -------------------------------------------------------
>>
>> Is my usage correct? or how can I output the format that I want?
>> What is the appropriate writing of "rdf:about"?
>>
>
> You probably mean kb:DemoRootImagineID001 as you subject, that is the
> thing you want to describe in your document. Is that right?
>
> Please describe what kind of data you want your document to contain.
>
>>
>> Any suggestion will be appreciated!
>>
>> ________________________________
>> son...@gm...
>>
>
> Regards,
> Tom
>
> [1]
> http://stackoverflow.com/questions/7118326/differences-between-rdfresource-rdfabout-and-rdfid
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> dotNetRDF-develop mailing list
> dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
>
|
|
From: Tomasz P. <tom...@gm...> - 2014-07-01 19:03:27
|
Hi Rob I installed the PCL update but now TeamCity fails with a swath of missing types and anmespaces including System.Uri and System.Xml. Is there something I must install or reconfigure? Tom On Tue, Jul 1, 2014 at 4:56 PM, Rob Vesse <rv...@do...> wrote: > Tom > > I've noticed that with the 1.0.5 changes to our PCL targets the PCL > libraries no longer build and the following warning is given in the build > logs: > > [GetReferenceAssemblyPaths] > C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(847, > 9): warning MSB3644: The reference assemblies for framework > ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To resolve > this, install the SDK or Targeting Pack for this framework version or > retarget your application to a version of the framework for which you have > the SDK or Targeting Pack installed. Note that assemblies will be resolved > from the Global Assembly Cache (GAC) and will be used in place of reference > assemblies. Therefore your assembly may not be correctly targeted for the > framework you intend. > > Can you please install the necessary PCL targeting pack so we can get things > building on TeamCity again? > > Thanks, > > Rob > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > |
|
From: Rob V. <rv...@do...> - 2014-07-01 14:57:09
|
Tom I've noticed that with the 1.0.5 changes to our PCL targets the PCL libraries no longer build and the following warning is given in the build logs: [GetReferenceAssemblyPaths] C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(847, 9): warning MSB3644: The reference assemblies for framework ".NETPortable,Version=v4.0,Profile=Profile136" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. Can you please install the necessary PCL targeting pack so we can get things building on TeamCity again? Thanks, Rob |
|
From: <son...@gm...> - 2014-07-01 10:23:55
|
Thank you Tom!
You are right, basically what I am trying to do is converting following class:
-------------------------------------
class MyClass01 {
public string Property01 {get; set;}
public MyClass02 myClass02 {get; set;}
}
//the instance of class has its own unique id
-------------------------------------
to this kind of text
-------------------------------------
<rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns# xmlns:KB="http://protege.stanford.edu/kb#">
<KB:MyClass01 rdf:about="that unique id">
<hasProperty01 >the value of this property</hasProperty01>
<MyClass02 rdf:about="the unique id">
//MyClass02's content
</MyClass02>
</KB:EndToEndBlueprintRoot>
</rdf:RDF>
-------------------------------------
Also I have to use this kind of format because it is the input of another system I have to use...
Thank you again!
son...@gm...
From: Tomasz Pluskiewicz
Date: 2014-07-01 10:13
To: dotNetRDF Developer Discussion and Feature Request
Subject: Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format
On Tue, Jul 1, 2014 at 7:44 AM, son...@gm...
<son...@gm...> wrote:
> Hi, all
>
> I am trying to write a RDF/XML like follows:
> -------------------------------------------------------
> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:KB="http://protege.stanford.edu/kb#">
> <KB:EndToEndBlueprintRoot
> rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001">
> xxxxx
> </KB:EndToEndBlueprintRoot>
> </rdf:RDF>
> -------------------------------------------------------
>
First of all this document is not a valid RDF/XML.
> Here is my code
> -------------------------------------------------------
> INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot");
> INode p = g.CreateUriNode("rdf:about");
> INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001");
>
> g.Assert(new Triple(s,p,o));
>
> RdfXmlWriter rxw = new RdfXmlWriter();
> string res = VDS.RDF.Writing.StringWriter.Write(g, rxw);
> -------------------------------------------------------
>
Secondly, the rdf:about is just a RDF/XML syntax feature and not a
predicate. It denotes that part of an RDF/XML document is grouped with
a common subject. Please read [1].
You should think in terms of triples, which define a relation
(predicate) between two objects (subjects and objects). That is much
like in natural language.
>
> But only got this
> -------------------------------------------------------
> <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://example.org/"
> xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:kb="http://protege.stanford.edu/kb#"
> xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
> <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot">
> xxx
> <ns3:about xmlns:ns3="http://protege.stanford.edu/system#"
> rdf:resource="&kb;DemoRootImagineID001" />
> </rdf:Description>
> </rdf:RDF>
> -------------------------------------------------------
>
> Is my usage correct? or how can I output the format that I want?
> What is the appropriate writing of "rdf:about"?
>
You probably mean kb:DemoRootImagineID001 as you subject, that is the
thing you want to describe in your document. Is that right?
Please describe what kind of data you want your document to contain.
>
> Any suggestion will be appreciated!
>
> ________________________________
> son...@gm...
>
Regards,
Tom
[1] http://stackoverflow.com/questions/7118326/differences-between-rdfresource-rdfabout-and-rdfid
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
dotNetRDF-develop mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2014-07-01 09:14:13
|
On Tue, Jul 1, 2014 at 7:44 AM, son...@gm... <son...@gm...> wrote: > Hi, all > > I am trying to write a RDF/XML like follows: > ------------------------------------------------------- > <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > xmlns:KB="http://protege.stanford.edu/kb#"> > <KB:EndToEndBlueprintRoot > rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001"> > xxxxx > </KB:EndToEndBlueprintRoot> > </rdf:RDF> > ------------------------------------------------------- > First of all this document is not a valid RDF/XML. > Here is my code > ------------------------------------------------------- > INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot"); > INode p = g.CreateUriNode("rdf:about"); > INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001"); > > g.Assert(new Triple(s,p,o)); > > RdfXmlWriter rxw = new RdfXmlWriter(); > string res = VDS.RDF.Writing.StringWriter.Write(g, rxw); > ------------------------------------------------------- > Secondly, the rdf:about is just a RDF/XML syntax feature and not a predicate. It denotes that part of an RDF/XML document is grouped with a common subject. Please read [1]. You should think in terms of triples, which define a relation (predicate) between two objects (subjects and objects). That is much like in natural language. > > But only got this > ------------------------------------------------------- > <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" > xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://example.org/" > xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > xmlns:kb="http://protege.stanford.edu/kb#" > xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> > <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot"> > xxx > <ns3:about xmlns:ns3="http://protege.stanford.edu/system#" > rdf:resource="&kb;DemoRootImagineID001" /> > </rdf:Description> > </rdf:RDF> > ------------------------------------------------------- > > Is my usage correct? or how can I output the format that I want? > What is the appropriate writing of "rdf:about"? > You probably mean kb:DemoRootImagineID001 as you subject, that is the thing you want to describe in your document. Is that right? Please describe what kind of data you want your document to contain. > > Any suggestion will be appreciated! > > ________________________________ > son...@gm... > Regards, Tom [1] http://stackoverflow.com/questions/7118326/differences-between-rdfresource-rdfabout-and-rdfid |
|
From: <son...@gm...> - 2014-07-01 05:44:36
|
Hi, all I am trying to write a RDF/XML like follows: ------------------------------------------------------- <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:KB="http://protege.stanford.edu/kb#"> <KB:EndToEndBlueprintRoot rdf:about="http://protege.stanford.edu/kb#DemoRootImagineID001"> xxxxx </KB:EndToEndBlueprintRoot> </rdf:RDF> ------------------------------------------------------- Here is my code ------------------------------------------------------- INode s = g.CreateUriNode("kb:"+"EndToEndBlueprintRoot"); INode p = g.CreateUriNode("rdf:about"); INode o = g.CreateUriNode("kb:"+"DemoRootImagineID001"); g.Assert(new Triple(s,p,o)); RdfXmlWriter rxw = new RdfXmlWriter(); string res = VDS.RDF.Writing.StringWriter.Write(g, rxw); ------------------------------------------------------- But only got this ------------------------------------------------------- <rdf:RDF xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://example.org/" xmlns:a="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:kb="http://protege.stanford.edu/kb#" xmlns:ns0="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="&kb;EndToEndBlueprintRoot"> xxx <ns3:about xmlns:ns3="http://protege.stanford.edu/system#" rdf:resource="&kb;DemoRootImagineID001" /> </rdf:Description> </rdf:RDF> ------------------------------------------------------- Is my usage correct? or how can I output the format that I want? What is the appropriate writing of "rdf:about"? Any suggestion will be appreciated! son...@gm... |
|
From: <tr...@do...> - 2014-06-30 13:16: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>Support custom parameters for SparqlRemoteEndpoint and SparqlRemoteUpdateEndpoint</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-06-30 02:15 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Bumping to unscheduled</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=396" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=396</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: Khalil A. <ka...@ne...> - 2014-06-30 11:39:20
|
Hi Rob, I totally understand the time that a release takes - I'm in a similar situation with BrightstarDB. I would certainly volunteer to make the 1.0.6 release now if I knew how to do it or had some steps to follow, so in the longer term moving to that situation would definitely be desirable. In the short term my problem is that the 1.0.5 release breaks quite a significant part of the LINQ-to-SPARQL implementation in BrightstarDB (as we rely on LIMIT in a subquery). The fix for that is now in develop, so a pre-release NuGet is actually all I need I think - I can easily update the BrightstarDB solutions and nuget packaging to require a 1.0.6 pre-release or later. That probably indicates that it might be a good idea to consider either: a) automating the publication of nuget pre-release packages as part of the TeamCity build or b) just documenting how to make a pre-release nuget package as a first step to documenting the whole release procedure. (a) might be the best way to go - the NuGet side of things is simpler than the full DNR package and automating the release would mean that the pre-release "channel" on nuget would always be the latest and greatest without you needing to do anything other than merge to develop. In fact having written this I'm going to look into doing just that with B*. I'm happy to help out with either of those things! Cheers Kal On Mon, Jun 30, 2014 at 11:53 AM, Rob Vesse <rv...@do...> wrote: > Kal > > I put a rough target date in the tracker which you can see on the Roadmap ( > http://dotnetrdf.org/tracker/Projects/Roadmap.aspx?pid=1) > > I am currently scheduling releases every 2 months so 1.0.6 is currently > scheduled for end of July. I can of course push out a pre-release build if > that is a usable option for you? > > I prefer not to do releases too often since a release takes on average > half a day to put together and publish *but* I only have half a day a > week to work on dotNetRDF so too frequent releases means I can't actually > get any fixes/new features done. > > Longer term the best way forward would be for me to make it possible for > other people to carry out all the necessary release steps (which requires > various bits of auth setup and documentation write up) so others can > volunteer to carry out releases. Since I've been working using branches > for all feature/bug fix development and only merging to default when things > are working therefore in principle with the necessary stuff done anyone > could cut a release when they see fit. Obviously if we want to move to > that model longer term then we likely need to have some process in place to > allow people to vote for/against a release e.g. if they have an important > bug they want to get a fix in for. > > Rob > > From: Kal Ahmed <ka...@ne...> > Date: Monday, 23 June 2014 09:17 > To: Rob Vesse <rv...@do...> > Subject: 1.0.6 release > > Hi Rob, > > Any thoughts on when a 1.0.6 release might be ready ? I'm just wondering > whether to make a B* release on 1.0.5 or wait for the bug fixes in 1.0.6. > > Cheers > > Kal > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com > > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > -- > Kal Ahmed > Director, Networked Planet Limited > e: <https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop> > kal...@ne... > w: www.networkedplanet.com > > |
|
From: Rob V. <rv...@do...> - 2014-06-30 10:54:31
|
Kal I put a rough target date in the tracker which you can see on the Roadmap (http://dotnetrdf.org/tracker/Projects/Roadmap.aspx?pid=1) I am currently scheduling releases every 2 months so 1.0.6 is currently scheduled for end of July. I can of course push out a pre-release build if that is a usable option for you? I prefer not to do releases too often since a release takes on average half a day to put together and publish but I only have half a day a week to work on dotNetRDF so too frequent releases means I can't actually get any fixes/new features done. Longer term the best way forward would be for me to make it possible for other people to carry out all the necessary release steps (which requires various bits of auth setup and documentation write up) so others can volunteer to carry out releases. Since I've been working using branches for all feature/bug fix development and only merging to default when things are working therefore in principle with the necessary stuff done anyone could cut a release when they see fit. Obviously if we want to move to that model longer term then we likely need to have some process in place to allow people to vote for/against a release e.g. if they have an important bug they want to get a fix in for. Rob From: Kal Ahmed <ka...@ne...> Date: Monday, 23 June 2014 09:17 To: Rob Vesse <rv...@do...> Subject: 1.0.6 release > Hi Rob, > > Any thoughts on when a 1.0.6 release might be ready ? I'm just wondering > whether to make a B* release on 1.0.5 or wait for the bug fixes in 1.0.6. > > Cheers > > Kal > -- > Kal Ahmed > Director, Networked Planet Limited > e: kal...@ne... > w: www.networkedplanet.com <http://www.networkedplanet.com> |
|
From: <tr...@do...> - 2014-06-26 07:43:01
|
<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>Unhandled null object reference exception in StoreManager</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Toolkit</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>jrhyne</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Store Manager</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>
Running the current release of StoreManager 1.0.3.0 with Stardog 2.1.3. </p>
<p>
The following SPARQL query causes StoreManager to abend with an unhandled null object reference exception.</p>
<div>
SELECT?subj ?obj ?aval</div>
<div>
WHERE {</div>
<div>
?bnode rdf:type owl:Axiom .</div>
<div>
?bnode owl:annotatedSource ?subj ;</div>
<div>
owl:annotatedProperty rdfs:subClassOf ;</div>
<div>
owl:annotatedTarget ?obj .</div>
<div>
?obj rdf:type owl:Restriction .</div>
<div>
OPTIONAL {?bnode thx-ctr:noRealization ?aval .}</div>
<div>
}</div>
<div>
</div>
<div>
The same query works with the Stardog Web Console and the Stardog CLI.</div></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=422" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=422</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-06-20 10:15:23
|
<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>Investigate performance problems reported involving sub-query and GRAPH clause interaction</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-06-20 11:14 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
CORE-420 found another bug related to sub-query evaluation so with 1.0.6 exact results for the query given in this bug will change again. So the results in 1.0.5 are incorrect, this is fixed in 1.0.6</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=416" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=416</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-06-20 10:12:39
|
<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>LIMIT not applied correctly in subquery</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-06-20 11:11 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Pull request approved and merged.</p>
<p>
</p>
<p>
As noted the CORE-416 test was indeed broken, I'd used ARQ 2.11.1 to check what the answer should be but it had an equivalent bug to this and so my expected answer was incorrect. With ARQ 2.11.2 which has an equivalent fix to your pull request I re-checked the CORE-416 test answers and fixed that test accordingly</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=420" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=420</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-06-20 10:11:07
|
<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>LIMIT not applied correctly in subquery</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 "Unassigned" to "Critical"
</li>
<li>Status changed from "New" to "Completed"
</li>
<li>Milestone changed from "Unassigned" to "1.0.6"
</li>
<li>Affected Milestone changed from "Unassigned" to "1.0.5"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Owner changed from "Unassigned" to "Kal"
</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=420" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=420</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>
|
48 messages has been excluded from this view by a project administrator.
