>Thanks for the help. So what you are saying is that I can use XML-
>string as follows:

>var item_xml_data = "<item> <product>Pen</product>
><price>19.99</price> <quantity>12</quantity> <discount>20</discount>
><make> Parker </make> <code> 123456</code> </item>";

Yes, but it's better not to, why not put it in a metadata element in the
page, it's a lot more efficient to not have to call parseXML ?

>But you said that, I would soon run into problems. Could you please
>elaborate? What kind of problems?

Well you won't be able to include CDATA in there and stuff, but basically
it's not a good idea to put XML in a string, inside javascript in an xml
document - just keep the xml document in the xml...

>I may need to exchange large chunks of data between various sub-
>systems/components. So, I wanted to use XML-strings as data-
>structures and use them as parameter, while calling functions in
>other components.

So pass XML documents around, I don't see the problem, I think you'd need
to explain why this was a problem.

>These are just few examples. The main objective is to emulate data-
>structures. When I am creating SVG file using Servlet/JSP file, I
>could include many pieces of data along with each component (ex:
>items that can be selected for shopping).

if they're trees (and they clearly are) then including the XML in the SVG
makes completely sense, saves lots of serialising...

>Is moomin a variable? Can I use parseXML(moomin, null)? It looks
>like, it has been already parsed. I could also use already parsed-
>data, if I can pass such variables as parameters in a function.

It's already parsed, no need to parse it again, much more efficient, and
of course you can pass the variables around.  in javascript everything's
an object, a string every bit as much as node.

>How can I implement this?
>> function buy_me() {
>>    var e = How Can I initialize this variable?  < -----------

you don't need to just get SVGDoc in the init, as a global variable, then
you just need the getElementById and add_to_cart functions.

Jim.

I am doing the same thing in my project. I am writing
a function onClickZoom() and I am using <animate
attributeName="viewBox" ....> function and changing
the viewbox values according to the requirments and it
sworking pretty fine.... I don't know whether this is
the problem you are referrring to...


Madhavi

--- Mayi <mayi4u_2000@...> wrote: > Hello,
>
> I'm a newbie to SVG & XML! I'm trying to override
> the zoomin
> functionality provided by Adobe's SVG viewer and use
> just a
> mouseclick (click a button, then click the map) to
> zoom. I have
> written a ZoomOnClick function (reused somebody's
> code) that I put
> into my map.svg file. I've changed
> onzoom="onSVGZoom()" to
> onZoom="ZoomOnClick(evt)". This doesn't seem to work
> however. What
> other changes do I need to make (e.g. adding an
> onClick event when
> the zoomin symbol is clicked) to get this working ?
> Any pointers
> would be really appreciated!
> Thanks very much,
> Mayi.
>
>

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

Mike Chambers wrote:


> I keep hearing from the SVG community the Mobile SVG is a great
> solution,


Yes, I and many others think it is.

Are you interested in SVG, or Mobile SVG? Conferences are a great place
to see demos and to get info.

> and I was just curious if device deployment reflected this.


Consumer market: not yet, since the specs are still young.

But many companies are very interested; you would have seen various live
demos at SVG Open, and you also would have gotten a lot of information
about the then current state of development.

Tobi


--
http://www.pinkjuice.com/

Jim Ley wrote:


>>var item_xml_data = "<item> <product>Pen</product>
>><price>19.99</price> <quantity>12</quantity> <discount>20</discount>
>><make> Parker </make> <code> 123456</code> </item>";
>>
> Yes, but it's better not to, why not put it in a metadata element in the
> page,


IMHO: The above XML looks like data, not metadata.

Tobi


--
http://www.pinkjuice.com/

> > I read a lot about how great XSLT is.
>
> It's just a programming language tailored for manipulating XML
> documents...


Hi,

This is a bit OT, but I wouldn't consider XSLT a
<i>programming</i> language. It's a transformation language.

-g

I've got the SVG ActiveX control embedded and behaving properly, and
now I just need to print the SVG. Has anyone gotten this working? Is
it something really simple that I'm overlooking?

Thanks,
    -gever

Jim and Tobi

> > So perhaps Batik doesn't support it, sorry.
>
>
> I also remember that it does support XSLT :)


Batik does support XSLT :-)


Take a look:

http://cvs.apache.org/viewcvs.cgi/xml-batik/samples/extensions/xsl/

http://www.w3.org/People/maxf/papers/2002-07-
SVGOpen/svgopen.html#id2590164

