Hi all,
Here's a snapshot of the latest draft. I would appreciate it if
we could talk about it during Wednesday's conference call.
What's new in this draft:
- new wording in section 1.1.3 Coordinate values.
- added a new 'src' attribute on the GetWebCGMDocument, we need to
standardize this!
- modified the applyCompanionFile method, I removed the 'refresh'
parameter and added a reloadPicture method on the Picture interface.
- improved the wording of getAppStructureById and
getAppStructuresByName (clearer now).
- new wording for highlight() method.
- fixed many typpos :-) in the 'style attribute' table. Note,
character-height and stroke-weight are in relative scale only. I
don't think the use case is there to justify anything else.
- added wording in the Event interface regarding the event
processing order.
- removed relatedTarget and added preventDefault() on the Event
interface.
- added appendix placeholders.
- getElementsByAttrNameValueNS is removed from this draft (can be
inserted back in if desired).
- getAppStructuresByType was removed (why retrieve by type when 95%+
of content are grobject)?
- the Text interface is not whitespace aware since WebCGM 1.0 is not
either.
New questions (sorry!):
- is it valid to have the 'src' property on the GetWebCGMDocument
interface?
- I'm still having a hard time with the 'attributes' attribute on
the Node interface. Currently, a script writer would have a real
hard time using this!
- do we need a removeEventListener method()?
- highlighting a layer, what happens?
- issue, does the interactivity attribute conflict with event
listeners.
- do we need a removeLinkuris and removeNames?
- In my opinion, the spec doesn't provide clear enough explanation
regarding coordinate values... what should clientX/Y say?
- What happens if a user clicks on the background of a CGM Picture
instead of on an APS? Anything?
What's still missing (I know I'm forgetting some):
- architectural illustration.
- rules for applying companion file (we don't have any wording for
that).
- examples & pictures to explain coordinate values of DOM.
- formula for intensity.
- editorial work.
- integrating DTD with spec (not really sure how the entire spec
should be organized).
--
Benoit mailto:
