[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
EDUML v0.4 (already!)
EDUML (XML) v0.4 (dec 11 1998)
------------------------------
changes since v0.3
+ <contact> tags everywhere; suggested by Duane Morin <dmorin@tiac.net>
+ <pronounce> tag suggested by Michael A Hamblin <michaelh@utdallas.edu>
+ <catalogue_code> and <edu:library> by Doug Loss <dloss@csrlink.net>
+ given, alias and family names are now details of <name> tag
+ course subscription is now a detail of optional course mailing list
+ added <stakeholder> for learner's parents/guardians/etc... contact
suggested by Tim Wilson <wilson@chemsun.chem.umn.edu>
+ symmetric structure and tag-names improved (<name> instead of <label>)
+ I hope I did not miss anyone ... I am really rushing this.
thanks to all for you quick and useful responses
question: should we use esperanto for tag names? (I'm thinking Mexico and
France would feel more at home with international looking tags); If so,
does anyone know enough esperanto to help me with the translation?
question: do librarians all use the cataloguing code as the unique resource
id for their resources? in which case I can eleminate redundancy.
<!doctype xml v1.0>
<edu:school id="unique-school-id-code, can be a home">
<name> Formal School Name </name>
<contact>
<snail> post office address goes here </snail>
<fax> fax number </fax>
<phone> phone number </phone>
<email> postmaster@school </email>
<uri> website for the school </uri>
</contact>
<learner id="unique-learner-id-in-this-school">
<name>
<given> Formal Given Name </given>
<alias> Informal Aliases </alias>
<middle> middle names </middle>
<family> Family Name </family>
<pronounce> phonetic spelling for substitutes </pronounce>
</name>
<contact>
<email> learner@email </email>
<snail> post office address goes here </snail>
<uri> URL of portfolio webpage </uri>
<style> learning style and preferences keywords </style>
<phone> phone number </phone>
<fax> fax number </fax>
</contact>
<stakeholder>
<name> name tags of parents/guardians/other stakeholder </name>
<contact>
<snail> land address </snail>
<phone> phone number </phone>
<email> stakeholder's email </email>
</contact>
</stakeholder>
<course id="unique-course-id-at-this-school">
<start> date learner started this course </start>
<attend id="particular date of attendance">
<status> absent, present, late, sick ... </status>
<comment> anecdote about this session </comment>
<duration> time spent during session </duration>
<lesson id="issuer:unique lesson identifier">
<comment> anecdote about this lesson </comment>
</lesson>
<test id="issuer:unique assessment identifier">
<scale> performance coding system used </scale>
<score> performance code </score>
<marker> marker's id </marker>
<comment> anecdote about this assessment </comment>
</test>
</attend>
<end> date course ends </end>
</course>
</learner>
<course id="unique course-id">
<name> Course Name </name>
<mentor> teacher, instructor, mentor unique id </mentor>
<contact>
<room> room, or virtual room where learners meet </room>
<email> course mailing list (if any)
<subscribe> email subscription address </subscribe>
</email>
</contact>
</course>
<room id="unique room id">
<name> label or name </name>
<contact>
words or tags to describe location
</contact>
<schedule>
<course id="unique course-id"> time slot </course>
</schedule>
</room>
</edu:school>
<--! assessment -------------------------------------------------->
<edu:issuer id="bruno">
<name> formal name of issuer </name>
<contact>
<email> issuer's email </email>
<snail> issuer's address </snail>
<uri> issuer's website </uri>
</contact>
<plo id="unique id for this issuer's prescribed learning outcome">
<plo id="issuer:unique id"> prerequisite or composite </plo>
<name> formal description for this PLO </name>
<alias> historical plo aliases for smooth transitions </alias>
<test id="unique assessment id (marked activity)">
<item type="mult. choice, short ans., mathching, t/f, assign, lab, ...">
<style> learning style + preferences keywords </style>
<listref> URI for reference list </listref>
<list> actual list typed in here </list>
<script id="unique prog. language id" library="URI for library">
question + instructions + loads reference lists;
randomize as much as possible based on lists;
code snippet that displays question, accepts input,
checks answer + scale matrix, provides score.
</script>
</item>
</test>
<lesson id="unique lesson id (un-marked activity)">
<item type="self-assignment, reading, self-lab, etc... >
<style> learning style code </style>
<script id="unique prog. language" library="URI for library">
code snippet for interactive lesson, or browser call or
just a plain paragraph that says "read p.310 of textbook"
</script>
</item>
</lesson>
</plo>
</edu:issuer>
<--! library catalog --------------------------------------------->
<edu:library id="unique library code">
<catalogue_system> dewey, Lib of Congress, etc... </catalogue_system>
<item id="resource-id">
<catalogue_code> dewey or Lib of Congress code </catalogue_code>
<title>resource title</title>
<author> author 1 </author>
<subtitle> section 1 </subtitle>
<date> date </date>
<cost> $ </cost>
<isbn> 123456789 </isbn>
<pub> publisher </pub>
<notes> notes </notes>
<loan>
<learner> learner-id from edu:school data </learner>
<start> date </start>
<duration> 3 weeks </duration>
<overdue> date first overdue sent </overdue>
<end> date returned </start>
</loan>
<item>
</edu:library>
NOTES
-----
0. I chose not to be fancy nor particularly politically correct (in exchange
for brevity; for example "test" instead of "assessment") with the tags. I
am keenly aware that there is educational stuff going on that need not
and does not want to be monitored, assessed or otherwise recorded in
databases. EDUML is only for those activities needing/wanting some sort
of certification, validation or simply being kept track of.
1. The XML data can be spread out over many files in various locations;
merging them all would provides the complete picture. But we are not
advocating a single (Big-Brother-ish) planetary database of unique
learner IDs.
2. XML here acts like a relational database and it can be structured in many
ways. I hope EDUML is arranged in natural groupings (the identations are
really relations) ... keeping the whole thing as simple as reality
allows. For example, the school grouping contains students rather than
the other way around because it is probably simpler to imagine.
3. Once this is approved, constructing a validating DTD would be nice: Most
tags can be repeated as needed; I show only one of each type here in
order to keep this document email-sized. Most tags are not mandatory.
4. Please send in proposed structural corrections, or renaming of tags or
suggest completely different XML proposals for education. I suggest we
check our existing admin and educational software export fields to make
sure the important ones are included here.
5. The core material requires something like /usr/lib/edu filled with
educational functions/methods in various programming languages for use
by the code snippets ... which in my significant experience with writing
testing programs is the most open-ended and creative way of dealing with
the classic problem of how to store question/answers. note: simple plain
question/answer pairs can be handled by lists (arrays) or via the simplest
function/method in the chosen language; just display parameter1 and compare
to parameter 2. I'll gladly expound on this if anyone lets me :-)