ehr is a great concept, and Ron's Java-kernel is a
great piece of work, the C# kernel is to, I am sure, it is build close
to the source of design.
I am building a Java-implementation too, based on Rong's kernel, he has
solved many problems and set directions, I am now using, and extending
t
> Bert Verhees wrote:
>>
>> In so far, not because I like to disagree, but regrettable, many of the
>> function/method-bodies in the Eiffel-code are empty. Eiffel seems merely
>> to be/have been used as a kind of case-tool instead of really building
>> a openehr k
% functionally, only I have bad luck when
looking at the source (looking at those 10% not ready?)
I don't know, please explain to me how to find the reference Eiffel
implementation source as used in the ADL-workbench.
Thanks very much
kind regards
Bert Verhees
-BEGIN PGP SIGNATURE-
Hi all,
I am building an application on base of an OpenEhr kernel.
I would be very happy if people can give some ideas about one question I
have.
I don't need complete technical worked out docuemnts (although I don't
mind to recieve them)
But just some hints make me happy.
My problem is, I am
Peter Gummer schreef:
> Bert Verhees wrote:
>
>> There is only one important step, that is, what is a good way to connect
>> the data to the archetypes. Is this dADL, or better XML, or other means.
>>
>> Are there any ideas?
>>
>
> Does this h
Tim Cook schreef:
> Hi Bert,
>
> [this thread may belong on the implementers list?]
>
> On Wed, 2008-04-23 at 14:43 +0200, Bert Verhees wrote:
>
>
>> I have my system ready in a way that it eats archetypes, and data
>> belonging to those archetypes, and stores
Tim Cook schreef:
> Hi Bert,
>
> Please note that this is MY understanding of the reference model and is
> subject to change by the expert opinion of others.
>
> On Wed, 2008-04-23 at 16:16 +0200, Bert Verhees wrote:
>
>> Archetypes are in fact RM-objects, I hav
Tim Cook schreef:
> On Wed, 2008-04-23 at 17:11 +0200, Bert Verhees wrote:
>
>
>> I want to hand this archetype with data, for example from a webform, or
>> a message interpreter to my kernel which knows what to do with it.
>>
>
> ...
>
>
>>
Thanks Heath, I must consider your writing, and tomorrow is Queens-day,
so it can take a few days before I answer
Bert
> Hola Pablo,
>
> there have been some discussions about the demographics on this list
> recently. Please have a look at the list archive
> http://www.nabble.com/openEHR-f18276.html
>
> You can find some demographics archetypes here:
> http://www.openehr.org/svn/knowledge/archetypes/dev/adl/openehr
> Hola Pablo,
>
> there have been some discussions about the demographics on this list
recently. Please have a look at the list archive
> http://www.nabble.com/openEHR-f18276.html
>
> You can find some demographics archetypes here:
> http://www.openehr.org/svn/knowledge/archetypes/dev/adl/openehr/d
Thilo Schuler schreef:
> Hi everybody,
>
> just a short note:
>
> I am more a front-end person (plan to start a OSS GUI project in
> 2008), although I have an vested interested in a open persistence
> solution, since I would like to see an end-to-end system demonstrator
> based on OSS components (
Thilo Schuler schreef:
> For openEHR I will concentrate on the GUI part. Had to investigate it
> for a uni project.
>
> Just wanted to let everybody know about IBM DB2 9.5, which I think is
> a fair, "uncrippled" offer.
oh
>
> On Jan 2, 2008 5:18 PM, Bert V
Bert Verhees schreef:
> Thilo Schuler schreef:
>> For openEHR I will concentrate on the GUI part. Had to investigate it
>> for a uni project.
>>
>> Just wanted to let everybody know about IBM DB2 9.5, which I think is
>> a fair, "uncrippled" offer.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karsten Hilbert schreef:
>> True, API persistence layer should be generic as said previously
>> mentioned. Although originally it needs to be developed based on a
>> reference DBMS and for this DB2 looks attractive (quick results?) on
>> first sight.
>
>>
>> regards Hugh
>>
>>
>>
>> Thilo Schuler wrote:
>> True, API persistence layer should be generic as said previously
>> mentioned. Although originally it needs to be developed based on a
>> reference DBMS and for this DB2 looks attractive (
Thomas Beale schreef:
> Bert Verhees wrote:
>> People discuss very seriuous all kind of subjects, very deeply, that is
>> OK, but why do they never discuss a solution to a Persistence-layer-API?
>> (not the layer itself, only the API.)
>> Another thing that is never dis
> If one wants an implementation to happen one needs to start
> one (and preferably open source it). From there one can go
> back and define a sensible API between specs and
> implementation which will not fall down with the next
> implementation.
>
Exactly that is what I am doing, and to not r
Karsten Hilbert schreef:
> On Fri, Jan 04, 2008 at 02:31:57PM +0100, Bert Verhees wrote:
>
>
>> Exactly that is what I am doing, and to not reinvent wheels
>> unnecessarily,
>>
> Good !
>
>
>> I am calling others to help do it.
>>
Tim Cook schreef:
> Hi All,
>
> I have watched this thread with great interest. My first question is;
> Why?
>
> Why is there such an interest in developing a specific persistence layer
> API for openEHR? I think that this is an area where we should encourage
> many implementations to follow the
Tim Cook schreef:
> Hi All,
>
> I have watched this thread with great interest. My first question is;
> Why?
>
> Why is there such an interest in developing a specific persistence layer
> API for openEHR? I think that this is an area where we should encourage
> many implementations to follow the
And the last thing I want to say about this.
You changed the subject of the discussion, I do not blame you (it is
called hijacking of subject), but it says something.
It says that you think that the discussion I was involved should change
to another discussion
http://en.wikipedia.org/wiki/Thread_
Thomas Beale schreef:
> Bert Verhees wrote:
>
>> But is has, in my opinion nothing to do with that. Maybe when the EQL
>> definition is ready to use (I don't see much of discussion about this
>> subject, but maybe the EQL discussion is a private discussion?), than
&
Thomas Beale schreef:
> Bert Verhees wrote:
>
>> The most important reason (amongst others) is that a defined API would
>> speed up the development of more implementations, also other
>> architectures could benefit from this. At this moment, there is hardly a
>>
change it, but start a new one, because, it
are also the messageID's which mess up.
Doesn't matter for now
Bert
> Cheers,
>
> Tim
>
>
> On Sat, 2008-01-05 at 11:22 +0100, Bert Verhees wrote:
>
>> And the last thing I want to say about this.
>>
Thomas Beale schreef:
> Bert Verhees wrote:
>
>> What I need is a strongly expressed intention to do something in a way I
>> suggest.
>> Serious people, not , say, pbublish your thing, and we will see. That is
>> not good enough.
>>
>> If we have
Tim Cook schreef:
> On Sat, 2008-01-05 at 16:59 +0100, Bert Verhees wrote:
>
>> Thomas Beale schreef:
>>
>>> Probably you need to clarify the concrete basis of this discussion from
>>> your point of view.
>>>
>>>
>
Karsten Hilbert schreef:
> On Sun, Jan 06, 2008 at 10:05:14AM +0100, Bert Verhees wrote:
>
>
>>> Maybe some clarification will help. Is there a place where you have
>>> made your Java implementation open source and available to others for
>>> assessment?
>
> the paths /items[at0002] and /items[at0003] always stand for themselves.
> The latter would not be able to have an internal reference to the
> former, because that would imply that the latter information structure
> could contain the former as a sub-structure. You can always work out
> wha
gt; Regards
>
> Heath
>
> Heath Frankel
> Product Development Manager
> Ocean Informatics
>
>
>> -Original Message-
>> From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
>> bounces at openehr.org] On
board and contribute, but
> there always needs some ONE to plant the seed.
>
> Heath
>
>
>> -Original Message-
>> From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
>> bounces at openehr.org] On Behalf Of Bert Verhees
>> Sent:
Probably is the version information in the pom.xml from adl-parser not the
same as the required version in dependencies of pom.xml of adl-serializer, or
you did not build adl-parser, so the required jar file does not exist on your
system.
Please check your pom-files and rebuild the packages.
B
x27;mvn
> install' for the adl-parser in there, it will build the
> adl-parser-with-dependencies.jar. With that, I can then build the
> adl-serializer then.
>
> It didn't get clear to me from the quick-start doc, that I have to do it
> this way. Or is it supposed to be done lik
Hi,
I wrote another message before, earlier this week, but that was addresses to
the Java-list, but I now think it is a problem of specification.
--
I want to know, is it in all cases possible to guess the rm-type in a dadl-
construct? I ask this, because the specification says:
On Thursday 24 July 2008 17:29:41 Thomas Beale wrote:
> Bert Verhees wrote:
> > Hi,
> >
> > I wrote another message before, earlier this week, but that was addresses
> > to the Java-list, but I now think it is a problem of specification.
> > --
> I would also like to start importing openEHR content into PatientOS in
> the new few weeks. I am less concerned with the data at this point,
> rather I would like to be able to take a template (perhaps initially
> just archetypes and I will combine them internally to be larger forms)
> import
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Ocean is also developing the idea of a Template Data Schema, which will be
> published as a draft on openEHR in the coming months. This does provide a
> specific XML schema for a template (or combined collect of archetypes) where
> the XML element
Tim Cook schreef:
> On Mon, 2008-11-03 at 14:35 -0600, Ignacio Valdes wrote:
>
>> Action is needed
>> on your part to answer the question: If open source is so great why is
>> no one using it?
>>
>
> There is a very simple answer. The current crop of offerings doesn't
> solve the problem
Tim Cook schreef:
> hi Bert,
>
> On Tue, 2008-11-04 at 09:03 +0100, Bert Verhees wrote:
>
>>>
>>>
>> Closed source doesn't solve the interoperability-problem either, at
>> least it didn't last twenty years, but it is use
Thomas Beale schreef:
> I also don't think that the metric means much, but for the record, there
> are 4 million patients in an openEHR server (v0.95) in Australia, some
> thousands (ultimate design vlume 1,000,000 EHRs) in the Netherlands, and
> probably some thousands in Brazil - that I know d
Gerard Freriks schreef:
> Perhaps you have not noticed
>
> The question was about Open Source and not about commercial
> proprietary ehr systems
Sorry Gerard, there were more closed systems discussed under this topic.
>
> Gf
>
> Sent from my iPhone
Very small keyboard?
Bert
Gerard Freriks schreef:
> Bert,
>
> What is the definition of 'closed system'?
Excuse me, I meant "closed source", typo.
Thomas discussed the Ocean system, which is (as he said himself) closed
source, which is (in my opinion) a commercial proprietary system.
There is nothing wrong with that, but,
Hi Mathias, there are a few things missing, you have to write them
yourself, or find someone who shares his work.
To keep it short for now, you need a persistence-layer, in which you can
store the RM-objects. There are many ways to build this, hibernate, XML,
object-database
You also need
> In this case, we use the API of Google Health Data to send or retrieve data
> so the openEHR EHR Service API isn't needed. Well, this really isn't the
> best mailing list for this type of discussion, let's continue this on
> technical or implementer list.
>
I think you are right, this must be do
All information below is published in the Dutch press, specially, the
always good informed website on health ICT: Qure (http://www.qure.nl).
Normally, I don't repeat press-messages on this or any other
mailinglist, but this looks very important to many of us, who are
working on a OpenEhr-impleme
Ian McNicoll schreef:
> Hi Seref,
>
> You said:
> "What about the legal consequences? For example: I can remember being
> told my multiple sources that it is not legal to store healthcare data
> of a UK citizen outside of UK."
>
> I am not aware of any law restricting the storage of healthcare data
Seref Arikan schreef:
> Hi Berth,
> Please let me add my set of questions to yours, for I have not been
> able to figure out the overall scheme of the discussed setup. Maybe
> its my fault, and I apologize in advance if I've missed the answers in
> the discussion or on the web.
> What is the ext
According to the documentation
(http://www.openehr.org/releases/1.0.1/architecture/rm/data_types_im.pdf) should
be marked abstract.
Bert
; From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
> > bounces at openehr.org] On Behalf Of Bert Verhees
> > Sent: Saturday, 11 April 2009 7:00 PM
> > To: openehr-technical at openehr.org
> > Subject: possible error small error in BaseTypes.xsd (vers
Op dinsdag 14-04-2009 om 14:48 uur [tijdzone +0100], schreef Thomas
Beale:
> Bert,
>
> can you raise this on the openEHR SPEC project tracker on Jira.
Sorry Thomas, maybe it is a question of authorization, but Specification
is not offered to me in Jira to add an Issue
(the other projects are)
B
> *We thought about this a number of times over the last few years. The
> problem is that many archetypes are completely compatible with multiple
> versions of the reference model, because changes occur in other parts of
> the reference model. So marking an archetype with "RM version 1.0"
> do
Thomas Beale schreef:
> Bert Verhees wrote:
>
>>> *We thought about this a number of times over the last few years. The
>>> problem is that many archetypes are completely compatible with multiple
>>> versions of the reference model, because changes occur in
>> Exactly what I mean, we must agree, which part of the version-number
>> indicates a possible incompatibility concernig archetypes/RM-version.
>> Bert
>>
>
> Don't try to get too complicated. Just have a list that states that
> this archetype has been validated against these RM versions. I
>
> Let's say RM=['1.0.1']
>
> (okay so I apologize for my Python syntax, but it's easy to read).
>
> Second: An archetype is edited (whether it's version changes or not)
> against a tool using RM 1.0.2.
>
> The RM = is now RM=['1.0.1,'1.0.2]
>
>
As I wrote before, if the choice will be that
> yes - but to do this, they need to be working with templates.
> Archetypes on their own don't make sense as direct data-capture models.
Thomas, I wonder why this is, maybe you can explain this or point to an
explanation.
Thanks
Bert
>> hope this clarifies
Thanks, Thomas, it clarifies why archetypes do not suffice in
application-context for data entry/presentation.
For the moment, we can live without templates (leave it to form-developers
to define where to use a specific archetype-item), or fabricate
template-definition for i
Williamtfgoossen at cs.com schreef:
> In a message dated 14-3-2009 17:23:18 W. Europe Standard Time,
> caultonpos at gmail.com writes:
>
>> How many more types of archetypes are we envisioning to support?
>
>
> I think the tools need to support ANY archetype that represents valid
> content in hea
Williamtfgoossen at cs.com schreef:
> In a message dated 14-3-2009 17:23:18 W. Europe Standard Time,
> caultonpos at gmail.com writes:
>
>> How many more types of archetypes are we envisioning to support?
>
>
> I think the tools need to support ANY archetype that represents valid
> content in hea
Heath Frankel schreef:
>
> Bert,
>
> The Ocean Archetype Editor was the first Archetype Editor written some
> 6+ years ago. It was implemented to support only EHR archetypes in a
> way that these RM types where implemented explicitly within the Editor
> providing the specific capability for cli
Sam Heard schreef:
>
> Hi Bert and all
>
>
>
> The demographic model was proposed a long time ago and is meant to
> support a demographic service -- like a PMI. These archetypes are not
> in the EHR. The EHR and demographic service can share archetypes like
> data_structures, clusters and elem
Thomas Beale schreef:
> Williamtfgoossen at cs.com wrote:
>
>> Sam,
>>
>> this below - demographics not relevant in the EHR is like the most
>> confusing comment ever I heard from you.
>>
>> About whom are we going to create a EHR then? If it is not possible to
>> have the individuals name, id
Sam, I often brought this subject up, maybe five times last year, the
answer differed from, "We'll add demographic archetypes to the
ArchetypeEditor within a year" to now carefully stating in a direction
that demographic archetypes will loose the relevance. I know Sam, the
latter is your positi
tc should be modelled
> in the EHR Model (though again, in reality, there may be some local
> variation in implementation.)
>
> Cheers,
>
> Ian
>
>
>
> Ian
>
>
> Dr Ian McNicoll
> office / fax +44(0)141 560 4657
> mobile +44 (0)775 209 7859
>
Bert Verhees schreef:
> Ian McNicoll schreef:
>> Hi Bert,
>>
>> Just for clarification, the work I have been doing in adding
>> demographics archetype support to the Ocean Editor is a personal
>> project, intended for the openEHR community and not an Ocean funde
Hi,
I am reading the document
http://www.openehr.org/releases/1.0.1/architecture/rm/common_im.pdf
In there, Chapter 5, page 39 I read:
"It provides a means of versioning FOLDER structures over
time, which is useful in the EHR, Demographics service or anywhere else
where Folders are used to group
hreef Thomas
Beale:
>
> Hi Bert,
>
> Although it is not explicitly stated, you could easily use a Folder
> directory in a demographic service that was managing Party objects.
> The Folders are just contained in their own VERSIONED_FOLDER object.
>
> - thomas beale
>
>
> that would be what I would do; the current spec does not say how to do
> this. I don't even know if it is useful in the demographic service ;-)
It is just that it is mentioned in the specifications of the reference
model, like I quoted, two emails ago.
So there is, (as I understand what you
Bert
Tim Cook schreef:
> Hi Bert,
>
> On Wed, 2009-05-06 at 14:46 +0200, Bert Verhees wrote:
>
>>> that would be what I would do; the current spec does not say how to do
>>> this. I don't even know if it is useful in the demographic service ;-)
>>>
An international airport/train station nearby would be good, it saves
days of traveling.
Bert
Op 27-11-09 17:25, Thomas Beale schreef:
>
> This is an initial informal question to the community about interest
> in an openEHR conference / meeting, probably initially located in
> Europe. Possibly ac
Greetings,
> Mikael
>
>
> From: openehr-technical-bounces at
> chime.ucl.ac.uk<mailto:openehr-technical-bounces at chime.ucl.ac.uk>
> [mailto:openehr-technical-bounces at chime.ucl.ac.uk] On Behalf Of Bert
> Verhees
> Sent: den 27 november 200
It is a library, you should write your own software to run it. There
should to be Junit-tests in the repository, you can look at them for
examples how to use the library
good luck
Bert
Op vrijdag 02-10-2009 om 10:45 uur [tijdzone +0100], schreef Paul
Linehan:
> Hi to all from Trinity College Dubl
Anyone already mentioned DocBook?
(I am sorry if I mention it again if someone already did)
It is an Oasis-standard. Here a list of others who use it:
http://wiki.docbook.org/topic/WhoUsesDocBook
People can format the layout as they like in any file-format they like.
Eventually a standaard PDF c
, because an
RM-object can only have one archetypeNodeID.
SO, please, help, a link to an explaining text somewhere will also do.
Thanks very much, and kind regards
Bert Verhees
sociate, CHIME, University College London
> openEHR Archetype Editorial Group
> Member BCS Primary Health Care SG Group www.phcsg.org
> <http://www.phcsg.org> / BCS Health Scotland
>
>
>
> On 22 August 2010 13:04, Bert Verhees <mailto:bert.verhees at rosa.
Honorary Senior Research Associate, CHIME, University College London
> openEHR Archetype Editorial Group
> Member BCS Primary Health Care SG Group www.phcsg.org
> <http://www.phcsg.org> / BCS Health Scotland
>
>
>
> On 23 August 2010 11:51, Bert Verhees <mailto:be
Please allow me a small question, I think, just for formality reasons.
Is a archetypeInternalRef always pointing to a node representing a
Locatable?
I haven't seen other way, but it is not explicitly mentioned in the ADL
1.4 specs
Thanks
Bert
e_node path would need to be a valid unique archetype
> path within the archetype.
>
> Regards
>
> Heath
>
>
>> -Original Message-
>> From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
>> bounces at openehr.org] On Behalf Of
Hi all,
About the Actor-class which has "roles" which are a set of PartyRef's
containing a link to version-containers having stored the role, instead
of directly linking to the role itself.
This is inconsistent to the support-specs, where a party-ref is
described as being a link to a identify a p
> It is imperative that DCM's are absolutely free to use and in the
> public domain. CEN/ISO and ANSI assure that with the standardisation
> IP rules in general.
> DCM's must be absolutely free from IP problems, well maintained in a
> formal, flexible, organisation, owned and controlled by all tha
Gerard,
It is possible to reject non-free archetypes and replace them by free
archetypes.
We have seen this mechanism many times, mostly the open standard wins,
even when it is technically slightly inferior, the openness is much more
important.
Than the non-free-snake will often byte its own tail
Op 10-02-10 14:32, Gerard Freriks schreef:
> Bert,
>
> There is only one answer.
> Hospitals we talk with have problems with the way IP is handled by
> openEHR.
> IP owned by two organisations (One UCL and the other Ocean
> Informatics) they consider not PUBLIC.
What is the problem, and on what is
Where you sleeping that you did not think about these urgent
IP-questions you bring up here?
A strange story.
regards
Bert Verhees
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20100210/cf72bd20/attachment.html>
you
discovered that you cannot use it? That you have to pay?
Where you sleeping that you did not think about these urgent
IP-questions you bring up here?
A strange story.
regards
Bert Verhees
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.
s that assumed values are most usually used in state, not
> data (e.g. assumed value of blood pressure position is sitting).
>
> Heath
>
>
>> -Original Message-
>> From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
>> bounce
are most usually used in state, not
>> data (e.g. assumed value of blood pressure position is sitting).
>>
>> Heath
>>
>>
>>> -Original Message-
>>> From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
>>> bounces at
Hi all,
I noticed that the JAVA ADL-parser marks a CObject existence as required
if it is not specified in ADL
If there is also an assumed value specified, then this is, in my opinion
conflicting, because the function of the assumed value is to use it when
there an attribute is not used
(page 21 A
Hi,
Excuse for the bit complex text below, I don't know how to say it more
simple
I have a small problem with the way ReverseRelationships are connected
to Party in the Demographic RM.
Maybe my problem is because of my misunderstanding.
The problem is not only conceptual, but it also causes p
Thanks, Thomas, for your reply.
>> The problem is that ReverseRelationships are a Set of LocatableRef.
>> This means that the PartyRelationship has to be stored before it can
>> be added to a party ReverseRelationship list.
>> The PartyRelationship has to be stored because LocatableRef takes a
Op 29-04-11 03:03, Heath Frankel schreef:
>
> I agree with Thomas, the reverse relationships should be derived from
> the forward relationships. The RM doesn't necessarily need to be
> reflected in the persistence model.
>
Thanks Heath, this is indeed a pitfall, trying to reflect the RM. I
som
Op 13-01-11 15:44, Tim Cook schreef:
> I choose the third one. There should be a mailing list for the
> development of ADL and tools.
I agree, except I do not want to receive them at all. I never read
SVN-information.
Just a notification when a release is delivered is fine for me.
I think anyway
Just for considering,
It would be a nice thing if GENERIC_ENTRY was an option in the
Archetype-Editor
(also demographics, but that is an old discussion)
Thanks,
Bert Verhees
Op 08-03-11 16:49, Diego Bosc? schreef:
> You can define openEHR demographic archetypes with LinkEHR
Thanks, I try it tomorrow, on a copy of my Eclipse (on Linux)
installation, because a few days ago I destroyed an Eclipse-installation
by installing a CDA-plugin in it. Now I am carefully
I let
Hi,
I have an archetype with following Element
ELEMENT[at0033] occurrences matches {0..1} matches {-- Condition Status
value matches {
DV_TEXT matches {*}
}
}
I noticed that it is not possible te create an Element-instance with
data-value null, because my own Object-validator
Hi,
I am sorry, but I am to busy to read all the discussions on future
ADL-versions.
So, now I have a small question, which possible is already explained,
Is it possible to write conditional constraints in future ADL?
The question is about implementing care-protocol into an archetype.
For exam
being finalised, but the general syntax will look
> like Xpath and the object model will be what you would expect from that.
>
> - thomas
>
> On 10/03/2011 15:48, Bert Verhees wrote:
>> Hi,
>>
>> I am sorry, but I am to busy to read all the discussions on future
>&g
finalised, so don't depend on it;
>>> however it is the left hand side that matters, i.e.
>>> $date_of_birth
>>> * environmental values, like
>>>o $current_date
>>>o $current_time
>>&
close to understanding of your criticism?
Bert
Op 23-03-11 12:07, Seref Arikan schreef:
> Also look at heartbeat is the problem here. My criticism stands, for
> every case your rules/guidelines go beyond data.
>
> Best Regards
> Seref
>
>
> On Wed, Mar 23, 2011 at 11:05 AM, B
Sounds reasonable,
thanks
Bert
Op 23-03-11 13:00, Thomas Beale schreef:
> On 23/03/2011 11:41, Bert Verhees wrote:
>> The idea is to implement guideline/rules etc in Archetypes.
>> In this way you can force software to look at some conditions if some
>> other conditions are
My two cents.
I wouldn't trust software which is not open source. You cannot judge if
it does its job well, especcially in long lasting use, like f.e. a
database, how do you know if it still works if your table reach the
million records and the table is 127 fields wide with on the second
field
On 16-09-11 19:17, Thomas Beale wrote:
> (Torvalds more or less still says that SVN is pretty hopeless, and in
> some ways he is right, depending on what your requirements are)
Torvalds even said that he passionately hated CVS, which he had to use
at Transmeta.
I feel the need to explain why ope
1 - 100 of 969 matches
Mail list logo