And I would look at SVG Demos on Max Froumentin page
http://www.w3.org/People/maxf/

he states:
<snip>
Note that Batik is now able to read and process the XSLT sources
directly.
</snip>

I not sure if this is what you are talking about. But it is
information that I think some people will find useful :-)

We all learn by sharing what we know
Robert A. DiBlasi
http://www.svgnotebook.com
rdiblasi@...
SVG User Group: Chicago IL. Chapter Member

"Tobias Reif" <tobiasreif@...> wrote in message
news:3DC2C30E.802@....
> Jim Ley wrote:
>
>
> >>var item_xml_data = "<item> <product>Pen</product>
> >><price>19.99</price> <quantity>12</quantity> <discount>20</discount>
> >><make> Parker </make> <code> 123456</code> </item>";
> >>
> > Yes, but it's better not to, why not put it in a metadata element in
the
> > page,
>
> IMHO: The above XML looks like data, not metadata.

So which container in the SVG Content Model would you suggest was
appropriate?

There's only DESC and METADATA that I can see, and as it's not a
description of the SVG, I'd rather have it in METADATA, I agree there
could be some debate but I see it as metadata not of the SVG document
itself (ie creator etc.) but metadata about what the SVG document is a
visualisation of, and therefore still appropriate for the METADATA
element, perhaps as SVG moves to an application environment, a DATA
element would be appropriate :-) whilst we just tacking on applications
to a graphics format, we have to live with what we've got!

Jim.

Jim Ley wrote:


> So which container in the SVG Content Model would you suggest was
> appropriate?


None.

External files, getURL, or other solutions perhaps. I don't have a
solution specific, he'll have to experiment, but the metadata element
clearly is for metadata.


Tobi


--
http://www.pinkjuice.com/

> > IMHO: The above XML looks like data, not metadata.
>
> So which container in the SVG Content Model would you suggest was
> appropriate?

This might be a solution?
http://www.w3.org/TR/SVG/extend.html#PrivateElementsAndAttribute

/niklas

> -----Original Message-----
> From: Tobias Reif [mailto:tobiasreif@...]

>
> > I keep hearing from the SVG community the Mobile SVG is a great
> > solution,
>
>
> Yes, I and many others think it is.

i didnt mean to suggest otherwise.

> Consumer market: not yet, since the specs are still young.
>
> But many companies are very interested; you would have seen
> various live
> demos at SVG Open, and you also would have gotten a lot of
> information
> about the then current state of development.
>

thanks. that is the info i was looking for.

mike chambers

mesh@...

Niklas,


--- In svg-developers@y..., "Niklas Gustavsson" <niklas@p...> wrote:
> > > IMHO: The above XML looks like data, not metadata.
> >
> > So which container in the SVG Content Model would you suggest was
> > appropriate?
>
> This might be a solution?
> http://www.w3.org/TR/SVG/extend.html#PrivateElementsAndAttribute
>
> /niklas

Nice idea! ;-)

New Namespace is always a good idea...

We all learn by sharing what we know
Robert A. DiBlasi
http://www.svgnotebook.com
rdiblasi@...
SVG User Group: Chicago IL Chapter Member

Mike there are many SVG viewer implementations available for PDA's:

* Bitflash has viewers for Mobile Phones and PDAs (mainly Pocket PC)
* ZoomOn has a SVG viewer for Mobile phones
* eSVG (Intesis) has an svg-embedded viewer for PocketPC and others
* Sharp has a viewer that can import SVGs
* Nokia is working on SVG Mobile
* a friend of mine is working on a SVG-viewer for the Sharp Zaurus
* Tinyline is a svg-viewer for the Ipaq, the Sharp Zaurus and other
devices supporting personal Java
* Hitachi and KDDI have developed SVG viewer (PSV) with support for
2.5 g and 3g mobile phones (their system is operational in japan for
about one year with 8 million devices sold) - they support location
based services on the base of SVG (subset)

So there are enough devices available for SVG support: mobile phones,
pdas, of course also laptops and embedded devices. Many companies
have svg-viewer that are very hardware-independent and can easily be
ported to many platforms.

finally: svg is now part of the 3gpp standard (with backing from the
largest mobile-phone companies, incl. Nokia)

As Tobias already mentioned there had been presentations at the
SVG.Open conference.

Andreas

