iwov dcr

Hey

How can I parse an iwov dcr ? Please explain with an example.

Thanks in advance

Find more posts tagged with

Comments

Hey

How can I parse an iwov dcr ? Please explain with an example.

Thanks in advance

You can use any parser, however you have to provide the element name you need to fetch.

Send your DCR as attachement and what needs to be extracted, then only an example can be set.

Ambuj

Hey

How can I parse an iwov dcr ? Please explain with an example.

Thanks in advance

Yes, you can.

It would be similar to parsing a normal XML file. BTW, what is your requirement? What do you want to achieve?

ISCBorisB

Hey

How can I parse an iwov dcr ? Please explain with an example.

Thanks in advance

Run perldoc on TeamSite: Smiley Very Happy

CRparser and TeamSite: Smiley Very Happy

CRnode, POD documentation contains usage samples as well.
For your purpose it's much easier than generic XMLParser, lots of DCR details are already covered.

gzevin

Run perldoc on TeamSite:CRparser and TeamSite:CRnode, POD documentation contains usage samples as well.
For your purpose it's much easier than generic XMLParser, lots of DCR details are already covered.

suprisingly, pretty often I use those modules for some non-iwov XML (there is no much if you are not using non-native XML for DCRs). Even though Jon **** wrote a pretty dirty code, it's sometimes easier than some common XML modules.

nipper

suprisingly, pretty often I use those modules for some non-iwov XML (there is no much if you are not using non-native XML for DCRs).

I cannot think of the last time I used the IWOV DCRs, I always define mine as XML.

gzevin

I cannot think of the last time I used the IWOV DCRs, I always define mine as XML.

apart from compatibility with LiveSite (I gueess?) and some other requirements and maybe some saving of a few kilobytes, old iwov xml is still pretty Ok to use. But I do start all new implementations with an industry XML, true.

ccprofessional

apart from compatibility with LiveSite (I gueess?) and some other requirements and maybe some saving of a few kilobytes, old iwov xml is still pretty Ok to use. But I do start all new implementations with an industry XML, true.

Same here.
I am at a client where we are planning on a lot of new templates. I would like to go with xml format, but I really would like to keep it all uniform and stick to one format.

I looked everywhere for a comprehensive list of gotcha's with either format without luck.

Here's my list:
1. cool factor - xml sounds better
2. I am used to using pathid
3. A lot of FormAPI I believe depends on pathid
4. Livesite likes it

None of the above reasons is something that my customer would like to hear unless I provide good examples.

Can some one add anything else?

gzevin

Same here.
I am at a client where we are planning on a lot of new templates. I would like to go with xml format, but I really would like to keep it all uniform and stick to one format.

I looked everywhere for a comprehensive list of gotcha's with either format without luck.

Here's my list:
1. cool factor - xml sounds better
2. I am used to using pathid
3. A lot of FormAPI I believe depends on pathid
4. Livesite likes it

None of the above reasons is something that my customer would like to hear unless I provide good examples.

Can some one add anything else?

actually, after my LiveSite training I can tell you that either way it works. Their training examples deal with both iwov or new formats. The only thing is that XPATH strings for iwov formats are longer.