I have to say, the more I look at YAML, the more I wonder what the
designers were thinking. For example, in this section of the spec,
multi-line quoted strings are only allowed if the 'key' is also quoted
(the strange looking JSON approach); if the key is not quoted (i.e.
'simple') then the
On 15/12/2011 11:31, Thomas Beale wrote:
I have to say, the more I look at YAML, the more I wonder what the
designers were thinking. For example, in this section of the spec,
http://yaml.org/spec/current.html#id2532720
multi-line quoted strings are only allowed if the 'key' is also quoted
Hi!
On Thu, Dec 15, 2011 at 12:44, Thomas Beale
thomas.beale at oceaninformatics.com wrote:
I have to say, the more I look at YAML, the more I wonder what the
designers were thinking. For example, in this section of the spec,
http://yaml.org/spec/current.html#id2532720
multi-line quoted
On 15/12/2011 12:51, Erik Sundvall wrote:
Hi!
Are you sure that is what it says?
Double quoted scalars are restricted to a single line when contained
inside a simple key.
well I read this to say:
* if you double quote a long String containing line breaks (if you
don't yet get into
.
To: For openEHR technical discussions
Subject: Re: Could YAML replace dADL as human readable AOM serialization format?
Oh sigh...
Trying to be open minded, thinking a few steps ahead, sharing thoughts and
regularly reevaluating design decisions does not seem to be appreciated by all
: Wednesday, 7 December 2011 11:30 p.m.
To: For openEHR technical discussions
Subject: Re: Could YAML replace dADL as human readable AOM serialization
format?
Oh sigh...
Trying to be open minded, thinking a few steps ahead, sharing thoughts and
regularly reevaluating design decisions does
I have no problems on having different representations. In fact,
having different representations means more happy people, not less
(for example, people has been using RDF to describe archetypes for
some time).
Anyway I love this kind of threads, as are great to see new
perspectives and
Erik,
Add my sigh next to yours... Lots of misunderstandings, will try to respond
to most obvious ones.
I have clearly expressed that all discussions here are useful. I've made no
connection to my agenda. My academic work does not even require the things
I've mentioned as high priority for
On 05/12/2011 12:36, Erik Sundvall wrote:
Hi!
On Mon, Dec 5, 2011 at 00:10, Heath Frankel
heath.frankel at oceaninformatics.com
mailto:heath.frankel at oceaninformatics.com wrote:
I think previously I had indicated I had no problem with the
stringified interval approach in XML,
On 06/12/2011 12:44, Seref Arikan wrote:
A bunch of responses, most of which should actually go to a wiki page
for Bosphorus
I've used binary serialization for AOM because although Eiffel is a
very impressive language, I am not happy about its libraries. Some of
them are mature, but for
On 07/12/2011 11:29, Erik Sundvall wrote:
Good old which ADL? Please go back in the thread and note the
difference between dADL and cADL in the reasoning, dADL is a
reinvention of the wheel (object tree serialization)
Erik,
out of academic interest: was either YAML or JSON around in 2000,
A bunch of responses, most of which should actually go to a wiki page for
Bosphorus
I've used binary serialization for AOM because although Eiffel is a very
impressive language, I am not happy about its libraries. Some of them are
mature, but for XML, I could not find anything that'd be
+1
Cheers,
Stef
Op 6 dec. 2011, om 12:44 heeft Seref Arikan het volgende geschreven:
Please do not get me wrong, all the discussion we are having here is useful,
it is just that in my humble opinion, some discussions are more useful than
others if this standard into which I am heavily
...@openehr.org] On Behalf Of Stef Verlinden
Sent: Wednesday, 7 December 2011 1:01 a.m.
To: For openEHR technical discussions
Subject: Re: Could YAML replace dADL as human readable AOM serialization format?
+1
Cheers,
Stef
Op 6 dec. 2011, om 12:44 heeft Seref Arikan het volgende geschreven:
Please do
I think previously I had indicated I had no problem with the stringified
interval approach in XML, but I am reverting my thinking on this and feel
that it would be counter intuitive for those who what to use the XML schemas
for code generation purposes. I think in this case the computable
YAML replace dADL as human readable AOM serialization
format?
I think previously I had indicated I had no problem with the stringified
interval approach in XML, but I am reverting my thinking on this and feel
that it would be counter intuitive for those who what to use the XML schemas
for code
: RE: Could YAML replace dADL as human readable AOM serialization
format?
I think previously I had indicated I had no problem with the stringified
interval approach in XML, but I am reverting my thinking on this and feel
that it would be counter intuitive for those who what to use the XML
On 05/12/2011 00:23, Sam Heard wrote:
Hi All
I am going to say it once more:
If there is an expression on occurrences of '0..*' anywhere in ADL
then it is an error, for that is not a constraint -- and can only be
wrong (ie the RM may have a narrower constraint). We just need a max
int
Hi!
On Mon, Dec 5, 2011 at 00:10, Heath Frankel
heath.frankel at oceaninformatics.com wrote:
I think previously I had indicated I had no problem with the stringified
interval approach in XML, but I am reverting my thinking on this and feel
that it would be counter intuitive for those who
Hi Erik,
I'll repeat a point I've tried to make before, since it is relevant in the
context of binary serialization.
I've used protocol buffers serialization of AOM in Bosphorus (I'll put the
source code under Opereffa's svn soon, it appears I don't even have time to
clean it up)
These are very
Hi Seref!
On Mon, Dec 5, 2011 at 13:32, Seref Arikan
serefarikan at kurumsalteknoloji.com wrote:
I'll repeat a point I've tried to make before, since it is relevant in the
context of binary serialization.
I've used protocol buffers serialization of AOM in Bosphorus
Why do you use binary
On 01/12/2011 21:37, Erik Sundvall wrote:
Hi!
Let the battle begin :-) see:
http://www.imt.liu.se/~erisu/2011/AOM-beauty-contest.html
http://www.imt.liu.se/%7Eerisu/2011/AOM-beauty-contest.html
nice page - that's quite fun to see them all pasted up there.
My question is: what's the/your
: Could YAML replace dADL as human readable AOM serialization
format?
Hi!
Let the battle begin :-) see:
http://www.imt.liu.se/~erisu/2011/AOM-beauty-contest.html
On Tue, Nov 22, 2011 at 13:24, Thomas Beale
thomas.beale at oceaninformatics.com wrote:
actually, ADL 2.0 as reported
On Thu, Dec 1, 2011 at 22:37, Erik Sundvall erik.sundvall at liu.se wrote:
Hi!
Let the battle begin :-) see:
http://www.imt.liu.se/~erisu/2011/AOM-beauty-contest.html
Hi Erik,
is the Javascript Object Dump missing regexps for 'address' and
'electronic_communications'? Or is that irrelevant?
On 02/12/2011 01:35, Heath Frankel wrote:
Thanks Erik,
Interesting to see the line up. Can't believe that XML wasn't the
longest file in the list, that kills one of the arguments for JSON vs XML.
For someone that is not aware of YAML, are the white space
significant. If so, this kinds
Hi!
Let the battle begin :-) see:
http://www.imt.liu.se/~erisu/2011/AOM-beauty-contest.html
On Tue, Nov 22, 2011 at 13:24, Thomas Beale
thomas.beale at oceaninformatics.com wrote:
actually, ADL 2.0 as reported in this document is now obsolete. The ADL
1.5 compiler already does this, and will
Hi!
A little suggestion/thought (that might be of value also for CIMI-folks and
others looking at archetyping using ADL and AOM and wondering if a
specific language is needed).
*Limitations:*
For efficient handling of RM (Reference Model) instances (patient data)
flying back and forth between
On 22/11/2011 11:51, Erik Sundvall wrote:
Hi!
A little suggestion/thought (that might be of value also for
CIMI-folks and others looking at archetyping using ADL and AOM and
wondering if a specific language is needed).
*Limitations:*
For efficient handling of RM (Reference Model)
28 matches
Mail list logo
