- From: Pat Hayes <phayes@ihmc.us>
- Date: Sun, 6 Jul 2014 10:02:33 -0500
- To: Victor Porton <porton@narod.ru>
- Cc: semantic-web@w3.org
On Jul 5, 2014, at 10:07 AM, Victor Porton <porton@narod.ru> wrote: > I work on this project: > http://freesoft.portonvictor.org/namespaces.xml > > It involves downloading RDF files from the Web. > > When a "bundle" (for lack of a better word), that is a set of related RDF triples I really do not know what you mean by 'related' or 'bundle'. Neither of these terms make RDF sense. > , is incomplete it should be ignored. That is a very odd rule to use when dealing with RDF. It is a basic aspect of the RDF design that information from various sources can be combined, and that no single source should be assumed to be complete (the 'open world' assumption). So you are using RDF here in a way which, while not formally incorrect, does violate the design presumptions of RDF. > > My question, if a bundle is split into several different RDF files, and each part of it is incomplete, should it nevertheless not be ignored if the union of all parts of the bundle is complete? I would say, clearly no. Which illustrates why this 'ignore' rule is troublesome. Pat Hayes > > A toy example (A, B1, B2, C be namespaces): > > In one file: > > <A> <B1> <C> . > > In an other file: > > <A> <B2> <C> . > > If both B1 and B2 properties are required, should this information be ignored (as incomplete bundles)? or should the information from the two files be merged and thus considered complete? > > -- > Victor Porton - http://portonvictor.org > > ------------------------------------------------------------ IHMC (850)434 8903 home 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 mobile (preferred) phayes@ihmc.us http://www.ihmc.us/users/phayes
Received on Sunday, 6 July 2014 15:03:05 UTC