dotnetrdf-develop — Developer Discussion and Feature Request

Re: [dotNetRDF-Develop] SPARQL and ill-formatted dates

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

Tom

The expected behaviour is that only dates that follow the XSD format (see
http://www.w3.org/TR/xmlschema11-2/#date) should be supported.  So for
your example it should be "2014-04-20".

Similarly for full date times only the XSD format (see
http://www.w3.org/TR/xmlschema11-2/#dateTime) should be supported

Likely we need to be much stricter about how we use
DateTime.Parse/TryParse and DateTimeOffset.Parse/TryParse in the code
base.  I have a feeling we aren't supplying any culture information to
those calls and so are allowing any date format that is valid in the
current culture.

Please go ahead and commit whatever changes are necessary to resolve this

Rob

On 25/07/2014 11:52, "Tomasz Pluskiewicz" <tom...@gm...>
wrote:

>Hi Rob
>
>We've just encountered an interesting case with parsing dates in
>SPARQL queries. Initially I though it was dotNetRDF's fault, but in
>the end it turned out I failed to notice we used invalid date format
>and it worked while in Polish locale but failed on a German machine.
>
>What it reveals however is that dotNetRDF is forgiving in terms of ate
>formatting. Our query used a date like "04/20/2014"^^xsd:date and
>compared it to some dates in the graph. The comparison works in Polish
>and English locale yielding expected results. Is the processor trying
>to fall back to local settings if the date isn't a valid xsd format?
>
>If so it causes a weird state where invalid query can actually produce
>false-positive results. Hence I think that we should be more strict
>about date format. Or maybe it is a behaviour that SPARQL defines?
>
>Thanks,
>Tom
>
>--------------------------------------------------------------------------
>----
>Want fast and easy access to all the code in your enterprise? Index and
>search up to 200,000 lines of code with a free copy of Black Duck
>Code Sight - the same software that powers the world's largest code
>search on Ohloh, the Black Duck Open Hub! Try it now.
>http://p.sf.net/sfu/bds
>_______________________________________________
>dotNetRDF-develop mailing list
>dot...@li...
>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

[dotNetRDF-Develop] Sync dotNetRDF.Test project

[Tomasz P. <tom...@gm...>]

Hi Rob

While looking at the SPARQL dates I also noticed something weird about
the dotNetRDF.Test project. Before build you exec the sync tool but in
my case it removes all the file from the csproj. Command line says
"Removing defunct file" and 203 changes at the end. Worse that causes
Visual Studio 2012 to crash whenever I'm running tests with resharper.

Why are all those files removed from the project?

Thanks,
Tom

[dotNetRDF-Develop] SPARQL and ill-formatted dates

[Tomasz P. <tom...@gm...>]

Hi Rob

We've just encountered an interesting case with parsing dates in
SPARQL queries. Initially I though it was dotNetRDF's fault, but in
the end it turned out I failed to notice we used invalid date format
and it worked while in Polish locale but failed on a German machine.

What it reveals however is that dotNetRDF is forgiving in terms of ate
formatting. Our query used a date like "04/20/2014"^^xsd:date and
compared it to some dates in the graph. The comparison works in Polish
and English locale yielding expected results. Is the processor trying
to fall back to local settings if the date isn't a valid xsd format?

If so it causes a weird state where invalid query can actually produce
false-positive results. Hence I think that we should be more strict
about date format. Or maybe it is a behaviour that SPARQL defines?

Thanks,
Tom

[dotNetRDF-Develop] dotNetRDF-commits Digest, Vol 21, Issue 2

[<dot...@li...>]

Send dotNetRDF-commits mailing list submissions to
	dot...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits
or, via email, send a message with subject or body 'help' to
	dot...@li...

You can reach the person managing the list at
	dot...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dotNetRDF-commits digest..."


Today's Topics:

   1. commit/dotnetrdf: 5 new changesets (Bitbucket)
   2. commit/dotnetrdf: 7 new changesets (Bitbucket)
   3. commit/dotnetrdf: zett...@RONMACPROWIN1: Added reasoning mode
      to URL parameter to support Stardog 2.2+ (Bitbucket)
   4. commit/dotnetrdf: 2 new changesets (Bitbucket)
   5. commit/dotnetrdf: 6 new changesets (Bitbucket)
   6. commit/dotnetrdf: rvesse: More work towards the	new Query API
      (Bitbucket)
   7. commit/dotnetrdf: zett...@RONMACAIRWIN1: updated DeleteGraph
      to pass parameters in requestParams (Bitbucket)
   8. commit/dotnetrdf: 13 new changesets (Bitbucket)


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

Message: 1
Date: Fri, 04 Jul 2014 09:38:51 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 5 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

5 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d6f5af15c7c4/
Changeset:   d6f5af15c7c4
Branch:      CORE-423
User:        rvesse
Date:        2014-07-04 11:05:52
Summary:     Test case and initial work towards fixing CORE-423
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/729a2779d67a/
Changeset:   729a2779d67a
Branch:      CORE-423
User:        rvesse
Date:        2014-07-04 11:07:31
Summary:     Initial fix for CORE-423
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b3f94e32cb92/
Changeset:   b3f94e32cb92
Branch:      CORE-423
User:        rvesse
Date:        2014-07-04 11:26:57
Summary:     Further unit tests and fixes for SPARQL Results JSON Parsing (CORE-423)
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b425c4d96ee7/
Changeset:   b425c4d96ee7
Branch:      CORE-423
User:        rvesse
Date:        2014-07-04 11:27:40
Summary:     Note CORE-423 fixes in Change Log
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1b842d5dfa87/
Changeset:   1b842d5dfa87
User:        rvesse
Date:        2014-07-04 11:28:56
Summary:     Merge CORE-423 fixes to default
Affected #:  3 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 2
Date: Fri, 04 Jul 2014 15:10:52 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 7 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

7 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f06cea129611/
Changeset:   f06cea129611
Branch:      1.9
User:        rvesse
Date:        2014-07-04 16:18:55
Summary:     Tweaks to IGraph contract tests and some code clean up
Affected #:  5 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/49e1b1b85318/
Changeset:   49e1b1b85318
Branch:      1.9
User:        rvesse
Date:        2014-07-04 16:33:15
Summary:     Expand IGraph contract tests further
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/858895383a52/
Changeset:   858895383a52
Branch:      1.9
User:        rvesse
Date:        2014-07-04 16:39:32
Summary:     Strip out Triple-centric methods from IGraphStore to make a clean separation between IGraph (Triple based) and IGraphStore (Quad/IGraph based)
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3217c5f3619e/
Changeset:   3217c5f3619e
Branch:      1.9
User:        rvesse
Date:        2014-07-04 16:47:10
Summary:     Split out Quad specific portions of IGraphStore into parent interface IQuadStore
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a8c43a6615b1/
Changeset:   a8c43a6615b1
Branch:      1.9
User:        rvesse
Date:        2014-07-04 16:55:30
Summary:     Reorganize Extension methods into more appropriately named classes
Affected #:  5 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0d224b63a190/
Changeset:   0d224b63a190
Branch:      1.9
User:        rvesse
Date:        2014-07-04 17:05:46
Summary:     Various minor tweaks and code clean ups
Affected #:  10 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2569b64070a7/
Changeset:   2569b64070a7
Branch:      1.9
User:        rvesse
Date:        2014-07-04 17:10:28
Summary:     Fix subtle error in SubTreeIndexedTripleCollection
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 3
Date: Sat, 05 Jul 2014 03:34:01 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: zett...@RONMACPROWIN1:
	Added reasoning mode to URL parameter to support Stardog 2.2+
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/de7f9b8c4def/
Changeset:   de7f9b8c4def
User:        zett...@RONMACPROWIN1
Date:        2014-07-05 05:33:52
Summary:     Added reasoning mode to URL parameter to support Stardog 2.2+
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 4
Date: Mon, 07 Jul 2014 16:03:59 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/83646e766766/
Changeset:   83646e766766
User:        rvesse
Date:        2014-07-07 18:01:52
Summary:     Fix for various minor bugs that were causing test failures on TeamCity
Affected #:  17 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2b9c54805a3a/
Changeset:   2b9c54805a3a
User:        rvesse
Date:        2014-07-07 18:03:39
Summary:     Merge remote changes
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 5
Date: Fri, 11 Jul 2014 11:35:46 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

6 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e0c21efc58f3/
Changeset:   e0c21efc58f3
User:        rvesse
Date:        2014-07-08 13:12:43
Summary:     Prep for first pre-release of 1.0.6
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a24354c42d32/
Changeset:   a24354c42d32
Branch:      CORE-425
User:        rvesse
Date:        2014-07-08 13:48:14
Summary:     Improve CORE-416 test cases to demonstrate the bug that has been logged as CORE-425
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/470a1d769d66/
Changeset:   470a1d769d66
Branch:      1.9
User:        rvesse
Date:        2014-07-11 11:19:43
Summary:     Temp project to store old SPARQL engine code while refactoring
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/af66f89eeb06/
Changeset:   af66f89eeb06
Branch:      1.9
User:        rvesse
Date:        2014-07-11 11:27:52
Summary:     Move old code out of Sparql.Core library to start refactoring in earnest
Affected #:  827 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4dabf52d050f/
Changeset:   4dabf52d050f
Branch:      1.9
User:        rvesse
Date:        2014-07-11 12:47:58
Summary:     Flesh out new SPARQL Results interfaces and implementations
Affected #:  11 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e8fd95185b01/
Changeset:   e8fd95185b01
Branch:      1.9
User:        rvesse
Date:        2014-07-11 13:21:13
Summary:     Start to stub out new IQuery interface for representing SPARQL Queries and is fully mutable
Affected #:  17 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 6
Date: Fri, 11 Jul 2014 13:12:54 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: More work
	towards the	new Query API
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e19084778678/
Changeset:   e19084778678
Branch:      1.9
User:        rvesse
Date:        2014-07-11 15:12:30
Summary:     More work towards the new Query API
Affected #:  41 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 7
Date: Mon, 14 Jul 2014 20:27:48 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: zett...@RONMACAIRWIN1:
	updated DeleteGraph to pass parameters in requestParams
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5386256c268d/
Changeset:   5386256c268d
User:        zett...@RONMACAIRWIN1
Date:        2014-07-14 22:27:40
Summary:     updated DeleteGraph to pass parameters in requestParams
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 8
Date: Fri, 18 Jul 2014 09:53:43 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 13 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

13 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/517fb9abbcbf/
Changeset:   517fb9abbcbf
Branch:      1.9
User:        rvesse
Date:        2014-07-15 14:43:00
Summary:     Various pieces of work towards the new Query API and Medusa engine (CORE-320, CORE-369)
Affected #:  23 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e3583b82e82c/
Changeset:   e3583b82e82c
Branch:      1.9
User:        rvesse
Date:        2014-07-15 16:51:32
Summary:     Make new Sparql.Core minimally buildable
Affected #:  53 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e257ea92dd35/
Changeset:   e257ea92dd35
Branch:      1.9
User:        rvesse
Date:        2014-07-15 17:29:15
Summary:     Basic BGP execution implementation
Affected #:  6 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cd3a1c3e2662/
Changeset:   cd3a1c3e2662
Branch:      1.9
User:        rvesse
Date:        2014-07-15 17:49:05
Summary:     Start writing basic unit tests for BGP execution
Affected #:  8 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c5ffbf15f258/
Changeset:   c5ffbf15f258
Branch:      1.9
User:        rvesse
Date:        2014-07-16 17:38:02
Summary:     Further tests for BGP execution and custom enumerables/enumerators
Affected #:  5 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dd4c8003f3cc/
Changeset:   dd4c8003f3cc
Branch:      1.9
User:        rvesse
Date:        2014-07-16 17:42:07
Summary:     Further improve custom enumerable/enumerator tests
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/af99e6afa99a/
Changeset:   af99e6afa99a
Branch:      1.9
User:        rvesse
Date:        2014-07-16 18:17:14
Summary:     More work on Medusa engine
Affected #:  14 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/aab03efa19fe/
Changeset:   aab03efa19fe
Branch:      1.9
User:        rvesse
Date:        2014-07-17 14:37:02
Summary:     More work on Medusa engine, improve custom IEnumerable/IEnumerator implemenations and tests
Affected #:  24 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/398514f71f80/
Changeset:   398514f71f80
Branch:      1.9
User:        rvesse
Date:        2014-07-17 15:39:18
Summary:     Refactor IBgpExecutor to handle graph management better
Affected #:  6 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3f56cb9ee78d/
Changeset:   3f56cb9ee78d
Branch:      1.9
User:        rvesse
Date:        2014-07-17 15:45:06
Summary:     Minor efficiency changes to IExecutionContext property definitions
Affected #:  4 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0470affd5e61/
Changeset:   0470affd5e61
Branch:      1.9
User:        rvesse
Date:        2014-07-17 16:04:19
Summary:     Comment MedusaAlgebraExecutor logic, additional QuadStoreBgpExecutorTests
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2c483db01e7f/
Changeset:   2c483db01e7f
Branch:      1.9
User:        rvesse
Date:        2014-07-17 18:00:09
Summary:     Refactor out base class from QuadStoreBgpExecutor, add a GraphBgpExecutor
Affected #:  4 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8baa808cb4ba/
Changeset:   8baa808cb4ba
Branch:      1.9
User:        rvesse
Date:        2014-07-17 18:16:59
Summary:     Stub out Filter implementation
Affected #:  10 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds

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

_______________________________________________
dotNetRDF-commits mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits


End of dotNetRDF-commits Digest, Vol 21, Issue 2
************************************************

Re: [dotNetRDF-Develop] Hybrid dataset -- In-memory/SQL

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

Simon

This is entirely possible though not well documented, your best bet would be
to look at the source for BrightstarDB
(https://github.com/BrightstarDB/BrightstarDB/tree/develop/src/core/Brightst
arDB/Query) which takes this approach.  A couple of their developers are on
this list/dotNetRDF committers so they may hopefully chime in with advice

The only obvious consequence of your proposed approach is that you might get
quite different performance characteristics for queries depending on whether
a query stays in memory or goes against the SQL database.  Provided your
ISparqlDataset implementation just returns the loaded Triple objects the
rest of the SPARQL engine shouldn't have any problems.

The other thing to be aware of is that the current SPARQL engine is memory
bound in that it does all operations in-memory often materialising large
amounts of data.  Therefore even if you personally aren't keeping all your
data in-memory dotNetRDF may need to pull lots of stuff into memory in order
to successfully evaluate queries.  Long term this will be changed but
realistically it will be a minimum of 3 months before early Alphas of this
functionality are available and 6-12 before it is production ready.

Rob

From:  Simon Ouellette <sou...@he...>
Reply-To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date:  Tuesday, 15 July 2014 16:38
To:  "dot...@li..."
<dot...@li...>
Subject:  [dotNetRDF-Develop] Hybrid dataset -- In-memory/SQL

>   
> Hi,  
>    
> We’re interested in potentially using dotNetRdf against a kind of “hybrid
> dataset” where nodes and object properties would be in-memory, as in the
> InMemoryDataset, however there would be the special case of scalar properties
> (a.k.a. data properties), which would be contained in a SQL table (our
> database is too big to hold everything in RAM, but holding everything on disk
> would be too slow).
>    
> I’ve looked a bit at the source code to see how this could be done, and so far
> my understanding is that I could derive my own Dataset class, and implement my
> own GetTriplesWithPredicate, GetTriplesWithSubjectPredicate and
> GetTriplesWithPredicateObject methods? When the predicate exists in memory, I
> would go through the usual InMemoryDataset approach, and when it isn’t I would
> run a SQL query against my database. I’m not sure if I’m on the right path, or
> if there are potentially breaking consequences to what I’m trying to do…
>    
> Any guidance on how to best accomplish this would be appreciated.
>    
> Thanks,  
> Simon Ouellette  
>  <gfidisc.helix-sys.com>
> CONFIDENTIALITY NOTICE
> This message contains confidential information intended only for the use of
> the individual or entity named as recipient. Any dissemination, distribution
> or copying of this communication by anyone other than the intended recipient
> is strictly prohibited. If you have received this message in error, please
> immediately notify us and delete your copy.
> 
> Thank you.
> 
> AVIS DE CONFIDENTIALITÉ
> Les informations contenues aux présentes sont de nature privilégiée et
> confidentielle. Elles ne peuvent être utilisées que par la personne ou
> l'entité dont le nom paraît comme destinataire. Si le lecteur du présent
> message n'est pas le destinataire prévu, il est par les présentes prié de
> noter qu'il est strictement interdit de divulguer, de distribuer ou de copier
> ce message. Si ce message vous a été transmis par mégarde, veuillez nous en
> aviser immédiatement et supprimer votre copie.
> 
> Merci.
> 
>  
>  <gfidisc.helix-sys.com>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and search
> up to 200,000 lines of code with a free copy of Black Duck Code Sight - the
> same software that powers the world's largest code search on Ohloh, the Black
> Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds_______________________________________________
> dotNetRDF-develop mailing list dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop

[dotNetRDF-Develop] Hybrid dataset -- In-memory/SQL

[Simon O. <sou...@he...>]

Hi,

We're interested in potentially using dotNetRdf against a kind of "hybrid dataset" where nodes and object properties would be in-memory, as in the InMemoryDataset, however there would be the special case of scalar properties (a.k.a. data properties), which would be contained in a SQL table (our database is too big to hold everything in RAM, but holding everything on disk would be too slow).

I've looked a bit at the source code to see how this could be done, and so far my understanding is that I could derive my own Dataset class, and implement my own GetTriplesWithPredicate, GetTriplesWithSubjectPredicate and GetTriplesWithPredicateObject methods? When the predicate exists in memory, I would go through the usual InMemoryDataset approach, and when it isn't I would run a SQL query against my database. I'm not sure if I'm on the right path, or if there are potentially breaking consequences to what I'm trying to do...

Any guidance on how to best accomplish this would be appreciated.

Thanks,
Simon Ouellette


CONFIDENTIALITY NOTICE
This message contains confidential information intended only for the use of the individual or entity named as recipient. Any dissemination, distribution or copying of this communication by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify us and delete your copy. 
Thank you.

AVIS DE CONFIDENTIALITÉ
Les informations contenues aux présentes sont de nature privilégiée et confidentielle. Elles ne peuvent être utilisées que par la personne ou l'entité dont le nom paraît comme destinataire. Si le lecteur du présent message n'est pas le destinataire prévu, il est par les présentes prié de noter qu'il est strictement interdit de divulguer, de distribuer ou de copier ce message. Si ce message vous a été transmis par mégarde, veuillez nous en aviser immédiatement et supprimer votre copie. 
Merci.

[dotNetRDF-Develop] Issue CORE-425 has been updated by Rob Vesse

[<tr...@do...>]

<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>CORE-416 test query demonstrates an intermittent parallelisation bug</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Core Library (dotNetRDF.dll)</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "Confirmed" to "In Progress"
                                </li>
        <li>Progress changed from "0 %" to "10 %"
                                </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=425" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=425</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>

[dotNetRDF-Develop] Issue CORE-425 has been updated by Rob Vesse

[<tr...@do...>]

<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>CORE-416 test query demonstrates an intermittent parallelisation bug</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>Parent issue changed from "" to "Added"
                                </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=425" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=425</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>

[dotNetRDF-Develop] Issue CORE-425 has been added to a project you are monitoring.

[<tr...@do...>]

<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>CORE-416 test query demonstrates an intermittent parallelisation bug</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>Milestone:</b></td>
    <td>1.0.6</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>Query</td>
  </tr>
  <tr>
    <td><b>Priority:</b></td>
    <td>Critical</td>
  </tr>
  <tr>
    <td><b>Type:</b></td>
    <td>Bug</td>
  </tr>
  <tr>
    <td><b>Description:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	In investigating why the unit test from CORE-416 was intermittently failing on the TeamCity server I have discovered that there is some parallelization bug being exposed because when run with PLinq evaluation off the test always passes but when run with PLinq evaluation on it will intermittently fail</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=425" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=425</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>

Re: [dotNetRDF-Develop] dotNetRDF patch for Stardog 2.2

[Ron M. Z. <ro...@ze...>]

Rob, I'll take a look through the unit tests, although I can't promise
anything. I hate to say it but I've never used NUnit or done any unit
testing so I'll have to get up to speed on that a bit. Although looking
through StardogTests.cs, it looks simple enough: I assume a Stardog
instance is launched (manually? automatically?) before the tests start, and
it just connects and runs through anything marked as a Test?

It even looks like there already is one test for reasoning:
StorageStardogReasoningQL? It doesn't test for all the variations of
reasoning that Stardog supports but it would have detected this bug once
you tested against Stardog 2.2.

Ron



On Mon, Jul 7, 2014 at 6:44 AM, Rob Vesse <rv...@do...> wrote:

> Ron
>
> I took a quick look over the changes and they looked fine to me, thanks
> for debugging and fixing this
>
> Btw if you have any time could you attempt to create some relevant unit
> tests for this that we could add to the stardog tests so this is more
> easily caught If anything changes in this regard in the future?
>
> Cheers,
>
> Rob
>
> From: Ron Michael Zettlemoyer <ro...@ze...>
> Date: Saturday, 5 July 2014 04:39
> To: Rob Vesse <rv...@do...>
> Subject: dotNetRDF patch for Stardog 2.2
>
> Hey Rob,
>
> As you might have seen in the back & forth with Clark & Parsia on Twitter,
> they changed how the reasoning mode is set for Stardog. The deprecated
> using the HTTP headers back in 2.0 and finally disabled it in 2.2; it's
> been replaced with a URL parameter. So I found that reasoning was broken
> when using dotNetRDF and Stardog 2.2. I checked in some minor code changes
> that will get it working again. I left the old headers in place because
> Mike said that only 2.2+ support the new URL parameter. I tested the change
> against Stardog 2.1.2 and 2.2 and it worked as expected.
>
> It's been awhile since I've been at all active in the project so hopefully
> I checked it into the right place.
>
> Ron
>
>

Re: [dotNetRDF-Develop] dotNetRDF patch for Stardog 2.2

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

Ron

I took a quick look over the changes and they looked fine to me, thanks for
debugging and fixing this

Btw if you have any time could you attempt to create some relevant unit
tests for this that we could add to the stardog tests so this is more easily
caught If anything changes in this regard in the future?

Cheers,

Rob

From:  Ron Michael Zettlemoyer <ro...@ze...>
Date:  Saturday, 5 July 2014 04:39
To:  Rob Vesse <rv...@do...>
Subject:  dotNetRDF patch for Stardog 2.2

> Hey Rob,
> 
> As you might have seen in the back & forth with Clark & Parsia on Twitter,
> they changed how the reasoning mode is set for Stardog. The deprecated using
> the HTTP headers back in 2.0 and finally disabled it in 2.2; it's been
> replaced with a URL parameter. So I found that reasoning was broken when using
> dotNetRDF and Stardog 2.2. I checked in some minor code changes that will get
> it working again. I left the old headers in place because Mike said that only
> 2.2+ support the new URL parameter. I tested the change against Stardog 2.1.2
> and 2.2 and it worked as expected.
> 
> It's been awhile since I've been at all active in the project so hopefully I
> checked it into the right place.
> 
> Ron
> 

[dotNetRDF-Develop] Issue TOOLS-422 has been updated by Rob Vesse

[<tr...@do...>]

<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>Unhandled null object reference exception in StoreManager</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Toolkit</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "Planned" to "Closed"
                                </li>
        <li>Resolution changed from "Unassigned" to "Invalid"
                                </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=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>

[dotNetRDF-Develop] Issue TOOLS-422 has a new comment

[<tr...@do...>]

<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>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>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2014-07-04 02:57 PM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	The latest release version of Store Manager is 1.0.5 and with that release I cannot reproduce this bug. &nbsp;Please upgrade and see if that resolves the issue.</p>
<p>
	If you can still reproduce with the latest release then please reopen this issue and provide a minimal complete test case, this will need to include the following:</p>
<ul>
	<li>
		How the Stardog database is created i.e. code/CLI commands run</li>
	<li>
		What data is in the database - if this can be reduced to a small dataset that reliably reproduces the issue then that is preferred</li>
	<li>
		The complete query including necessary namespace prefixes - the given query is missing the namespace definitions so we can&#39;t be sure of the exact query you are running</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=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>

[dotNetRDF-Develop] Issue TOOLS-422 has been updated by Rob Vesse

[<tr...@do...>]

<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>Unhandled null object reference exception in StoreManager</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Toolkit</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "Unknown" to "Planned"
                                </li>
        <li>Milestone changed from "Unassigned" to "1.0.6"
                                </li>
        <li>Affected Milestone changed from "Unassigned" to "1.0.3"
                                </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=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>

[dotNetRDF-Develop] Issue CORE-423 has been updated by Rob Vesse

[<tr...@do...>]

<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>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 colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "In Progress" to "Completed"
                                </li>
        <li>Resolution changed from "Unassigned" to "Fixed"
                                </li>
        <li>Progress changed from "0 %" to "100 %"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=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>

[dotNetRDF-Develop] Issue CORE-423 has a new comment

[<tr...@do...>]

<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>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>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Date:</b></td>
    <td>2014-07-04 11:15 AM</td>
  </tr>
  <tr>
    <td><b>Comment:</b></td>
  </tr>
  <tr>
    <td colspan="2"><p>
	The specific case and some related cases have been fixed.</p>
<p>
	Please note that our parser is designed to be streaming so it is unlikely to ever cope with every possible unusual variation of the SPARQL Results JSON. &nbsp;In principal we could in the future add a DOM based parser that would not attempt to stream the data rather it would load the whole JSON document into memory up-front. &nbsp;That obviously makes a trade off in terms of memory usage and likely leads to an inability to cope with really large result sets which is something we&#39;ve seen with our XML based parsers in the past. &nbsp;While the overhead of a JSON DOM is likely much lower than that of an XML DOM the issue would still exist.</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>

[dotNetRDF-Develop] Issue CORE-423 has been updated by Rob Vesse

[<tr...@do...>]

<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>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 colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Priority changed from "Unassigned" to "Low"
                                </li>
        <li>Milestone changed from "Unassigned" to "1.0.6"
                                </li>
        <li>Assigned to changed from "Unassigned" to "Rob Vesse"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=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>

[dotNetRDF-Develop] Issue CORE-423 has been updated by Rob Vesse

[<tr...@do...>]

<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>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 colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "New" to "In Progress"
                                </li>
        <li>Assigned to changed from "Unassigned" to "none"
                                </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=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>

[dotNetRDF-Develop] Issue TOOLS-424 has been updated by Rob Vesse

[<tr...@do...>]

<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>rdfWebDeploy is out of date with respect to rest of code base</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Toolkit</td>
  </tr>
  <tr>
    <td colspan="2"><b>Changes:</b></td>
  </tr>
  <tr>
    <td colspan="2">
      <ul>
        <li>Status changed from "Confirmed" to "Completed"
                                </li>
        <li>Resolution changed from "Unassigned" to "Fixed"
                                </li>
        <li>Progress changed from "0 %" to "100 %"
                                </li>
      </ul>
    </td>
  </tr>
</table>
<p>
            More information on this issue can be found at
            <a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=424" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=424</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>

[dotNetRDF-Develop] dotNetRDF-commits Digest, Vol 21, Issue 1

[<dot...@li...>]

Send dotNetRDF-commits mailing list submissions to
	dot...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits
or, via email, send a message with subject or body 'help' to
	dot...@li...

You can reach the person managing the list at
	dot...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dotNetRDF-commits digest..."


Today's Topics:

   1. commit/dotnetrdf: rvesse: Merge CORE-421 fixes	to default
      (Bitbucket)
   2. commit/dotnetrdf: rvesse: Merged in kal_ahmed/dotnetrdf (pull
      request #29) (Bitbucket)
   3. commit/dotnetrdf: 2 new changesets (Bitbucket)
   4. commit/dotnetrdf: 2 new changesets (Bitbucket)
   5. commit/dotnetrdf: 3 new changesets (Bitbucket)
   6. commit/dotnetrdf: 2 new changesets (Bitbucket)
   7. commit/dotnetrdf: rvesse: Make MS Build warnings 3245 and
      3644 be treated as errors for PCL build so build systems with
      incorrect PCL targeting packs fail fast with meaningful errors
      (Bitbucket)
   8. commit/dotnetrdf: rvesse: IFDEF out CORE-421 tests that can't
      run in PCL test suite due to lack of LoadFromFile() method.
      Remove MSBuild warnings from PCL build warnAsErrors configuration
      since that configuration pertains only to compiler errors (Bitbucket)
   9. commit/dotnetrdf: 3 new changesets (Bitbucket)


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

Message: 1
Date: Fri, 20 Jun 2014 09:55:59 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merge CORE-421
	fixes	to default
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1c3afdf26721/
Changeset:   1c3afdf26721
User:        rvesse
Date:        2014-06-20 11:55:36
Summary:     Merge CORE-421 fixes to default
Affected #:  14 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 2
Date: Fri, 20 Jun 2014 10:07:08 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merged in
	kal_ahmed/dotnetrdf (pull request #29)
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0887e9698d9a/
Changeset:   0887e9698d9a
User:        rvesse
Date:        2014-06-20 12:07:01
Summary:     Merged in kal_ahmed/dotnetrdf (pull request #29)

Test and fix for CORE-420
Affected #:  2 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 3
Date: Fri, 20 Jun 2014 10:07:09 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID: <201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3f0955542bb3/
Changeset:   3f0955542bb3
User:        kal_ahmed
Date:        2014-06-17 13:28:06
Summary:     Test and fix for CORE-420
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0887e9698d9a/
Changeset:   0887e9698d9a
User:        rvesse
Date:        2014-06-20 12:07:01
Summary:     Merged in kal_ahmed/dotnetrdf (pull request #29)

Test and fix for CORE-420
Affected #:  2 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 4
Date: Fri, 20 Jun 2014 10:10:06 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a773d8262ad5/
Changeset:   a773d8262ad5
User:        rvesse
Date:        2014-06-20 12:09:15
Summary:     Merge CORE-420 fixes
Affected #:  2 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1d0bb7da4422/
Changeset:   1d0bb7da4422
User:        rvesse
Date:        2014-06-20 12:09:41
Summary:     Note CORE-420 fix in Change Log
Affected #:  1 file

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 5
Date: Fri, 20 Jun 2014 10:39:51 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

3 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b75aa2d71f0d/
Changeset:   b75aa2d71f0d
Branch:      1.9
User:        rvesse
Date:        2014-06-20 12:33:06
Summary:     Bring 1.9 branch up to date with default (probably breaks the bits that build)
Affected #:  185 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d9fda38eb22e/
Changeset:   d9fda38eb22e
Branch:      1.9
User:        rvesse
Date:        2014-06-20 12:37:32
Summary:     Fix up some project files and remove defunct project files
Affected #:  3 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2cfe1ac64d01/
Changeset:   2cfe1ac64d01
Branch:      1.9
User:        rvesse
Date:        2014-06-20 12:39:27
Summary:     More project file fix ups
Affected #:  5 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 6
Date: Fri, 20 Jun 2014 11:26:07 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

2 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4b9a8b57d88e/
Changeset:   4b9a8b57d88e
Branch:      1.9
User:        rvesse
Date:        2014-06-20 13:15:01
Summary:     Start to flesh out more tests on 1.9 branch
Affected #:  12 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/adf092066d77/
Changeset:   adf092066d77
Branch:      1.9
User:        rvesse
Date:        2014-06-20 13:25:43
Summary:     Fix various bugs in RDF 1.1 Node implementations
Affected #:  3 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 7
Date: Wed, 02 Jul 2014 09:23:05 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Make MS Build
	warnings 3245 and 3644 be treated as errors for PCL build so build
	systems with incorrect PCL targeting packs fail fast with meaningful
	errors
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/20d64a97199f/
Changeset:   20d64a97199f
User:        rvesse
Date:        2014-07-02 11:22:34
Summary:     Make MS Build warnings 3245 and 3644 be treated as errors for PCL build so build systems with incorrect PCL targeting packs fail fast with meaningful errors
Affected #:  11 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 8
Date: Thu, 03 Jul 2014 09:13:18 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: IFDEF out
	CORE-421 tests that can't run in PCL test suite due to lack of
	LoadFromFile() method. Remove MSBuild warnings from PCL build
	warnAsErrors configuration since that configuration pertains only to
	compiler errors
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

1 new commit in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fb9e8a8a071f/
Changeset:   fb9e8a8a071f
User:        rvesse
Date:        2014-07-03 11:12:54
Summary:     IFDEF out CORE-421 tests that can't run in PCL test suite due to lack of LoadFromFile() method.  Remove MSBuild warnings from PCL build warnAsErrors configuration since that configuration pertains only to compiler errors
Affected #:  2 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

Message: 9
Date: Fri, 04 Jul 2014 08:43:14 -0000
From: Bitbucket <com...@bi...>
Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets
To: dot...@li...
Message-ID:
	<201...@ap...>
Content-Type: text/plain; charset="utf-8"

3 new commits in dotnetrdf:

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dfdbe8a967ea/
Changeset:   dfdbe8a967ea
Branch:      TOOLS-424
User:        rvesse
Date:        2014-07-04 10:37:24
Summary:     Update list of required DLLs and remove defunct references from rdfWebDeploy (TOOLS-424)
Affected #:  7 files

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/563401826bf7/
Changeset:   563401826bf7
Branch:      TOOLS-424
User:        rvesse
Date:        2014-07-04 10:38:21
Summary:     Note TOOLS-424 fix in Change Log
Affected #:  1 file

https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9f67e5b7ae92/
Changeset:   9f67e5b7ae92
User:        rvesse
Date:        2014-07-04 10:42:39
Summary:     Merge TOOLS-424 fixes to default
Affected #:  8 files

Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.



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

------------------------------------------------------------------------------
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-commits mailing list
dot...@li...
https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits


End of dotNetRDF-commits Digest, Vol 21, Issue 1
************************************************

[dotNetRDF-Develop] Issue TOOLS-424 has been added to a project you are monitoring.

[<tr...@do...>]

<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>rdfWebDeploy is out of date with respect to rest of code base</td>
  </tr>
  <tr>
    <td><b>Project:</b></td>
    <td>Toolkit</td>
  </tr>
  <tr>
    <td><b>Created By:</b></td>
    <td>Rob Vesse</td>
  </tr>
  <tr>
    <td><b>Milestone:</b></td>
    <td>1.0.6</td>
  </tr>
  <tr>
    <td><b>Category:</b></td>
    <td>rdfWebDeploy</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>
	As reported at&nbsp;<a href="http://stackoverflow.com/questions/24353444/missing-dependencies-in-latest-rdfwebdeploy">http://stackoverflow.com/questions/24353444/missing-dependencies-in-latest-rdfwebdeploy</a>&nbsp;it looks like rdfWebDeploy is out of date with respect to the code base since it appears to be setting up dependencies incorrectly and testing for the wrong things</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=424" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=424</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>

Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format

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

Song

dotNetRDF provides limited configurability of the RDF/XML writer because
we prefer correctness over human readability

As Tom has already pointed out the serialisation is somewhat irrelevant
you just need to focus on the triples, if another system requires a
specific serialisation rather than triples then that is a bug/limitation
in that system

Again as Tom has already pointed out to create such typed nodes you need
to have relevant rdf:type triples present in your graph otherwise they can
never be output.

dotNetRDF will try to use typed nodes in RDF/XML depending on the
configuration of the writer though it can never guarantee that it will
produce them.  You can try increasing the CompressionLevel property of
your RdfXmlWriter instance to a higher value (10 is the highest currently,
see WriterCompressionLevels for constants) which will make it more likely
that these will be output but does not guarantee it

Rob



On 04/07/2014 08:48, "Tomasz Pluskiewicz" <tom...@gm...>
wrote:

>I do not know.
>
>Rob, please help us out here :)
>
>On Fri, Jul 4, 2014 at 9:42 AM, song xin <son...@gm...> wrote:
>> Hi, Tom
>>
>> I think Example 15 in section 2.13 is what I want….
>> Can dotnetpdf output like that?
>>
>> Thanks again!
>>
>> 在 4 Jul 2014，08:17，Tomasz Pluskiewicz <tom...@gm...> 写道：
>>
>>> The document actually represents 5 triples. Those you mention and
>>> additionally the rdf:type property for both resources.
>>>
>>> <MyClass01Id> rdf:type <KB:MyClass01> .
>>> <MyClass02Id> rdf:type <KB:MyClass02> .
>>>
>>> This is implicit by using a typed XML node.
>>>
>>> <KB:MyClass02 rdf:about="MyClass02Id" />
>>>
>>> is equivalent to (relevent parts ommitted)
>>>
>>> <rdf:Description><rdf:type>type</rdf:type></rdf:Descritpion>.
>>>
>>> Please have a look at section 2.13 of RDF syntax documentation [1].
>>>
>>> I don't think that it is possible with dotNetRDF to enforce one way or
>>> another of writing RDF/XML documents.
>>>
>>> Rob, is it?
>>>
>>> Tom
>>>
>>> [1] http://www.w3.org/TR/rdf-syntax-grammar/#section-Syntax-typed-nodes
>>>
>>> On Fri, Jul 4, 2014 at 8:48 AM, song xin <son...@gm...> wrote:
>>>> 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-rdfr
>>>>>>>>esource-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
>>>>
>>>>
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-------
>>>> 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

Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format

[Tomasz P. <tom...@gm...>]

I do not know.

Rob, please help us out here :)

On Fri, Jul 4, 2014 at 9:42 AM, song xin <son...@gm...> wrote:
> Hi, Tom
>
> I think Example 15 in section 2.13 is what I want….
> Can dotnetpdf output like that?
>
> Thanks again!
>
> 在 4 Jul 2014，08:17，Tomasz Pluskiewicz <tom...@gm...> 写道：
>
>> The document actually represents 5 triples. Those you mention and
>> additionally the rdf:type property for both resources.
>>
>> <MyClass01Id> rdf:type <KB:MyClass01> .
>> <MyClass02Id> rdf:type <KB:MyClass02> .
>>
>> This is implicit by using a typed XML node.
>>
>> <KB:MyClass02 rdf:about="MyClass02Id" />
>>
>> is equivalent to (relevent parts ommitted)
>>
>> <rdf:Description><rdf:type>type</rdf:type></rdf:Descritpion>.
>>
>> Please have a look at section 2.13 of RDF syntax documentation [1].
>>
>> I don't think that it is possible with dotNetRDF to enforce one way or
>> another of writing RDF/XML documents.
>>
>> Rob, is it?
>>
>> Tom
>>
>> [1] http://www.w3.org/TR/rdf-syntax-grammar/#section-Syntax-typed-nodes
>>
>> On Fri, Jul 4, 2014 at 8:48 AM, song xin <son...@gm...> wrote:
>>> 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
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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

Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format

[song x. <son...@gm...>]

Hi, Tom

I think Example 15 in section 2.13 is what I want….
Can dotnetpdf output like that?

Thanks again!

在 4 Jul 2014，08:17，Tomasz Pluskiewicz <tom...@gm...> 写道：

> The document actually represents 5 triples. Those you mention and
> additionally the rdf:type property for both resources.
> 
> <MyClass01Id> rdf:type <KB:MyClass01> .
> <MyClass02Id> rdf:type <KB:MyClass02> .
> 
> This is implicit by using a typed XML node.
> 
> <KB:MyClass02 rdf:about="MyClass02Id" />
> 
> is equivalent to (relevent parts ommitted)
> 
> <rdf:Description><rdf:type>type</rdf:type></rdf:Descritpion>.
> 
> Please have a look at section 2.13 of RDF syntax documentation [1].
> 
> I don't think that it is possible with dotNetRDF to enforce one way or
> another of writing RDF/XML documents.
> 
> Rob, is it?
> 
> Tom
> 
> [1] http://www.w3.org/TR/rdf-syntax-grammar/#section-Syntax-typed-nodes
> 
> On Fri, Jul 4, 2014 at 8:48 AM, song xin <son...@gm...> wrote:
>> 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
>> 
>> 
>> ------------------------------------------------------------------------------
>> 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

Re: [dotNetRDF-Develop] Writing <rdf:about> as RDF/XML format

[Tomasz P. <tom...@gm...>]

The document actually represents 5 triples. Those you mention and
additionally the rdf:type property for both resources.

<MyClass01Id> rdf:type <KB:MyClass01> .
<MyClass02Id> rdf:type <KB:MyClass02> .

This is implicit by using a typed XML node.

<KB:MyClass02 rdf:about="MyClass02Id" />

is equivalent to (relevent parts ommitted)

<rdf:Description><rdf:type>type</rdf:type></rdf:Descritpion>.

Please have a look at section 2.13 of RDF syntax documentation [1].

I don't think that it is possible with dotNetRDF to enforce one way or
another of writing RDF/XML documents.

Rob, is it?

Tom

[1] http://www.w3.org/TR/rdf-syntax-grammar/#section-Syntax-typed-nodes

On Fri, Jul 4, 2014 at 8:48 AM, song xin <son...@gm...> wrote:
> 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
>
>
> ------------------------------------------------------------------------------
> 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