Re: An alternative RDF

Hello Victor,

when using RDF, you cannot decree that certain entities have to be described
using blank nodes. RDF users are free to choose between URIs or blank nodes and
your app should be able to cope with both.

I do not see much in your RDF examples that would be of use for humans or 
outside the context of your app so you may reconsider using XML Schema instead
of RDF to avoid any consistency issues from the start.

Otherwise, you will have to check for all possible cases of inconsistency -
even if converting RDF to an internal data structure one file at a time.

Regards,

Michael Brunnbauer

On Thu, Jul 10, 2014 at 03:04:48PM +0300, Victor Porton wrote:
> 10.07.2014, 14:26, "Michael Brunnbauer" <brunni@netestate.de>:
> > Hello Victor,
> >
> > On Thu, Jul 10, 2014 at 02:18:40PM +0300, Victor Porton wrote:
> >>>  Why does your app combine data from different files? How about using named
> >>>  graphs instead?
> >>  The reason that I choose RDF is because my app combine data from different files.
> >
> > This can be achieved with any database engine. Can you be a bit more specific?
> 
> The files (or rather they are called "resources") are downloaded from the Web.
> 
> I need to somehow combine data from different sources and have the language extensible.
> 
> So RDF.
> 
> --
> Victor Porton - http://portonvictor.org

-- 
++  Michael Brunnbauer
++  netEstate GmbH
++  Geisenhausener Straße 11a
++  81379 München
++  Tel +49 89 32 19 77 80
++  Fax +49 89 32 19 77 89 
++  E-Mail brunni@netestate.de
++  http://www.netestate.de/
++
++  Sitz: München, HRB Nr.142452 (Handelsregister B München)
++  USt-IdNr. DE221033342
++  Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer
++  Prokurist: Dipl. Kfm. (Univ.) Markus Hendel