OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cgmo-webcgm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re[4]: [cgmo-webcgm] Question about 'grnode'


DW> how does that work in XML, e.g.

DW> <p id="foo">some text </p>
DW> <p>some more text</p>
DW> <p id="bar">even more text</p>

DW> If you now traverse from foo to the unnamed p and then to bar
DW> this is comparable to going from a grobject to a grnode to a grobject,
DW> n'est-ce-pas?
From my perspective, not quite. In WebCGM, all APS must have an 'id',
which would mean that your example becomes:
<p id="foo">some text </p>
<p id="limitedAccess">some more text</p>
<p id="bar">even more text</p>

So 'limitedAccess' is not accessible via getAppStructureById
(even though it has an id), but is accessible via Node.nextSibling!
I'll try to think of a good way to explain this in the spec.

Something else I have been wondering about is if we need another
WebCGMNode const value for nodeType? Or will APP_STRUCTURE_NODE
suffice for both 'grnode' and 'grobject'?

-- 
 Benoit   mailto:benoit@itedo.com


DW> -----Original Message-----
DW> From: Benoit Bezaire [mailto:benoit@itedo.com]
DW> Sent: Wednesday, January 26, 2005 10:01 PM
DW> To: CGM Open WebCGM TC
DW> Subject: Re[2]: [cgmo-webcgm] Question about 'grnode'


DW> Good point, and I agree. I just don't know how to properly word the
DW> fact that getAppStructureByXX doesn't work, but Node.nextSibling does.
DW> I'll think about it.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]