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[2]: [cgmo-webcgm] Question about 'grnode'


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

-- 
 Benoit   mailto:benoit@itedo.com

 
Wednesday, January 26, 2005, 3:58:06 PM, Dieter wrote:

DW> I think that traversal methods like Node.next etc must work,
DW> otherwise it will be difficult to see a complete structure.
DW> getAppStructureByXX should not work, the ID should be opaque.

DW> regards,Dieter

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


DW> Hi guys,

DW> Lofton and I have been exchanging emails regarding various spec
DW> issues (mostly editing questions).

DW> One of the things that came up was the 'grnode' APS.  We agreed that
DW> companion file metadata cannot be attached to 'grnode' elements.  That
DW> was clearly minuted.  We also said that getElementById would throw
DW> exceptions if the targetted APS was a 'grnode'.

DW> My question: Is 'grnode' _completely_ transparant to DOM access
DW> functions (i.e., getAppStructureById, getAppStructuresByName,
DW> Node.next, Node.previous, Node.firstChild, Node.parentNode etc...),
DW> that was not so clear to me.

DW> Cheers,




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