Re: Typo in stroke-type style property

According to the minutes of the f2f meeting in Needham (
http://www.oasis-open.org/committees/download.php/28523/f2f_meeting_minutes_may_2008.pdf),
here's what we said about style properties issues:
Style property issues

   - stroke-type

Resolution: Allow line types 1-15, plus negatives.  A reference to an
undefined negative has no effect. Use numbers for all the indices, instead
of names.

   - fill-style

Resolution: Use integers. Note: The name should be interior-style.

   - hatch-type

Resolution: Allow negative values.  Note: The name should be hatch-index

   - pattern-type

Resolution: The user would need some knowledge of pattern table to use
it.  Note:
The name should be pattern-index

   - fill-offset: Resolution: The name should be fill-referencepoint


Hope this clarifies....

Dave
On Wed, Jan 7, 2009 at 7:59 AM, Bezaire, Benoit <bbezaire@ptc.com> wrote:

>  I'm reading the on the new style properties, and I see some
> inconsistencies.
>
> It's unclear with the current spec which style properties are set by a name
> or integer value. At the moment it seems like stroke-type can be set using
> "solid" or "1". But other style properties like interior-style and
> hatch-index only seem to be settable using it's integer value. I think some
> clarification and consistency is needed.
>
> While it's still unclear if PTC will implement getStyleProperty(), I wonder
> if the implementation has to return the exact same string that was used to
> set the attribute.
>
> Example for stroke-type: setStyleProperty("stroke-type", "solid"),
> getStyleProperty("stroke-type") returns 1.
> Example for stroke-weight: setStyleProperty("stroke-weight", "200%"),
> getStyleProperty("stroke-weight") returns 0.5 (assuming original was 0.25).
>
> Thoughts?
> Benoit.
>
>  ------------------------------
> *From:* Bezaire, Benoit
> *Sent:* Wednesday, January 07, 2009 10:26 AM
> *To:* WebCGM WG
> *Subject:* Typo in stroke-type style property
>
>  Current wording says: "[...] Valid values are: integers 1-6 (which
> correspond to solid, dash, dot, dash-dot, dash-dot-dot)", the "1-6" should
> be replaced by "1-5".
>
> Benoit.
>
>