Re: Jena Property Table

2018-02-28 Thread Claude Warren
This sounds like a data serialization question.   Would it not be easier to
write out the triples in turtle and read them in by normal means?

On Feb 28, 2018 6:36 AM, "Samita Bai / PhD CS Scholar @ City Campus" <
s...@iba.edu.pk> wrote:

> Yes Andy, I am also thinking to switch to TDB, cheers.
>
>
> I felt so good you helped me.
>
>
> Now I can convince my supervisor 
>
>
> Regards,
>
> Samita Bai
>
> 
> From: Andy Seaborne <a...@apache.org>
> Sent: 28 February 2018 16:24:21
> To: users@jena.apache.org
> Subject: Re: Jena Property Table
>
> I read the javadoc :-)
>
> """
> Each Row of the PropertyTable has an unique rowKey Node of the subject
> (or s for short).
> """
>
> I'm not convinced all the implementations follow this but if they don't,
> I do not see how it is useable.
>
> A direct implementation as a graph looks just as easy.
>
> If you don't have a lot or data and so don't need the compactness of a
> custom implementation, use Modelfactory.createDefaultModel (or the graph
> version Factory.createGraphMem( )). Because Graph is an interface, you
> can replace the default implementation later.
>
> If you are going to be doing querying and updates, then DatasetFactory
> and use a transactional dataset (or TDB for a persistent one).
>
> It depends what's important to your project - if this is a necessary
> implementation component with no performance implications, do whatever
> is the least work.
>
> Could you say something about your project and what are you trying to 0o?
>  Andy
>
> On 28/02/18 11:07, Samita Bai  / PhD CS Scholar @ City Campus wrote:
> > Thank you Andy for such a detailed reply. I am not getting this 'one
> subject only'. Is it not possible to add more subjects in a single property
> table?
> >
> > And you are suggesting me to extend GraphBase right? Ok I will work it
> now.
> >
> >
> >
> > Thank you so much.
> >
> > 
> > From: Andy Seaborne <a...@apache.org>
> > Sent: 28 February 2018 15:50:38
> > To: users@jena.apache.org
> > Subject: Re: Jena Property Table
> >
> > The PropertyTable abstraction is for regular data where for each subject
> > there are the same properties, and the same number of each property for
> > every subject.
> >
> > Each row of the property table has a unique key which is the subject of
> > each triple. Being unique, it is assuming one subject - one row.
> >
> >
> > If your data is one subject, one RDFS.seeAlso, a property table could be
> > used. If your data is one subject, potentially many RDFS.seeAlso, then
> > PropertyTable isn't the right abstaction.
> >
> > GraphPropertyTable is the Graph implementation over PropertyTable.
> > Graphs are central to Jena.  A quick look at the code and I think it has
> > bugs (it ignores the subject in a Graph.find operation which looks wrong
> > to me).
> >
> > Personally, I'd consider not using that at all but instade doing your
> > own implementation of Graph by extending GraphBase ; you only have to
> > implement:
> >
> > performAdd( Triple t )
> > performDelete( Triple t )
> > graphBaseFind(Triple triplePattern)
> >
> > then check triple added match your restriction to RDFS.seeAlso
> > Choose the datastructure to store the (subject, object) pairs needed.
> > (A Multimap<Node,Node> for example).
> >
> > And write test cases :-)
> >
> >   Hope that helps,
> >   Andy
> >
> > The name is taken from this earlier work:
> > http://www.hpl.hp.com/techreports/2006/HPL-2006-140.html
> > which is for a SQL-storage system no longer in Jena.
> >
> >
> > On 28/02/18 10:31, Samita Bai  / PhD CS Scholar @ City Campus wrote:
> >> Dear Andy,
> >>
> >>
> >> I am working on my Ph.D thesis and I have created a dataset of triples
> in which the property is same (i.e. RDFS.seeAlso), means I have only one
> property for all triples. I thought I will be creating a property table
> with one column and many rows. And I coded it too. But I am bit concerned
> because property table is now deprecated.
> >>
> >>
> >> Please suggest me any indexing or storing mechanism where we want to
> store only one property for many triples.
> >>
> >>
> >> Thanks & Regards,
> >>
> >> Samita Bai
> >>
> >> 
> >> From: Andy Seaborne <a...@apache.org>
> >> Sen

Re: Jena Property Table

2018-02-28 Thread Samita Bai / PhD CS Scholar @ City Campus
Yes Andy, I am also thinking to switch to TDB, cheers.


I felt so good you helped me.


Now I can convince my supervisor 


Regards,

Samita Bai


From: Andy Seaborne <a...@apache.org>
Sent: 28 February 2018 16:24:21
To: users@jena.apache.org
Subject: Re: Jena Property Table

I read the javadoc :-)

