Response to WebCGM 2.1 Last Call comment: more getObjectExtent()

Dear Benoit,

The WebCGM Working Group has reviewed the comment you sent [1] about the 
WebCGM 2.1 Last Call Working Draft [2] published on 18 November 
2008.  Thank you for having taken the time to review the document and send 
us comments.

The Working Group's response resolution to your comment is included below.

Please review it carefully and acknowledge this WebCGM WG response by 
replying to this mail and copying the WebCGM public mailing list 
<public-webcgm@w3.org>. Let us know if you agree with it or not before 11 
Jan 2009.  If we receive no reply from you by January 11, then we will 
default your reply to "WebCGM WG response accepted."

In case of disagreement, you are requested to provide a specific solution 
for or a path to a consensus with the Working Group.

If such a consensus cannot be achieved, you will be given the opportunity 
to raise a formal objection which will then be reviewed by the Director 
during the transition of this document to the next stage in the W3C 
Recommendation Track.

Best regards,

On behalf of the WebCGM Working Group, a
Lofton Henderson, WebCGM WG Chair.

[1] http://lists.w3.org/Archives/Public/public-webcgm-wg/2008Nov/0028.html
[2] http://www.w3.org/TR/2008/WD-webcgm21-20080917/
_____________________________________________________________
* Comment Sent: Tue, 18 Nov 2008
* Archived:
http://lists.w3.org/Archives/Public/public-webcgm-wg/2008Nov/0028.html

The WebCGM WG has the following responses to your comment:
----------------------------------------------------------

SUMMARY of your comment:

>The wording says "[...] The bounding box calculation is based on the 
>abstract locus of the primitives within the APS." What does 'abstract 
>locus' mean?I'd like to know if getObjectExtent() returns a tight bounding 
>box on a given APS. i.e., given a polybezier, are control points part of 
>the bounding box calculations or not?

RESPONSE to your comment:

>1.) In the text description of getObjectExtent (section 5.7.6), change 
>"abstract locus" to "locus", and link "locus" to a new Glossary definition 
>in Appendix C.
>
>2.) Add this definition to the Glossary (Appendix C):
>locus --
>A general definition from the Oxford dictionary defines 'locus' 
>as:  "Curve formed by all points satisfying particular equation of 
>relation between coordinates, or by point, line, or surface, moving 
>according to mathematically defined conditions."  In the WebCGM 
>specification, locus refers to the set of points that comprise the path or 
>shape of a Graphical Primitive element, or in the appropriate context, the 
>combined shapes or paths collectively of all of the Graphical Primitive 
>elements in an Application Structure (APS).  I.e., the locus of an APS 
>comprises the combined loci of all of the graphical primitives in the 
>APS.  Locus does not include defining data that are not part of the shape 
>or path of the graphical primitive, such as control points of Bezier 
>primitives, or the center point of a Circular Arc Center primitive."
>
>(Ed note. The WG closes the present issue with this resolution, 
>anticipating that further detailed questions of clarification will arise 
>as implementations progress.)

--------------------------- end -------------------------------

Received on Thursday, 18 December 2008 18:20:44 UTC