Re: DTB frozen and last changes

I believe the two editor's notes at the end of section 1 are obsolete.
As I pointed out earlier today, there are problems with the definitions
of literalNotIdentical and isLiteralOfType [1]. It would be good to have
links to this e-mail in relevant parts of the document so that we don't
forget it.
Concerning the last editor's note in section 3.1: it was decided that
the value spaces of decimal and double are disjoint. ( I believe this
was a resolution in the last face-to-face )
I'm hoping that the issue pointed out in the first editor's note in
section 3.2 can be addressed quickly, since it has been a long standing
issue that really needs to be addressed before we can publish the next
revision of this document.


Best, Jos

[1] http://lists.w3.org/Archives/Public/public-rif-wg/2009Apr/0036.html

Axel Polleres wrote:
> The latest changes in DTB are mainly in terms of rdf:text:
> 
> 1) Casting from rdf:text to xs:string is now included, a respective
> editor's note in Section 3.2.9 on Casting to xs:string has been added.
> 
> 
> The following old note is no longer needed, given the latest changes in
> rdf:text:
> 
> "Note: Since RIF implementations MAY choose to interpret
> <tt>xs:string</tt> and its subtypes as subtypes of <tt>rdf:text</tt>
> following Section 3.1 of <nowiki>[</nowiki>[[#ref-rdf-text|RDF-TEXT]]],
> in such implementations this cast function also serves for conversions
> to <tt>rdf:text</tt>."
> 
> 2) I needed to temporarily change the reference to rRDF-TEXT to the
> wiki-doc, as the TR version is totally outdated.
> 
> 3) I removed the Editor's notes on the example on xs:string vs rdf:text.
> after isLiteralNotOfType (Section 3.1.2.2)
> 
> Note: I am inquiring this again in the rdf:text-mailinglist, but my
> understanding is that he value space of rdf:text now is a superset of
> the value space of xs:string, such that automatically each value in
> xs:string is also in rdf:text.
> 
> 
> 
> Other, non-rdf-text related changes:
> 
> 4) literal-not-equal was changed to literalNotIdentical
> 
> 5) Ed note
> 
> "Shouldn't we have a uniform naming convention here
> <tt>pred:literal-equal</tt> vs. <tt>pred:isLiteralOfType</tt>, i.e.
> dashes vs. CamelCase is not used uniformly."
> 
> has been removed, since obsoleted.
> 
> 6) The editor's note for isLiteralOfType now explicitly refers to
> ISSUE-93.
> 
> {{EdNote|text=Note that it is assumed the second argument of
> isLiteralOfType to be a rif:iri at the moment, cf.
> [http://www.w3.org/2005/rules/wg/track/issues/93 ISSUE-93].}}
> 
> 

-- 
+43 1 58801 18470        debruijn@inf.unibz.it

Jos de Bruijn,        http://www.debruijn.net/
----------------------------------------------
Many would be cowards if they had courage
enough.
  - Thomas Fuller

Received on Friday, 10 April 2009 14:39:53 UTC