Content in XML and Schema as DTD

In this assignment, the scenario created in the first assignment is used to create some content in XML, and to describe the schema constraining this content with a DTD. In order to test the DTD (and to make sure that it works reasonably well for the content you want to manage), create at least three entries that have some variety in the way how they use the DTD. Here are the requirements for this assignment, please make sure your XML/DTD satisfies all of them:

• There need to be at least three Flickr images (added to the XML2011 group) that are used as the starting point for the entries. If you use images other than your own, make sure that you are not violating any copyright.
• For each Flickr image, there has to be an entry about that image (depending on your scenario).
• For the entry content, there is the structure you proposed in assignment 1, and each of the entries should have a slightly different structure (repeating repeatable elements, omitting omittable elements, using different classification/categorization of content).
• There has to be at least one cross-reference in the content where one of the entries points to another entry.
• Your DTD should use some comments to describe the elements it defines so that it is mildly self-documenting.
• Your DTD should use parameter entities where appropriate, for example for attributes that contain certain data types.
• The DTD must be associated with the XML and the XML must validate against the DTD.

Even though this is not required for submission, it is very helpful if you think about how you envision you XML being rendered as a formatted document. We will use HTML for this, but most importantly, the question is: How will the XML be transformed into content that is useful for a person to read, adding things such as human-readable dates, pulling in image thumbnails, adding clickable links to other entries or outside resources, and creating a navigable structure for all entries that will still work when there are dozens of entries over a period of months or even years. Content management is very important, but in the end it is just a method to manage content so that it can be published, and the sooner you think about what publication should look like, the easier it will be to understand what you need in your XML to drive the publishing process.

Please send a brief outline of what you have created, along with the actual data in XML and the associated DTD, to yliu@ischool.berkeley.edu. Please send plain text email with the XML and DTD files as attachments. HTML emails will not be accepted.