dtd « WordPress.com Tag Feed

DTD TUTORIAL

theshravan — Wed, 07 Oct 2009 04:14:45 +0000

Why is my design broken in other browsers?..Try a different DTD

kourtesy — Wed, 30 Sep 2009 02:00:54 +0000

Chances are that if you are reading this you probably spent hours (maybe less if you’re lucky) trying to fix your design so that several browsers will display it symmetrically.

If that is the case you may or may not be kicking yourself after you read the rest of this article. Sometimes, the answer to cross-browser compatibility is as simple as changing the DTD or document type declaration. I know that this was the case for me. For my site, I am using the HTML 4.01 transitional DTD with the DTD URL. This DTD is shown below.

< !DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”
“http://www.w3.org/TR/html4/loose.dtd” >

The reason that I chose this DTD is because it is accepted as standards mode in most browsers, and is almost standards mode in others. Furthermore, I have some deprecated elements and attributes in my code forcing me to stick to a transitional DTD. If you did not include depracated elements, tags, or attributes in your source code; then, a strict DTD would be your best option. Almost every strict DTD is accepted as standards mode in all major browsers.

Hating DTD: Our New Fave Hobby

taintvfruit — Thu, 24 Sep 2009 21:07:03 +0000

TheHair: this is my friend Erin: aaaand DTD continues his reign of woman-hating.

TheAss: oh no

again?

i didnt read

Erin: not as bad as the last one, but it’s just so blatant, how much he hates women.

i love her

TheAss: hahaha

she is spot on

TheHair: Erin: he’s all about his power over women. i think this one’s a slut. i think that one’s conceited. the only constant in all his little vignettes (95% of which i am convinced are pure fiction) is how he’s smarter, better, quicker, classier, above them ALL

TheAss: hahahaha

YES

TheAss: she just articulated what i have been trying to voice

SO WELL

TheAss: from his blog:

“Every man should have the experience of saying no to a woman who is unaccustomed to hearing the word. It is an invigorating experience.”

TheHair: I HATE HIM

OMG

im worked up

sorry

hating DTD is my new favorite hobby

TheAss: hahaha

you know i support this

Tattoo Style

kanival — Thu, 17 Sep 2009 17:09:48 +0000

Hair – .+*Corn*+.Mattcocoa [MS]

Pants – Denim ripped open with belt-BLUE [N-core]

Tattoo – **KANIVAL TATTOO** – 96. Angel

Corset – <TheAbyss> F_Gear//[Black]Pruriency_Corset

Blinder – ::DtD::BlackLeatherBlinder (1L)

Tattoo – **KANIVAL TATTOO** – 84. Chaos Blood

My Blog – http://kanival.wordpress.com/

Document Management Consultant

Spiller László — Mon, 14 Sep 2009 14:03:52 +0000

Microsoft szerver operációs rendszerek (Windows 2000 Server, Windows 2003 Server) UNIX operációs ren

Schemas from DTDs: The root (element) of evil?

xatapult — Mon, 07 Sep 2009 13:32:10 +0000

Once upon a time XML was born from SGML. And along with its birth came DTDs to define the document structure. Life was good. Everybody used to writing DTDs for SGML could keep doing so. And so they did…

But what happened? Newer and shinier methods for describing XML structures came along. W3C Schemas, Relax NG and others saw the light. Suddenly things that were impossible to do with DTDs became feasible: data typing, design modularization and many, many more. Wow! Suddenly you could really be strict about your document structure.

And so what happened in the ivory towers from which the gods send us their XML standards for us mere mortals to use? Where the standards accompanied by schemas in addition to the traditional DTDs? Yes, they were! Hurrah, a step forward. Now we can really and truly verify our documents.

But look closely. Are this schemas? Technically… yes. However they look an awful lot like DTDs. If I am not mistaken most of the DTDs are simply converted into schemas.

All right, so what? The standard developers (at least, most of them) seem to have chosen to keep on using DTDs. As a gesture to us humans they add schemas, but only schemas converted from their DTDs. No data typing, no modularization, nothing but elements and attributes.

And so we stay in the dark ages of XML design and miss all the opportunities to be more strict. But what’s even worse, it introduces an ambiguity: You can now validate documents with a completely different root element than intended…

Multiple root elements?

As an illustrative example, let’s assume we want to define the structure for this very complex XML document:

<Names>
   <Name>Erik</Name>
   <Name>John</Name>
   <!-- etc. -->
