|
|
|
Re: [teneo/jpox] Question of design of metadata [message #86815 is a reply to message #86759] |
Tue, 19 June 2007 22:26 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Martin Taal![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=mtaal%40springsite.com) Messages: 5468 Registered: July 2009 |
Senior Member |
|
|
Hi Julia,
See inline below.
gr. Martin
Julia wrote:
> Hi Martin,
>
> My current application outputs all data to xml files. We want to be able
> to scale upwards to use a database. but we still need to ability to use
> file datastores. We want to maintain a common code base iwthout
> radically altering previous code.
>
> 1) Yes I think that having a single set of base.xsd tables should work.
> I will test this out. But I'm a little puzzled how the system would know
> what row belongs to what xsds? There does not appear to be anyting
> linking the referring xsd to the base.xsd. Do I have to add that as say
> a separate column in base.xsd?
MT>> I am not sure what you mean, the link between the referring xsd and the base.xsd is the
ereference from the referring xsd to the base.xsd, maybe I am missing something?
Or do you mean that when creating the actual data in the tables you don't know which data was
entered for the base.xsd as such or which data is refered to from the other xsd's?
>
> 2) Navigation.xsd refers to topology.xsd but as it turns out
> topology.xsd data is divided into to separate xml files (topology.xml
> and global-topology.xml). So data from both these xmls can be used in
> navigation.xsd tables. I was going to create separate tables for
> topology,global-topology.xml and for the topology elements in
> navigation.xsd. But I'm not sure if this is the right direction to go.
> Could I use one set of topolopy.xsd tables and some how recognize what
> row belongs to what xsd?
MT>> I am not sure what you mean with 'recognize what row belongs to what xsd', do mean what rows
belongs to what xml?
>
> 3) Yes a single metadata file per xsd would be easier to maintain.
>
> Julia
>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
|
|
Re: [teneo/jpox] Question of design of metadata [message #607018 is a reply to message #86759] |
Tue, 19 June 2007 22:26 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Martin Taal![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=mtaal%40springsite.com) Messages: 5468 Registered: July 2009 |
Senior Member |
|
|
Hi Julia,
See inline below.
gr. Martin
Julia wrote:
> Hi Martin,
>
> My current application outputs all data to xml files. We want to be able
> to scale upwards to use a database. but we still need to ability to use
> file datastores. We want to maintain a common code base iwthout
> radically altering previous code.
>
> 1) Yes I think that having a single set of base.xsd tables should work.
> I will test this out. But I'm a little puzzled how the system would know
> what row belongs to what xsds? There does not appear to be anyting
> linking the referring xsd to the base.xsd. Do I have to add that as say
> a separate column in base.xsd?
MT>> I am not sure what you mean, the link between the referring xsd and the base.xsd is the
ereference from the referring xsd to the base.xsd, maybe I am missing something?
Or do you mean that when creating the actual data in the tables you don't know which data was
entered for the base.xsd as such or which data is refered to from the other xsd's?
>
> 2) Navigation.xsd refers to topology.xsd but as it turns out
> topology.xsd data is divided into to separate xml files (topology.xml
> and global-topology.xml). So data from both these xmls can be used in
> navigation.xsd tables. I was going to create separate tables for
> topology,global-topology.xml and for the topology elements in
> navigation.xsd. But I'm not sure if this is the right direction to go.
> Could I use one set of topolopy.xsd tables and some how recognize what
> row belongs to what xsd?
MT>> I am not sure what you mean with 'recognize what row belongs to what xsd', do mean what rows
belongs to what xml?
>
> 3) Yes a single metadata file per xsd would be easier to maintain.
>
> Julia
>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
Powered by
FUDForum. Page generated in 0.05347 seconds