--- In svg-developers@y..., "Mike Chambers" <mchamber@m...> wrote:
>
>
> > -----Original Message-----
> > From: Tobias Reif [mailto:tobiasreif@p...]
>
> >
> > > I keep hearing from the SVG community the Mobile SVG is a great
> > > solution,
> >
> >
> > Yes, I and many others think it is.
>
> i didnt mean to suggest otherwise.
>
> > Consumer market: not yet, since the specs are still young.
> >
> > But many companies are very interested; you would have seen
> > various live
> > demos at SVG Open, and you also would have gotten a lot of
> > information
> > about the then current state of development.
> >
>
> thanks. that is the info i was looking for.
>
> mike chambers
>
> mesh@m...

On Fri, 01 Nov 2002, Ian Tindale wrote:

> > -----Original Message-----
> > From: www-svg-request@... [mailto:www-svg-request@...] On Behalf Of
> > Dean Jackson
> > Sent: 30 October 2002 11:49
> > To: www-svg@...; svg-developers@yahoogroups.com
> > Subject: SVG page at W3C
> >
> >
> > In a renewed burst of enthusiasm, Chris and I have been updating the
> > SVG page at W3C.
> >
> > http://www.w3.org/Graphics/SVG/
> >
> > A major update to the implementations page is
> > expected real soon now!
>

> If the idea of doing similar at the 'implementations' page ever
> becomes that palatable (Ian ducks), I thought that it would be
> interesting and useful to have a special table for 'firmware'. That

This is a good suggestion. I believe there are a lot of updates
to the page of this type in the wings.

> is, phones and devices which have SVG awareness built into their
> firmware, and how it uses it (ie, wrapped in an MMS context, etc.)
> and which version. That's the trouble - the firmware version
> tracking can easily race ahead with little actual released info on
> what has been added. For example, I've just updated my and my wife's
> Ericsson T68 phones to T68i firmware (they're the same base product,
> different colours on outside, different bytes on inside, that's
> all). Now I find I've got a phone that can make sense of (some) MMS,
> and WAP2/(some XHTML profile or other - not sure which or how much
> yet). SVG browsers could 'creep' into peoples pockets quite easily
> this way.

That's right. Andreas lists many in a later email (and he forgot
some public ones :).

There are also a bunch of companies that have embedded SVG in
devices but have not yet announced that publicly. We're talking
phones as well as embedded devices such as home-automation and
in-car navigation systems. With all the great demos, going to an
SVG Working Group meeting is sometimes like going to a consumer
electronics show (and not all the implementations we see come from
inside the group).

Why do these companies have interest in SVG? Mostly because it
is a standard not controlled by a single vendor (*), and that it
is XML, so fits easily into workflow.