"""
Each Row of the PropertyTable has an unique rowKey Node of the subject
(or s for short).
"""

I'm not convinced all the implementations follow this but if they don't,
I do not see how it is useable.

A direct implementation as a graph looks just as easy.

If you don't have a lot or data and so don't need the compactness of a
custom implementation, use Modelfactory.createDefaultModel (or the graph
version Factory.createGraphMem( )). Because Graph is an interface, you
can replace the default implementation later.

If you are going to be doing querying and updates, then DatasetFactory
and use a transactional dataset (or TDB for a persistent one).

It depends what's important to your project - if this is a necessary
implementation component with no performance implications, do whatever
is the least work.

Could you say something about your project and what are you trying to 0o?
 Andy

On 28/02/18 11:07, Samita Bai  / PhD CS Scholar @ City Campus wrote:
> Thank you Andy for such a detailed reply. I am not getting this 'one subject 
> only'. Is it not possible to add more subjects in a single property table?
>
> And you are suggesting me to extend GraphBase right? Ok I will work it now.
>
>
>
> Thank you so much.
>
> 
> From: Andy Seaborne <a...@apache.org>
> Sent: 28 February 2018 15:50:38
> To: users@jena.apache.org
> Subject: Re: Jena Property Table
>
> The PropertyTable abstraction is for regular data where for each subject
> there are the same properties, and the same number of each property for
> every subject.
>
> Each row of the property table has a unique key which is the subject of
> each triple. Being unique, it is assuming one subject - one row.
>
>
> If your data is one subject, one RDFS.seeAlso, a property table could be
> used. If your data is one subject, potentially many RDFS.seeAlso, then
> PropertyTable isn't the right abstaction.
>
> GraphPropertyTable is the Graph implementation over PropertyTable.
> Graphs are central to Jena.  A quick look at the code and I think it has
> bugs (it ignores the subject in a Graph.find operation which looks wrong
> to me).
>
> Personally, I'd consider not using that at all but instade doing your
> own implementation of Graph by extending GraphBase ; you only have to
> implement:
>
> performAdd( Triple t )
> performDelete( Triple t )
> graphBaseFind(Triple triplePattern)
>
> then check triple added match your restriction to RDFS.seeAlso
> Choose the datastructure to store the (subject, object) pairs needed.
> (A Multimap<Node,Node> for example).
>
> And write test cases :-)
>
>   Hope that helps,
>   Andy
>
> The name is taken from this earlier work:
> http://www.hpl.hp.com/techreports/2006/HPL-2006-140.html
> which is for a SQL-storage system no longer in Jena.
>
>
> On 28/02/18 10:31, Samita Bai  / PhD CS Scholar @ City Campus wrote:
>> Dear Andy,
>>
>>
>> I am working on my Ph.D thesis and I have created a dataset of triples in 
>> which the property is same (i.e. RDFS.seeAlso), means I have only one 
>> property for all triples. I thought I will be creating a property table with 
>> one column and many rows. And I coded it too. But I am bit concerned because 
>> property table is now deprecated.
>>
>>
>> Please suggest me any indexing or storing mechanism where we want to store 
>> only one property for many triples.
>>
>>
>> Thanks & Regards,
>>
>> Samita Bai
>>
>> 
>> From: Andy Seaborne <a...@apache.org>
>> Sent: 28 February 2018 15:26:25
>> To: users@jena.apache.org
>> Subject: Re: Jena Property Table
>>
>> Hi Samita,
>>
>> The jena-csv module sees less attention than the major modules and is
>> considered "legacy".  That said, it is not going away any time soon and
>> the source code will always be available.
>>
>> Could you say something about your project and what are you trying to do
>> with property tables?  Maybe there is a different approach somewhere.
>>
>>Andy
>>
>>
>>
>> On 28/02/18 09:36, Samita Bai  / PhD CS Scholar @ City Campus wrote:
>>> Oh Ok, then please follow this link
>>>
>>>
>>> https://github.com/apache/jena/tree/master/j

Re: Jena Property Table

2018-02-28 Thread Andy Seaborne

I read the javadoc :-)

"""
Each Row of the PropertyTable has an unique rowKey Node of the subject 
(or s for short).

"""

I'm not convinced all the implementations follow this but if they don't, 
I do not see how it is useable.


A direct implementation as a graph looks just as easy.

If you don't have a lot or data and so don't need the compactness of a 
custom implementation, use Modelfactory.createDefaultModel (or the graph 
version Factory.createGraphMem( )). Because Graph is an interface, you 
can replace the default implementation later.


If you are going to be doing querying and updates, then DatasetFactory 
and use a transactional dataset (or TDB for a persistent one).


It depends what's important to your project - if this is a necessary 
implementation component with no performance implications, do whatever 
is the least work.


