Monday, November 7, 2011

Muddiest Point for XML

Can XML or its stylesheets be used to specify display order? So, say I always want my data to display in this order:
<unitid>LIS 2600</unitid>
<title>Introduction to IT</title>
<date>November 7, 2011</date>
<subject>Muddiest Point for XML</subject>

Is there any code (or whatever) I can add to force it to display as such despite that it was entered it in a different order? Say for instance:
<title>Introduction to IT</title>
<unitid>LIS 2600</unitid>
<subject>Muddiest Point for XML</subject>
<date>November 7, 2011</date>

Or will it just not parse correctly? If that's the case, is there a way to automatically rearrange my tags and their text?

Digital Libraries Readings


Andreas Paepcke, et al, “Dewey Meets Turing”

Are Google’s original algorithms really derived from DLI? Where’s the reference?
There isn’t enough background to understand what’s going on in this article. It precludes an advanced understanding of DLI. For instance, what do publishers have to do with anything? I thought it was an NSF project.

           
William H. Mischo, “Digital Libraries: Challenges and Influential Work”

Oops. I guess I needed to read this first before “Dewey Meets Turing.” Now everything makes slightly more sense except the software companies. If you already have a fleet of computer scientists used to building things from the ground up (as “Dewey Meets Turing” mentions) what added value did restricting the final product add? Especially if you were just going to have to use government funds again to buy it back.

Clifford A. Lynch, “Institutional Repositories: Essential Infrastructure for Scholarship in the Digital Age”

Are institutional repositories not succeeding because of policy, management failure, or technical problems? It doesn’t seem like it, at least not in the way Lynch means it. Instead, the problem seems to be that the old system works for faculty, and therefore if it works why fix it? They have no incentive to use an IR. Publishing occurs for a variety of reasons and only one of them is accessibility. The others like prestige, job promotion, and other concerns are equally important issues to address. Lynch has got all the technological bases covered, but misses the human element of getting people to use IRs.

Monday, October 31, 2011

Muddiest Point for CSS lecture

Nothing too confusing this week. It was nice to go over everything twice in class and lab.

XML Readings


“An Introduction to the Extensible Markup Language (XML)”
by Martin Bryan of The SGML Centre

You never hear about SGML anymore, does it still exist or is it still relevant?
So, beyond the fact that XML allows you to compound documents, it lets you identify where digital objects appear, how they are controlled, as well as add metadata to a file. It isn’t however a set of tags like HTML, but a way of using tags predefined by some type of governing body.
I get how you define attributes and tags, but where do definitions live? That must be the processing instructions and hyperlink to a document type declaration.

“Extending Your Markup,” Andre Bergholz
SGML is what lets you write define the structure.
Is what was described in the previous article DTD or schema?
The stylesheet sounds pretty interesting – follow up on it.

“A survey of XML standards: Part 1,” Uche Ogbuji

Catalogs: instructions for how an XML processor revolves entity identifiers into documents.
Namespaces: a mechanism for universal element and attribute naming. Can be identical to another language if you define it differently here.
Base: associates elements with UROs
Inclusions (XInclude): a system to merge XML documents.
Inforset: a way of describing objects with special properties.
Pointer: defines a language that can be used to refer to fragments of an XML document.
XLink: framework for expressing links in XML
Relax NG vs. W3C XML Schema vs. Schematron: Competing schemas, who won?

W3C Schema tutorial
A tutorial on schemas from W3C, nuff’ said.