January 2 2001 Attendees: Peter Ian Lyn Frank Mike Jeff Kelly Deb Pat Jim ~~~~~~~~~~~~~~~~~~~~~~~~ Happy New Year DAML.org non-resolvable Minutes from the 19th - approved Big Agenda Item: DAML+OIL release Frank's open issues: Ian has already sent around the new language definition a few weeks ago. He wrote a new version of the walkthrough and also updated the example file to match it. He wrote a description of the language elements described in english. Only feedback from Ian and Peter. Two versions of the reference file, short and long. Suggests that we remove the short version and use only the long as a single reference document. How to deal with lists, hiding content (avoiding exposed content), domain and name restrictions as inherited from RDF schema. First ... how to deal with lists. Dan invented a new parse type "daml:collection" which is a shorthand for list notation. This will parse but it will just get thrown out. Do we go with this or make life easier for tool developers? Ordered but ordering not relevant in the collection notation. Will order ever matter? ... long discussion ... Requests to do this outside of the telecon!! Could this just be a naming issue? We need to make sure we don't break rdf parsers even if they don't understand it. Lets break on this and come back with some info on this and pros and cons for next week!! Dan and Stephan will contribute before next weeks telecon. Next ... avoiding exposed content. We are ok except with cardinality. New syntax to fix this ... looking for an ok from the group. Mike says that most people are probably more interested in avoiding exposed content in instances. Two options, one is more useful. Complaint about numbers being strings. We have syntax for numerals, but not integers. (numeral is "1111"). Third ... Domain and range restrictions. In or Out? If we want max compatability with RDF schema then we need to leave then in, but RDF Schema is already broken (but we assume / expect it will be fixed). Put in the walkthrough to be careful with their use (maybe deprecated) but do not completely cut them out. Any thing else holding up the release? Frank: KIF core -- SUO KIF Not well defined so far. Dont think we should do too much with this because it might be a working group. ACTION ITEMS: Frank: Replace the reference long and short with just ref.html Dan and Stephan: Prepare list proposals before next week Frank: exposed content - footnote addition Peter and Deborah: updating for DAML+OIL for domain and range Frank: Add comment to be careful with domain and range Frank: Add note about no concrete types in this release Ian: When using same property as can be used in both directions