[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re[2]: [cgmo-webcgm] ISSUE: relative URIs in 'linkuri'
Hi Lofton, <snip> LH> Do you think anything more is needed to close this? (And if LH> 'yes',would you please supply the wording?) With wording, uh..., then my answer is no :) -- Benoit mailto:benoit@itedo.com LH> -Lofton. LH> but here are my thoughts LH> anyway... LH> I don't understand what the problem is; or what is meant by'linkuri'. LH> 'linkuri' the WebCGM 1.0/2.0 APS attribute; or <linkuri> elementof LH> the XCF? LH> If we are talking about the WebCGM 1.0/2.0 APS attribute, then thisis LH> easy, relative URIs should behave in 2.0 liked they behaved inWebCGM LH> 1.0. I'm sure you'll all agree. LH> I suspect Dieter was talking about the <linkuri> element of theXCF. LH> Please don't forget that applying an XCF onto a WebCGM document is LH> 'replacing' the existing WebCGM APS attribute values with the newones LH> found in the XCF. When an implementation sees: LH> <grobject apsid="one"> LH> <linkuri uri="#myObject" /> LH> <grobject> LH> The string '#myObject' is set within the 'one' APS, like so: LH> BEGAPS 'one' 'grobject' STLIST; LH> APSATTR 'linkuri' "14 3 '#myObject' '' ''"; LH> BEGAPSBODY; LH> ... LH> ENDAPS; LH> And the hyperlinking behavior of such a file should be well defined LH> (as per WebCGM 1.0). LH> Regards,
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]