COAP:COAP-2180/week3: Difference between revisions

The educational technology and digital learning wiki
Jump to navigation Jump to search
mNo edit summary
 
(22 intermediate revisions by the same user not shown)
Line 1: Line 1:
=== Week 3 [[Help:COAP-2180|COAP 2180]] ===
== Week 3 Summary [[Help:COAP-2180|COAP 2180]] ==


(''' under construction ''')
On week three you will finish learning how to create your own simple DTD:
 
On week three you will learn how to create your own DTDs:
* Defining an '''information architecture''' (sketching out elements and attributes)
* Defining an '''information architecture''' (sketching out elements and attributes)
* Defining DTD '''rules for elements and attributes'''
* Defining DTD '''rules for elements and attributes'''
Line 9: Line 7:
This homework can be a prototype for a part of your term project.
This homework can be a prototype for a part of your term project.


==== Teaching materials ====
== Teaching materials ==
 
''' [[Tour de XML]]'''
(This week: [[BPMN_1.2_tutorial|BPMN]])


; [[Tour de XML]] (This week: to be announced)
'''Defining a DTD'''


; Defining a DTD
* [[DTD tutorial]] (wiki lecture notes)
* [[DTD tutorial]] (wiki lecture notes)
* [http://tecfa.unige.ch/guides/te/files/xml-dtd.pdf xml-dtd.pdf] (slides)
* [http://tecfa.unige.ch/guides/te/files/xml-dtd.pdf xml-dtd.pdf] (slides)


; Examples files (same as before)
'''Using XML Exchanger'''
* After each DTD changer close/reopen the XML file.
* Read [[Exchanger XML Editor]], if needed.
 
'''Examples files (same as before)'''
 
* [http://tecfa.unige.ch/guides/xml/examples/dtd-examples/ DTD and XML templates example directory]
* [http://tecfa.unige.ch/guides/xml/examples/dtd-examples/ DTD and XML templates example directory]


; Textbook chapters  
'''Textbook chapters'''
 
If you find that my lecture notes and slides are incomplete, too short or not good enough, reading '''either one or both texts''' is '''mandatory''' !
If you find that my lecture notes and slides are incomplete, too short or not good enough, reading '''either one or both texts''' is '''mandatory''' !
* ''XML in a Nutshell'', Chapter 3 Document Type Definitions (start here)
* ''XML in a Nutshell'', Chapter 3 Document Type Definitions (start here)
Line 30: Line 36:
* [[:Category:XML|XML Category]] (All XML-related articles in this wiki)
* [[:Category:XML|XML Category]] (All XML-related articles in this wiki)
* [http://en.wikipedia.org/wiki/Xml XML] (on Wikipedia)
* [http://en.wikipedia.org/wiki/Xml XML] (on Wikipedia)
* Mix in some XHTML: See [http://tecfa.unige.ch/guides/xml/examples/composites/xml_plus_xhtml.xml this example]. You then must declare these tags in your DTD using the same prefix as in the XML file.
<source lang="XML">
<!ELEMENT xhtml:img EMPTY>
<!ATTLIST xhtml:img src CDATA #REQUIRED>
</source>


==== Homework 3 - Week 3 ====
== Homework 3 - Week 3 ==


'''Task'''
'''Task'''


Create a DTD and create an associated XML test file.
Create a DTD and create an associated XML test file.
* Your DTD should be somewhat text-centric (i.e. be meant for creating documents that can be displayed as a web page with CSS or XSLT)
* Your DTD should be somewhat text-centric (i.e. be meant for creating documents that can be displayed in some way)
* You can decide the purpose of the DTD (document types you wish to model), but it's best to discuss it in class on Monday and/or Wednesday
* You can define the purpose of the DTD you wish to model, but it's best to discuss your plans in class.
: I strongly suggest to think about a study area you are interested and model for example a process, a typical document class, a description of a class of artifacts, etc. Avoid lists of CDs, cars, etc.
: I strongly suggest to consider a study area you are interested in, and to model for example a process, a document genre, a description of a class of artifacts, etc. Avoid lists of CDs, cars, etc.
: If you reuse elements from an other DTD, please tell so (in the comments of the DTD). '''Plagiarism will be punished''', but '''documented reuse''' of elements from an existed DTD or even inclusion of a whole DTD is just fine !
: If you reuse elements from an other DTD, please tell so (in the comments of the DTD). '''Plagiarism will be punished''', but '''documented reuse''' of elements from an existing DTD or even inclusion of a whole DTD (e.g. for formatting) is just fine !


Tips:  
Tips:  
* Take into account that you will be able reuse this DTD in most follow-up projects, including the term project !!
* Take into account that you may reuse this DTD in most follow-up projects, including the term project !!
* Do not attempt to define a too simple DTD (lists) or a very complex one.
* Do not attempt to define a too simple DTD (lists) or a very complex one. Make it both interesting and reasonable.
* Do '''not worry''' about rendering (display). It will be done in homework 4. In week 4/5 you will learn how to add information to a text, e.g. if you have an <nowiki>adress>Mr. X., 1 Cool st., Geneva</address></nowiki> you'll be able to make the result look like: ''Private Address''': Mr X. ,......^''. In other words: '''Think about data''', not display !
* Do '''not worry''' about rendering (display). It will be done in homework 4. In week 4/5 you will learn how to add information to a text, e.g. if you have an element like:
<nowiki><adress>Mr. X., 1 Cool st., Geneva</address></nowiki>
you will be able to make the result look like: ''Private Address''': Mr X. ,......''. In other words: '''Think about data''', not display !
 
'''Use of the xngr editor'''
* The editor reads the DTD when you load the XML file. This implies that you will have to define a skeleton before you can actually use/test the DTD. E.g.
<source lang="XML">
<?xml version="1.0"?>
<!DOCTYPE cd-list SYSTEM "cd-list.dtd">
 
<cd-list>
</cd-list>
</source>
This also implies, that you will have to close the XML file and to reload it after making changes to the DTD.


'''Deadline and submission:'''
'''Deadline and submission:'''
* '''Monday week 4''' (before start of class)
* '''<span style="color:red">Monday week 4</span>''' (<span style="color:green">before 9h</span>)
* Use the world classroom: https://webster.blackboard.edu/
* Use the world classroom
* Submit the *.dtd plus the *.xml test files and an optional report file (see below)
* Submit the *.dtd plus the *.xml test files and an optional report file (see below)


'''Evaluation criteria (roughly)'''
'''Evaluation criteria'''
 
Consult the evaluation grid in the world classroom for details !


''Work considered as weak:''
''Work considered as weak:''
* Correct DTD that contains at least 5 elements that you invented yourself and a somewhat valid XML example file
* Correct DTD that contains at least 5 elements that you invented yourself and a somewhat valid XML example file


''Work considered as minimalistic:''
''Work considered as minimalist:''
* A correct DTD that fits a purpose (including a valid XML example file)
* A correct small DTD that fits a purpose (including a valid XML example file)


''Good work may include one or several of the following
''Good work may include one or several of the following
* Inserted comments <!-- ... --> in the DTD and that explains the purpose of the DTD, the purpose of each elements, authorship, date, etc.
* Inserted comments <!-- ... --> in the DTD and that explains the purpose of the DTD, the purpose of each element, authorship, date, etc.
* A DTD that is "interesting" and useful for a given domain, e.g. it should include more than just 5 elements, either yours or elements that found in other DTDs.
* A DTD that is "interesting" and useful for a given domain, e.g. it should include more than just 5 elements
* Use of attributes
* Use of attributes
* Use of entities
* Use of entities
* A DTD that is more complex than a simple table (e.g. contains recursive elements)
* A DTD that is more complex than a simple table (e.g. one that contains recursive elements or links)
* A good XML example that uses all elements more than once (i.e. you do information architecture testing)
* A good XML example that uses all elements more than once (i.e. you do information architecture testing)


''Excellent work (A-) includes in addition''
''Excellent work (A-) includes in addition''
* A 1-2 page report that discusses your information architecture (the DTD structure) and results (what do you think of it, how could you improve it, etc.)
* A 1-2 page report that discusses your information architecture (the DTD structure) and results (what do you think of it, how could you improve it, etc.). You may include this report as "comment" in the DTD.


''Brilliant work (A)
''Brilliant work (A)
* Does all of the above, i.e. produces a DTD that could be used for real plus a good documentation.
* Does most of the above, i.e. produces a DTD that could be used for real plus a decent documentation.

Latest revision as of 08:40, 5 April 2017

Week 3 Summary COAP 2180

On week three you will finish learning how to create your own simple DTD:

  • Defining an information architecture (sketching out elements and attributes)
  • Defining DTD rules for elements and attributes

This homework can be a prototype for a part of your term project.

Teaching materials

Tour de XML (This week: BPMN)

Defining a DTD

Using XML Exchanger

Examples files (same as before)

Textbook chapters

If you find that my lecture notes and slides are incomplete, too short or not good enough, reading either one or both texts is mandatory !

  • XML in a Nutshell, Chapter 3 Document Type Definitions (start here)
  • Learning XML, Chapter 4 Quality Control with Schemas (additional reading)

These chapters are available through the world classroom.

For the adventurous
  • XML Category (All XML-related articles in this wiki)
  • XML (on Wikipedia)
  • Mix in some XHTML: See this example. You then must declare these tags in your DTD using the same prefix as in the XML file.
<!ELEMENT xhtml:img EMPTY>
<!ATTLIST xhtml:img src CDATA #REQUIRED>

Homework 3 - Week 3

Task

Create a DTD and create an associated XML test file.

  • Your DTD should be somewhat text-centric (i.e. be meant for creating documents that can be displayed in some way)
  • You can define the purpose of the DTD you wish to model, but it's best to discuss your plans in class.
I strongly suggest to consider a study area you are interested in, and to model for example a process, a document genre, a description of a class of artifacts, etc. Avoid lists of CDs, cars, etc.
If you reuse elements from an other DTD, please tell so (in the comments of the DTD). Plagiarism will be punished, but documented reuse of elements from an existing DTD or even inclusion of a whole DTD (e.g. for formatting) is just fine !

Tips:

  • Take into account that you may reuse this DTD in most follow-up projects, including the term project !!
  • Do not attempt to define a too simple DTD (lists) or a very complex one. Make it both interesting and reasonable.
  • Do not worry about rendering (display). It will be done in homework 4. In week 4/5 you will learn how to add information to a text, e.g. if you have an element like:
<adress>Mr. X., 1 Cool st., Geneva</address>

you will be able to make the result look like: Private Address: Mr X. ,....... In other words: Think about data, not display !

Use of the xngr editor

  • The editor reads the DTD when you load the XML file. This implies that you will have to define a skeleton before you can actually use/test the DTD. E.g.
<?xml version="1.0"?>
<!DOCTYPE cd-list SYSTEM "cd-list.dtd">

<cd-list>
	
</cd-list>

This also implies, that you will have to close the XML file and to reload it after making changes to the DTD.

Deadline and submission:

  • Monday week 4 (before 9h)
  • Use the world classroom
  • Submit the *.dtd plus the *.xml test files and an optional report file (see below)

Evaluation criteria

Consult the evaluation grid in the world classroom for details !

Work considered as weak:

  • Correct DTD that contains at least 5 elements that you invented yourself and a somewhat valid XML example file

Work considered as minimalist:

  • A correct small DTD that fits a purpose (including a valid XML example file)

Good work may include one or several of the following

  • Inserted comments in the DTD and that explains the purpose of the DTD, the purpose of each element, authorship, date, etc.
  • A DTD that is "interesting" and useful for a given domain, e.g. it should include more than just 5 elements
  • Use of attributes
  • Use of entities
  • A DTD that is more complex than a simple table (e.g. one that contains recursive elements or links)
  • A good XML example that uses all elements more than once (i.e. you do information architecture testing)

Excellent work (A-) includes in addition

  • A 1-2 page report that discusses your information architecture (the DTD structure) and results (what do you think of it, how could you improve it, etc.). You may include this report as "comment" in the DTD.

Brilliant work (A)

  • Does most of the above, i.e. produces a DTD that could be used for real plus a decent documentation.