<trackbot> Created ACTION-521
- Work with Jie Bao (of OWL-WG) to put together draft on
rif:text/owl:internationalizedText, due 27 June 2008 [on Axel
Polleres - due 2008-06-17].

<AxelPolleres> Can someone
point me to a mail or draft page where
owl:internationalizedText is referenced?

<AxelPolleres> ... or to an
email.

<AxelPolleres> Editor's note:
Although <tt>rif:iri</tt> is not a datatype, I left
conversions from and to <tt>rif:iri</tt>s in the
list of cast functions, to cover use cases in the context of
RDF where you want to extract a string from an IRI denoting an
RDF resource and vice versa.

<trackbot> ACTION-501 Put
text about "metadata should survive roundtripping out of RIF
and back again" in Conformance section of BLD closed

Harold: Regarding the actions to edit BLD (Basic Logic Dialect) and FLD (Framework for Logic Dialects): MichaelK and I both made multiple
updates, but we weren't coordinating, so we used different
terminology

ACTION-499 pending discussion

ACTION-497 continued

ACTION-496 closed

<trackbot> ACTION-496 Update
all examples for Presentation Syntax and XML syntax for curies
and entities. Also add Prefix to presentation syntax.
closed

<AdrianP> Yes, action-496 is
done

<AdrianP> sorry I ment action
495 is done

ACTION-495 closed

<trackbot> ACTION-495 Respond
to Dan2 (about well-formedness) closed

Christian: Where in the document is
XML syntax for curies and entities defined?

Harold: (points to an example
6)

ChrisW: Presentation syntax should
not have curies in them

Harold: I used prefixes

<Hassan> Are the contents of
the IRI declarations for PS complete and fine?

JosB: Maybe we should mention that
entities are optional, and also in example 6 we should expand
one of the entities

<sandro> +1 jos, have one of
the prefixes not turn into an entity, to show the
correspondance is optional

ChrisW: Re: Action-482 we discussed
that DTB (Data Types and Built-ins) would contain a comprehensive list of all data types, and
when defining a dialect the dialect designer would choose from the catalog of data types defined in DTB

ACTION-454 complete

ACTION-475 continued

ACTION-152 continued

ChrisW: In addition, a number of resolutions from
F2F10 didn't have actions associated with them, so I want to
confirm that they're done

ChrisW: AxelP, there was a resolution about xsd subtypes

AxelP: Yes, I made the update in
DTB

Harold: BLD doesn't require any
update for this item

ChrisW: My understanding that DTB
would be a comprehensive catalog of data types and builtins, and so BLD would
have to add a paragraph saying which of those from DTB that BLD
uses

ChrisW: Another resolution was that we
would add pred:numeric-less-or-equal, pred:numeric-greater-or-equal, pred:numeric-not-equal to DTB

AxelP: This is done - these operators were added for each data type

ChrisW: Does the BLD just need to
list data types, and it is implied that it supports all builtins
for each data type that it supports?

Sandro: Yes, I think so

ChrisW: So adding those predicates
wouldn't impact the BLD text

ChrisW: Another resolution was to remove symbol space ids in
RIF

JosB: This meant symbol space ids
must now be IRIs

AxelP: This is done

<ChrisW> modify Presentation
Syntax to include "Const ::= STRING" (allowing "chat" as short
for "chat"^^xs:string).

AxelP: Harold, you can just copy
updated const grammar from DTB

<josb> very good!

ChrisW: There was a resolution about
syntax for rif:local

AxelP: Yes, these updates are
made

ChrisW: We had a resolution to add
xsd:double

AxelP: Done

ChrisW: There was a resolution on XML
syntax for ordered=yes

Harold: Done

ChrisW: Resolution to point people to
Dublin core for metadata properties

Harold: Done

ChrisW: Any other discussion on
actions?

Public Comments

ChrisW: This is about the response to
PFPS's response
... this is our only outstanding public comment
... Jos has made a pass at it on the wiki, and now I will finish it
... Jos, do you want to discuss your response to Peter here?

JosB: I don't think we need to; you can review the web page

JosB: Also, on a different public comment - Dan Connolly responded to my
response, and said that it addressed his concerns (although he found it counter-intuitive)

Sandro: That section was updated
since last week, but it is more verbose than we need

ChrisW: It needs to be reworded using
standard language of requirements

<sandro> The RIF dialect
targetting a group of similar rule languages must support, at a
minimum, interchange of rules using all the features which are
common to all the major rule languages in that group.

<AdrianP> ok sound good and
compact

<sandro> (as full replacement
for 5.1.6)

ChrisW: I'd change "must" to
"should"

Sandro: All the other
requirements use must, except for the implementability
requirement

ChrisW: But this (5.1.6) is a fuzzy
requirement

<sandro> "must"

<ChrisW> Straw poll: prefer
must/should in 5.1.6

<sandro> strawpoll: must vs
should on that 5.1.6 text

<csma> 0

<Hassan> 0

<AdrianP> +1 for must

<josb> don't care

<AxelPolleres> should

<csma> +/- must/should

<Harold> +0.8 for must

<mdean> 0

<csma> or could be
should/must

<AxelPolleres> +1 for
mould

<Hassan> +1 for mould

<AdrianP> the general
requirements should describe fundamental properties

<ChrisW> not mould, mold

<AxelPolleres> These people
from the US have this tendency to drop "u"s from English
words...

ChrisW: Straw poll not conclusive. Wording of 5.1.6 is left up to the editor's discretion

<GaryHallmark> Christian, I
see XML data as a tree of frames with constraints on its
structure which could be achieved in theory by embedding XML
(Schema) axioms into RIF

ChrisW: Adrian, anything else to
discuss on UCR?

Acknowledgements

ChrisW: All the documents need an
acknowlegement section

ChrisW: It is customary to list by
name all members of working group, but this group is
large with many inactive members. So we can use other criteria to come up with the list of WG members to acknowledge

<josb> +1

<mdean> +1

<sandro> "The regular
attendees at Working Group meetings at the time of publication
were:"

<AxelPolleres> THere are
means to kick out non-active members. I think we should put the
non-active people in "bad standing"

<AxelPolleres> i.e. contact
their AC Reps.

Harold:
Some people made contributions early on and then didn't attend
calls

Sandro:
We can have several criteria for selecting contributers and several different types of acknowledgements

<sandro> Sandro: the
"acknowledgements" section should have this Regular Attendees
bit, PLUS thanks for all the reviews, PLUS any other thanks the
editors feel appropriate to give.