W3C home > Mailing lists > Public > public-owl-wg@w3.org > July 2008

Re: ISSUE-53 Proposal to resolve

From: Bijan Parsia <bparsia@cs.man.ac.uk>
Date: Wed, 9 Jul 2008 00:13:31 +0100
Message-Id: <4658617B-2A49-479F-B569-BA4A36E30BAE@cs.man.ac.uk>
Cc: Evan Wallace <ewallace@cme.nist.gov>, Ian Horrocks <ian.horrocks@comlab.ox.ac.uk>, "OWL 1.1" <public-owl-wg@w3.org>
To: Alan Ruttenberg <alanruttenberg@gmail.com>

On Jul 8, 2008, at 5:30 PM, Alan Ruttenberg wrote:

> I'm content to close this issue, as long as doing so does not imply  
> that the technical issues were resolved.

What technical issues?

Does it matter? I don't refer to this issue *at all* when working on  
n-ary. It has no useful content.

But fine:

"""" N-ary datatypes seem both fragile and wrongly expressive (as  
compared, e.g., to dl-safe rules with built-ins)""""

They are not fragile (or no worse than transitive roles). They are  
rightly expressive (see use cases).

(Some people still doubt the latter, but does this issue help  
organize that? I'm sure Boris will raise it if it is necessary.)

"""there are no built-in n-ary datatypes, nor a language for defining  
them. E.g., see:"""

And that was just "it's a bluff" trash talking. We have a proposal  
for built-in types and a language for defining them.

There are issues with all this, but those are more narrowly technical  
and are being handled anyway.

> I'm confident we can find appropriate wording. It may the case that  
> closing it as something other than "resolved" is appropriate.

I propose we close this as withdrawn with a reference to Jeremy's email.

Close issue-53 as well along Ian's line.

(Personally, I don't like stale issue and stale action items. At some  
point, they can get in the way.)

Cheers,
Bijan.
Received on Tuesday, 8 July 2008 23:14:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:42:05 UTC