Could you say something about your project and what are you trying to 0o?
Andy

On 28/02/18 11:07, Samita Bai  / PhD CS Scholar @ City Campus wrote:

Thank you Andy for such a detailed reply. I am not getting this 'one subject 
only'. Is it not possible to add more subjects in a single property table?

And you are suggesting me to extend GraphBase right? Ok I will work it now.



Thank you so much.


From: Andy Seaborne <a...@apache.org>
Sent: 28 February 2018 15:50:38
To: users@jena.apache.org
Subject: Re: Jena Property Table

The PropertyTable abstraction is for regular data where for each subject
there are the same properties, and the same number of each property for
every subject.

Each row of the property table has a unique key which is the subject of
each triple. Being unique, it is assuming one subject - one row.


If your data is one subject, one RDFS.seeAlso, a property table could be
used. If your data is one subject, potentially many RDFS.seeAlso, then
PropertyTable isn't the right abstaction.

GraphPropertyTable is the Graph implementation over PropertyTable.
Graphs are central to Jena.  A quick look at the code and I think it has
bugs (it ignores the subject in a Graph.find operation which looks wrong
to me).

Personally, I'd consider not using that at all but instade doing your
own implementation of Graph by extending GraphBase ; you only have to
implement:

performAdd( Triple t )
performDelete( Triple t )
graphBaseFind(Triple triplePattern)

then check triple added match your restriction to RDFS.seeAlso
Choose the datastructure to store the (subject, object) pairs needed.
(A Multimap<Node,Node> for example).

And write test cases :-)

  Hope that helps,
  Andy

The name is taken from this earlier work:
http://www.hpl.hp.com/techreports/2006/HPL-2006-140.html
which is for a SQL-storage system no longer in Jena.


On 28/02/18 10:31, Samita Bai  / PhD CS Scholar @ City Campus wrote:

Dear Andy,


I am working on my Ph.D thesis and I have created a dataset of triples in which 
the property is same (i.e. RDFS.seeAlso), means I have only one property for 
all triples. I thought I will be creating a property table with one column and 
many rows. And I coded it too. But I am bit concerned because property table is 
now deprecated.


Please suggest me any indexing or storing mechanism where we want to store only 
one property for many triples.


Thanks & Regards,

Samita Bai


From: Andy Seaborne <a...@apache.org>
Sent: 28 February 2018 15:26:25
To: users@jena.apache.org
Subject: Re: Jena Property Table

Hi Samita,

The jena-csv module sees less attention than the major modules and is
considered "legacy".  That said, it is not going away any time soon and
the source code will always be available.

Could you say something about your project and what are you trying to do
with property tables?  Maybe there is a different approach somewhere.

   Andy



On 28/02/18 09:36, Samita Bai  / PhD CS Scholar @ City Campus wrote:

Oh Ok, then please follow this link


https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable

[https://avatars3.githubusercontent.com/u/47359?s=400=4]<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>

apache/jena<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
github.com
jena - Mirror of Apache Jena






From: Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
Sent: 28 February 2018 13:44:33
To: users@jena.apache.org
Subject: Re: Jena Property Table

Attachments do not work on this mailing list.


On 28.02.2018 09:21, Samita Bai / PhD CS Scholar @ City Campus wrote:


Dear Lorenz,


I have attached the screenshot, I am talking about property table in
jena csv package. Please have a look and suggest me.


Regards,


*From:* Lorenz Buehmann &l

Re: Jena Property Table

2018-02-28 Thread Samita Bai / PhD CS Scholar @ City Campus
Dear Andy,


My data is as follows,


subject_1  rdfs:seeAlso object_1

subject_2  rdfs:seeAlso object_2

subject_3  rdfs:seeAlso object_3



subject_n  rdfs:seeAlso object_n


so it is actually one subject one rdfs:seeAlso, so should I go for property 
table?


From: Andy Seaborne <a...@apache.org>
Sent: 28 February 2018 15:50:38
To: users@jena.apache.org
Subject: Re: Jena Property Table

The PropertyTable abstraction is for regular data where for each subject
there are the same properties, and the same number of each property for
every subject.

Each row of the property table has a unique key which is the subject of
each triple. Being unique, it is assuming one subject - one row.


If your data is one subject, one RDFS.seeAlso, a property table could be
used. If your data is one subject, potentially many RDFS.seeAlso, then
PropertyTable isn't the right abstaction.

GraphPropertyTable is the Graph implementation over PropertyTable.
Graphs are central to Jena.  A quick look at the code and I think it has
bugs (it ignores the subject in a Graph.find operation which looks wrong
to me).

Personally, I'd consider not using that at all but instade doing your
own implementation of Graph by extending GraphBase ; you only have to
implement:

performAdd( Triple t )
performDelete( Triple t )
graphBaseFind(Triple triplePattern)

then check triple added match your restriction to RDFS.seeAlso
Choose the datastructure to store the (subject, object) pairs needed.
(A Multimap<Node,Node> for example).

And write test cases :-)

 Hope that helps,
 Andy