</Names>

A DTD for this could look like this:

<!ELEMENT Names ((Name+))>
<!ELEMENT Name (#PCDATA)>

This DTD defines that <Names> is the root element because it is not part of any other element’s definition. But if we convert this DTD directly into a schema (I use the build-in XML Spy convertor) something like this appears:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
   <xs:element name="Names">
       <xs:complexType>
           <xs:sequence>
               <xs:choice>
                   <xs:element ref="Name" maxOccurs="unbounded"/>
               </xs:choice>
           </xs:sequence>
       </xs:complexType>
   </xs:element>
   <xs:element name="Name">
       <xs:complexType mixed="true"/>
   </xs:element>
</xs:schema>

So, what’s wrong with this: The root element has become ambiguous! For instance, this is a perfectly valid XML document according to our brand new schema:

<Name>Erik</Name>

Not exactly what we would like, is it?

But is it a problem?

Yes. Definitely. Period.

DTDs were introduced to be able define the structure of our XML documents unambiguous. Schemas were introduced to make this even better. But now, by actually using schemas, we make it worse.

It could be the cause of all kinds of subtle and not so subtle errors when invalid XML, which a validator accepts undeserved, passes through systems. It might open backdoors for hackers because invalid data is accepted without raising alarms. And you could spent many unproductive hours debugging something that might have been detected very easily.

Oh, by the way: The schema feature to have more than one root elements is not a bug as such. There are situations you actually need it. For instance when you on purpose want to have a schema that allows multiple root elements. Or when you define a schema with elements for use inside another namespace.

What to do about it?

Do not blindly convert your DTDs into schemas and think you’re finished.

Create your schemas (or adapt the conversions) in such a way that only one root element is possible (unless of course you mean something else on purpose).

And to get the best results: Use the features a schema language possesses to define the structure of your XML as tight as possible. And that is a lot more tight than a DTD!

Exercise 8: XML Introduction

Jason Rankmore — Mon, 07 Sep 2009 11:26:33 +0000

This topic provided an introduction to the the structure, use and workings of XML, i found this topic interesting because XML can be used to mark up pretty much anything you like, whether it be a newspaper, rss feed or the document which we were tasked with creating a catalogue; in this instance a car catalogue.

My XML DTD is as follows:

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE catalogue[
<!ELEMENT catalogue(car*)>
<!ELEMENT car(make, model, year, colour, engine, number_of_doors, transmission_type, accessories*)>
<!ELEMENT make (#PCDATA)>
<!ELEMENT model (#PCDATA)>
<!ELEMENT year (#PCDATA)>
<!ELEMENT colour (#PCDATA)>
<!ELEMENT engine (number_of_cylinders, fuel_system)>
<!ELEMENT number_of_cylinders (#PCDATA)>
<!ELEMENT fuel_system (#PCDATA)>
<!ELEMENT number_of_doors (#PCDATA)>
<!ELEMENT transmission_type (#PCDATA)>
<!ELEMENT accessories (#PCDATA)>
]>

An example of how this would be used to catalogue a car is as follows:

<catalogue>
<car>
<make>Holden</make>
<model>VX Commodore</model>
<year>2001</year>
<colour>Black</colour>
<engine>
<number_of_cylinders>6</number_of_cylinders>
<fuel_system>Unleaded</fuel_system>
</engine>
<number_of_doors>4</number_of_doors>
<transmission_type>Automatic</transmission_type>
<accessories>CD Player</accessories>
<accessories>18″ Wheels</accessories>
<accessories>ABS Braking</accessories>
</car>
</catalogue>

To add additional cars to this catalogue you would define it a new <car></car> declaration, this of course would have to be between the existing <catalogue></catalogue> tags.

XML training in Oxford

Duncan — Fri, 04 Sep 2009 15:13:55 +0000

The XML Summer School returns this year at St. Edmund Hall, Oxford from 20th-25th September 2009. As always, it’s packed with high quality technical training for every level of expertise, from the Hands-on Introduction for beginners through to special classes devoted to XQuery and XSLT, Semantic Technologies, Open Source Applications, Web 2.0, Web Services and Identity. The Summer School is also a rare opportunity to experience what life is like as a student in one of the world’s oldest university cities while enjoying a range of social events that are a part of the unique summer school experience.

This year, classes and sessions are taught and chaired by:

Tony Coates, Londata Ltd., blogs at kontrawize
John Chelsom, City University and Eleven Informatics LLP.
Neil Cowles, Tolven Inc.
Leigh Dodds, Talis Information Ltd., blogs at Lost Boy.
Paul Downey, Osmosoft (Open Source applications from British Telecom) blogs at whatfettle
Bob DuCharme, TopQuadrant Inc., blogs at snee.com
Peter Flynn, blogs at silmaril.ie
Marc Hadley, Sun Microsystems, blogs at java.net
Duncan Hull, yours truly, blogs here.
Michael Kay, Saxonica Ltd., home of the Saxon XSLT and XQuery Processor blogs at blogharbor
Debbie Lapeyre, Mulberry Technologies,
Eve Maler, PayPal Inc., blogs at Pushing String.
Simon Phipps, Sun Microsystems Inc., blogs at sun.com
Adam Retter, blogs at adamretter.org.uk
Rich Salz, IBM, blogs at developerWorks
Andy Seaborne, Hewlett-Packard laboratories, blogs at ARQtick
Michael Sperberg-McQueen, Black Mesa Technologies LLC., blogs at Messages in a Bottle
Ron Summers, Loughborough University
Jeni Tennison, Jeni Tennison Consulting Ltd., blogs at jenitennison.com
Norm Walsh, Mark Logic, blogs at norman.walsh.name
Priscilla Walmsley, Datypic consulting
Lauren Wood blogs at laurenwood.org

The Extensible Markup Language (XML) has been around for just over ten years, quickly and quietly finding its niche in many different areas of science and technology. It has been used in everything from modelling biochemical networks in systems biology [1], to electronic health records [2], scientific publishing, the provision of the PubMed service (which talks XML) [3] and many other areas. As a crude measure of its importance in biomedical science, PubMed currently has no fewer than 800 peer-reviewed publications on XML. It’s hard to imagine life without it. So whether you’re a complete novice looking to learn more about XML or a seasoned veteran wanting to improve your knowledge, register your place and find out more by visiting xmlsummerschool.com. I hope to see you there…

References

Hucka, M. (2003). The systems biology markup language (SBML): a medium for representation and exchange of biochemical network models Bioinformatics, 19 (4), 524-531 DOI: 10.1093/bioinformatics/btg015
Bunduchi R, Williams R, Graham I, & Smart A (2006). XML-based clinical data standardisation in the National Health Service Scotland. Informatics in primary care, 14 (4) PMID: 17504574
Sayers, E., Barrett, T., Benson, D., Bryant, S., Canese, K., Chetvernin, V., Church, D., DiCuccio, M., Edgar, R., Federhen, S., Feolo, M., Geer, L., Helmberg, W., Kapustin, Y., Landsman, D., Lipman, D., Madden, T., Maglott, D., Miller, V., Mizrachi, I., Ostell, J., Pruitt, K., Schuler, G., Sequeira, E., Sherry, S., Shumway, M., Sirotkin, K., Souvorov, A., Starchenko, G., Tatusova, T., Wagner, L., Yaschenko, E., & Ye, J. (2009). Database resources of the National Center for Biotechnology Information Nucleic Acids Research, 37 (Database) DOI: 10.1093/nar/gkn741

XHTML Strict, XHTML Transitional ve XHTML Frameset Arasındaki Fark

fentanyl — Sat, 08 Aug 2009 23:32:05 +0000

Eğer web sitenizi hazırlarken web standartlarına uygun HTML kodu yazmak istiyorsanız HTML sayfanızın başına html dosya tipini ve hangi standarta göre html kodu yazdığınızı belirten bir kod eklemeniz gerekiyor. validator.w3.org gibi uyumluluk kontrolü yapan siteler bu koda bakarak html kodunuzun uyumluluğunu denetliyor… XHTML için üç adet DTD (Document Type Definition) var. Bu arada hala HTML 4.01 standartını da kullanabileceğinizi hatırlatmak istiyorum.

Üç adet XHTML DTD var. Peki ne gibi durumlarda hangisini kullanacağız ? Sizin için hangisi en uygun ?

XHTML Strict DTD (Sıkı XHTML)

XHTML Strict eğer standartlara uygun kod yazmak istiyorsanız ve sayfanıza görünüm vermek için CSS (Cascading Style Sheets) kodlarını kullanacaksanız bu tip sizin için. XHTML Strict DTD kullanacağınız HTML kodlarınızın başına eklemeniz gerek kod;

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd>

XHTML Transitional DTD (Geçiş XHTML)

XHTML Transitional DTD eğer standartlara uygun kod yazmak istiyorsanız ve XHTML’in görünüm yeniliklerini yani CSS’i kullanmayacaksanız. Örneğin <font> gibi html etiketlerini kullanıyorsanız bu tip sizin için uygun.

XHTML Strict <font> <u> gibi etiketleri desteklemez.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

XHTML Frameset DTD (Çerçeveli XHTML)

XHTML Frameset DTD eğer standartlara uygun bir kod yazmak istiyor ve sayfanız çerçeveli bir tasarıma sahip ise bu döküman tipini kullanmalısınız.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">

Kaynak :

http://webdefterim.net/viewtopic.php?f=9&t=153

Componentes burros

iguessimnotcrazy — Wed, 05 Aug 2009 00:18:28 +0000

A idéia

Título estranho para um texto que tende a ser pior ainda.. Este post é na verdade parte da compilação de uma de minhas pesquisas mais recentes para realização de um projeto arquitetural. Não almejo que em um post eu consiga explicar corretamente o que vem a ser esta idéia do então chamado Frankie (de Frankenstein, claro) como um todo mas como tudo tem que começar de alguma forma, vamos lá…

Burro, mas bem burro mesmo…

Fazem algumas semanas eu e um outro colega recebemos a atribuição de desenvolver um framework que inicialmente trataria apenas de mais um ORM com algumas diferenças básicas; Nesta primeira idéia, teriamos que criar além do ORM propriamente dito que seria responsável por gerar, e manter, o repositório de entidades mapeadas do banco de dados sempre atualizado.

Foi então que definimos uma atribuição extra interessante para este robô, que seria a de manter também atualizado um arquivo DTD baseado nas definições strict da W3C; Este passo do processo é muito interessante do ponto de vista da separação das camadas possibilitando ao designer ou seja lá quem for o responsável por desenvolver a UI (Template) uma visão clara da camada de dados sem precisar conhecer a mesma…

A idéia geral é baseada em uma única, simples e resumida idéia de que todos os componentes envolvidos em um dado processo devem ser completamente burros. Em suma, não deve existir qualquer tipo de conexão intelectual entre nenhum dos participantes do modelo arquitetural. Você pode até me dizer que esta é uma premissa antiga, mas te respondo que esta merda nunca é seguida a risca!

Uma forma simples de explicar esta implementação e as facilidades do DTD é dizendo que meu template tem que saber o que quer do banco de dados porém não deve de forma alguma se preocupar com como diabos estes dados estão sendo printados ali, quais os adapters, transações, processos, servidores, serviços, linguagens ou qualquer outra parafernalha envolvido neste fluxo.

Modelo Burro

No modelo acima, nenhum dos componentes possui qualquer conhecimento sobre o funcionamento ou mesmo localização dos demais objetos, porém, tem total conhecimento do que ele precisa para desempenhar o seu papel corretamente. Idealmente, poderiamos construir a Interface inteiramente apenas utilizando o HTML que foi utilizado para prototipar o sistema contanto que este HTML contenha instruções em sua marcação que indique a forma que o bind deverá ser realizado.

DTD trick

A história do DTD na arquitetura é bem simples, ao construir um template/protótipo/página html, o designer ou programador responsável por esta tarefa adicionaria o DTD com as entidades mapeadas do banco direto no código HTML que está sendo construindo, para que com isto, seja possível por exemplo um full intelissence das possibilidades de binding e formatos de exibição disponíveis, desprezando assim todo e qualquer conhecimento de negócio ou específico da tecnologia que está sendo aplicado na renderização do template e claro, no bind propriamente dito porém, adicionando esta funcionalidade ao artefato desde sua criação.

Este aproach permite também que, por exemplo, a linguagem base que é utilizada pela equipe seja alterada da noite para o dia sem alteração alguma de programação na UI. Ok, este não é um caso lá muito comum.. Isto se você não trabalha onde eu trabalho!

Como dito anteriormente, o DTD deve refletir as entidades e a visão relacional do banco de dados e ser atualizado com a mesma frequencia que qualquer outra entidade ou objeto Entity é alterado…

1 <!ENTITY % ProdutoS
2 ” (Produto. |
3 Produto.Nome |
4 Produto.Preco)”
5 >
6
7 <!ELEMENT label %Inline;>
8 <!ATTLIST label
9 %attrs;
10 for IDREF #IMPLIED
11 accesskey %Character; #IMPLIED
12 onfocus %Script; #IMPLIED
13 onblur %Script; #IMPLIED
14 datasource %ProdutoS; #IMPLIED
15 >

O script acima é um escopo do que poderia ser uma mapeamento em DTD da tabela de produtos, onde a mesma seria utilizada para preencher a propriedade “datasource” do objeto “label“.. No Visual Studio, o intellisense nos daria algo do tipo:

IntelliSense Custom DTD - Visual Studio 2008

Este artigo é parte dos pre-requisitos para um o artigo que tende a ser o principal do Blog. Frankie is coming soon, get ready!

Considerações finais

O python tem alguns modelos de template bem interessantes os quais recomendo ao menos a leitura das idéias do Genshi…

Mais em: http://wiki.python.org/moin/Templating

<!ENTITY % ProdutoS
” (Produto. |
Produto.Nome |
Produto.Preco)”
><!ELEMENT label %Inline;>
<!ATTLIST label
%attrs;
for         IDREF          #IMPLIED
accesskey   %Character;    #IMPLIED
onfocus     %Script;       #IMPLIED
onblur      %Script;       #IMPLIED
datasource %ProdutoS;      #IMPLIED
>

xml dtd

tahsin352 — Wed, 29 Jul 2009 09:20:00 +0000

Question:

What XML technology is used when you mix two different document types in a single XML document?

Answer:

1. Validators
2. DTD
DTD describes the document type definition of a xml document.
3. Transformations
4. Namespaces

More of a good trauma game!

mrpony — Wed, 22 Jul 2009 19:58:00 +0000

The Space Game 2 is out!

Cold Warning free download at Sound Cloud

coldwarning — Mon, 20 Jul 2009 16:47:31 +0000

DTD (2008 Re-work) by Cold Warning

Difference - DTD and XSD

javajee — Fri, 12 Jun 2009 04:20:38 +0000

Here are a number of differences. Some are not important, some

are real important and easy to understand, some are real important

and hard to understand. This list is not exhaustive.

DTD’s are not namespace aware.

DTD’s have #define, #include, and #ifdef — or, less C-oriented, the ability to define shorthand abbreviations, external content and some conditional parsing.

A DTD describes the entire XML document, a schema can define portions.

XSD has a type system.

XSD has a much richer language for describing what element or attribute

content “looks like.” This is related to the type system.

You can put a DTD inline into an XML document, you cannot do this with

XSD. This means DTD’s are more secure (you only have to protect one

bytestream — the xml/dtd — and not multiple).

The official definition of “valid XML” requires a DTD. Since this may

be impractical, if not impossible, you often have to settle for

schema-

Moved to my new blog at http://jeejava.blogspot.com/2009/06/difference-between-dtd-and-xsd.html

—–

javejee

"I survived a week with my Dad" Chapter 13

chellemc — Wed, 27 May 2009 18:01:26 +0000

check out and spend our last day in the world

We really should have gone to bed earlier! It’s after 8am and no one is moving. We still need to pack, undecorate the tree, and breakfast might be good – I’m hungry. After all of the obsessive planning with the Disney Dining Plan, DH & I have realized that we didn’t add it up right and we still have 3 Table Service credits left (2 of us, counting multiple times and we came up with the same wrong # every time) We also have 5 Counter Service credits and a whopping 13 snack credits left!!! Our thought last night was get a couple of Counter Service breakfasts from the bakery and then we’ll have lunch at DTD with the TS credits. Goofys Snack Co. will be a good place to “blow” our snack credits with stuff to take home. But first people need to get up and get moving!

Ok so that plan doesn’t seem to be working. We’re up, packed and manage to call Bell Services just before 11am (check out time). Breakfast is not going to happen. New plan, lunch with Table Service and Counter Service at Earl of Sandwich to take on the road with us. That could work . While DH loads/packs the truck, I take our tree to Bell Services to leave for the next family on the tree exchange. Hope they enjoy it as much as we did!

We head to Downtown Disney and it looks pretty busy. Lot 1 is closed already. We decided to park by Pleasure Island. We can have lunch at Planet Hollywood, walk to the Market Place and back to the car. Sounds like a plan! We walk into Planet Hollywood and are seated immediately. Allright, last big meal of the trip. We order the potato skins, Texas Tostados & the Spinach dip for our appetizers. We shared amongst the 4 of us. All were very good and easily big enough to have eaten as entrees. Our waitress told us there was only 1 item on the menu that wasn’t included on the DDP (I don’t remember what it was, but the price made it obvious-I think it was something for 2 people) Since DD had tried so many other foods during the week, she was ready for the Roasted Half Chicken w/mashed potatoes. DH had the LA Lasagna that he tried & loved in June. I figured what the heck, I had the 14 oz Ribeye. Mmmmm! It was perfectly cooked and delicious, but I couldn’t finish it. Not after the appetizers, and there was still dessert to order. DS had enjoyed our appetizers, and the kids pizza and didn’t have much room for dessert. Until he heard that there was a creme brulee on the menu. DH was pretty full, so he & DS shared the Banana Split Creme Brulee (they loved it, and ate every last bite!) DD & I both ordered the Double Chocolate Brownie sundae. Wow, so rich, so delicious! Ok, good thing we planned to walk to Market Place and shop. There’s no way I can get in the truck for a 8 hour drive right now!

Time to shop. DS still hasn’t figured out what to buy with the money my Dad gave him. He doesn’t want a new hat, he’s not into charater shirts, ok what? Maybe a coffee mug for cocoa? Nope, the only ones he likes are the super huge ones that he can barely pick up, so we keep looking. And looking! DS isn’t very good at making decisions (especially when it comes to spending his money) so we talk. Dad had wanted to buy him some pins, because he watched DS pin trade all week, but since Dad didn’t know anything about pins he thought money would be better. DH & I tell DS that we can probably order a bulk set of pins online, for a lot less money per pin and then he’d have lot’s of “traders”. That’s what we’ll do. Good, now I just grab a Baby Pooh Bear for my niece’s 1st Christmas present.

Now to kill off the food credits. We look at Earl of Sandwich, but we’re so full nothing is looking good or looking like it will travel well. We’ve heard some people say you can get a couple of snacks (like we really need more of those ) for 1 Counter Service, but Goofy’s Candy Co. says no. Each kid gets to pick out 1 snack, special for them. After a lot of thought (and time) they each decide on cotton candy. We ordered 4 create your own snacks (2 Mickey Rice Krispie treats & 2 fudge covered cookies) that’s 6 snacks, 7 more to go. We grab 3 boxes of cookies, 3 packages of lollipops and a chunk of fudge. That was a lot of work! We might have used more snack credits at the beginning of the trip, but I was afraid we’d run out of them. Boy was I wrong about that! What do we do with the Counter Servuce credits? I really don’t want to let them go to waste, so we decide to get out of the craziness of DTD and go to Artist Palette at Saratoga Springs Resort. It’s right around the corner from DTD, very convenient and they have great food. We end up getting 2 Turkey & Brie sandwiche combos, which come with chips, drink & dessert (really need more desserts ) 2 fruit plates, with all of the above & they let us make a “meal” out of a bagel, piece of fruit (got an orange), drink and of course, dessert. DH was very happy when he found out he could get his special Saratoga water as the drink, so we got 5 bottles of Saratoga water. We got 2 brownies & 3 cookies from the bakery section as the desserts.

Food gets loaded into the cooler, everyone gets buckled up and we leave Disney for our drive home (at 4pm yikes! we’ve spent 5 hours eating and shopping -mostly for food)

Next up, odds & ends and final thoughts

Registering local DTDs or XML schemas with NetBeans

sinewalker — Tue, 12 May 2009 00:27:55 +0000

The NetBeans online help describes the steps for registering a local DTD or XML file with NetBeans

Mapping Hierarchy to Table

hrachyag — Sat, 09 May 2009 13:24:49 +0000

XML and XSLT implementations are enclosed.

<?xml version=”1.0″ encoding=”UTF-8″?>


<!--
 Document   : organization02.xml
 Created on : December 10, 2008, 8:15 PM
 Author     : hrachya
 Description:
 Mapping a Hierarchy to a Table
-->

<?xml-stylesheet type="text/xsl" href="organization02.xsl"?>

<university name = "University of Antarctica">
 <provost> Dr. Morris Fishbine </provost>
 <college name = "Science">
 <dean> Dr. Bif Conway </dean>
 <department name = "Math">
 <faculty rank = "full" chair = "true">
 Dr. Wendy Coots
 </faculty>
 <faculty rank = "full"> Dr. Tina Anit </faculty>
 <faculty rank = "assoc"> Dr. Carl Noprol </faculty>
 <group name = "Logic and Methodology">
 <faculty rank = "asst"> Dr. Al Tarski </faculty>
 </group>
 </department>
 <department name = "Physics">
 <faculty rank = "full" chair = "true">
 Dr. Clerk Maxwell
 </faculty>
 <faculty rank = "asst"> Dr. Ralph Bigamy </faculty>
 <faculty rank = "assoc"> Dr. Cindy Blair </faculty>
 <faculty rank = "assoc"> Dr. Fred Astaire </faculty>
 </department>
 <department name = "Biology">
 <faculty rank = "full" chair = "true">
 Dr. Arnold Coop
 </faculty>
 <faculty rank = "full"> Dr. Wayne Newton </faculty>
 <faculty rank = "assoc"> Dr. Tim Bone </faculty>
 </department>
 </college>

 <college name = "Engineering">
 <dean> Dr. Andrew Awful </dean>
 <school name = "Computational Studies">
 <department name = "Computer Science">
 <faculty rank = "full" chair = "true">
 Dr. Eva Luator
 </faculty>
 <faculty rank = "full"> Dr. Hai Phuong</faculty>
 <faculty rank = "assoc"> Dr. Jose Barracho </faculty>
 </department>
 <department name = "Computer Engineering">
 <faculty rank = "full" chair = "true">
 Dr. Lew Sbolt
 </faculty>
 <faculty rank = "asst"> Dr. Nan Tucket</faculty>
 <faculty rank = "full"> Dr. Blaise pascal </faculty>
 </department>
 <department name = "Software Engineering">
 <faculty rank = "full" chair = "true">
 Dr. Sid Wong
 </faculty>
 <faculty rank = "asst"> Mr. Kent Beck </faculty>
 <faculty rank = "assoc"> Dr. Ray Rachett </faculty>
 </department>
 </school>
 <department name = "Electrical Engineering">
 <faculty rank = "full" chair = "true">
 Dr. Arf Barker
 </faculty>
 <faculty rank = "asst"> Mr. Sparks Mallone</faculty>
 <faculty rank = "assoc"> Dr. Carl LaFong </faculty>
 </department>
 <department name = "Structural Engineering">
 <faculty rank = "full" chair = "true">
 Dr. Hale Hoyle
 </faculty>
 <faculty rank = "asst"> Ms. Lois Lane</faculty>
 </department>
 </college>
 <college name = "Humanities">
 <dean> Dr. Slim Luckmann </dean>
 <department name = "History">
 <faculty rank = "full" chair = "true">
 Dr. Gil Snapon
 </faculty>
 <faculty rank = "asst"> Dr. Hugh Head </faculty>
 </department>
 <department name = "English">
 <faculty rank = "full" chair = "true">
 Dr. Sharon Rockman
 </faculty>
 <faculty rank = "asst"> Dr. Ernest Hemingway </faculty>
 </department>
 <department name = "Art">
 <faculty rank = "full" chair = "true">
 Dr. Pita Loaf
 </faculty>
 <faculty rank = "asst"> Ms. Barbara Painter </faculty>
 </department>
 </college>
</university>

<?xml version="1.0" encoding="UTF-8" ?>

<!--
 Document   : organization02.xsl
 Created on : December 10, 2008, 8:26 PM
 Author     : hrachya
 Description:
 Mapping a Hierarchy to a Table
-->

<xsl:stylesheet
 version="1.0"
 xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
 xmlns="http://www.w3.org/TR/REC-html40">

 <xsl:template match="university">
 <HTML>
 <HEAD>
 <TITLE>
 Hierarchy Test Variant2
 </TITLE>
 </HEAD>
 <BODY bgcolor="#f7ffee">

 <CENTER>
 <FONT size = "6" color="#blue">
 <B>
 Welcome to
 <xsl:value-of select="@name"/>
 </B>
 </FONT>
 </CENTER>

 <BR>
 <CENTER>
 <FONT size ="4" color="#blue">
 Provost:
 <xsl:value-of select="provost"/>
 </FONT>
 </CENTER>
 </BR>

 <BR>
 <CENTER>
 <FONT size ="4"  color="#blue">   
 We're proud of our
 <xsl:value-of select="count(//faculty)"/>
 Faculty Members
 </FONT>
 </CENTER>
 </BR>

 <CENTER>
 <TABLE  width ="50%" border ="4" BORDERCOLOR="#blue">
 <TR>
 <TH><FONT SIZE ="2"  COLOR="#blue">Name</FONT></TH>
 <TH><FONT SIZE ="2"  COLOR="#blue">Department</FONT></TH>
 <TH><FONT SIZE ="2"  COLOR="#blue">College</FONT></TH>
 <TH><FONT SIZE ="2"  COLOR="#blue">Rank</FONT></TH>
 </TR>
 <xsl:apply-templates select="//faculty"/>
 </TABLE>
 </CENTER>

 </BODY>
 </HTML>
 </xsl:template>
 <xsl:template match="faculty">

 <TR>
 <TD><CENTER><FONT size ="2"  color="#083174"><xsl:value-of select="."/></FONT></CENTER></TD>
 <TD><CENTER><FONT size ="2"  color="#083174"><xsl:value-of select="./ancestor::department/@name"/></FONT></CENTER></TD>
 <TD><CENTER><FONT size ="2"  color="#083174"><xsl:value-of select="./ancestor::college/@name"/></FONT></CENTER></TD>
 <TD><CENTER><FONT size ="2"  color="#083174"><xsl:value-of select="./@rank"/></FONT></CENTER></TD>
 </TR>

 </xsl:template>

</xsl:stylesheet>

Lies, Damn Lies & MSDN Documentation

corrywht — Sat, 04 Apr 2009 02:27:54 +0000

The MSDN documentation for XmlDocument.LoadXml() states “This method does not do DTD or Schema validation. If you want validation to occur, use the Load method and pass it an XmlValidatingReader. See XmlDocument for an example of load-time validation”. As it turns out, this is only a half-truth.

If you happen to be dealing with XHTML (or any other standard that has a publicly accessible DTD), then you’ll most likely have a DOCTYPE declaration at the top of the document, like

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

However, if you try to load an XHTML document containing the DOCTYPE declaration into an XmlDocument object using LoadXml(), the underlying XmlTextReader will try to resolve the URIs in the DOCTYPE. This is usually fine in a development environment, but can cause major headaches when working in a restricted production environment, where, for example, the Web severs cannot access the Internet in general, or the W3C site in particular.

So, what do to?

Well, you have two options:

1. Set the XmlResolver object in the XmlDocument to null, i.e.

XmlDocument xdXhtmlContent = new XmlDocument();
xdXhtmlContent.XmlResolver = null;

2. Copy the DTD(s) locally and create your own XmlUrlResolver that overrides the URI for them (e.g. to a local path):

public class FileSystemDTDUriResolver : XmlUrlResolver
{
/// <summary>
/// Resolves the absolute URI from the base and relative URIs.
/// </summary>
/// <param name="baseUri">The base URI used to resolve the relative URI.</param>
/// <param name="relativeUri">The URI to resolve. The URI can be absolute or relative. If absolute, this value effectively replaces the baseUri value. If relative, it combines with the baseUri to make an absolute URI.</param>
/// <returns></returns>
/// <remarks>The baseUri and relativeUri are given to match the method signature of XmlUrlResolver. However, for the purpose of an XmlDocument's XmlResolver, the Uri cannot be relative.</remarks>
public override Uri ResolveUri(Uri baseUri, string relativeUri)
{
if (relativeUri.ToLower().EndsWith(".dtd"))
{
string sRequestedDtd = relativeUri.Substring(relativeUri.LastIndexOf('/')).TrimStart('/');
string sDTDFilesLocation = ConfigurationManager.AppSettings["DTDFileSystemLocation"].Replace('\\', '/');    //C:\Webfiles\w3xml\DTD\
if (sDTDFilesLocation.LastIndexOf('/') != sDTDFilesLocation.Length - 1)
{
sDTDFilesLocation += "/";
}
return new Uri("file:///" + sDTDFilesLocation + sRequestedDtd);
}
return base.ResolveUri(baseUri, relativeUri);
}
}

Then set the XmlResolver as:

xdXhtmlContent.XmlResolver = new FileSystemDTDUriResolver();

One thing to note about this approach is that you cannot use a relative Uri with the XmlResolver, so you can either specify a file system path (using file:///) or (if you modify the sample code slightly) an absolute local URL, e.g. http://localhost/w3xml/DTD/