<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 15/12/2010 10:16, Mark Proctor wrote:
<blockquote cite="mid:4D08956A.8080206@codehaus.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 15/12/2010 09:38, Wolfgang Laun wrote:
<blockquote
cite="mid:AANLkTinZM9emUrOAre40w6N2E4ukOrGPehew7qemW8zQ@mail.gmail.com"
type="cite">Constraining the scope of applicable when-fragment
might be added on top of the current DSL syntax, providing a
compatible migration path. Notice that constraining the scope is
similar to the rule attribute "auto-focus", but unqualified
entries may have to remain active throughout.<br>
<br>
Expansion will have to be able to handle insertions not only for
the last preceding pattern but also to other parenthesized
condition phrases, e.g. eval, forall, etc.<br>
</blockquote>
yaml looks pretty nice these days, as the underlying document
storage format.<br>
</blockquote>
There are two approaches to schemas in yaml that I know of:<br>
<a class="moz-txt-link-freetext" href="http://rx.codesimply.com/">http://rx.codesimply.com/</a><br>
<a class="moz-txt-link-freetext" href="http://www.kuwata-lab.com/kwalify/">http://www.kuwata-lab.com/kwalify/</a><br>
<br>
Mark<br>
<blockquote cite="mid:4D08956A.8080206@codehaus.org" type="cite"> <br>
Mark<br>
<blockquote
cite="mid:AANLkTinZM9emUrOAre40w6N2E4ukOrGPehew7qemW8zQ@mail.gmail.com"
type="cite"><br>
-W<br>
<br>
<br>
<br>
<div class="gmail_quote"> On 15 December 2010 10:18, Mark
Proctor <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div text="#000000" bgcolor="#ffffff"> Thought I'd mention
where I'd like to see DSLs go in the future, if anyone is
interested. DSLs are template fragments that can be used
in conjuction with each other. I'll refer to them as
template fragments from now on.<br>
-Selecting one template fragment constraints which peer
fragments may be used after it.<br>
-Template fragments may have nested template fragments.
The available nested fragments are themselves constrained
and depending on which child fragment is chosen cosntrains
any allowed peer child fragments.<br>
-As well as constraining which peer or child fragments can
be used cardinality can also be constrained.<br>
-The peering and nesting itself can be recursively
applied,<br>
<br>
So what we are talking about here is something that is
almost xsd schema like, for producing constrained
documents.<br>
<br>
Mark
<div class="im"><br>
On 15/12/2010 07:41, Wolfgang Laun wrote: </div>
<blockquote type="cite">
<div>
<div class="h5">On 13 December 2010 19:58, Edson
Tirelli <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:ed.tirelli@gmail.com"
target="_blank">ed.tirelli@gmail.com</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204,
204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;"> Hi Wolfgang,<br>
<br>
Mark said you would like us to take a look at
some of your commits?<br>
Can you let me know which ones?<br>
<br>
</blockquote>
<div><br>
Hi Edson,<br>
<br>
I have reached a state where I think changes
might be committed - see the attached README.
I'll just go through the code and add some
comments and make sure no "noise" remains. Then
I'll send you the zipped tarball of all changes.
If there are no objections, I'll also commit,
but I need to do this before the git change
incapacitates me. (I just don't have the time
right now for making this conversion, and I
won't have it until E12/2010. Worst time of the
year for doing a change like that!)<br>
<br>
@developers: Anybody interested in this set of
changes can ask me for the sources.<br>
<br>
Best<br>
Wolfgang <br>
<br>
<br>
</div>
</div>
<br>
</div>
</div>
<pre><fieldset></fieldset>
_______________________________________________
rules-dev mailing list
<div class="im"><a moz-do-not-send="true" href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</div></pre>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
<br>
</blockquote>
</div>
<br>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>