Chris presented many of the public implementations at SVG Open.
I'm not sure if his presentation is on the Web - I know mine isn't :(

dean


(*) of course SVG isn't controlled by a single vendor - it's
controlled by me, from my secret hideout inside a hollowed out
volcano..... mwwhhhaaaa hahahahahahaha. Did I say that or just think
it?






> --
> Ian Tindale
>
>
>
>
> -----
> To unsubscribe send a message to: svg-developers-unsubscribe@yahoogroups.com
> -or-
> visit http://groups.yahoo.com/group/svg-developers and click "edit my
membership"
> ----
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

>>This is a bit OT, but I wouldn't consider XSLT a
<i>programming</i> language. It's a transformation language.<<

And IMHO, as great as XSLT is, that is where it belongs...even though some would
argue otherwise...

http://www.topxml.com/xsl/articles/fp/

BUT!! If you are after a fully XML based OO programming language, check out
Kimanzi Mati's x++ language...

http://xplusplus.sourceforge.net/index.htm

Pete

Mike Chambers of Macromedia had asked:

### Begin Quote
let me try again:

Is there a list available of non PC devices which have SVG support?

such as PS2, Pocket PC, Palm, other embedded devices, etc...

I keep hearing from the SVG community the Mobile SVG is a great
solution, and I was just curious if device deployment reflected this.

mike chambers

mesh@...
### End Quote


In a thread only slightly aligned Dean had written:
### Begin Quote
With all the great demos, going to an
SVG Working Group meeting [it] is sometimes like going to a consumer
electronics show (and not all the implementations we see come from
inside the group).
### End Quote

So, we find an excellent solution to remove Macromedia's ignorance of what is
happening in the SVG world, and to avoid it re-occurring ....


.... Macromedia could join the SVG Working Group.

Problem solved.

Andrew Watt

Dean,


> Chris presented many of the public implementations at SVG Open.
> I'm not sure if his presentation is on the Web - I know mine isn't :(


It would be great to have your hypnotizing art online :)


> (*) of course SVG isn't controlled by a single vendor - it's
> controlled by me, from my secret hideout inside a hollowed out
> volcano..... mwwhhhaaaa hahahahahahaha.


I *knew* it!

Tobi

--
http://www.pinkjuice.com/

"Niklas Gustavsson" <niklas@...> wrote in message
news:apuisl$g96$1@....
> > > IMHO: The above XML looks like data, not metadata.
> >
> > So which container in the SVG Content Model would you suggest was
> > appropriate?
>
> This might be a solution?
> http://www.w3.org/TR/SVG/extend.html#PrivateElementsAndAttribute

I'm already using the private namespaces - which are basically allowed
anywhere at all, but it's still nice to put them somewhere sensible -
that page puts them in the DEFS element, which is another workable
solution I hadn't considered - I'd thought of that as more related to
graphical elements being defined.

It's a useful feature in SVG, and if you always need the content are
much more efficient than using the non-standard getURL/parseXML
extensions, however powerful they are.

Jim

"Tobias Reif" <tobiasreif@...> wrote in message
news:3DC2CA42.5030008@....
> Jim Ley wrote:
>
>
> > So which container in the SVG Content Model would you suggest was
> > appropriate?
>
>
> None.
>
> External files, getURL,

I'm surprised, advocating a non-standard extension, to a problem that is
easily solvable within SVG, you could of course just put it off the root
element, which I don't really like as it's sort of floating in nothing.
The svg spec uses DEFS for a similar role (23.1), I'm a bit unsure of
that, depending on the nature of the DATA, but it seems workable.
Perhaps I'm biased, because I already do this with RDF in the METADATA
element (which is encouraged in the SVG Spec, tools are taught to expect
RDF in the metadata element - and RDF would not automatically be related
to the document.)

> or other solutions perhaps. I don't have a
> solution specific, he'll have to experiment, but the metadata element
> clearly is for metadata.

So the idea that we can mix XML namespaces in SVG is bogus, I consider
that a strength of SVG - I know I'm misrepresenting you - but if this is
not a use of mixed namespace content - what is?

Jim.

Jim Ley wrote:


> I'm surprised, advocating a non-standard extension,


Well, you snipped "I don't have a solution specific,"
(which was garbled from "I don't have a specific solution,").


>>or other solutions perhaps. I don't have a
>>solution specific, he'll have to experiment, but the metadata element
>>clearly is for metadata.
>>
> So the idea that we can mix XML namespaces in SVG is bogus,


Nope, and I don't like your "I'll misunderstand you intentionally and
endlessly" game.

Metadata inside the metadata element will be from other namespaces; how
did I say that's bogus? I just said that it's not meant to contain
anything else than metadata, AFAICS.

Tobi

--
http://www.pinkjuice.com/

--- In svg-developers@y..., "Jim Ley" <jim@j...> wrote:
>
> "Tobias Reif" <tobiasreif@p...> wrote in message
> news:3DC2C30E.802@p...
> > Jim Ley wrote:
> >
> >
> > >>var item_xml_data = "<item> <product>Pen</product>
> > >><price>19.99</price> <quantity>12</quantity>
<discount>20</discount>
> > >><make> Parker </make> <code> 123456</code> </item>";
> > >>
> > > Yes, but it's better not to, why not put it in a metadata
element in
> the
> > > page,
> >
> > IMHO: The above XML looks like data, not metadata.
>
> So which container in the SVG Content Model would you suggest was
> appropriate?
>
> There's only DESC and METADATA that I can see, and as it's not a
> description of the SVG, I'd rather have it in METADATA, I agree
there
> could be some debate but I see it as metadata not of the SVG
document
> itself (ie creator etc.) but metadata about what the SVG document
is a
> visualisation of, and therefore still appropriate for the METADATA
> element, perhaps as SVG moves to an application environment, a DATA
> element would be appropriate :-) whilst we just tacking on
applications
> to a graphics format, we have to live with what we've got!
>
> Jim.


I think, I agree with Jim. It would be great to have a DATA tag, but
until that time, I could live with METADATA.

Niklas has pointed to an interesting link which states that:
-------------------------Begin------------------
SVG's ability to include foreign namespaces can be used for the
following purposes:

· Application-specific information so that authoring
applications can include model-level data in the SVG content to serve
their "roundtripping" purposes (i.e., the ability to write, then read
a file without loss of higher-level information).

· Supplemental data for extensibility. For example, suppose you
have an extrusion extension which takes any 2D graphics and extrudes
it in three dimensions. When applying the extrusion extension, you
probably will need to set some parameters. The parameters can be
included in the SVG content by inserting elements from an extrusion
extension namespace.

To illustrate, a business graphics authoring application might want
to include some private data within an SVG document so that it could
properly reassemble the chart (a pie chart in this case) upon reading
it back in:

<?xml version="1.0" standalone="yes"?>
<svg width="4in" height="3in"
      xmlns = 'http://www.w3.org/2000/svg'>
   <defs>
     <myapp:piechart xmlns:myapp="http://example.org/myapp"
                     title="Sales by Region">
       <myapp:pieslice label="Northern Region" value="1.23"/>
       <myapp:pieslice label="Eastern Region" value="2.53"/>
       <myapp:pieslice label="Southern Region" value="3.89"/>
       <myapp:pieslice label="Western Region" value="2.04"/>
       <!-- Other private data goes here -->
     </myapp:piechart>
   </defs>
   <desc>This chart includes private data in another namespace
   </desc>
   <!-- In here would be the actual SVG graphics elements which
        draw the pie chart -->
</svg>
--------------------End--------------------

I think, could I include the data as follows (using foreign
namespace):

   <defs>
     <data:piechart xmlns:data="none"  id="xml_data"
                     title="Sales by Region">
       <data:pieslice label="Northern Region" value="1.23"/>
       <data:pieslice label="Eastern Region" value="2.53"/>
       <data:pieslice label="Southern Region" value="3.89"/>
       <data:pieslice label="Western Region" value="2.04"/>
       <!-- Other private data goes here -->
     </data:piechart>
   </defs>

> function draw_chart(evt) {
>           SVGDoc = evt.getTarget().getOwnerDocument()
>           xml_data=SVGDoc.getElementById('xml_data')
>           refresh_cart(xml_data)
> }
Is this above code valid? Does it work?

Best Regards,
Bharat Singh

bharat1_singh wrote:


>>There's only DESC and METADATA that I can see, and as it's not a
>>description of the SVG,


> I think, I agree with Jim. It would be great to have a DATA tag, but
> until that time, I could live with METADATA.


desc el is for descriptions, metadata el is for metadata, AFAICS.


> <svg width="4in" height="3in"
>      xmlns = 'http://www.w3.org/2000/svg'>
>   <defs>
>     <myapp:piechart xmlns:myapp="http://example.org/myapp"
>                     title="Sales by Region">
>       <myapp:pieslice label="Northern Region" value="1.23"/>
>       <myapp:pieslice label="Eastern Region" value="2.53"/>

defs el seems to be the most appropriate.

Tobi

--
http://www.pinkjuice.com/

> I think, could I include the data as follows (using foreign
> namespace):

>   <defs>
>     <data:piechart xmlns:data="none"  id="xml_data"
>                     title="Sales by Region">
>       <data:pieslice label="Northern Region" value="1.23"/>
>       <data:pieslice label="Eastern Region" value="2.53"/>
>       <data:pieslice label="Southern Region" value="3.89"/>
>       <data:pieslice label="Western Region" value="2.04"/>
>       <!-- Other private data goes here -->
>     </data:piechart>
>   </defs>

> Is this above code valid?

If you define your extra data in an internal DTD as specified in the spec it
should be yes :-)

/niklas

--- In svg-developers@y..., "Niklas Gustavsson" <niklas@p...> wrote:
> > I think, could I include the data as follows (using foreign
> > namespace):
>
> >   <defs>
> >     <data:piechart xmlns:data="none"  id="xml_data"
> >                     title="Sales by Region">
> >       <data:pieslice label="Northern Region" value="1.23"/>
> >       <data:pieslice label="Eastern Region" value="2.53"/>
> >       <data:pieslice label="Southern Region" value="3.89"/>
> >       <data:pieslice label="Western Region" value="2.04"/>
> >       <!-- Other private data goes here -->
> >     </data:piechart>
> >   </defs>
>
> > Is this above code valid?
>
> If you define your extra data in an internal DTD as specified in
the spec it
> should be yes :-)
>
> /niklas

Niklas,

