[seek-kr-sms] my emails on SWRL: lost images
Bertram Ludaescher
ludaesch at ucdavis.edu
Sat Apr 23 21:41:56 PDT 2005
Hi Serguei:
Now we're talking! =B-)
Shawn and I have picked up again on our Sparrow work (actually mostly
Shawn ;-) and we'll have human-readable and machine-readable
"everything" rather soon..
By "everything" I mean of course not really everything. But, e.g.,
things like
- DL concept expressions (hopefully soon with the constructs you put
on the wish-list) -- we call those sometimes "semantic types"
- DL axioms
- "structural types", i.e. XML DTD like expressions
- "association mappings" between structural and semantic types
and more.
I think we'll have many details of this language ready for prime time
by May 12th (the Berkeley Ptolemy/Kepler miniconf.) and even before
for the SEEK meeting.. are you going as well? You should meet with
Shawn then! (Unfortunately, I won't be able to make it, as much as I'd
like to..)
cheers
Bertram
Serguei Krivov writes:
>
>
> has_uncle(X1,X3) :- has_parent(X1,X2), has_brother(X2,X3).
>
>
>
> This is as clear as it gets. It's human readable, easy to parse, and I
>
> don't see how it can be improved (if it ain't broken don't fix it ;-).
>
>
>
> Hi Bertram,
>
> I apologize again about the mess around html format.
>
>
>
> I love prolog syntax. If this syntax could be extended to cleanly describe
> OWL-DL constructs, such as unions, complements, enumerations, and worst of
> all- property restrictions, then it would be the best for SWRL. Currently
> SWRL abstract syntax uses OWL abstract syntax for this purpose. ( It is
> called abstract because rdfs based syntax, which is the worst is assumed to
> be concrete)
>
>
>
> I love to use my LaTeX editor and paste images from pdf files to email, but
> I would much prefer not to do it. But how could I describe concisely in
> ascii the example of rule as follows ( I added it also in attachments):
>
> The question is actually how to describe property restrictions that could be
> nested and combined with Boolean operations in any manner.
>
>
>
>
>
> serguei
>
> <html>
>
> <head>
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
>
>
> <meta name=Generator content="Microsoft Word 10 (filtered)">
>
> <style>
> <!--
> /* Style Definitions */
> p.MsoNormal, li.MsoNormal, div.MsoNormal
> {margin:0in;
> margin-bottom:.0001pt;
> font-size:12.0pt;
> font-family:"Times New Roman";}
> a:link, span.MsoHyperlink
> {color:blue;
> text-decoration:underline;}
> a:visited, span.MsoHyperlinkFollowed
> {color:purple;
> text-decoration:underline;}
> p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
> {margin:0in;
> margin-bottom:.0001pt;
> font-size:10.0pt;
> font-family:"Courier New";}
> @page Section1
> {size:8.5in 11.0in;
> margin:1.0in 77.95pt 1.0in 77.95pt;}
> div.Section1
> {page:Section1;}
> -->
> </style>
>
> </head>
>
> <body lang=EN-US link=blue vlink=purple>
>
> <div class=Section1>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'> </span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'>has_uncle(X1,X3) :- has_parent(X1,X2), has_brother(X2,X3).</span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'> </span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'>This is as clear as it gets. It's human readable, easy to parse, and I</span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'>don't see how it can be improved (if it ain't broken don't fix it ;-).</span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'> </span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'>Hi Bertram,</span></font></p>
>
> <p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
> font-family:"Courier New"'>I apologize again about the mess around html format.</span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'> </span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'>I love prolog syntax. If this syntax could be extended to cleanly
> describe OWL-DL constructs, such as unions, complements, enumerations, and worst
> of all- property restrictions, then it would be the best for SWRL.
> Currently SWRL abstract syntax uses OWL abstract syntax for this
> purpose. ( It is called abstract because rdfs based syntax, which is the worst
> is assumed to be concrete)</span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'> </span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'> I love to use my LaTeX editor and paste images from pdf files to
> email, but I would much prefer not to do it. But how could I describe concisely
> in ascii the example of rule as follows ( I added it also in attachments): <img
> width=594 height=26 src="cid:image001.jpg at 01C54862.D9465FF0"></span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'>The question is actually how to describe property restrictions that
> could be nested and combined with Boolean operations in any manner.</span></font></p>
>
> <p class=MsoPlainText><font size=2 face="Courier New"><span style='font-size:
> 10.0pt'> </span></font></p>
>
> <p class=MsoPlainText><font size=2 color=black face="Courier New"><span
> style='font-size:10.0pt;color:black'> </span></font></p>
>
> <p class=MsoPlainText><font size=2 color=black face="Courier New"><span
> style='font-size:10.0pt;color:black'>serguei</span></font></p>
>
> </div>
>
> </body>
>
> </html>
More information about the Seek-kr-sms
mailing list