[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cgmo-webcgm] ISSUE: change VDC to NVDC in OBJECT?
Hi Lofton, Either one (alt 1 or alt 2) is fine with me. I do agree that redefining an existing attribute would cause some problems for existing content (we don't want that). -- Benoit mailto:benoit@itedo.com Monday, June 13, 2005, 12:51:00 PM, Lofton wrote: LH> From Dieter's comments: LH> http://lists.oasis-open.org/archives/cgmo-webcgm/200506/msg00021.html LH> ISSUE: should 2.0 change VDC to NVDC in the VIEWPORT'param' LH> sub-element of the 'object' element? LH> VIEWPORT topx topy botx boty LH> This should no longer use VDC coordinates but NVDCinstead. LH> DISCUSSION. We have defined NVDC to be the coordinate system LH> of DOMtransactions with the metafile. WebCGM 1.0 defined VDC to LH> be thecoordinates to used for VIEWPORT 'param' sub-elements of the LH> 'object'element, in HTML content. Changing the specification for LH> 2.0 wouldmean that any 1.0 HTML documents would break with a 2.0 LH> viewer. LH> Alternative 1. Leave 1.0 specification as is (VDC) for 2.0. LH> Alternative 2. Define a new 'param', VIEWPORTN, with LH> NVDCcoordinates and deprecate the VIEWPORT (VDC) 'param'. LH> (Note: I'm not proposing "change VDC to NVDC forVIEWPORT", LH> because I think it's a bad policy to make changes thatbreak LH> existing content.) LH> RECOMMENDATION: Alt.1 -- leave it as is. LH> Regards, LH> -Lofton.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]