I am new to SVG/XML. What do you mean by `internal DTD as specified
in the spec'? Could you please elaborate, if possible with an example?

Thanks and Best Regards,
Bharat Singh

As you can write a Turing Machine in XSLT and therefore by definition
compute pretty well anything, then it probably should be regarded as
a programming language. If you don't like that term then it is a
translator writing system. A transformation language sounds more like
SNOBOL!

Bob

--- In svg-developers@y..., "Peter Schonefeld"
<peter.schonefeld@b...> wrote:
>
> >>This is a bit OT, but I wouldn't consider XSLT a
> <i>programming</i> language. It's a transformation language.<<
>
> And IMHO, as great as XSLT is, that is where it belongs...even
though some would
> argue otherwise...
>
> http://www.topxml.com/xsl/articles/fp/
>
> BUT!! If you are after a fully XML based OO programming language,
check out
> Kimanzi Mati's x++ language...
>
> http://xplusplus.sourceforge.net/index.htm
>
> Pete

> I am new to SVG/XML. What do you mean by `internal DTD as specified
> in the spec'? Could you please elaborate, if possible with an example?

Hi

Custom elements and attributes must be defined in the DTD for your file. The
way to do this (you will find an example at
http://www.w3.org/TR/SVG/extend.html#PrivateElementsAndAttribute) is to add
an internal DTD in your file (you can also do this in a new DTD that
combines the SVG DTD and an internal DTD, this is good if you need to re-use
it).

A valid file for your example could be:

<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN"
   "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd"
[
<!ENTITY % defsExt "| data:piechart" >
<!ELEMENT data:piechart (data:pieslice+)>
<!ATTLIST data:piechart
   xmlns:data CDATA #FIXED "none"
   %stdAttrs;
   title CDATA #IMPLIED>

<!ELEMENT data:pieslice EMPTY>
<!ATTLIST data:pieslice
   xmlns:data CDATA #FIXED "none"
   %stdAttrs;
   label CDATA #IMPLIED
   value CDATA #IMPLIED>
]>
<svg xmlns="http://www.w3.org/2000/svg">

     <defs>
      <data:piechart xmlns:data="none"  id="xml_data" title="Sales by
Region">
       <data:pieslice label="Northern Region" value="1.23"/>
       <data:pieslice label="Eastern Region" value="2.53"/>
       <data:pieslice label="Southern Region" value="3.89"/>
       <data:pieslice label="Western Region" value="2.04"/>
       <!-- Other private data goes here -->
      </data:piechart>
     </defs>
</svg>

Hope that helps!
/niklas

--- In svg-developers@y..., "Jim Ley" <jim@j...> wrote:
> >I may need to exchange large chunks of data between various sub-
> >systems/components. So, I wanted to use XML-strings as data-
> >structures and use them as parameter, while calling functions in
> >other components.
>
> So pass XML documents around, I don't see the problem, I think
you'd need
> to explain why this was a problem.
>

Jim, I am new to SVG/XML. I don't know what do mean by XML documents?
This means parsed XML-string? In that case, I don't have a problem.


> >These are just few examples. The main objective is to emulate data-
> >structures. When I am creating SVG file using Servlet/JSP file, I
> >could include many pieces of data along with each component (ex:
> >items that can be selected for shopping).
>
> if they're trees (and they clearly are) then including the XML in
the SVG
> makes completely sense, saves lots of serialising...

I am coming from Java/C/C# background. I am evaluating, if I could
build components to build data-driven applications. To build that, I
need to extensively exchange data-structures between components.
Because, there are no data structures in SVG/Jscript, I am trying to
figure a way using XML. As long as, I could accomplish this I am
happy (for now at least). I have to store lot of data in the SVG
file, I could not use getURL() to get data.

Please suggest me best way to store XML-data in the SVG file and set
that to a variable as string or parsed-XML-object.

Thanks,
Bharat Singh

Niklas Gustavsson wrote:


> A valid file for your example could be:
>
> <?xml version="1.0" standalone="no"?>
> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN"
>   "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd"
> [
> <!ENTITY % defsExt "| data:piechart" >
> <!ELEMENT data:piechart (data:pieslice+)>
> <!ATTLIST data:piechart
>   xmlns:data CDATA #FIXED "none"
>   %stdAttrs;
>   title CDATA #IMPLIED>
>
> <!ELEMENT data:pieslice EMPTY>
> <!ATTLIST data:pieslice
>   xmlns:data CDATA #FIXED "none"
>   %stdAttrs;
>   label CDATA #IMPLIED
>   value CDATA #IMPLIED>
> ]>


Just FYI:

* Xerce's DOMCount:
######################################################################
Fatal Error at file C:\tmp\from_stdin.663099, line 9, char 4
    Message: PE refs are not allowed inside markup in the internal subset
######################################################################

* libxml's xmllint:
######################################################################
xmllint niklas.svg --valid --noout --catalogs
niklas.svg:9: error: ATTLIST: no name for Attribute
    %stdAttrs;
    ^
\niklas.svg:10: error: xmlParseInternalSubset: error detec
ted in Markup declaration
    title CDATA #IMPLIED>
    ^
niklas.svg:10: error: DOCTYPE improperly terminated
    title CDATA #IMPLIED>
    ^
niklas.svg:10: error: Start tag expected, '<' not found
    title CDATA #IMPLIED>
     ^
######################################################################

Some SVG showing a way to extend SVG via the internal subset:
(just to show how it can be extended; it does something else than Niklas
sample)
    http://www.pinkjuice.com/svg/svgz/layout02.xhtml
    http://www.pinkjuice.com/svg/svgz/layout02.svgz
(does this validate for everyone?)

Tobi

--
http://www.pinkjuice.com/

--- In svg-developers@y..., "Niklas Gustavsson" <niklas@p...> wrote:
> > I am new to SVG/XML. What do you mean by `internal DTD as
specified
> > in the spec'? Could you please elaborate, if possible with an
example?
>
> Hi
>
> Custom elements and attributes must be defined in the DTD for your
file. The
> way to do this (you will find an example at
> http://www.w3.org/TR/SVG/extend.html#PrivateElementsAndAttribute)
is to add
> an internal DTD in your file (you can also do this in a new DTD that
> combines the SVG DTD and an internal DTD, this is good if you need
to re-use
> it).
>
> A valid file for your example could be:
>
> <?xml version="1.0" standalone="no"?>
> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN"
>   "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd"
> [
> <!ENTITY % defsExt "| data:piechart" >
> <!ELEMENT data:piechart (data:pieslice+)>
> <!ATTLIST data:piechart
>   xmlns:data CDATA #FIXED "none"
>   %stdAttrs;
>   title CDATA #IMPLIED>

Niklas:

Is there a way to use just 'Well Formed XML' as opposed to 'Valid
XML'? This is because, I have to use many such XML-data strings. It
is very difficult for me to track all of them. But all my data
requirements are as simple as name and value pairs. Very rarely, I
use trees at this moment.

What kind of problems, I will face, If I don't have associated DTD.

I think, parseXML() could parse 'Well Formed XML' data-streams. If it
parsed, I could access various values using names from this parsed
DOM tree. Am I wrong? Don't you think it would work? Why?


Thanks,
Bharat Singh

>
> <!ELEMENT data:pieslice EMPTY>
> <!ATTLIST data:pieslice
>   xmlns:data CDATA #FIXED "none"
>   %stdAttrs;
>   label CDATA #IMPLIED
>   value CDATA #IMPLIED>
> ]>
> <svg xmlns="http://www.w3.org/2000/svg">
>
>     <defs>
>      <data:piechart xmlns:data="none"  id="xml_data" title="Sales by
> Region">
>       <data:pieslice label="Northern Region" value="1.23"/>
>       <data:pieslice label="Eastern Region" value="2.53"/>
>       <data:pieslice label="Southern Region" value="3.89"/>
>       <data:pieslice label="Western Region" value="2.04"/>
>       <!-- Other private data goes here -->
>      </data:piechart>
>     </defs>
> </svg>
>
> Hope that helps!
> /niklas

"neumannandreas" <neumann@...> wrote in message
news:apuqoa+qd3d@....

> So there are enough devices available for SVG support: mobile phones,
> pdas, of course also laptops and embedded devices. Many companies
> have svg-viewer that are very hardware-independent and can easily be
> ported to many platforms.

I was recently at Mobile Commerce World Europe, I was working, not a
delegate so not completely free to wonder around, but I was very
disappointed about the
lack of toys available, the only non-computer device there with vector
graphics support was the Pogo (which does flash....).  Also none of the
content providers who were delivering services were pitching for what
SVG could do, they were all in the much simpler scheme, so it seems
we're some time away :-( .

Jim.