The name is taken from this earlier work:
http://www.hpl.hp.com/techreports/2006/HPL-2006-140.html
which is for a SQL-storage system no longer in Jena.


On 28/02/18 10:31, Samita Bai  / PhD CS Scholar @ City Campus wrote:
> Dear Andy,
>
>
> I am working on my Ph.D thesis and I have created a dataset of triples in 
> which the property is same (i.e. RDFS.seeAlso), means I have only one 
> property for all triples. I thought I will be creating a property table with 
> one column and many rows. And I coded it too. But I am bit concerned because 
> property table is now deprecated.
>
>
> Please suggest me any indexing or storing mechanism where we want to store 
> only one property for many triples.
>
>
> Thanks & Regards,
>
> Samita Bai
>
> 
> From: Andy Seaborne <a...@apache.org>
> Sent: 28 February 2018 15:26:25
> To: users@jena.apache.org
> Subject: Re: Jena Property Table
>
> Hi Samita,
>
> The jena-csv module sees less attention than the major modules and is
> considered "legacy".  That said, it is not going away any time soon and
> the source code will always be available.
>
> Could you say something about your project and what are you trying to do
> with property tables?  Maybe there is a different approach somewhere.
>
>   Andy
>
>
>
> On 28/02/18 09:36, Samita Bai  / PhD CS Scholar @ City Campus wrote:
>> Oh Ok, then please follow this link
>>
>>
>> https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable
>>
>> [https://avatars3.githubusercontent.com/u/47359?s=400=4]<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
>>
>> apache/jena<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
>> github.com
>> jena - Mirror of Apache Jena
>>
>>
>>
>>
>>
>> 
>> From: Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
>> Sent: 28 February 2018 13:44:33
>> To: users@jena.apache.org
>> Subject: Re: Jena Property Table
>>
>> Attachments do not work on this mailing list.
>>
>>
>> On 28.02.2018 09:21, Samita Bai / PhD CS Scholar @ City Campus wrote:
>>>
>>> Dear Lorenz,
>>>
>>>
>>> I have attached the screenshot, I am talking about property table in
>>> jena csv package. Please have a look and suggest me.
>>>
>>>
>>> Regards,
>>>
>>> 
>>> *From:* Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
>>> *Sent:* 28 February 2018 13:07:47
>>> *To:* users@jena.apache.org
>>> *Subject:* Re: Jena Property Table
>>>
>>> Can you be a bit more precise please? What exactly is deprecated? And
>>> what do you want to do in your project?
>>>
>>>
>>> On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:
>>>> Hello Jena team,
>>>>
>>>&

Re: Jena Property Table

2018-02-28 Thread Samita Bai / PhD CS Scholar @ City Campus
Thank you Andy for such a detailed reply. I am not getting this 'one subject 
only'. Is it not possible to add more subjects in a single property table?

And you are suggesting me to extend GraphBase right? Ok I will work it now.



Thank you so much.


From: Andy Seaborne <a...@apache.org>
Sent: 28 February 2018 15:50:38
To: users@jena.apache.org
Subject: Re: Jena Property Table

The PropertyTable abstraction is for regular data where for each subject
there are the same properties, and the same number of each property for
every subject.

Each row of the property table has a unique key which is the subject of
each triple. Being unique, it is assuming one subject - one row.


If your data is one subject, one RDFS.seeAlso, a property table could be
used. If your data is one subject, potentially many RDFS.seeAlso, then
PropertyTable isn't the right abstaction.

GraphPropertyTable is the Graph implementation over PropertyTable.
Graphs are central to Jena.  A quick look at the code and I think it has
bugs (it ignores the subject in a Graph.find operation which looks wrong
to me).

Personally, I'd consider not using that at all but instade doing your
own implementation of Graph by extending GraphBase ; you only have to
implement:

performAdd( Triple t )
performDelete( Triple t )
graphBaseFind(Triple triplePattern)

then check triple added match your restriction to RDFS.seeAlso
Choose the datastructure to store the (subject, object) pairs needed.
(A Multimap<Node,Node> for example).

And write test cases :-)

 Hope that helps,
 Andy

The name is taken from this earlier work:
http://www.hpl.hp.com/techreports/2006/HPL-2006-140.html
which is for a SQL-storage system no longer in Jena.


