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: [cgmo-webcgm] WebCGM and the <object> tag



It is a subtle point, whether the WebCGM standard can place conformance
requirements on HTML content that references WebCGM instances.  However the
prescription in WebCGM (section 3.4) is unambiguous:

>The only standard way to reference in-line CGMs from HTML documents is
>through the OBJECT tag, using the DATA attribute for the CGM file and the
>TYPE attribute to specify the full Mime Type. The minimal tag for adding
>CGM into a document would be:
><OBJECT DATA="xxx.cgm" TYPE="image/cgm;Version=4;ProfileId=WebCGM";
>WIDTH=200; HEIGHT=100>

-Lofton.

I agree, but I think the wording is not really clear enough.
What does "reference" mean?
An OBJECT tag is an integral portion of the HTML content, so it is included
in the document. it uses parameters that point to a MIME type and to
a CGM file.
This is NOT an inline CGM in the sense as SVG does inline SVG.
I agree that it is difficult to place conformance requirements on HTML, how
does SVG do it?
What if there is only an href in the HDML that is being clicked upon, and
the
result is a new window with a viewer it it WITHOUT an OBJECT tag?
What if the src parameter of a window is set to point to a WebCGM file? Is
this
invalid?
What if we use the DOM to steer this?

Probably the best way to handle this variety of options is to say "viewers
are expected
to handle OBJECT tags with the following parameters" or similar.

Ideas?



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