- From: Curran Kelleher <curran.kelleher@gmail.com>
- Date: Fri, 17 Feb 2012 19:12:09 -0500
- To: Dave Reynolds <dave.e.reynolds@gmail.com>
- Cc: public-gld-comments@w3.org
- Message-ID: <CAPMxy1XkaQiQieQ_4P3ztqfD6h7+a-1mdquMPEGUeMDcT7MaTQ@mail.gmail.com>
Hi Dave, Great! Thank you very much for your response. Best, Curran On Fri, Feb 17, 2012 at 9:52 AM, Dave Reynolds <dave.e.reynolds@gmail.com>wrote: > Hi Curran, > > Many thanks for your comments. The editorial suggestions will be addressed. > > I wanted to respond to a couple of your non-editorial points: > > * However, it is also permissible to attach attributes at other levels >> >> of the structure such as the overall data set <- I'm wondering, what >> is the full set of possible levels at which attributes can be >> attached? does it include slices? I suggest it be more concrete and >> say: "However, it is also permissible to attach attributes at the >> slice or data set level." >> > > It is possible to attach at the slice level, indeed that's a key usage, so > I agree the wording needs to be cleaned up. Reviewing and at least > clarifying the abbreviation mechanism is something we intended to address > before reaching Last Call. > > * The data cube vocabulary permits either representation approach to >> >> be used though they cannot be mixed within the same data set. <- So >> this means that any tooling developed for combining data sets >> together into larger data sets must handle both forms, and transform >> its output into one form or the other? >> > > Yes, as things stand that's correct. > > * Property: qb:slice ( qb:DataSet -> qb:Observation ) -> based on this >> >> triple which appears in the examples "eg:dataset-le2 qb:slice >> eg:slice2", shouldn't this be Property: qb:slice ( qb:DataSet -> >> qb:Slice ) ? >> > > Correct. That's been fixed in the actual vocabulary but needs fixing in > the document. > > Cheers, > Dave >
Received on Saturday, 18 February 2012 00:13:27 UTC