On 28/02/18 10:31, Samita Bai  / PhD CS Scholar @ City Campus wrote:
> Dear Andy,
>
>
> I am working on my Ph.D thesis and I have created a dataset of triples in 
> which the property is same (i.e. RDFS.seeAlso), means I have only one 
> property for all triples. I thought I will be creating a property table with 
> one column and many rows. And I coded it too. But I am bit concerned because 
> property table is now deprecated.
>
>
> Please suggest me any indexing or storing mechanism where we want to store 
> only one property for many triples.
>
>
> Thanks & Regards,
>
> Samita Bai
>
> 
> From: Andy Seaborne <a...@apache.org>
> Sent: 28 February 2018 15:26:25
> To: users@jena.apache.org
> Subject: Re: Jena Property Table
>
> Hi Samita,
>
> The jena-csv module sees less attention than the major modules and is
> considered "legacy".  That said, it is not going away any time soon and
> the source code will always be available.
>
> Could you say something about your project and what are you trying to do
> with property tables?  Maybe there is a different approach somewhere.
>
>   Andy
>
>
>
> On 28/02/18 09:36, Samita Bai  / PhD CS Scholar @ City Campus wrote:
>> Oh Ok, then please follow this link
>>
>>
>> https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable
>>
>> [https://avatars3.githubusercontent.com/u/47359?s=400=4]<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
>>
>> apache/jena<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
>> github.com
>> jena - Mirror of Apache Jena
>>
>>
>>
>>
>>
>> 
>> From: Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
>> Sent: 28 February 2018 13:44:33
>> To: users@jena.apache.org
>> Subject: Re: Jena Property Table
>>
>> Attachments do not work on this mailing list.
>>
>>
>> On 28.02.2018 09:21, Samita Bai / PhD CS Scholar @ City Campus wrote:
>>>
>>> Dear Lorenz,
>>>
>>>
>>> I have attached the screenshot, I am talking about property table in
>>> jena csv package. Please have a look and suggest me.
>>>
>>>
>>> Regards,
>>>
>>> 
>>> *From:* Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
>>> *Sent:* 28 February 2018 13:07:47
>>> *To:* users@jena.apache.org
>>> *Subject:* Re: Jena Property Table
>>>
>>> Can you be a bit more precise please? What exactly is deprecated? And
>>> what do you want to do in your project?
>>>
>>>
>>> On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:
>>>> Hello Jena team,
>>>>
>>>>
>>

Re: Jena Property Table

2018-02-28 Thread Andy Seaborne
The PropertyTable abstraction is for regular data where for each subject 
there are the same properties, and the same number of each property for 
every subject.


Each row of the property table has a unique key which is the subject of 
each triple. Being unique, it is assuming one subject - one row.



If your data is one subject, one RDFS.seeAlso, a property table could be 
used. If your data is one subject, potentially many RDFS.seeAlso, then 
PropertyTable isn't the right abstaction.


GraphPropertyTable is the Graph implementation over PropertyTable. 
Graphs are central to Jena.  A quick look at the code and I think it has 
bugs (it ignores the subject in a Graph.find operation which looks wrong 
to me).


Personally, I'd consider not using that at all but instade doing your 
own implementation of Graph by extending GraphBase ; you only have to 
implement:


performAdd( Triple t )
performDelete( Triple t )
graphBaseFind(Triple triplePattern)

then check triple added match your restriction to RDFS.seeAlso
Choose the datastructure to store the (subject, object) pairs needed. 
(A Multimap<Node,Node> for example).


And write test cases :-)

Hope that helps,
Andy

The name is taken from this earlier work:
http://www.hpl.hp.com/techreports/2006/HPL-2006-140.html
which is for a SQL-storage system no longer in Jena.


On 28/02/18 10:31, Samita Bai  / PhD CS Scholar @ City Campus wrote:

Dear Andy,


I am working on my Ph.D thesis and I have created a dataset of triples in which 
the property is same (i.e. RDFS.seeAlso), means I have only one property for 
all triples. I thought I will be creating a property table with one column and 
many rows. And I coded it too. But I am bit concerned because property table is 
now deprecated.


Please suggest me any indexing or storing mechanism where we want to store only 
one property for many triples.


Thanks & Regards,

Samita Bai


From: Andy Seaborne <a...@apache.org>
Sent: 28 February 2018 15:26:25
To: users@jena.apache.org
Subject: Re: Jena Property Table

Hi Samita,

The jena-csv module sees less attention than the major modules and is
considered "legacy".  That said, it is not going away any time soon and
the source code will always be available.

Could you say something about your project and what are you trying to do
with property tables?  Maybe there is a different approach somewhere.

  Andy



On 28/02/18 09:36, Samita Bai  / PhD CS Scholar @ City Campus wrote:

Oh Ok, then please follow this link


https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable

