Review of XML-DATA

Overall this version is much better than the previous and, with two 
exceptions and some editorial tweaks, is OK to publish as a working draft.

The first exception is Section 4.1.1 on DM-Name. I don't think we should 
define a DM-Name for all rif constants via casting to xs-string. Only 
rif:iri constants should have a DM-Name, using the same algorithm you 
give here.  I see no advantage in being able to treat, e.g., a string as 
corresponding to an XML information item.

The other non-editorial issue is section 4.2. The notion of the "domain 
of all variables" is not something that is meaningful in BLD, only (I 
assume) in PRD.  I think you either need to make the embedding (when it 
is done) normative or provide a model-theoretic semantics for the 
RIF/XML combination in the same way that Jos did for SWC. However, I'd 
be happy for the document to be published in this state with just an 
Editor's Note explaining that that section will be reworked.

For the record, I don't agree with the Editor's note after example 4.6, 
equating a string to an integer is something I think we should avoid. 
However, that need not hold up publication as a working draft since it 
is already clearly marked as to be discussed.

** Editorial

** Section 1

[Same hard to parse sentence in para6 that I commented on last time.]
s/Followingly, this/This/
s/possible, the corresponding XML schemas/where available the
corresponding XML schemas,/

Delete para7 ("However, an instance of the data model can be ....") 
since the rest of the document has dropped the direct mapping from 
relational tables.

** Section 2

para 2,  s/limited to identify/limited to identifying/

** Section 3.1

s/befor ethe/before the/

The order of the definitions of sequence, atomics is awkward. Suggest 
putting the two definitions of Atomic first, then the definition of 
Sequence, then the para "A sequence cannot be a member of a sequence 
..." then the definition of Document order.

In the definition of sequence:
    s/or more items/or more information items/

** Section 3.2

In 6.  s/represented an/represented by an/

** Section 4

para 2,  s/a mean to/a means to/

** Section 4.5

In the first bullet:
    s/v is the sequence of/v is the list of/
[sequence is not a defined RIF data structure and later on you give an 
example which makes it clear you do mean to use RIF lists here]

In example 4.6 please leave spaces around the "->" character pairs, the 
sequence ">->" is hard to read :-)

s/dta source/data source/

In Example 4.7, the matching string text should, I think, have a space 
between "Widget" and ".". I'm not sure what whitespace normalization you 
are assuming here but at least in the input document there is white 
space between the <item> element and the ".".

In the Editor's note, s/minOccure/minOccur/

** Appendix A

In Editor's note:
   s/does not exits/does not exist/
   s/doe snot/does not/

Dave

Received on Saturday, 26 September 2009 12:12:16 UTC