- From: Timothy Lebo <lebot@rpi.edu>
- Date: Thu, 31 May 2012 22:01:38 -0400
- To: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
- Cc: public-prov-wg@w3.org
Luc, Thanks for taking the time to work this navigational nit. The style is much nicer now. I'm glad to see that the constraint title is selectable and is linked to itself. There's one more tiny nit that I wouldn't worry about, but I'll state it for completeness. Following your example below… On May 31, 2012, at 6:46 PM, Luc Moreau wrote: > Hi Tim, > > The latest Editor's draft has now fixed that problem. > > Go to: > http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-constraints.html#derivation-use > > The text that follows inference 5 has a cross-reference to the text that precedes the rule > Constraint 17 (generation-uniqueness). > > It links to: > http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-constraints.html#generation-uniqueness_text > preceding Constraint 17. The links from inference 5 to Constraint 17 does go to the text [1], but selecting Constraint 17's link [2] hides the text about Constraint 17: "We assume that an entity has exactly one generation and invalidation event (either or both may, however, be left implicit). So, PROV-DM allows for two distinct generations g1 and g2 referencing the same entity provided they occur simultaneously. This implies that the two generation events are actually the same and caused by the same activity, though provenance may contain several statements for the same world activity." [1] http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-constraints.html#generation-uniqueness_text [2] http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-constraints.html#generation-uniqueness I would suggest that Constraint 17's link to itself be [1] and not [2], so that the text about it is in view. Though, another interpretation is that that text above Constraint 17 is NOT about Constraint 17, in which case it is not clear which narrative talks about which constraint (the text above it or below it?) "5.2.1 Activity constraints" handled it with divs to pair up the narrative with the boxes, and I'm fond of that style. Regards, Tim > > I trust this addresses your concern. > I am closing this issue, pending your review. > > Cheers, > Luc > > > On 21/05/12 18:51, Timothy Lebo wrote: >> One part to consider is where the anchor "lands" - it does not show the narrative that appears above the constraint. >> >> Ideally, the anchor would be moved to above the narrative, so one could read it without scrolling up. >> >> But I did notice that divs were added to delineate the narrative+constraint. That was the main aspect of this issue (which is addressed). >> >> -TIm >> >> On May 21, 2012, at 11:02 AM, James Cheney wrote: >> >> >>> Hi, >>> >>> I believe this issue has been addressed. Tim, do you agree with closing it? >>> >>> --James >>> >>> On Apr 11, 2012, at 3:44 PM, Provenance Working Group Issue Tracker wrote: >>> >>> >>>> PROV-ISSUE-345 (delineate-constraints): style hinders readability: constraints not separated clearly enough [prov-dm-constraints] >>>> >>>> http://www.w3.org/2011/prov/track/issues/345 >>>> >>>> Raised by: Timothy Lebo >>>> On product: prov-dm-constraints >>>> >>>> http://dvcs.w3.org/hg/prov/raw-file/default/model/releases/ED-prov-dm-20120402/prov-dm-constraints.html#usage-precedes-invalidation >>>> >>>> does not clearly delineate where the discussion for one constraint starts and where the next ends. This makes it unreasonably difficult to read. >>>> >>>> BLOCKER for release as public draft. >>>> >>>> This can be fixed with styling to visually separate the pile of constraints. >>>> >>>> >>>> >>>> >>>> >>> >>> -- >>> The University of Edinburgh is a charitable body, registered in >>> Scotland, with registration number SC005336. >>> >>> >>> >>> >> >> > >
Received on Friday, 1 June 2012 02:02:09 UTC