[https://avatars3.githubusercontent.com/u/47359?s=400=4]<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>

apache/jena<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
github.com
jena - Mirror of Apache Jena






From: Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
Sent: 28 February 2018 13:44:33
To: users@jena.apache.org
Subject: Re: Jena Property Table

Attachments do not work on this mailing list.


On 28.02.2018 09:21, Samita Bai / PhD CS Scholar @ City Campus wrote:


Dear Lorenz,


I have attached the screenshot, I am talking about property table in
jena csv package. Please have a look and suggest me.


Regards,


*From:* Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
*Sent:* 28 February 2018 13:07:47
*To:* users@jena.apache.org
*Subject:* Re: Jena Property Table

Can you be a bit more precise please? What exactly is deprecated? And
what do you want to do in your project?


On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:

Hello Jena team,


I have a query regarding Jena Property table, it is deprecated, is

any alternative provided for this? Should I use it in my project or not?



Please help me.


Regards,

Samita

P : Please consider the environment before printing this e-mail



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments

may contain confidential and privileged information. If you are not
the intended recipient, please notify the sender immediately by return
e-mail, delete this e-mail and destroy any copies. Any dissemination
or use of this information by a person other than the intended
recipient is unauthorized and may be illegal.






*P /: Please consider the environment before printing this e-mail/*



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments
may contain confidential and privileged information. If you are not
the intended recipient, please notify the sender immediately by return
e-mail, delete this e-mail and destroy any copies. Any di

Re: Jena Property Table

2018-02-28 Thread Samita Bai / PhD CS Scholar @ City Campus
Dear Andy,


I am working on my Ph.D thesis and I have created a dataset of triples in which 
the property is same (i.e. RDFS.seeAlso), means I have only one property for 
all triples. I thought I will be creating a property table with one column and 
many rows. And I coded it too. But I am bit concerned because property table is 
now deprecated.


Please suggest me any indexing or storing mechanism where we want to store only 
one property for many triples.


Thanks & Regards,

Samita Bai


From: Andy Seaborne <a...@apache.org>
Sent: 28 February 2018 15:26:25
To: users@jena.apache.org
Subject: Re: Jena Property Table

Hi Samita,

The jena-csv module sees less attention than the major modules and is
considered "legacy".  That said, it is not going away any time soon and
the source code will always be available.

Could you say something about your project and what are you trying to do
with property tables?  Maybe there is a different approach somewhere.

 Andy



On 28/02/18 09:36, Samita Bai  / PhD CS Scholar @ City Campus wrote:
> Oh Ok, then please follow this link
>
>
> https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable
>
> [https://avatars3.githubusercontent.com/u/47359?s=400=4]<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
>
> apache/jena<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
> github.com
> jena - Mirror of Apache Jena
>
>
>
>
>
> 
> From: Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
> Sent: 28 February 2018 13:44:33
> To: users@jena.apache.org
> Subject: Re: Jena Property Table
>
> Attachments do not work on this mailing list.
>
>
> On 28.02.2018 09:21, Samita Bai / PhD CS Scholar @ City Campus wrote:
>>
>> Dear Lorenz,
>>
>>
>> I have attached the screenshot, I am talking about property table in
>> jena csv package. Please have a look and suggest me.
>>
>>
>> Regards,
>>
>> ----
>> *From:* Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
>> *Sent:* 28 February 2018 13:07:47
>> *To:* users@jena.apache.org
>> *Subject:* Re: Jena Property Table
>>
>> Can you be a bit more precise please? What exactly is deprecated? And
>> what do you want to do in your project?
>>
>>
>> On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:
>>> Hello Jena team,
>>>
>>>
>>> I have a query regarding Jena Property table, it is deprecated, is
>> any alternative provided for this? Should I use it in my project or not?
>>>
>>>
>>> Please help me.
>>>
>>>
>>> Regards,
>>>
>>> Samita
>>>
>>> P : Please consider the environment before printing this e-mail
>>>
>>> 
>>>
>>> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments
>> may contain confidential and privileged information. If you are not
>> the intended recipient, please notify the sender immediately by return
>> e-mail, delete this e-mail and destroy any copies. Any dissemination
>> or use of this information by a person other than the intended
>> recipient is unauthorized and may be illegal.
>>>
>>> 
>>>
>>
>> *P /: Please consider the environment before printing this e-mail/*
>>
>> 
>>
>> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments
>> may contain confidential and privileged information. If you are not
>> the intended recipient, please notify the sender immediately by return
>> e-mail, delete this e-mail and destroy any copies. Any dissemination
>> or use of this information by a person other than the intended
>> recipient is unauthorized and may be illegal.
>>
>> 
>
>
> P : Please consider the environment before printing this e-mail
>
> 
>
> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may 
> contain confidential and privileged information. If you are not the intended 
> recipient, please notify the sender immediately by return e-mail, delete this 
> e-mail and destroy any copies. Any dissemination or use of this information 
> by a person other than the intended recipient is unauthorized and may be 
> illegal.
>
> 
>

P : Please consider the environment before printing this e-mail



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may 
contain confidential and privileged information. If you are not the intended 
recipient, please notify the sender immediately by return e-mail, delete this 
e-mail and destroy any copies. Any dissemination or use of this information by 
a person other than the intended recipient is unauthorized and may be illegal.




Re: Jena Property Table

2018-02-28 Thread Andy Seaborne

Hi Samita,

The jena-csv module sees less attention than the major modules and is 
considered "legacy".  That said, it is not going away any time soon and 
the source code will always be available.


Could you say something about your project and what are you trying to do 
with property tables?  Maybe there is a different approach somewhere.


Andy



On 28/02/18 09:36, Samita Bai  / PhD CS Scholar @ City Campus wrote:

Oh Ok, then please follow this link


https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable

[https://avatars3.githubusercontent.com/u/47359?s=400=4]<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>

apache/jena<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
github.com
jena - Mirror of Apache Jena






From: Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
Sent: 28 February 2018 13:44:33
To: users@jena.apache.org
Subject: Re: Jena Property Table

Attachments do not work on this mailing list.


On 28.02.2018 09:21, Samita Bai / PhD CS Scholar @ City Campus wrote:


Dear Lorenz,


I have attached the screenshot, I am talking about property table in
jena csv package. Please have a look and suggest me.


Regards,


*From:* Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
*Sent:* 28 February 2018 13:07:47
*To:* users@jena.apache.org
*Subject:* Re: Jena Property Table

Can you be a bit more precise please? What exactly is deprecated? And
what do you want to do in your project?


On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:

Hello Jena team,


I have a query regarding Jena Property table, it is deprecated, is

any alternative provided for this? Should I use it in my project or not?



Please help me.


Regards,

Samita

P : Please consider the environment before printing this e-mail



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments

may contain confidential and privileged information. If you are not
the intended recipient, please notify the sender immediately by return
e-mail, delete this e-mail and destroy any copies. Any dissemination
or use of this information by a person other than the intended
recipient is unauthorized and may be illegal.






*P /: Please consider the environment before printing this e-mail/*



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments
may contain confidential and privileged information. If you are not
the intended recipient, please notify the sender immediately by return
e-mail, delete this e-mail and destroy any copies. Any dissemination
or use of this information by a person other than the intended
recipient is unauthorized and may be illegal.





P : Please consider the environment before printing this e-mail



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may 
contain confidential and privileged information. If you are not the intended 
recipient, please notify the sender immediately by return e-mail, delete this 
e-mail and destroy any copies. Any dissemination or use of this information by 
a person other than the intended recipient is unauthorized and may be illegal.





Re: Jena Property Table

2018-02-28 Thread Samita Bai / PhD CS Scholar @ City Campus
Oh Ok, then please follow this link


https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable

[https://avatars3.githubusercontent.com/u/47359?s=400=4]<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>

apache/jena<https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable>
github.com
jena - Mirror of Apache Jena






From: Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
Sent: 28 February 2018 13:44:33
To: users@jena.apache.org
Subject: Re: Jena Property Table

Attachments do not work on this mailing list.


On 28.02.2018 09:21, Samita Bai / PhD CS Scholar @ City Campus wrote:
>
> Dear Lorenz,
>
>
> I have attached the screenshot, I am talking about property table in
> jena csv package. Please have a look and suggest me.
>
>
> Regards,
>
> 
> *From:* Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
> *Sent:* 28 February 2018 13:07:47
> *To:* users@jena.apache.org
> *Subject:* Re: Jena Property Table
>
> Can you be a bit more precise please? What exactly is deprecated? And
> what do you want to do in your project?
>
>
> On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:
> > Hello Jena team,
> >
> >
> > I have a query regarding Jena Property table, it is deprecated, is
> any alternative provided for this? Should I use it in my project or not?
> >
> >
> > Please help me.
> >
> >
> > Regards,
> >
> > Samita
> >
> > P : Please consider the environment before printing this e-mail
> >
> > 
> >
> > CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments
> may contain confidential and privileged information. If you are not
> the intended recipient, please notify the sender immediately by return
> e-mail, delete this e-mail and destroy any copies. Any dissemination
> or use of this information by a person other than the intended
> recipient is unauthorized and may be illegal.
> >
> > 
> >
>
> *P /: Please consider the environment before printing this e-mail/*
>
> 
>
> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments
> may contain confidential and privileged information. If you are not
> the intended recipient, please notify the sender immediately by return
> e-mail, delete this e-mail and destroy any copies. Any dissemination
> or use of this information by a person other than the intended
> recipient is unauthorized and may be illegal.
>
> 


P : Please consider the environment before printing this e-mail



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may 
contain confidential and privileged information. If you are not the intended 
recipient, please notify the sender immediately by return e-mail, delete this 
e-mail and destroy any copies. Any dissemination or use of this information by 
a person other than the intended recipient is unauthorized and may be illegal.




Re: Jena Property Table

2018-02-28 Thread Lorenz Buehmann
Attachments do not work on this mailing list.


On 28.02.2018 09:21, Samita Bai / PhD CS Scholar @ City Campus wrote:
>
> Dear Lorenz,
>
>
> I have attached the screenshot, I am talking about property table in
> jena csv package. Please have a look and suggest me.
>
>
> Regards,
>
> 
> *From:* Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
> *Sent:* 28 February 2018 13:07:47
> *To:* users@jena.apache.org
> *Subject:* Re: Jena Property Table
>  
> Can you be a bit more precise please? What exactly is deprecated? And
> what do you want to do in your project?
>
>
> On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:
> > Hello Jena team,
> >
> >
> > I have a query regarding Jena Property table, it is deprecated, is
> any alternative provided for this? Should I use it in my project or not?
> >
> >
> > Please help me.
> >
> >
> > Regards,
> >
> > Samita
> >
> > P : Please consider the environment before printing this e-mail
> >
> > 
> >
> > CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments
> may contain confidential and privileged information. If you are not
> the intended recipient, please notify the sender immediately by return
> e-mail, delete this e-mail and destroy any copies. Any dissemination
> or use of this information by a person other than the intended
> recipient is unauthorized and may be illegal.
> >
> > 
> >
>
> *P /: Please consider the environment before printing this e-mail/*
>
> 
>
> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments
> may contain confidential and privileged information. If you are not
> the intended recipient, please notify the sender immediately by return
> e-mail, delete this e-mail and destroy any copies. Any dissemination
> or use of this information by a person other than the intended
> recipient is unauthorized and may be illegal.
>
> 



Re: Jena Property Table

2018-02-28 Thread Samita Bai / PhD CS Scholar @ City Campus
Dear Lorenz,


I have attached the screenshot, I am talking about property table in jena csv 
package. Please have a look and suggest me.


Regards,


From: Lorenz Buehmann <buehm...@informatik.uni-leipzig.de>
Sent: 28 February 2018 13:07:47
To: users@jena.apache.org
Subject: Re: Jena Property Table

Can you be a bit more precise please? What exactly is deprecated? And
what do you want to do in your project?


On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:
> Hello Jena team,
>
>
> I have a query regarding Jena Property table, it is deprecated, is any 
> alternative provided for this? Should I use it in my project or not?
>
>
> Please help me.
>
>
> Regards,
>
> Samita
>
> P : Please consider the environment before printing this e-mail
>
> 
>
> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may 
> contain confidential and privileged information. If you are not the intended 
> recipient, please notify the sender immediately by return e-mail, delete this 
> e-mail and destroy any copies. Any dissemination or use of this information 
> by a person other than the intended recipient is unauthorized and may be 
> illegal.
>
> 
>


P : Please consider the environment before printing this e-mail



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may 
contain confidential and privileged information. If you are not the intended 
recipient, please notify the sender immediately by return e-mail, delete this 
e-mail and destroy any copies. Any dissemination or use of this information by 
a person other than the intended recipient is unauthorized and may be illegal.




Re: Jena Property Table

2018-02-28 Thread Lorenz Buehmann
Can you be a bit more precise please? What exactly is deprecated? And
what do you want to do in your project?


On 28.02.2018 08:45, Samita Bai / PhD CS Scholar @ City Campus wrote:
> Hello Jena team,
>
>
> I have a query regarding Jena Property table, it is deprecated, is any 
> alternative provided for this? Should I use it in my project or not?
>
>
> Please help me.
>
>
> Regards,
>
> Samita
>
> P : Please consider the environment before printing this e-mail
>
> 
>
> CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may 
> contain confidential and privileged information. If you are not the intended 
> recipient, please notify the sender immediately by return e-mail, delete this 
> e-mail and destroy any copies. Any dissemination or use of this information 
> by a person other than the intended recipient is unauthorized and may be 
> illegal.
>
> 
>



Jena Property Table

2018-02-27 Thread Samita Bai / PhD CS Scholar @ City Campus
Hello Jena team,


I have a query regarding Jena Property table, it is deprecated, is any 
alternative provided for this? Should I use it in my project or not?


Please help me.


Regards,

Samita

P : Please consider the environment before printing this e-mail



CONFIDENTIALITY / DISCLAIMER NOTICE: This e-mail and any attachments may 
contain confidential and privileged information. If you are not the intended 
recipient, please notify the sender immediately by return e-mail, delete this 
e-mail and destroy any copies. Any dissemination or use of this information by 
a person other than the intended recipient is unauthorized and may be illegal.