Connexions Tutorial and Reference Á Ã 1 ü - Chinese)

Connexions Tutorial and Reference(Á%Ã¨�1ü - Chinese)

Collection Editors:Brent Hendricks

Adan GalvanMark Husband

Wei-Cheng Wong

Connexions Tutorial and Reference(Á%Ã¨�1ü - Chinese)

Collection Editors:Brent Hendricks

Adan GalvanMark Husband

Wei-Cheng Wong

Authors:

Elizabeth BartmessChuck Bearden

ConnexionsSarah CoppinAdan Galvan

Brent HendricksMark Husband

Ricardo Radaelli-SanchezCharlet ReedstromWei-Cheng Wong

Online:< http://cnx.org/content/col10340/1.2/ >

C O N N E X I O N S

Rice University, Houston, Texas

This selection and arrangement of content as a collection is copyrighted by Wei-Cheng Wong. It is licensed under

the Creative Commons Attribution 2.0 license (http://creativecommons.org/licenses/by/2.0/).

Collection structure revised: March 9, 2006

PDF generated: October 26, 2012

For copyright and attribution information for the modules contained in this collection, see p. 124.

Table of Contents

1 Connexions °y

1.1 Connexions ó� . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 `¨ Connexions �¾9& . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 B Connexions Ü¦ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 Connexions ¿ê� . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Connexions ì�¿

2.1 ì�¿Ã¨ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Ü¦[U+5167]MAØ{-�

3.1 Ø{�É . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 ô\³Xz1A[� . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.3 A[øç . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.4 [U+589E]`<1²�b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.5 ly§ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.6 m{A[ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4 XML � CNXML

4.1 XML Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.2 Combining XML Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.3 The Basic CNXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.4 The Intermediate CNXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.5 The Advanced CNXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774.6 CNXML Reference Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

5 3;{ÝX½�

5.1 Content MathML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875.2 QML 1.0 tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

6 A[ XML

6.1 Editing CNXML with Altova's Authentic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1056.2 Using Mathematica to Output MathML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

7 ü[U+9304]

7.1 z1MÅ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077.2 Grilling a Good Steak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087.3 Grilling a Better Steak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097.4 Grilling the Best Steak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137.5 Example module for use of cnxml/mathml tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Attributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

iv

Available for free at Connexions <http://cnx.org/content/col10340/1.2>

Chapter 1

Connexions °y

1.1 Connexions ó�1

warning: This module contains Connexions documentation which is out-of-date. The contents ofthis module are provided here for historical purposes only and should not be considered accu-rate for the current version of the Connexions website. The current (English-language) version ofthis module can be located at http://cnx.org/content/m10884/latest/2. If you have any additionalquestions or cannot �nd the answer to your question, please contact [email protected] and wewill be happy to assist in any way we can.

If you would like to assist Connexions by helping us update this module with an appropriate trans-lation from the current English version, please contact us at [email protected] as we would appreciateyour help with improving our support for non-English-speaking users.

1.1.1 °B

ConnexionshºÊÊ�w�Ü¦,¶Í�«ÿìºIâA%bm��"�B��Connexions^7¿��:ContentCommonsÜ¦É»�ª�5i4:@Ü¦,òå²Ø�,¶m��"��51:@Ü¦�ConnexionsAþ{�3ìo��A¨@5

,i±lConnexions<4ê,5About6(ó6)Ç×Y��¦ºé,Connexions Jºa«�Ü¦»¦�{áO,«�ô:�X,z1Ã¨��A[�a«º÷\ÊÊ�A¥K�:@Ü¦�Connexions,¶ñ¢�¦iÜ�Aå²Ø�[U+5E6B]�Sy��z1Ã¨��A[��"�:@Ü9Ü[U+7522],�´�,¨©ú«��Ó�ÊÊ�%,�4:@A~ok�~³XCreative

Commons Attribution license6 (îXCC)AAça�ConnexionsA³X�Í}ê4�8�Å:

• Students Sy � ³XConnexionsl¿ê51Ü9,«�¨zÝ�• Authors A[� � )óÜ¦ÕConnexions�,3%b2ùeºmodulesøç�• Instructors z1Ã¨� � m�z1,z1h®Í�¸#�A,ióAøç%bå^lÍf�

l[U+60A8]¦º³XConnexionsB�Ï,[U+60A8]wµ�[U+67E5][U+60A8]h�Q4�4»^Aå²,�¨[U+95B1]Connexions�+¦[U+555F]Ã¨7

,««�[U+60A8]�D^Aå²,«�[U+67E5]Yå^«½�[U+60A8]Yiå²�

1This content is available online at <http://cnx.org/content/m13477/1.3/>.2"Introduction to Connexions" <http://cnx.org/content/m10884/latest/>[email protected]@cnx.org5http://cnx.rice.edu/aboutus/tour/6http://creativecommons.org/licenses/by/2.0/7http://cnx.org/help/qstart/


1

2 CHAPTER 1. CONNEXIONS °y

1.1.2 Connexions <4

Connexions<4 (Figure 1.1)h[U+60A8]³XConnexions�¦ºAªj,74YØÁ�:

• <4�ó6�Ü¦�å²��R� (Section 1.1.2.1: <4�ó6�Ü¦�å²��R�)• ¨@Ø (Section 1.1.2.2: ¨@Ø)• Â5 (Section 1.1.2.3: Â5)• �+¦[U+555F] (Section 1.1.2.4: �+¦[U+555F]å^)• z1 (Section 1.1.2.5: z1å^)• �0Ø�Ø (Section 1.1.2.6: Personal Toolbar �0Ø�Ø)• ¨@�× (Section 1.1.2.7: Navigation ¨@�×)• gó�× (Section 1.1.2.8: Log in gó�×)• ó6�× (Section 1.1.2.9: Spotlight ó6�×)• \½@��× (Section 1.1.2.10: e-Mailbag \½@��×)• �&�× (Section 1.1.2.11: What's New �&�×)• Ø{/�× (Section 1.1.2.12: Workspaces Ø{/�×)

:@��w�l3;Connexionsÿ4ê�

Figure 1.1: Connexions <4�


3

1.1.2.1 <4�ó6�Ü¦�å²��R�

Connexions<4Eêj4Home<4�Aboutó6�ContentÜ¦�Softwareå²��HelpR��Ç×,�U[U+64CA]:@Ç×,«^ñYØConnexionsAÁÿ4:

• <48 ,��Connexions<4�• ó69 ,^7ConnexionsA°��×,«�ó6ConnexionsèáfAÍ@å^,^âô\þ{�¶¶0Ø��ã[U+7E6B]jù�• Ü¦,^ñøçØÌ�z1ØÌ,a«�:Çg�A[�� ó�å®�ÌØwu�• å²10 ,^ñ5Connexions Technology6(ConnexionsrxÄ&),^7Connexionså²�Ø�Aóå^�• R�11 ,^ñó6£��1üÜ¦��4ó6ConnexionsA gÜ9Aóå^�

1.1.2.2 ¨@Ø

5You are here6([U+60A8]l:)A¨@Ø(Breadcrumb navigation bar) (Fig-ure 1.2)lHome<4�Aboutó6�ContentÜ¦�Softwareå²��HelpR�Ç×Yj�£[U+60A8]-óConnexions¶�lAÍ�4õé,¨@Øh[U+60A8]¶�^ñAConnexions4õAg�,[U+60A8]a«�:U[U+64CA]¨@Ø�A÷\ÍÜ«��µ4õ�k6lØ{%ç�-�Á��AØ{¶,:Ê�k6a«��Ø{%çÇ�4õh£4XA�

Figure 1.2: Breadcrumb navigation bar ¨@Ø�

1.1.2.3 Â5

[U+60A8]a«³XConnexions<4åêjASearchÂ5¥��%åjÅ,lContent Com-monsÜ¦É»�ª�Â5¸#Aøç z1��lÂ5%åjÅ��óçe�ó�å�z1Çg�øçÇg�å� �bIDA�,/U[U+64CA]SearchÂ5¥�,Connexionsi^ñó�[U+60A8]�)ó%åA�4øç�z1ØÌ,^B Í�øç z1,�U[U+64CA]µÇg�

1.1.2.4 �+¦[U+555F]å^

�lConnexions<4åêjU[U+64CA].å^,«^ñ5Connexions Quick StartGuide6(Connexions�+¦[U+555F]Ã¨)4õ�.4õ[U+5E6B]�A[��z1Ã¨��+³XConnexions¦ºm�Ü¦�

1.1.2.5 z1å^

.å^lConnexions<4åêj,^ñ�ÏlConnexionsÜ¦É»�ª�Az1ØÌ�[U+60A8]a«®z1Çg�Xìçe� A[�çå�Å,«^ñz1,[U+5E6B]�[U+60A8]¡�Í�z1�^D¦Í�z1,�U[U+64CA]z1çe�

1.1.2.6 Personal Toolbar �0Ø�Ø

�0Ø�Øl5Quick Start6(�+¦[U+555F])�5Courses6(z1)å^Yj�.Ø�ØAÉ�,ã[U+60A8]h�góÕB��ò4ã¦A^ñ�ôi[U+60A8]µÍgóÕConnexions, �[U+60A8]-Z4ConnexionsÛ�,[U+60A8]a«U[U+64CA].Ø�Ø

(Figure 1.3)Aå^,«-�YØÁ�¥{:

• góÕB� (p. 6)�• �`�¾9& (Section 1.2)�• �Í�ConnexionsÛ� (Section 1.1.3: Û�^�)�

8http://cnx.org/9http://cnx.org/aboutus/

10http://cnx.org/technology/11http://cnx.org/help/



Figure 1.3: góÏA�0Ø�Ø�

ôi[U+60A8]4ConnexionsÛ�,òé¶�góÕB��,[U+60A8]a«U[U+64CA].Ø�Ø (Fig-ure 1.4)Aå^,«-�YØÁ�¥{:

• ^ñ[U+60A8]�0AØ{/�• �l[U+60A8]AConnexionsÛ��)ó�0Ü9,Èô^âeÃ�lç�\½�S�[U+60A8]�0ÿ4ÿÇ�[U+60A8]h�D^[U+8AAA]é�«�[U+60A8]h�D^^ñlç,[U+60A8]�a«l� #[U+60A8]AÛ�Ò8�• �`�¾9&�• gwB��

Figure 1.4: gó¶A�0Ø�Ø�

1.1.2.7 Navigation ¨@�×

.�×�^7ó6ConnexionsA4XÜ9Aå^,Åâ6[U+60A8]�~Home<4�Aboutó6�ContentÜ¦�Softwareå²��HelpR�Ç×�51�AÜ9�

1.1.2.8 Log in gó�×

ôi[U+60A8]4ConnexionsÛ�,[U+60A8]a«l.�×�góB��.«,4Í�å^�[U+60A8]l Ò8(ôi[U+60A8]�dÒ8),«�4Í�å^«å��^�Í��AConnexionsÛ�(Section 1.1.3: Û�^�)A4õ�ôi[U+60A8]µÍgóÕB��,i�^ñ.�× (Figure 1.5)�

Figure 1.5: 5Log in6gó�×�

1.1.2.9 Spotlight ó6�×

.�×0^h¹^Í�>�ÌO,k6ConnexionsÜ¦É»�ª�4Yw�\AA[��.A[�AÍ?,�ã;��Ø{AÍ��×,«�;�AConnexionsÜ¦Aå^,Ífw��

1.1.2.10 e-Mailbag \½@��×

.�×^ñ¢�¢ConnexionsA³X�¶|AÈ½,4Í�å^hè<³X�A�~¶|�


5

1.1.2.11 What's New �&�×

.�×74ConnexionsT�áOwuAÁ��å^�&12 �

1.1.2.12 Workspaces Ø{/�×

.�× (Figure 1.6)^7Í@å^,�[U+60A8]A�0Ø{/�[U+60A8]�4oØ+[U+4EFD]A÷\Ø{%ç�«�[U+60A8]a«m�Í�Ø{%çAm�Ø{%ç13

4õ�.��{�l[U+60A8]góÕB�é^��

Figure 1.6: 5Workspaces6(Ø{/)�×�

1.1.3 Û�^�

^ �Í�ConnexionsÛ�,�®YØ[U+6B65]¤:

1. �l5Log in6(gó)�×�U[U+64CA]New author or instruc-tor?(�AA[� z1Ã¨�?),i^ñ^�Í�ConnexionsÛ� (Figure 1.7)4õ�

12http://cnx.org/news/news_all13http://cnx.org/create_workgroup



Figure 1.7: 5Request a Connexions Account6(^�Í�ConnexionsÛ�)4õ�

2. ��ó[U+60A8]AeÃ�lç�\½�S��<4ÿÇ,"Y4÷j�A�Éh»^A��3. �U[U+64CA]ContinueBK,i�^ñ5Account Request: Select User-

name6(Û�^�:Éñ³X�çe)4õ�4. ��óÍ�³X�çe,9î[U+60A8]�)óAl�ç�Ü¦(First, Middle, Last

Name),i�4ÍØA³X�çew��5. (¤»^A)��ó[U+60A8]��\AóSS³É,Ãw[U+60A8]ô\¡�Connexion,�ó[U+60A8]k6ConnexionsA÷\¶|,«�[U+8AAA]é[U+60A8]C¶[U+5E6B]�)Ù�Ê�A¶C�6. �U[U+64CA]ContinueBK,i�^ñ5Account Request: Con�rmation6(Û�^�:Éú)4õ�7. ��ÖAç¦¶4õ�8. �Éñ[U+60A8]¶[U+95B1]�~é¦¶.4õAçAjÅ�9. �U[U+64CA]Request Account^�Û�,i�^ñ5Account Request Com-

plete6(Û�^�o)4õ,Connexionsiá�Í�\½@bÕ[U+60A8]Ï�)óA\½�S,.�b^7[U+555F]¥[U+60A8]�Û�Aó[U+8AAA]éÃñ�

1.1.4 gó�gw

^góÕConnexions,�l5Log in6(gó)�×�)ó[U+60A8]A³X�çe�Ò8,U[U+64CA]Log ingó�

l[U+60A8]gó¶,Ø{/�× (Section 1.1.2.12: WorkspacesØ{/�×)i1bgó�×,�0Ø�Ø�iw�MyWorkspace�AØ{/�My Account�AÛ��^gw,�lConnexions<4Aåêj�0Ø�Ø (Figure 1.4)�U[U+64CA]Log outgwå^�


7

1.2 `¨ Connexions �¾9&14

1.2.1 ¢�Í��¾`¨

l÷\å²|b�,[U+60A8]ka� �Ê�ê %b�Am²��i:@m² �¾,³XReport aBug`¨�¾å^�©,�Connexions¾_,.å^lConnexions<415 �Connexions3;ÿ4A�0Ø�Ø��^`¨Í��¾9&,�®YØ[U+6B65]¤:

1. �U[U+64CA]Report a Bug`¨�¾å^,i^ñ�¾`¨¢�ÌÅ(Bug Report Submission Form)16 �2. �)ó[U+60A8]Açe�3. �)ó[U+60A8]A\½�S�4. ôi�¾hw�l51Í�øçé,�)óøçA�ID,:hÍç�8,Èôm99999�ôi[U+60A8]ã©°øç�8,�B .øç�^ñ5About6(ó6) 5History6([U+6B77]¶)4õ,øçAA�i�ØlÖ@4õê�5. �Ãé�¾An,�l5Type6(�ó)�É�U[U+64CA]ÏY¾¡,«��Y¶�[U+9304]ÁÉñC£A)ó�6. �[U+8AAA]é�¾�!oA�Ö,�l5Severity6(©l)�É�U[U+64CA]ÏY¾¡,«��Y¶�[U+9304]ÁÉñC£A)ó�7. �l5Task Title6(÷ÜÇg)�É�)ó�¾A�Ø�^,ñ�8. �l5Description6([U+8AAA]é)�É�)ó�¾õÌA�~;^â[U+60A8]��A¥{,«�B�A¥{�¨²A�¾õÌ�ôia�A�,�^âaSê[U+7522]y.�¾A»�[U+6B65]¤AÃñ[U+8AAA]é�9. �U[U+64CA]Submit Bug¢��¾«i�¾)óÕConnexions�îB��

Resetl±iw£[U+60A8]lÌÅê��A)ó�

1.2.2 ó6¢��¾`Ä^³

:�4Í@ó6¢��¾`Ä^³,ia[U+5E6B]��è�Kv�¾�

• <©,l[U+60A8]ÈµóÜ9Ï��ó1error message�¾9&^ñ,^â[U+60A8]A�¾`¨�Ùº�¾A9&^7lÂÜ9,ôi[U+60A8]�Y gò-ó�¾`¨¢�ÌÅ17 4õ, Í�R�18 4õ,�l[U+60A8]Aë@Hê³XBackêÍ4Ê�«^ñ�¾9&�

• �^âÍ��¾4õA§�ôi�¾h^ñÍ�¥{êA�¾9&,��~.9&%å,iWTl�¾`¨�;6Õ6^â�¾9&AHTML�º%b[U+5167]Mº_,��AÍ@B�lHTMLË~��^7lÂÜ9�£�¾9&^ñé,�U[U+64CA][U+60A8]åìå�,®î[U+60A8]�³XAë@HÉñView

Source View Page Source�Ö�º[U+6A94],«^ñ.4õAHTML[U+6A94],Ò¶[U+60A8]a«�~.HTMLÜ9,«�TÕ�¾`¨��• è<AÜ9iè4[U+5E6B]��k6�Connexions:ôA�B�,qA�¾Ðyi¤ô4X;ôi[U+60A8]A�¾hlÍ�¸#Aøç,�,¶øççe;ôi[U+60A8]A�¾w�lA[¡õ,�,¶[U+60A8]�Ø{AØ{%ç øç;ôi[U+60A8]³Xz1A[�(Course

Composer),�,�[U+60A8]vlØ{Az1,��;^7�¾w�4õAÉ�ÿÇ�ôia«A�,�[U+8AAA]é[U+60A8]�vlÜ�AØ{�

1.3 B Connexions Ü¦19


If you would like to assist Connexions by helping us update this module with an appropriatetranslation from the current English version, please contact us at [email protected] as we wouldappreciate your help with improving our support for non-English-speaking users.

�[U+67E5][U+95B1]Connexionsó� (Section 1.1)øç,««�ConnexionsA°B�

14This content is available online at <http://cnx.org/content/m13478/1.4/>.15http://cnx.org/16http://mountainbunker.org/bugReport17http://mountainbunker.org/bugReport18http://cnx.org/help/19This content is available online at <http://cnx.org/content/m13480/1.3/>.20"Viewing Connexions Content" <http://cnx.org/content/m11837/latest/>[email protected]@cnx.org



1.3.1 Â5Ü¦É»�ª

[U+60A8]a«³XConnexionsÿ4åêjASearchÂ5¥��%åjÅ,lContent Com-monsÜ¦É»�ª�Â5Í�¸#øç z1��lÂ5%åjÅ��óÍ�çe�ó�å�z1Çg�øçÇg�å�� bA�,U[U+64CA]SearchÂ5�Connexionsi^ñó�[U+60A8]�)óA�4øç�z1,^B Í�øç z1,�U[U+64CA]3Çg�

1.3.2 ³Xì�¿¨@ Connexions z1

Connexionsì�¿�½�[U+60A8]lConnexions�¡5�B Ü¦,:é[U+60A8]»?³XMozillaë@H«¦[U+555F]ì�¿�ì�¿Ã¨(Section 2.1)��4Í�ó6ì�¿Ê�AÐy,«�ô\³XW�

1.3.3 ã³Xì�¿¨@ Connexions z1

ì�¿ãhConnexions�*ÍA¨@jù,ôi[U+60A8]³XÍ�ãÄ&ì�¿Aë@H51Connexions,[U+60A8]\Òa«³X3;¨@Ø�,«[U+60A8]AjùB z1�

1.3.3.1 ¦[U+555F]Í�z1

�lConnexionsÿ4åêÌU[U+64CA]z1å^,«^ñConnexionsÖtêAz1�[U+60A8]�a«�:Éñ5Content6(Ü¦)Ç×(lYouare here: [U+60A8]l:¨@ØAêj)«^ñÖt,«��4õÁ:Éñ5Courses6(z1)Ç×�.Ç×iØw�4¶�á[U+4F48]lÜ¦É»�ª�Az1�k6[U+6BCF]�z1,Ç×ilã¦z�^ñz1Çg�Xìçe�«�z1Ã¨�çe��U[U+64CA]z1Çg«^ñz1�

Figure 1.8: Connexions z1�


9

1.3.3.2 lÍ�z1�¨@

£[U+60A8]eÍêD¦z1é,i�^ñz1Çg4õ�.4õ^7¿�äju:Í�hCourse Con-tentz1Ü¦äju,74.z1�AÍ�Ü¦ØÌ,ØwÁ¢�øççe;[U+53E6]«Í�äju^ñStartCourse¦ºz1å^,«�z1Ü9,ÈôÊSXì�z1Ã¨��\AA[��«�z1AÍ�#�Ðy��U[U+64CA]StartCourse¦ºz1«^ñqAz1,i��eÍ�øç¦º�£[U+60A8]lÍ�z1�^ñÍ�øçé,[U+60A8]a«�:U[U+64CA]åêÌA��PREV��êÍ� NEXT��YÍ��å^,«Elz1�½¥�ÏÍ�øç ¶Í�øç�lÍ�z1�A[U+6BCF]Í�øç,[U+60A8]a«Sê^ñz1Çg4õ,{Û[U+64CA]øçåêÌATable

of ContentsÜ¦ØÌå^�

Figure 1.9: lÍ�z1�å^ÕÏ ¶Aøç�

È¶: ��PREV��êÍ� NEXT��YÍ��å^,«�Table of Con-tentsÜ¦ØÌå^,{�l[U+60A8]�Í�z1Á-óÍ�øçéZ�w�;ôi[U+60A8]�ë@H÷�51Í�øç,iã�w�.å^�

1.3.4 B óm¦

[U+60A8]a«³Xw�løçÜ¦E#A5Related Material6(óm¦)äjuÁAå^,«B øçAóm¦,äju^â:

• È½Aå^�R�m¦� �:øçA[��,¶A©Km¦�:@åÂl^n,h«å^çeE#jÅA��^��:@åâ�hConnexions�Am¦, �hConnexions«�ÿ4�• 3;øç,74Åâ6�ÏøçÜ¦Aøççe��U[U+64CA]Í�øççe,«^ñµøç�• ÷\3;^7.øçAz1��U[U+64CA]Í�z1çe,«^ñµz1�

Figure 1.10: å^Õóm¦�



1.3.5 ��4õ�Å

[U+60A8]a«l5Personalize6(�0Z)jÅ�ÉñÍ�style�Å2ù,«��Ü¦^�4õA¿§[�Åù,I AÜ¦^�4õ�ÅhSummerSky|N�4O8�Å«¶Éñ,^âPlaylandbÈ��,h J¢Î��AConnexions³X��

Figure 1.11: �ÅÉñjÅ�

1.3.6 -��+A[

ôi[U+60A8]4£é�B øçAA[ç�,[U+60A8]a«³XEdit In Place£ñA[å^,«E#¸�+ª-�A[��[U+67E5][U+95B1]ó6Edit in Place23 AConnexions4õ«Èµè<Ü9�

1.3.7 ó6øçA^ñÜ9

^^ñøçAmetadataÆ~Ü¦,�løçA%�U[U+64CA]More about this con-tentè<óÜ¦«Èµå^�Æ~Ü¦hó6øçAÍ�¤[U+5167]MÜ9,ÈôøçA��Aça2ù�x§�8�m�ñU�K�ñU�A[��Ü¦¾¿��xçè4��øççe�ó�å�«�=^�

1.3.8 B øçK�[U+6B77]¶

^B Í�øçAK�[U+6B77]¶,�U[U+64CA]øç%�AVersion Historyx§[U+6B77]¶å^,«^ñøçAHistory[U+6B77]¶ÿ4å^�lá[U+4F48]Í��øçAéÆ,Connexions�Ã#Í�K�A�«kw6øçx§�ôi4D^è�øç,A[�a«-��[U+67E5]�A[�«�Sêá[U+4F48]øç,�4Í�O[U+589E]AKvA�iÃ#¢è�~Ax§�Connexions�5�4AK�Ü9,[U+60A8]a«løçAHistory[U+6B77]¶ÿ4ê-�B �

1.3.9 ØÖÍ�øç

^[U+7522]yÍ�[U+60A8]a«ØÖAøçPDF[U+6A94]§,�U[U+64CA]w�løçåêÌAPrint(PDF)ØÖå^�4éÆÙºSSêAD^,[U+60A8]a�D^Í�m¦AØÖ§,[U+60A8]a«l÷Íøç[U+7522]yÍ�PDF[U+6A94]§,PDF[U+6A94]§AÅù�448�4<�4©�«�4<A��:6h³XÍ�PDF[U+6A94]§-�ØÖ,[U+60A8]»?l[U+60A8]A\½ê£�a«ØÖPDF[U+6A94]§Aå²�ôi[U+60A8]D^Íq�z1AÑ§ØÖ,�ãConnexionsJ¿¾_ã[U+7E6B]�lConnexionsÍuè�AØ�,[U+60A8]ia«ØÖÍq�z1òãD^ConnexionsJ¿¾_A½��

1.4 Connexions ¿ê� 24

note: This module has been retired as it contained Connexions documentation which is nolonger accurate and/or relevant. Please visit the help page25 for up-to-date information aboutthe Connexions website, including support for viewing and authoring content and the CNXML

23http://cnx.org/technology/EditingTools/editInPlace.html24This content is available online at <http://cnx.org/content/m13481/1.3/>.25http://cnx.org/help


11

language. If you have any additional questions or cannot �nd the answer to your question, pleasecontact [email protected] and we will be happy to assist in any way we can.

If you would like to assist Connexions by helping us update our documentation with an appropriatetranslation of a current English module, please contact us at [email protected] as we would appreciateyour help with improving our support for non-English-speaking users.

[email protected]@cnx.org


Chapter 2

Connexions ì�¿

2.1 ì�¿Ã¨1

note: This module has been retired as it contained Connexions documentation which is nolonger accurate and/or relevant. Please visit the help page2 for up-to-date information aboutthe Connexions website, including support for viewing and authoring content and the CNXMLlanguage. If you have any additional questions or cannot �nd the answer to your question, pleasecontact [email protected] and we will be happy to assist in any way we can.

If you would like to assist Connexions by helping us update our documentation with an appropriatetranslation of a current English module, please contact us at [email protected] as we would appreciateyour help with improving our support for non-English-speaking users.

1This content is available online at <http://cnx.org/content/m13479/1.3/>.2http://cnx.org/[email protected]@cnx.org


13

14 CHAPTER 2. CONNEXIONS ì�¿


Chapter 3

Ü¦[U+5167]MAØ{-�

3.1 Ø{�É1



3.1.1 Connexions Ø{�É

Connexions,¶¿8�ÉÅ2«-�Ü¦Ü�AØ{:5MyWorkspace6(�AØ{/)�5Workgroups6(Ø{%ç)�[U+60A8]a«l¿�Ø{�ÉÁ-�¦AÜ¦m��A[��"�Ø{�.¿�Ø{�É/AF¼h³X�A51ç��5�AØ{/6hÍ�Ï0Ø{�É,{4[U+60A8]a«-ó.�ÉB �K�Ü¦�Q4ConnexionsÛ�A[U+6BCF]�0k4;�ô�A5�AØ{/6,:lConnexionsÛ�m�AéÆ�ô¥m�fu�5Ø{%ç6hº Ü��{øùAJ¿,Í�³X�A%ç«�%ç�oØA[U+6BCF]Í�0ka«51�õAÜ¦,òa«-�B �K�Ü¦�5Ø{%ç6»?:[U+60A8]um�,[U+60A8]a«m�<�Ø{%ç,�[U+6BCF]Í�J¿kw�ã¦AØ{%ç�:¿8AØ{�Ékl.øçÁáf[U+8AAA]é�

3.1.1.1 B Ø{�É

Í�[U+60A8]góConnexions¶,lConnexions<45 EYjA5Log in6(gó)�×i�:5Workspaces6(Ø{/)�×�1b�{^[U+60A8]gó¶,.�×i5ll<4ê�Connexions3;Aÿ4ê,�[U+60A8]a«jE��+ªl[U+60A8]AØ{�É/-�"��

1This content is available online at <http://cnx.org/content/m13482/1.3/>.2"MyCNX Dashboard" <http://cnx.org/content/m10885/latest/>[email protected]@cnx.org5http://cnx.org/


15

16CHAPTER 3. Ü¦[PLEASE INSERT

\PRERENDERUNICODE{\UNICHAR{20839}} INTO PREAMBLE]MAØ{-�

Figure 3.1: 5Ø{/6�×�

3.1.1.2 �AØ{/

lConnexions�,5�AØ{/6h[U+60A8]�0AØ{�É,�[U+60A8]X�Ø{,90Þl-ó�l.Ø{�É�,[U+60A8]4[U+60A8]ô�Aøç�[U+6A94]§��z1,:@h90ÞlB � -�K�A�<{�liøç z1½¥�5Ø{%ç6Ï,G+l5�AØ{/6�Ü�øç z1AóØ{,òØ{%ç(Section 3.1.1.3: Ø{%ç)h»¦�{�AÍ�%ça«Ë� A[m¦Aªj��:U[U+64CA]5Workspaces6(Ø{/)�×�AMyWorkspace�AØ{/å^, �U[U+64CA]5Personal

toolbar6(�0Ø�Ø)�AMyWorkspace�AØ{/å^,[U+60A8]a«�Í�Connexionsÿ4^ñ[U+60A8]�0AØ{�É�

3.1.1.3 Ø{%ç

Ø{%ç(Workgroup)hÍ%ConnexionsAAd��Q4A¤É¦�s�É(scratch area),l.a«»¦Ü�;�»4Aøç,ÕAd�ÍfØ{��Ö-p,òã��«¡0¹ �;�AØ{-��

L�: �db,Ø{%çãh�»¦�{�/-�ñ�Aªj�Í�Ø{%çAoØ»?¦iùA°ñ�,ÙºØ{%ç��4AoØkQ4¦� A³Xç;Í�Ø{%ç�A÷\oØa«[U+589E]` ½£3;oØ,«�K��[U+589E]`� ½£Ü¦;Í�Ø{%çAm��Z4Ö«Aç��

[U+6BCF]Í�Ø{%ça�4óãAøç [U+6A94]§,Ø{%çAoØa«�Ü¦É»�ª�5lAøçÁ[U+589E]`ÕØ{%ç��Í�m�Í�øç [U+67E5]Æ~Í�øç,Ø{%ç�A÷\oØ�4A[Aç�,òa«k.øç-�K��º ^�4A[Aç�,:�0»?�4:�øçAÜ¦¾¿�AÌ,�á|A[øçÌ (Section 3.3.7:A[øçÌ)�£[U+60A8]h�Í�Ø{%çAoØé,Ø{%çAçe�ØlØ{/(Workspaces)�×��[U+60A8]a«U[U+64CA]Ø{%ç�Açå,«^ñÍ�Ø{%çAÜ¦�

3.1.1.4 m�Í�Ø{%ç

^m�Í�Ø{%ç,�®YØ[U+6B65]¤:

1. �U[U+64CA]5Workspaces6(Ø{/)�×�ACreate a workgroupm�Í�Ø{%ç,i�^ñ5Createworkgroup6(m�Ø{%ç)Öt�

2. �l5Name6(çe)�É��óØ{%çAçe�3. (¤»^)�l5Email6(\½�S)�É��óÍç\½�S,a«hÍ�»XA\½�S .Ø{%ç�4oØA�SØÌ�4. (¤»^)�l5Description6([U+8AAA]é)�É��óØ{%çAó[U+8AAA]é�5. �U[U+64CA]Createm�,i�^ñ�Ø{%çAÖt�

Ùº:hÍ��AØ{%ç,�õZ4Ü¦,òé[U+60A8]h:*ÍoØ��[U+67E5][U+95B1]"�Ø{�ÉÜ¦(Section 3.1.2: "�Ø{�ÉÜ¦)[U+5167]AÐy[U+8AAA]é,«l�AØ{%ç�[U+589E]`Ü¦��[U+67E5][U+95B1]"�Ø{%çoØ(Section 3.1.4: "�Ø{%çoØ)[U+5167]AÐy[U+8AAA]é,«l�AØ{%ç�[U+589E]`oØ�


17

3.1.2 "�Ø{�ÉÜ¦

^^ñ�AØ{/,�U[U+64CA]5Workspaces6(Ø{/)�×�AMyWorkspace�AØ{/å^�^^ñÍ�Ø{%ç,�U[U+64CA]5Workspaces6(Ø{/)�×�Açe�,:h[U+60A8]eÍê^ñ5MyWorkspace6(�AØ{/), �,[U+60A8]�m�Ø{%ç,Ø{�É�õã�4Ü¦�5MyWorkspace6(�AØ{/)A^ñÖt�4Í�5Content6(Ü¦)�Í�5Properties6(yn)Ç×�5Workgroups6(Ø{%ç)�^ñ5Content6(Ü¦)�5Properties6(yn)��5Members6(oØ)Ç×�¿�Ø{�ÉA5Content6(Ü¦)Ç×h¦A,£ ÖÍ4êjAçe«�Y¿Á^ñÍ�5My

Workspace6(�AØ{/)A5Content6(Ü¦)Ç×,74Í�z1��øç�

Figure 3.2: 5�AØ{/6A5Content6(Ü¦)Ç×�

[U+60A8]a«�5Content6(Ü¦)Ç×ê-�YØAØ{:

• m�� (Section 3.1.2.1: m��)• �Ü¦É»�ª[U+589E]`¶5lA�� (Section 3.1.2.2: �Ü¦É»�ª[U+589E]`¶5lA��)• B Ø{�ÉÜ¦ (Section 3.1.2.3: B Ø{�ÉÜ¦)• �Í�Ø{�É½£�� (Section 3.1.2.4: �Í�Ø{�É½£��)• lÍ�Ø{�É�l�èç�� (Section 3.1.2.5: lÍ�Ø{�É�l�èç��)• lÍ�Ø{�É�ñT �~�� (Section 3.1.2.6: lÍ�Ø{�É�ñT �~��)

3.1.2.1 m��

^lØ{�É�m��Aøç z1,�®YØ[U+6B65]¤:

1. �U[U+64CA]%ÔjÅ�Create New Itemm��¥�"AÏY¾¡,i�w�Í�aX��2ùAY¶ØÌ�2. �Éñ5Course6(z1) 5Module6(øç)��2ù,U[U+64CA]Create New

Itemm��,i�^ñ5New content: Licesing6(�Ü¦:Aç)Öt�3. �ÉñÉújÅ«¦¶.Aç,U[U+64CA]NextYÍ[U+6B65]�,[U+60A8]Éñz15Course6(z1),i�l5Edit

Course6(A[z1)Ötê^ñ5Metadata6(Æ~Ü¦)Ç×;�[U+67E5][U+95B1]ô\³Xz1A[�(Section 3.2)A[U+5167]M««�ô\A[Í�z1�,[U+60A8]Éñ5Module6(øç),i�l5EditModule6(A[øç)Ötê^ñ5Metadata6(Æ~Ü¦)Ç×;�[U+67E5][U+95B1]A[øç (Sec-tion 3.3)A[U+5167]M««�ô\A[Í�øç�




^lØ{�É�m��A[U+6A94]§ ¿?,�®YØ[U+6B65]¤ê¢[U+6A94]§ ¿?:

1. �U[U+64CA]%ÔjÅ�Create New Itemm��¥�"AÏY¾¡,i�w�Í�aX��2ùAY¶ØÌ�2. �Éñ5Image6(¿?) 5File6([U+6A94]§)2ù,U[U+64CA]Create New

Itemm��,[U+60A8]Éñ5File6([U+6A94]§),i�^ñ5Edit File6(A[[U+6A94]§)Öt;,[U+60A8]Éñ5Image6(¿?),i�^ñ5EditImage6(A[¿?)Öt�

3. �U[U+64CA]Browseë@,«�i�[U+589E]`A[U+6A94]§ ¿?i±�[U+60A8]�É±�4. �Éñ��/U[U+64CA]OK(É#),«ê¢[U+6A94]§ ¿?�5. �U[U+64CA]Save�5«lØ{�É�[U+589E]`[U+6A94]§ ¿?�

5Image6(¿?)�5File6([U+6A94]§)��2ù,�[U+60A8]a«ô:ê¢[U+60A8]úl[U+5167]MÁ³X�Am¦,:@m¦»?l[U+60A8]¢�ÕConnexionsÏI¶�5l�£[U+60A8]lØ{�É�m�[U+6A94]§ ¿?¶,[U+60A8]lConnexions�¶`jêm� :��£[U+60A8]m�Í��A¿?��,Í�[U+60A8]U[U+64CA]Save�5¶,i�w�¿?AI@,«�^ñÍ�9&[U+8AAA]é[U+60A8]A¿?¶ �5�£[U+60A8]m�Í��A[U+6A94]§��/U[U+64CA]Save�5¶,i�w�[U+6A94]§^ñAÜ9,«�w�Click

here to get the �le�¥.Ü«Èµ[U+6A94]§å^�

3.1.2.2 �Ü¦É»�ª[U+589E]`¶5lA��

[U+60A8]a«[U+589E]`¶5l6Ü¦É»�ª�Aøç z1Õ[U+60A8]AØ{�É�,Ù.[U+60A8]a«S�XConnexions�3;ªjAÜ9�^[U+589E]`¶5lA��,�®YØ[U+6B65]¤:

1. �U[U+64CA]Search for Published ContentÂ5¶á[U+4F48]Ü¦,i�^ñ5Search the Connex-ions repository6(Â5ConnexionsÜ¦�)Öt�

2. �lSearchÂ5¥�")óÍ��bA�ID�çe�ó�å�A[�lç� %ÔÁå��3. ,4»^,�1È5modules6(øç) 5courses6(z1)AÉújÅ,U[U+64CA]SearchÂ5,i�4ó�[U+60A8]Â5�bAøç�z1ØÌ^ñlÖtê�4. �Éñ[U+60A8]�D^A��"AÉújÅ,`óÕ[U+60A8]AØ{�É, �³Xçe[U+6A6B]�ÁAÉújÅ«Éñ�4��5. �U[U+64CA]5Add selected content6([U+589E]`�ÉÜ¦)%åjÅ�AÏY¾¡,i�^ñy6[U+60A8]AÓ�Ø{�ÉAÍ�Y¶ØÌ,��:ØÌÁÉñÍ�Ø{�É�6. �U[U+64CA]Add[U+589E]`,[U+60A8]�ÉA��i�[U+589E]`ÕØ{�É,Ò¶^ñµØ{�ÉA5Content6(Ü¦)Ç×�


19

Figure 3.3: ¶5lÜ¦AÂ5^i�

3.1.2.3 B Ø{�ÉÜ¦

Í�Ø{�Éa«^7øç�z1�[U+6A94]§�¿?,Í�Ø{�ÉA�ÏÜ¦a«�Ø{�ÉêA5Content6(Ü¦)Ç×uB �lØ{�É�X«^ñ[U+6BCF]Í��AÜ9,+ôY�ñ:

• Title - (Çg).z^ñÇg�[U+6A94]§çe, �[U+60A8]¶�m�A��ID, �[U+589E]`ÕØ{�É%çA�• Type - (2ù).z^ñ�Ø��A2ù,2ù^7:¿?�[U+6A94]§�øç��z1�• Size - ([U+6A94]§d³).z^ñµ��A[U+6A94]§d³(kilobytes),øç z1/ã^ñ[U+6A94]§d³�• Modi�ed - (¶K�).z^ñµ��T¶K�AñU�é/,ôih�A��,.z^ñm�ñU�é/�• Status - ([U+72C0]S).z^ñµ��ÏA[U+72C0]S,4¸8a�[U+72C0]S:

· Published - (¶á[U+4F48]).��¶góÕÜ¦É»�ª,�Ïa«�d[U+773E]51�· Checked Out - (¶[U+67E5]Æ).��~ôÜ¦É»�ª,i±l[U+60A8]AØ{�É�«¶A[�· Created - (¶m�).��¶ m�,/i±l[U+60A8]AØ{�É�,}.��Z4§5i6Ü¦É»�ª�· Modi�ed - (¶K�).��¶[U+67E5]Æ~éè�~,è�~A[U+5167]M¶ �5�£[U+60A8]m�Í��éè�3[U+5167]M¶,µ��A[U+72C0]Si�5Created6(¶m�)�o5Modi�ed6(¶K�)�

3.1.2.4 �Í�Ø{�É½£��

^�Í�Ø{�ÉÁ½£Í��,�Éñ[U+60A8]�^½£A��çe"AÉújÅ,U[U+64CA]Remove½£;[U+60A8]a«�Ø{�ÉÁÉñ<��/éÍêÓ�½£�




3.1.2.5 lÍ�Ø{�É�l�èç��

^lÍ�Ø{�É�l�èç��,�®YØ[U+6B65]¤:

1. �Éñ[U+60A8]�^l�èçA��çe"AÉújÅ,U[U+64CA]Renamel�èç,i�^ñ5Renameitem6(l�èç��)Öt�

2. �l5New Name6(�çe)�É�)óµ��A�çe�3. �l5New Title6(�Çg)�É�)óµ��A�Çg�4. �U[U+64CA]Rename Allè�Ó�çe,[U+60A8]a«Íêl�èç<��,alØ{�ÉÜ¦ÖtêÉ#<��

l5Content6(Ü¦)Ç×ê�^ñA��i�-�è��

3.1.2.6 lÍ�Ø{�É�ñT �~��

^lÍ�Ø{�É��~�TêÍ��,�®YØ[U+6B65]¤:

1. �Éñ[U+60A8]�^ñY �~A��"AÉújÅ,U[U+64CA]CutñY Copy�~;CutñYi�½£�uA��,Copy�~�l�uªj�Y�§A��2. �^ñ[U+60A8]�^Tê�bA±,Èô[U+53E6]Í�Ø{�É,U[U+64CA]PasteTê;ôi[U+60A8]l�uAØ{%ç�TêÍ��~A��,[U+60A8]i[U+7522]y�§��AÍ�§�

3.1.3 Ø{�Éyn

[U+60A8]a«A[Í�Ø{�ÉA¸#yn,ÈôÍ�Ø{%çAçe, �h[U+60A8]�0AØ{�É5MyWorkspace6AÍ�Ðy[U+8AAA]é;a«lØ{�ÉA5Properties6(yn)Ç×ê51:@��

3.1.3.1 A[�AØ{/Çg�[U+8AAA]é

^A[�AØ{/AÇg [U+8AAA]é,�®YØ[U+6B65]¤:

• �U[U+64CA]My Workspace�AØ{/«^ñ[U+60A8]�0AØ{�ÉÖt�• �U[U+64CA]5Properties6(yn)Ç×,i�^ñ5Edit Folder Properties6(A[Ü¦�yn)Öt�• �l5Title6(Çg)�É�º[U+60A8]�0AØ{�É�óÍ��AÇg çe�• �l5Description6([U+8AAA]é)�É�º[U+60A8]�0AØ{�É�óÍ��A[U+8AAA]é�• �U[U+64CA]Save�5�

3.1.3.2 A[Í�Ø{%ççe�\½�S��[U+8AAA]é

^A[Çg�\½�SÛ��«�[U+60A8]��4oØ+[U+4EFD]AÍ�Ø{%ç[U+8AAA]é,�®YØ[U+6B65]¤:

• �U[U+64CA]l5Workspace6(Ø{/)�AØ{%ççe,«^ñØ{%çÖt�• �U[U+64CA]5Properties6(yn)Ç×,«^ñ5Properties of6(yn)Öt�• �l5Name6(çe)�É�ºØ{%ç�óÍ��AÇg çe�• �l5Email6�É��óÍç\½�SÛ�,a«hÍ�»XA\½�SÛ�, µØ{%ç�4oØA\½�SØÌ�• �l5Description6([U+8AAA]é)�É��óÍ�Ø{%çAÐy[U+8AAA]é�• �U[U+64CA]Updateè��

3.1.4 "�Ø{%çoØ

Í�[U+60A8]m� Í�Ø{%ç, �[U+60A8]oºÍ�¶�5lAØ{%çAoØé,[U+60A8]a«[U+589E]`3;oØÕ.Ø{%ç�,:@oØa«k:Ø{%ç�AÜ¦Íf-�Ø{�

È¶: {4£Í�0Q4ConnexionsAÛ�Za«oºÍ�Ø{%çAoØ�


21

Ø{%çoØAçe�\½�S�Øl5Member6(oØ)Ç×�;:Ç×/ã5l65MyWorkspace6(�AØ{/)Ø{�É�,ÙºÖh[U+60A8]�0AØ{�É,[U+60A8]h*Ía«51:Ø{�ÉA0�

Figure 3.4: Ø{%ç5Members6(oØ)Ç×�

[U+60A8]a«�5Member6(oØ)Ç×ê-�YØØ{:

• [U+589E]òØÕÍ�Ø{%ç (Section 3.1.4.1: [U+589E]òØÕÍ�Ø{%ç)• �Í�Ø{%ç½£oØ (Section 3.1.4.2: �Í�Ø{%ç½£oØ)• kq�Ø{%çá�\½@b (Section 3.1.4.3: kq�Ø{%çá�\½@b)• kÍ��9oØá�\½@b (Section 3.1.4.4: kÍ��9oØá�\½@b)• �¦Í�Ø{%ç (Section 3.1.4.6: �¦Í�Ø{%ç)• ç£Í�Ø{%ç (Section 3.1.4.7: ç£Í�Ø{%ç)

`óÍ�Ø{%çD^Í�X�R,�[U+67E5][U+95B1]`óÍ�Ø{%ç (Section 3.1.4.5:`óÍ�Ø{%ç)«Èµè<Ü9�

3.1.4.1 [U+589E]òØÕÍ�Ø{%ç

^[U+589E]`�AoØÕ[U+60A8]�lAÍ�Ø{%ç,�®YØ[U+6B65]¤:

1. �lSearch¥�"�ó[U+60A8]�N�[U+589E]òØAçåØÌ�2. �U[U+64CA]SearchÂ5,i�4ó�Â5å�AÍ�ConnexionsÛ�è4�ØÌw�;ôiÂ5î^ñZ4Ü¦,�SÙÍê{XÍ�³X�çe Í�lÌlast

nameÂ5�3. �Éñ[U+60A8]N�[U+589E]`ÕØ{%çA0Açå"AÉújÅ�4. �U[U+64CA]Add selected users[U+589E]`�É³X�,i�è�5Current Group Mem-

bers6(�Ï%çoØ)ÌÅ,«^â�AoØ�

3.1.4.2 �Í�Ø{%ç½£oØ

^�[U+60A8]AØ{%ç�½£oØ,�®YØ[U+6B65]¤:

1. �l[U+60A8]�N�ôØ{%çÁ½£oØA5Remove6(½£)z�,ÉñÉújÅ�2. �U[U+64CA]Remove selected users from group�%ç½£�ÉoØ,i�è�5Current Group

Members6(�Ï%çoØ)ÌÅ,«^ñ½£AoØ�




3.1.4.3 kq�Ø{%çá�\½@b

^kq�Ø{%çá�\½@b,�®YØ[U+6B65]¤:

1. �l5Current Group Member6(�Ï%çoØ)ØÌÇg",U[U+64CA]emailgroup\½�S%çå^;i�¦[U+555F][U+60A8]A\½@bå²,^ñÍ��A9&,ã.Ø{%çoØã[U+7E6B]�

2. ��ó9&%b,«�á��

3.1.4.4 kÍ��9oØá�\½@b

£ kq�Ø{%çá�\½@b«,[U+60A8]a«kÍ�Ø{%çA�9oØá�\½@b�^kÍ��9oØá�\½@b,�®YØ[U+6B65]¤:

1. k6[U+60A8]�^á�\½@bAÍ�oØçå,�U[U+64CA]çe"YA5E-mail6(\½�S)z;i�¦[U+555F][U+60A8]A\½@bå²,^ñÍ��A9&,ã.Ø{%çoØã[U+7E6B]�

2. ��ó9&%b,«�á��

3.1.4.5 `óÍ�Ø{%ç

^`óÍ�%ç,µ%çAÍ��4oØ»?i[U+60A8][U+589E]`Õ.Ø{%çoØØÌ�;ôi[U+60A8]N�`óÍ�Ø{%ç,�ã[U+7E6B]Ö�Ø{%çAÍ�oØ,^�;�i[U+60A8]`óÕØ{%ç��

3.1.4.6 �¦Í�Ø{%ç

ôi[U+60A8]�¦Í�Ø{%ç, ��oØØÌ�½£[U+60A8]ô�,[U+60A8]IãShÖ�Ø{%çAÍ�oØ;^SoºÍ�oØ,µ%çAÍ��4oØ»?i[U+60A8]S[U+589E]`Õ.Ø{%çoØØÌ��^�¦Í�Ø{%ç,�®YØ[U+6B65]¤:

1. �l[U+60A8]N��¦AØ{%ç�^ñ5Members6(oØ)Ç×�2. �Éñ[U+60A8]çå"A5Remove6(½£)z�AÉújÅ�3. �U[U+64CA]Remove selected users from group�%ç½£�ÉoØ,i�^ñ5Leave Work-

group6(�¦Ø{%ç)AÉúÖt�4. �U[U+64CA]Yes, LeavehA,�¦,[U+60A8]i�.Ø{%ç�½£,òé.Ø{%çAçeil[U+60A8]AConnexionsÿ4êA5Workspaces6(Ø{/)�×Á½£�

Í�Í�Ø{%çA[U+6BCF]�oØk�¦.%ç,.%çi ç£;T¶Í��¦AoØi Y «Éú.[U+6B65]¤�

3.1.4.7 ç£Í�Ø{%ç

£Í�Ø{%çãS�4÷\oØé,.Ø{%çi ç£;ôi[U+60A8]^ç£Í�Ø{%ç,[U+60A8]»?½£�4AoØ,^â[U+60A8]ô��^ç£Í�Ø{%ç,�®YØ[U+6B65]¤:

1. �l[U+60A8]N�ç£AØ{%ç�^ñ5Members6(oØ)Ç×�2. �Éñ[U+6BCF]Í�oØçå"A5Remove6(½£)z�AÉújÅ�3. �U[U+64CA]Remove selected users from group�%ç½£�ÉoØ,i�^ñ5Delete Work-

group6(ç£Ø{%ç)ÉúÖt�4. �U[U+64CA]Yes, Delete ithA,ç£,�4oØi�.Ø{%ç�½£,�iç£.Ø{%ç,òé.Ø{%çAçeil�4oØAConnexionsÿ4êA5Workspaces6(Ø{/)�×Á ½£�

3.2 ô\³Xz1A[�6

warning: This module contains Connexions documentation which is out-of-date. The contents ofthis module are provided here for historical purposes only and should not be considered accu-rate for the current version of the Connexions website. The current (English-language) version ofthis module can be located at http://cnx.org/content/m10288/latest/7. If you have any additional

6This content is available online at <http://cnx.org/content/m13489/1.3/>.7"How to Use the Collection Composer" <http://cnx.org/content/m10288/latest/>


23

questions or cannot �nd the answer to your question, please contact [email protected] and wewill be happy to assist in any way we can.


3.2.1 z1A[�

Connexionsz1A[��[U+60A8]a«m�Í��Az1, A[Í�¶�5lAz1,[U+60A8]a«³Xz1A[�-�YØÁ�Ø{:

• m�Í��z1 (Section 3.2.2: m�Í��z1)• ºÍ��z1)óa¶ýúAÆ~Ü¦ (Section 3.2.3: ºÍ��z1)óa¶ýúAÆ~Ü¦)• [U+589E]`Í��¢ (Section 3.2.4: [U+589E]`Í��¢)• [U+589E]`Í�½¢ (Section 3.2.5: [U+589E]`Í�½¢)• [U+589E]`Í�øç (Section 3.2.6: [U+589E]`Í�øç)• ,¶Í�U�AøçÇg (Section 3.2.7: ,¶Í�U�AøçÇg)• Éñøçx§ (Section 3.2.8: Éñøçx§)• A[ [U+589E]`å^ (Section 3.2.9: A[ [U+589E]`å^)• l�£&Ü¦ (Section 3.2.10: l�£&Ü¦)• ½£z1Ü¦ (Section 3.2.11: ½£z1Ü¦)• Ã#»¦�{AA[�AÌ# (Section 3.2.12: Ã#»¦�{AA[�AÌ#)• ±Çd1� (Section 3.2.13: ±Çd1�)• IÖz1 (Section 3.2.14: IÖz1)• á[U+4F48]z1 (Section 3.2.15: á[U+4F48]z1)• A[Í�¶5lAz1 (Section 3.2.16: A[Í�¶5lAz1)

3.2.2 m�Í��z1

m�Í��z1,Åâ6m�Í��øç (Section 3.1.2.1: m��),[U+60A8]a«�[U+60A8]AØ{/ Ø{%ç10

Á-óCourse Composer(z1A[�)�

1. �lCreate New Itemm��¥�"AY¶ØÌÁÉñCoursez1,/U[U+64CA]Create New

Itemm��,i�^ñ5New Content: Licensing6(�Ü¦:Aça)Öt�2. �ÉñlÖt%�AÉújÅ,«Î�[U+60A8]¦¶i.z1±6Creative Commons Attribution li-

cense(îXCCAç��)11 aY�3. �U[U+64CA]NextYÍ[U+6B65],5Metadata6(Æ~Ü¦)Ç×^ñÍ�9&Ìñ¶m�Í�z1�ÖtE#i�w�5Course

Status6(z1[U+72C0]S)�×,«�.z1�Ï[U+72C0]SAØÌ�T¶�-�A¥{,½%m�.z1A0Açå,«�\ém�.z1�

[email protected]@cnx.org

10http://cnx.org/help/reference/workgroups11http://creativecommons.org/licenses/by/2.0/




Figure 3.5: z1A[�(Course Composer)A[Öt�

3.2.3 ºÍ��z1)óa¶ýúAÆ~Ü¦

1. �lz1A[��Éñ5Metadata6(Æ~Ü¦)Ç×�2. �lÆ~Ü¦�É�)óC£AÜ9,^7:

• course title z1çe(»Â)�• institution name Xìçe � Ê¨.z1ASê Xì�• course code z1A� � �[U+9304]A�,ÈôBIO 201�• instructor name z1Ã¨�çe � Ê¨.z1A0�• course home page z1<4 � Í�URLÓç,5http://6,Èôhz1A�� ÊSdú�• keywords ó�å � .��X«[U+5E6B]�Connexions³X�Â5�.z1�• abstract =^ � .z1AÍ�#�Ðy(»Â)�

ôi[U+60A8]6Í�»Â�É�Z4)óÜ¦,£[U+60A8]U[U+64CA]Save�5é,i� ,�^-�)ó¥{,«d[U+9304].Æ~Ü¦�

3. �U[U+64CA]Save�5,i��5Æ~Ü¦,5Content6(Ü¦)Ç×�i^ñ.z1Çg�.Ç×hbÌ[U+60A8]`jç�.z1Aªj,�4¿��É;Ç×E#^ñÍ�z1°^,Ç×å#h[U+60A8][U+589E]`�£&� ½£z1ÁÜ¦�bAªj�

3.2.4 [U+589E]`Í��¢

Í�5¢6(section)hÍ�z1�AóøçA_A,[U+6BCF]Í�5¢6�4Í�Çg«,¶B �ýúÜ¦,[U+60A8]a«l5¢6�i±5¢6,�m�5½¢6(subsection)�


25

1. �lz1A[��Éñ5Content6(Ü¦)Ç×�2. ôiz1çeµÍÄíwu,�lz1°^�U[U+64CA]z1çe;:hlz1°^��T�� A�b�3. ôiµÍ^ñ5Content6(Ü¦)Ç×,��3^ñwu�4. �l5Content6(Ü¦)Ç×�U[U+64CA]Add New Section[U+589E]`�¢,z1°^�i[U+589E]`Í��A¢oºT��b,«�^ñ5Edit6(A[)Ç×,/4Í��É«¶)ó�¢çe�5. �l5Title6(Çg)�É�)ó�¢Açe�6. �U[U+64CA]Save�5�

[U+60A8]�)óAÇgiw�oºz1°^�A�¢,.¢ Äíwu,�[U+60A8]a«l�õ[U+589E]`Ü¦,[U+589E]`Í�½¢ Í�øç�

3.2.5 [U+589E]`Í�½¢

Í�½¢hlÍ�¢�AÍçóøç,[U+6BCF]Í�½¢�4Í�Çg«,¶B �ýúÜ¦�

1. �lz1A[��Éñ5Content6(Ü¦)Ç×�2. ôi¢AÇgµÍÄíwu,�lz1°^�U[U+64CA]µ¢Çg�3. ôiµÍ^ñ5Content6(Ü¦)Ç×,��3^ñwu�4. �l5Content6(Ü¦)Ç×�U[U+64CA]Add New Section[U+589E]`�¢;lz1°^�ÄíwuA¢AYj,i[U+589E]`Í��A½¢�i^ñ5Edit6(A[)Ç×,/4Í�E5Title6(Çg)�É«¶)ó�½¢çe�5. �l5Title6(Çg)�É�)ó½¢Açe�6. �U[U+64CA]Save�5�

[U+60A8]�)óAÇgiw�lz1°^�oº�A½¢,.½¢ Äíwu,�[U+60A8]a«l�õ[U+589E]`Ü¦�

3.2.6 [U+589E]`Í�øç

[U+60A8]a«�Ü¦É»�ª, �Í�z1Q4�ô�AØ{/ Ø{%ç12 ,[U+589E]`Í�¶á[U+4F48]AøçÕz1�õ�[U+589E]`Í�øçé,Connexions/ã�~µøçÕ[U+60A8]Az1�,.øçJ�lÜ¦É»�ª�,Connexions�ÖóÍ�1ü Í�ÃÇÕ[U+60A8]z1�Aøç�÷\�A ¶5lAøçlYØõÌY,[U+589E]`�Í�z1�:

• Í�øçã�ÖóÕÍ�z1�ï~Íê�• l[U+60A8]iÍ�øçÖóÕÍ�z1�Ï,µz1»?¶�lConnexions�á[U+4F48]�• lContent CommonsÜ¦É»�ª�Â5øçAÇg�çe�{��ó�å %Ôå��

ôiZ4¡�[U+60A8]�Â5å�AóÜ¦,Connexionsi�^ñó6Â5)ójùAm{�

3.2.6.1 ôÜ¦É»�ª[U+589E]`Í�øç

^lÜ¦É»�ª�Â5Í�øç,/éi3[U+589E]`Õ[U+60A8]Az1�,�®YØ[U+6B65]¤:

1. ôiµÍ^ñ5Content6(Ü¦)Ç×,�lz1A[��Éñ5Content6(Ü¦)Ç×�2. ôi��ÇgµÍÄíwu,l[U+60A8]^ÖóøçAªj,�lz1°^�U[U+64CA]��Çg;��a«hz1Çg�Í�¢AÇg� Í�½¢Çg�3. �lÂ5%åjÅ�)óó6.øçAÍ�å Í�å��4. �ã^Éñ5Courses6(z1)AÉújÅ,�Y�ÉA5Modules6(øç)ÉújÅ�5. �U[U+64CA]SearchÂ5,ó�Â5)ó%åA�4øçØÌi�^ñwu;ôiw�<øçï~Í�ÿ4A�¼,�Øw3;ó�AÖ«ÿ4wu�6. �Éñ[U+60A8]^[U+589E]`oºÜ¦A÷Íÿ4AÉújÅ�7. �U[U+64CA]Add selected content[U+589E]`�ÉÜ¦�

l[U+60A8]�ÉA¢%Y,É#Aøçiw�lz1°^��

3.2.6.2 ô[U+60A8]AØ{/ Ø{%ç[U+589E]`Í�øç

^�[U+60A8]AØ{/ Ø{%ç[U+589E]`Í�øç�º[U+60A8]z1�AÜ¦,�®YØ[U+6B65]¤:

1. l[U+60A8]^7��z1�øçAØ{/ Ø{%ç,�^ñ5Content6(Ü¦)Ç×�2. �ÉñD^AøçAÉújÅ,[U+60A8]a«{[U+589E]`l5Published6(¶á[U+4F48])[U+72C0]SYAÖ@øç�

12http://cnx.org/help/reference/workgroups




3. �U[U+64CA]Copy�~,�4Í�9&^ñ.��¶ �~�4. �U[U+64CA]z1Çg«-óz1A[�,�ll5Content6(Ü¦)Ç×ê�w�PasteTê¥�,mSÓCutñY�Copy�~��Remove½£¥��

5. �¥Y[U+60A8]�^ÖóøçA¢AÇg�6. �lz1A5Content6(Ü¦)Ç×êU[U+64CA]PasteTê¥��

.øçAÇgi�w�l[U+60A8]�ÉA¢YAz1°^��

È¶: ôi[U+60A8]Ù[U+589E]`Í�µÍá[U+4F48]Aøç,i�^ñÍ��¾9&;^-�£�Ah[U+60A8]�^[U+589E]Àøç¶ á[U+4F48],�l[U+60A8]AØ{�ÉA5Content6(Ü¦)Ç×B 5State6([U+72C0]S)z�

3.2.7 ,¶Í�U�AøçÇg

lÜ¦É»�ª�Aøç�4W�A[��¢DAÇg;£.øçl[U+60A8]Az1Á³X,:@Çga�/ãC��[U+60A8]a«,¶:�øçÍ�U�AÇg,�3w�lRoadmapì�¿Az1°B�,«�l[U+60A8]z1AØÖx§��£[U+60A8]ë@øç%bé,\�^ñ�uA[�AÇg�

1. �lz1°^�U[U+64CA]øçÇg,øç� A5Edit6(A[)Ç×i�w�lÖtå#�2. �l5Alternate Title6(U�Ç×)�É��ó.øçA�Çg�3. �U[U+64CA]Save�5�

l:z1°^�AøçÇgi�o�U�AÇg�

3.2.8 Éñøçx§

£Í�øçè� A[¶,Connexions��5.øçÏA[U+6B77]¶x§,ò³X.øçT¶Ax§«¶B �Í�øçA[U+6BCF]Íê�x§�¢#Í��y�å,[U+60A8]a«Éñ[U+6BCF]Í�øçA¸#x§,«³Xl[U+60A8]Az1��

1. �lz1°^�U[U+64CA]øçÇg,øç� A5Edit6(A[)Ç×i�w�lÖtå#�2. �Éñ[U+60A8]�^³Xlz1�Aøçx§,U[U+64CA]Versionx§,`¥�,I º5Always use newest

version6(2³XT�x§)�3. �U[U+64CA]Save�5�

3.2.9 A[ [U+589E]`å^

åâ«�B �«U[U+64CA]åìAjù,^ñóAÜ9 È½,ò:@[U+5167]Mãhz1�AÍ�[U+4EFD]�åâ«lz1� � #x, ��9Aøç� ��lÍ�5lAøç�,÷\[U+60A8]k6å^��A��,{�^ñ[U+60A8]z1�ãøç4óAõÌ�

3.2.9.1 A[¶5lAå^

1. �lz1°^�U[U+64CA]øçÇg,øç� A5Edit6(A[)Ç×i�w�lÖtå#�2. �U[U+64CA]5Links6(å^)Ç×�3. lÇ×A5Edit Links6(A[å^)äju�,�l5Name6(çe)�5Link Type6(å^2S)��5Strength6(Äp)�É�-�DÂ��

4. k6[U+60A8]ãú^w�løç�A÷\å^,�Éñ5Delete6(ç£)z�AÉújÅ�5. �U[U+64CA]Update Linksè�å^�

£.øç B é,.��+.k�uA[�Aå^ØÌ,òiw�l5Links6(å^)�×��

3.2.9.2 [U+589E]`å^ÕÍøç

1. �lz1°^�U[U+64CA]øçÇg,øç� A5Edit6(A[)Ç×i�w�lÖtå#�2. �U[U+64CA]5Links6(å^)Ç×�3. º )óÍ��å^,lÇ×A5Add a New Link6([U+589E]`Í��å^)äju�,�l5Enter a

Name6()óÍ�çe)�É��óå^çe�4. �l5Link Type6(å^2S)�É"AY¶ØÌÁÉñåÂÅ9�


27

5. �l5Strength6(Äp)�É"AY¶ØÌÁÉñåÂl^n�6. �l5Module ID6(øçA�) 5Link URL6(å^ÿÇ)�É�)óåÂ�Ç�7. �U[U+64CA]Add[U+589E]`�

£.øç B é,.åî�w�l5Links6(å^)�×�,/mS÷\a�A�uA[�Aå^�

3.2.10 l�£&Ü¦

z1A[��4¿8jl,«¶l�£&Í�z1�AÜ¦��;eÍ�jl+³XÏê�ÏY¾¡,«lÍ�z1� ¢�X«½¥��;eè�jl+³XCutñY�PasteTê¥�,X«½¥��,�z1Õ¢�, �¢Õ¢��

3.2.10.1 ³XÏê�ÏY¾¡l�£&

^lÍ�z1� ¢�³XÏê�ÏY¾¡½¥��,�®YØ[U+6B65]¤:

1. �lz1A[��Éñ5Content6(Ü¦)Ç×�2. �lz1�U[U+64CA]z1Çg,X«l�£&Ü¦��; �U[U+64CA]Í�¢AÇg,X«lÖ�¢�l�£&Ü¦��;Ò¶Aå#i�w�z1 �É¥uAÜ¦ØÌ�3. �l5Move6(½¥)z�U[U+64CA]Ïê� ÏY¾¡,«lz1 ¢�iÍ�Ü¦��l�Ã#ÕÍã¦±;«�A¿�¾¡�iÜ¦��½¥ÕeÍ� T¶Í�±,[U+5167]�A¿�¾¡�iÜ¦��½¥<ê <YÍ�±�

Figure 3.6: 5Title6(Çg)�5Move6(½¥)z�

3.2.10.2 ³X5Cut6(ñY)�5Paste6(Tê)¥�l�£&

^³XCutñY�PasteTê¥�½¥��,�z1Õ¢�, �¢Õ¢�,�®YØ[U+6B65]¤:

1. �lz1A[��Éñ5Content6(Ü¦)Ç×�2. �lz1°^�U[U+64CA]z1Çg,X«lz1�ñY�Tê��; �lz1°^�U[U+64CA]Í�¢Çg,X«lÖ�¢�ñY�Tê��;Ò¶Aå#i�w�z1 �ÉA¢AÜ¦ØÌ�3. �l[U+60A8]�^½¥A��E#ÉñÉújÅ�4. �U[U+64CA]CutñY�5. k6[U+60A8]�^TêÜ¦��A¢,�lz1°^�U[U+64CA]¢AÇg�6. �U[U+64CA]PasteTê,Ü¦��iw�lz1°^�A�ÉA¢%Y,òé��uAz1 ¢Çg�È��

3.2.11 ½£z1Ü¦

^�Í�z1 Í�z1�A¢½£Í�Ü¦��,�®YØ[U+6B65]¤:

1. �lz1A[��Éñ5Content6(Ü¦)Ç×�2. �U[U+64CA]z1Çg,X«�z1�½£Í�Ü¦��; �U[U+64CA]Í�¢Çg,X«�µ¢½£Í�Ü¦��;Ò¶å#i�w�µ¢AÜ¦ØÌ�3. �Éñ�bAÉújÅ«E½£�4. �U[U+64CA]Remove½£,.��i��z1 ¢� ½£�




3.2.12 Ã#»¦�{AA[�AÌ#

^Ã#[U+60A8]�»¦�{AA[�AÌ13 #,�®YØ[U+6B65]¤:

1. �lz1A[��Éñ5Roles6(Ì)Ç×�2. lÂ5%åjÅ�,��ó[U+60A8]�^¢#A[��Ü¦¾¿�� xçè4�A0Açå,:�0»?4Í�ConnexionsÛ��3. �U[U+64CA]SearchÂ5,i�w�ó�Â5å�AÛ�è4�ç��4. �Éñ�DA»¦�{�AÉújÅ�5. �U[U+64CA]Add People[U+589E]`0Ø,Öt%�iw�5Roles Pending Ap-

proval6(ÌÍ#úa)jÅ�6. �Éñ.0�C�ÌAÉújÅ, �ãÉñ�7. k6�4[U+60A8]�^lÍ�z1»¦�{A0,�l�[U+6B65]¤2Õ5�8. �U[U+64CA]Update Rolesè�Ì�

ConnexionsÈ¶��AA[�l;�Yêgóé,ÌA^�hoòÍ[A;{^:@^� �>,:@Ì¶ ú#ºh¶� ��C�A51ç��

3.2.13 ±Çd1�

lã¦z1�Aøça«³Xã¦Ajl!�¦A��,ÈôÏ±�[U+865B]�;[U+60A8]a«³X^ñ1�,l[U+60A8]Az1�Éñ:@��!�Ajù�^l[U+60A8]Az1� #:@1�,�®YØ[U+6B65]¤:

1. �lz1A[��Éñ5Parameters6(1�)Ç×�2. �Éñ�DÇdA,`¥�,I w�leÍz�3. �U[U+64CA]Update Propertiesè�yn�

Connexions³X¸9AÇd1�,«lz1�^ñ�4Aøç�

3.2.14 IÖz1

�lz1A[��Éñ5Preview6(IÖ)Ç×,«^ñê¿Az1,½%Í�Sya«B .oAz1;.IÖÊ��[U+60A8]a«£�[U+60A8]�ú^^ñAz1�

3.2.15 á[U+4F48]z1

Í�¶á[U+4F48]Az1a«�ÿjÿìêú^B WA÷\0a« µ�,Í�o.z1,[U+60A8]i^lConnexions�á[U+4F48]�

1. �£�[U+60A8]�^AÆ~Ü¦�Ì��z1A¿êx§�2. �lz1A[��U[U+64CA]5Publish6(á[U+4F48])Ç×�3. �l5Description of Changes6(è�[U+8AAA]é)�É��ó.z1K4xA#��~,.¥%å�^ñl.z1AK4[U+6B77]¶ÿ4ê�4. �U[U+64CA]Publishá[U+4F48]�

.z1¶á[U+4F48]lConnexions�,[U+60A8]a«l÷\éÆ³Xz1A[��[U+67E5].z1,«�-�K4�

È¶: lConnexionsá[U+4F48]Í�z1Ï,.z1»?4Í�0eºA[��Ü¦¾¿��xçè4�Ì;.«,.z1Z4oòÍ[AÌ^�,�4ÌA^�»? �> ¨[U+7D55]�

3.2.16 A[Í�¶5lAz1

[U+60A8]a«�X[U+60A8]m�Í��z1¦Ajl,³Xz1A[�A[Í�¶5lAz1;[U+60A8]{a«A[[U+60A8]�4Ü¦¾¿�ÌAÖ@z1�^kÍ�¶5lAz1³Xz1A[�,�¦[U+555F][U+60A8]AØ{/ Ø{%ç,«�®YØ[U+6B65]¤:

1. �U[U+64CA]Search for Published ContentÂ5¶á[U+4F48]Ü¦,i�^ñ5Search the Connex-ions repository6(Â5ConnexionsÜ¦�)Öt�

2. �lÂ5%åjÅ�)óãz1óAå å��

13http://cnx.org/help/reference/roles


29

3. �¥£5Modules6(øç)AÉújÅ,�Y�ÉA5Course6(z1)ÉújÅ�4. �U[U+64CA]SearchÂ5,i�^ñó�.Â5å�A�bØÌ�5. �Éñ�Dz1AÉújÅ�6. ��5Add selected content to6([U+589E]`�ÉÜ¦)Y¶ØÌÁÉñ.z1�^i±AØ{/ Ø{%ç�7. �U[U+64CA]Add[U+589E]`,.z1i[U+589E]`Õ[U+60A8]�Ã#AØ{/ Ø{%ç�8. �lz1A[��D¦.z1,ô¦.¥uÏõm�Í��z1 (Section 3.2.2: m�Í��z1)Y�yAjl-�A[�

3.3 A[øç14



3.3.1 aÌhøç(Module)?

øçhÍ�Connexionsz1AI§ìm��[U+60A8]a«�Wú�oÍ�Ü¦�,�õ^7%å�¿?�«�CNXML[U+6A94]§,ÇñÍ��Í0g, Í�0gAÍ�¸5B��øçAA[�[#øçAd³�ôi4»^,[U+6BCF]Í�øçwµ^7a«X�Ä[U+6490]A*[U+5920]Ü9�k6Í�SyB Í�z1,Í�øçhÍ�#�Aÿ4,74Í�¸#0gAÜ9�øça«�SylÍ�z1�ÙÓÜ9Aì�,ò:ì�h:z1A[��£&A; ��a«D��§c$ò�Sy�Q4;�ô�Aì��k6Í�z1A[�iÜ¦ÍfilÍ�z1�,lã¦Aøç�4ã¦A0g,$¸6Éñ�£&:@Ü9�mìÍ�z1é,z1A[�a«�9Az1��5lAøç^7-u, �3;ASg³É,{^:k6z10gA!�hl^A�ôFigure 3.7�ñ,ºÍ��øçAÜ¦÷È,^ñ5Manage Files6("�[U+6A94]§)ÖtA5File6([U+6A94]§)Ç×�

Figure 3.7: Í�{74index.cnxml[U+6A94]A�øçA5Files6([U+6A94]§)Ç×�

14This content is available online at <http://cnx.org/content/m13493/1.3/>.15"Overview of Authoring Modules" <http://cnx.org/content/m10887/latest/>[email protected]@cnx.org




3.3.2 øç[U+72C0]S�×

k6øçA[�4�XnAØ{,øç[U+72C0]S (Figure 3.8)�×�4ãøç��å^4óAl^[U+72C0]SÜ9��×w�løçÜ¦å#,74YØ��:

• State [U+72C0]S (p. 19) � øçA�Ï[U+72C0]S�• Last action T¶A¥{ � k6øç�-�AT¶¥{A0�é/�• Actions ¥{ � k6�Aøç,.��^ñå^ÕConnexionsÿ4,«Eiøçá[U+4F48]

(Section 3.3.11: á[U+4F48]øç)ÕÜ¦É»�ª,«�[U+62CB]W (Section 3.3.10:[U+62CB]W[U+60A8]Aè�)k6øçA�Ïÿ{�A[Í�¶5lAøçé,.��^ñ3;å^,m{A[(Section 3.6)¢�¢�A[�A[m{,«�kÍ�¶5løçm�ly§ (Section 3.5)�

• View B � k6�Aøç,.��^ñøçA¿ê (Section 3.3.9.1: ¿êIÖøç)x§�ØÖ(Section 3.3.9.2: IÖøçAÍ�ØÖx§)x§��CNXML�º8 (Section 3.3.9.4:IÖA8�)å^�A[Í�¶5lAøçé,.��^ñÍ�=^,Øwl[U+60A8]AØ{�É�T¶á[U+4F48]x§/øçx§AF¼(Section 3.3.9.3: B è��^)�

Figure 3.8: Í��øçA5Module Status6(øç[U+72C0]S)�×�

3.3.3 A[øç

Í�[U+60A8]¶�m� (Section 3.1.2.1: m��)Í��Aøç, �[U+589E]` (Section 3.1.2.2:�Ü¦É»�ª[U+589E]`¶5lA��)Í�¶5lAøçÕ[U+60A8]AØ{�É,[U+60A8]iD^A[.øç«[U+589E]`Ü¦�[U+6A94]§�¿?��:@ÿ{h«å^-�,«�:5Manage Files6("�[U+6A94]§)Öt 5Module Status6(øç[U+72C0]S)�×êA¥�u-�ÿ{�k6��:@ÿ{Am{,il.øç��[U+8AAA]é,«�YØAÍ@ÿ{:

1. A[CNXML (Section 3.3.4: A[ CNXML [U+6A94]§)[U+6A94]§�2. [U+589E]` (Section 3.3.5: [U+589E]`óãA[U+6A94]§ÕÍ�øç)÷\[U+60A8]úºãøç4óãA[U+6A94]§�3. A[Æ~Ü¦ (Section 3.3.6: A[Æ~Ü¦),«)óC�AÂ5%å�øçÇg�4. A[øçÌ (Section 3.3.7: A[øçÌ)�5. [U+589E]`å^ (Section 3.3.8: [U+589E]`å^ÕÍ�øç)Õµøç�6. IÖ (Section 3.3.9: IÖøç)øçAØÖx§�¿êx§�


31

7. á[U+4F48] (Section 3.3.11: á[U+4F48]øç)øç�

A[øçA:@ÿ{��ilYØÁ¥Á��

3.3.4 A[ CNXML [U+6A94]§

k6øçA5Edit6(A[)Ç×^ñ5index.cnxml6[U+6A94]§A[U+5167]M�.[U+6A94]§^7w�løç�A%å,«�CNXMLAÃñ[U+8AAA]é,^7÷\¿?��X� 3;w�løç�A[U+6A94]§�I h«Edit-In-Place(£ñA[)A[H^ñÜ¦�-�A[� �,[U+60A8]a«U[U+64CA]Switch to Editing Full

Source("�ÕA[Ó��º[U+6A94]),ò«5Full Source6(Ó��º[U+6A94])A[H^ñ�A[Ü¦��:Ç×[U+60A8]a«k[U+6A94]§-�YØ¥{:

• )óÜ¦Õindex.cnxml[U+6A94]§� (Section 3.3.4.1: )óÜ¦Õindex.cnxml[U+6A94]§�)• )windex.cnxml[U+6A94]§ÕÍ�«�AXMLA[H (Section 3.3.4.2: )windex.cnxml[U+6A94]§ÕÍ�«�AXMLA[H)• ³XEdit-In-PlaceA[HA[index.cnxml[U+6A94]§ (Section 3.3.4.3: ³XEdit-In-

PlaceA[HA[index.cnxml[U+6A94]§)• ³XFull SourceA[HA[index.cnxml[U+6A94]§ (Section 3.3.4.4: ³XFull

SourceA[HA[index.cnxml[U+6A94]§)• ³X«�%bA[HA[index.cnxml[U+6A94]§ (Section 3.3.4.5: ³X«�%bA[HA[index.cnxml[U+6A94]§)

Figure 3.9: 5Edit6(A[)Ç×^ñlEdit-In-PlaceA[HøùYAindex.cnxml[U+6A94]§Ü¦�




3.3.4.1 )óÜ¦Õindex.cnxml[U+6A94]§�

^)óÜ¦Õindex.cnxml[U+6A94]§�,�®YØ[U+6B65]¤:

1. lImport)ó¥�",��Y¶É�ÁÉñ[U+60A8]�^)óA[U+6A94]§Åù,aXAÅùº:MicrosoftWord18 �OpenO�ce Writer�XMLSpy/Authentic (Section 6.1) � Plain XML�

2. �U[U+64CA]Import)ó¥�,i�4Í�Öt^ñÍ�%åjÅ,�[U+60A8]Mêú^)ó[U+6A94]§Aì�ç�3. �l%åjÅ��ó[U+6A94]§ì�ç, ³XBrowseë@«l%åjÅ�^ñ[U+6A94]§ì�ç�4. �U[U+64CA]Import)ó¥�,[U+60A8]�Ã#[U+6A94]§AÜ¦i�~Õ[U+60A8]øç�Aindex.cnxml[U+6A94]§��

L�: £[U+60A8]lT¶§¥U[U+64CA]Import)ó¥�é,index.cnxml[U+6A94]§AÜ¦i� )ó[U+6A94]§AÜ¦��³�

3.3.4.2 )windex.cnxml[U+6A94]§ÕÍ�«�AXMLA[H

[U+60A8]a«)windex.cnxml[U+6A94]§,�[U+60A8]a«³XA[XML[U+6A94]§Aå²|b-�A[�index.cnxml[U+6A94]§»?"�Õ�XMLA[Ha«�1�òéÍ�[U+60A8]¶�oA[,»?Sê"�[U+6A94]§«��A[HAa�n�ConnexionsA)w�)óÊ�,�ô¥[U+589E]`�½£A[Ha�nA��Ï,Connexions{Ä&XMLA[H,³XAltova19

xmlspy® A[H, Altova authentic® A[H�

^)windex.cnxml[U+6A94]§ÕÍ�«�AXMLA[H,�®YØ[U+6B65]¤:

1. lExport)w¥�",��Y¶É�ÁÉñ[U+60A8]�^ÛwA[U+6A94]§Åù,aXAÅùº:XMLSpy/Authentic(Section 6.1) � Plain XML�

2. �U[U+64CA]Export)w,i�^ñÍ�k�jÅ,Y [U+60A8]h�^¦[U+555F].[U+6A94]§ �5Õð[U+789F]�3. �Ã#[U+60A8]�^�5Õð[U+789F]A[U+6A94]§�4. �Ã#[U+60A8]�^�5[U+6A94]§Aì�ç�5. �¦[U+555F][U+60A8]AXMLA[H«A[[U+6A94]§�

^)ó[U+6A94]§�¥ÕConnexions�,�®.øçÁêj�,�[U+5167]M,�Connexions«�)óÜ¦ (Sec-tion 3.3.4.1: )óÜ¦Õindex.cnxml[U+6A94]§�)A�×�

3.3.4.3 ³XEdit-In-PlaceA[HA[index.cnxml[U+6A94]§

Edit-In-PlaceA[Hhl5Edit6(A[)Ç×ê�I AA[H�[U+60A8]a«Öó�A%å�1²�bÕÍ�øç�, ³X.A[HKvÍ�øç¶5lAÜ¦�[U+60A8]ã»v�CNXMLÇ×«³XEdit-In-Place�£[U+60A8]l[U+6A94]§�)óÍ��A��é,W�º[U+60A8]ÖóC�ACNXMLÇ×�.«,4[U+8AAA]é%å,X«Ðy[U+60A8]�ÖóA�� A[éACNXMLÇ×�

3.3.4.3.1 ÖóÜ¦ÕÍ�Aøç�

^Öó%å�1²�bÕÍ�A�øç�,�®YØ[U+6B65]¤:

1. lEdit-In-PlaceA[H�,�U[U+64CA]l jÅ�A5Click To Insert Text6(U[U+64CA]«Öó%å)�

18http://cnx.org/help/UsingMSWord19http://www.altova.com


33

Figure 3.10: Edi-In-PlaceA[H�A5Click To Insert Text6(U[U+64CA]«Öó%å)%åjÅ�

jÅ:Í�|A[jÅ�1b�

2. �l|jÅ�A5Insert Module Text Here6(l.Öó%å)Ü�ó[U+60A8]úÂ%å�

Figure 3.11: Edi-In-PlaceA[H�A5Insert Module Text Here6(l.Öó%å)A[jÅ�

3. �U[U+64CA]Save�5«�5[U+60A8]��óA%å,|A[jÅi:Í� jÅ�1b,«^ñ[U+60A8]A)ó�

3.3.4.3.2 ³XEdit-In-PlaceA[¶5lAÜ¦

Â[Í�øçAÜ¦,�®YØ[U+6B65]¤:

1. �³XEdit-In-Place^ñ[U+60A8]�Â[Aøç�2. �Y¶«^ñ[U+60A8]úÂ[��A %åjÅÜ�3. �U[U+64CA]%åjÅ, jÅ�:Í�|A[jÅ�1b,^ñ��%å�




Figure 3.12: Edi-In-PlaceA[H�A|A[jÅ�

4. �k.��-�»Âè��5. �U[U+64CA]Save�5«�5)óA%å, �U[U+64CA]Cancel1È«w£|A[jÅÁ)óA%å�6. �l�[U+6B65]¤2Õ5,«A[[U+60A8]A��

È¶: l %åjÅÁ,�Sù½A^ñI�løçÁ�^ñAô½�l|A[jÅÁ,�Sù½«MathML½�jù^ñ;A[ù½»?"�oMathML�

3.3.4.3.3 ³XEdit-In-Place[U+589E]`Ü¦��

[U+60A8]a«³XEdit-In-Place[U+589E]`�AÜ¦��ÕÍ�øç,[U+60A8]a«[U+589E]À��4ù4:%å¥u��Ø�U��[U+9304]�ù½�{Ý�¿?�A8�½d��È½��Edit-In-Placel��"�¦[U+555F]�ó1CNXMLÇ×,i[U+7522]yÍ�*ÍA��ID�^[U+589E]`��,�®YØ[U+6B65]¤:

1. �³XEdit-In-Place^ñ[U+60A8]�Â[Aøç�2. �Y¶«^ñ[U+60A8]ú^ÖóÜ¦��AøçÁ±,[U+60A8]a«�:³XAdd

Here.Ü[U+589E]`¥�,l¶5l��Aêj YjÜ)ó��3. lAdd Here.Ü[U+589E]`¥�",��Y¶É�ÁÉñ[U+60A8]�^)óA��4ù,I º5Paragraph6(%å¥u);:@��4[U+8AAA]é%å,a«�Y¶É�ÁÉñ5Other

Elements6(3;��)u�1�4. �U[U+64CA]Add Here.Ü[U+589E]`,k6[U+60A8]�ÉA��iw�Í�A|A[jÅ;[U+60A8]a«�:l|jÅåêÌÁU[U+64CA]Help

editing xxx A[[U+8AAA]é,^ñ[U+60A8]�É��A[U+8AAA]é%å,3Áxxxh[U+60A8]�É��ACNXMLÇ×�5. �l|A[jÅÁ�óC�A��4ù�6. �l|A[jÅÁU[U+64CA]Save�5«�5)ó, �U[U+64CA]Cancel1È«w£)ó�7. �l�[U+6B65]¤2Õ6,«løçÁ[U+589E]`�AÜ¦��

3.3.4.4 ³XFull SourceA[HA[index.cnxml[U+6A94]§

[U+60A8]a«³XFull SourceA[H,lConnexionsAindex.cnxml[U+6A94]§�A[Ü¦�CNXMLÇ×;m{A[AjläCX6�+�è[U+5167]M�:h#�A%åA[H,/Z4«Ý%åA[H-§AÊ�,Èô[U+62FC]å�[U+67E5]�%åÂ5�^³XFull SourceA[HA[[U+6A94]§,�®YØ[U+6B65]¤:

1. �l5Edit6(A[)Ç×êU[U+64CA]Switch to Editing Full Source "�ÕA[Ó�A8�,index.cnxml[U+6A94]§�AÜ¦i�^ñlFullSourceA[HøùY�


35

Figure 3.13: lFull SourceA[HøùY,5Edit6(A[)Ç×^ñindex.cnxml[U+6A94]§�AÜ¦�

2. �Y¶«^ñ[U+60A8]ú^ÖóÜ¦��AøçÁ±�3. �U[U+64CA]%åÖt¦ºA[�4. �U[U+64CA]Save�5«�5[U+60A8]Aè��

£[U+60A8]A[index.cnxml[U+6A94]§é,�CéU[U+64CA]Save�5«�5[U+60A8]Aè��l[U+6BCF]ê[U+60A8]�5[U+60A8]Aè�é,4õ��1��[U+60A8]ACNXML�#¥{y��ôiZ4CNXMLÇ×�¾,[U+60A8]A�#h4�A,5Saved6(¶�5)�w�lÇ×êjAÜ9jÅÁ�ôil[U+60A8]ACNXML�#Á4�¾,�Øl[U+6A94]§Ü¦êj�

È¶: �5�á[U+4F48]h¿8�Òã¦Aþ{�£[U+60A8]lFull SourceA[HÁ�5[U+60A8]AA[è�é,[U+60A8]�-�Aè��5l[U+60A8]AØ{�ÉÁ;/ã-óConnexionsÜ¦�Á�[U+60A8]»?á[U+4F48][U+60A8]Aøç«-óÕÜ¦�Á,òa«�å�ÕConnexionsAB �51�ó6á[U+4F48]AÜ9,� .øçÁ_¶Aá[U+4F48]øç(Section 3.3.11: á[U+4F48]øç)�

3.3.4.4.1 lFull SourceA[H��[U+67E5][U+60A8]AØ{

[U+60A8]á[U+4F48]lConnexionsÜ¦��A÷\index.cnxml[U+6A94]§,»?hÍ�4�ACNXML%b,«�[U+6A94]§»?^ìqéZ4CNXML�¾;ôi4�¾,£[U+60A8]U[U+64CA]Save�5éi�w�[U+6BCF]Í��¾A�y(Figure 3.14)�÷��4�¾k¶Kv,[U+60A8]Za«�5[U+60A8]A��




Figure 3.14: lFull SourceA[H�A�[U+67E5]�¾AÈ½�

�¾A�yw�lÜ¦êjAÜ9jÅÁ�

L�: [U+60A8]ã�lConnexionsÁá[U+4F48]øç,÷��4ACNXML�¾k¶�4v,éindex.cnxml[U+6A94]§h4�A�

3.3.4.5 ³X«�%bA[HA[index.cnxml[U+6A94]§

[U+53E6]Í8A[index.cnxml[U+6A94]§Ajlh³XÍ�«�%bA[H,/ã¸9 J6X{XMLA[H��È¶,£[U+60A8]l5Files6([U+6A94]§)Ç×êB øçé,Í�³A3½¥��w�lindex.cnxml[U+6A94]§[U+6A94]çåj;�U[U+64CA].¥�,«lÍ�«�%bA[Hê��A[index.cnxml[U+6A94]§�.A[jlhº[U+60A8]Yi�êiindex.cnxml[U+6A94]§,}W{hÍ�%bA[H,[U+60A8]»?3¥)ó�4ACNXMLÇ×�ôi[U+60A8]ãv�CNXML,.jlÎÈé��;.jll[U+60A8]³XÏ,�D^[U+60A8] [U+60A8]AB�"�Ø #«�A[H«{º.cnxml2ù[U+6A94]§AI A[H�.«,[U+60A8] [U+60A8]AB�"�Ø»?lWindows�ÂÁ£�ZopeExternalEditor, �lMacintosh�ÂÁ£�Zope EditManager�

3.3.5 [U+589E]`óãA[U+6A94]§ÕÍ�øç

£ index.cnxml[U+6A94]§,Í�øça^73;A[U+6A94]§,Èôãøç4óãA¿?�[U+6A94]§��CNXML%b�[U+60A8]a«�5Files6([U+6A94]§)Ç×[U+589E]`:@[U+6A94]§;l[U+60A8][U+589E]`ÕøçÏ,:@[U+6A94]§»?5l�[U+60A8]a«lÖ«A[U+6B65]¤Ám�CNXML%b�£[U+60A8][U+589E]`:@��é,[U+60A8]lConnexions�¶m�:@��A5l�

3.3.5.1 [U+6A94]§"�^³

l[U+60A8][U+589E]`Í�óã[U+6A94]§ÕÍ�øçÏ,�È¶YØ[U+6A94]§�[U+6A94]çA"�^³:

• [U+6A94]§d³»?³610MB�• [U+6A94]çAeÍ�åYã�h�å�Èô,[U+6A94]çº51965mustangphoto.gif6i¨²�¾,�l�èç

(Section 3.1.2.5: lÍ�Ø{�É�l�èç��)[U+6A94]çº5photo1965mustang.gif6«£ñ�¾�


37

• [U+6A94]çã�^7¯óùÅ�Èô[U+6A94]çº5ei�el tower.png6i¨²�¾,�l�èç (Sec-tion 3.1.2.5: lÍ�Ø{�É�l�èç��)[U+6A94]çº5ei�el_tower.png6 5ei�eltower.png6«£ñ�¾�

• �l[U+6A94]ç�{�³X�%åY �å�"."(U)�"-"([U+6A6B]¿)��"_"(%¿)��• <1²[U+6A94]§ (Section 3.4)»?4Í�úaAMIME½#(Multipurpose Internet Mail Exten-

sion)2ù�

3.3.5.2 [U+589E]`Í�¿?ÕÍ�øç

^[U+589E]`Í�¿?ÕÍ�øç,�®YØ[U+6B65]¤:

1. �U[U+64CA]Add New Item[U+589E]`��"A%åjÅÁAÏY¾¡,i�w�Í�4��AY¶ØÌ�2. ��Y¶ØÌÁÉñ5Image6(¿?),/U[U+64CA]Add New Item[U+589E]`��,i�w�5Edit Im-

age6(A[¿?)Ç×�3. �U[U+64CA]Browseë@,i�^ñ5File Upload6(ê¢[U+6A94]§)k�jÅ�4. �Éñ¿?[U+6A94]§C�i±A±,/U[U+64CA][U+6A94]ç�5. �U[U+64CA]Open¦[U+555F],¿?[U+6A94]çi�w�lBrowseë@"A%åjÅÁ�

6. �U[U+64CA]Save�5«ê¢¿?[U+6A94]§ÕConnexions,i�^ñÍ�Éú9&�¿?IÖ�

3.3.5.3 [U+589E]`Í�[U+6A94]§ÕÍ�øç

^[U+589E]`Í�[U+6A94]§ÕÍ�øç,�®YØ[U+6B65]¤:

1. �U[U+64CA]Add New Item[U+589E]`��"A%åjÅÁAÏY¾¡,i�w�Í�4��AY¶ØÌ�2. ��Y¶ØÌÁÉñ5File6([U+6A94]§),/U[U+64CA]Add New Item[U+589E]`��,i�w�5Edit

File6(A[[U+6A94]§)Ç×�3. �U[U+64CA]Browseë@,i�^ñ5File Upload6(ê¢[U+6A94]§)k�jÅ�4. �Éñ[U+6A94]§C�i±A±,/U[U+64CA][U+6A94]ç�5. �U[U+64CA]Open¦[U+555F],[U+6A94]§çeiw�lBrowseë@"A%åjÅÁ�

6. �U[U+64CA]Save�5«ê¢[U+6A94]§ÕConnexions,i�^ñÍ�Éú9&�[U+6A94]§AÜ9�

3.3.5.4 [U+589E]`Í�CNXML%bÕÍ�øç

^[U+589E]`Í�CNXML%bÕÍ�øç,�®YØ[U+6B65]¤:

1. �U[U+64CA]Add New Item[U+589E]`��"A%åjÅÁAÏY¾¡,i�w�Í�4��AY¶ØÌ�2. ��Y¶ØÌÁÉñ5CNXML Document6(CNXML%b),/U[U+64CA]Add New

Item[U+589E]`��,i�w�5Edit CNXML File6(A[CNXML[U+6A94]§)Ç×�3. �)óÜ¦ÕCNXML[U+6A94]§,�ó%åÕ5Edit Directly6(÷�A[)jÅÁ,ê¢Í�[U+6A94]§, )óÍ�[U+6A94]§�4. �U[U+64CA]Save�5,i�^ñÍ�Éú9&�ó6CNXML[U+6A94]§AÜ9�

3.3.5.5 lÍ�øç�l�èç�ñT��~�«�½£��

[U+60A8]a«l�èç�ñY��~� ½£÷\��ÕÍ�øç�:@ÿ{løç� Áo,ô¦lØ{�ÉÁA� �� Í�Ø{�É½£��(Section 3.1.2.4: �Í�Ø{�É½£��)�lÍ�Ø{�É�l�èç�� (Section 3.1.2.5:lÍ�Ø{�É�l�èç��)�«�lÍ�Ø{�É�ñT �~�� (Section 3.1.2.6:lÍ�Ø{�É�ñT �~��),««�ô\lØ{�É�-�Ö@ÿ{�

È¶: [U+60A8]ãwµl�èç�ñY��~� Têindex.cnxml[U+6A94]§�




3.3.6 A[Æ~Ü¦

º �[U+5920]�³X�lConnexionsÜ¦É»�ªÂ5øç,Connexions»?4øçAÍ@óÜ9;Ù.[U+60A8]ÖóÆ~Ü¦(Figure 3.15)Õøç�h¤ôl^A�

Figure 3.15: 5Metadata6(Æ~Ü¦)Ç×�)óçe�ó�å�=^AÈ½�

^ÖóÆ~Ü¦,�®YØ[U+6B65]¤:

1. �U[U+64CA]5Metadata6(Æ~Ü¦)Ç×«^ñwu�2. �l5Name6(çe)�É��ó[U+60A8]�^¢DøçAçe,.çei�w�lConnexions�AøçÇg�3. �l5Keywords6(ó�å)�É��ó0gó��,�³X�a«Â5�øç,�l[U+6BCF]ÍØê)óÍ��4. �l5Abstract6(=^)�É��óøç0gAÍ�#�Ðy��l=^�l�øçÇg;=^^ñløç�AÇgYj,Ù.l=^�lyøçÇgh<pA�5. �U[U+64CA]Save�5,i�^ñÍ�9&[U+8AAA]éÆ~Ü¦¶ è�,lÖtÇg�øçAçå�1b5New

Module6(�øç)�

3.3.7 A[øçÌ

{ºÍ�øçAm��,I Á[U+60A8]Q4�4��Ì20 :A[��Ü¦¾¿��xçè4��[U+60A8]a«Aç¢3;ConnexionsÛ�è4�Í� <�Ì,{^[U+60A8]ú^�;1ã.øç�%�ÌÅA5Roles6(Ì)(Figure 3.16)Ç×^ñ³X�çe�;��ÏAÌ�l5Author6(A[�)�5Maintainer6(Ü¦¾¿�)� 5CopyrightHolder6(xçè4�)zÁAÉújÅ�Ãw Aç.ÌA0�

20http://cnx.org/help/reference/roles/document_view


39

Figure 3.16: 5Roles6(Ì)Ç×�

3.3.7.1 Aç3;³X�Ì

Âç3;³X�Ì21 ,�®YØ[U+6B65]¤:

1. �U[U+64CA]5Roles6(Ì)Ç×«^ñwu�2. �lSearchÂ5"AÉújÅÁ�ó[U+60A8]úÂçÌA³X�çå�3. �U[U+64CA]SearchÂ5,i�Â5ConnexionsÛ��ó�Â5å�A�4³X�wu�4. �ÉñDÂ³X�çe"AÉújÅ,/U[U+64CA]Add People[U+589E]`0Ø,i�4Í�5Roles Pend-

ing Approval6(ÌÍ#úa)Ì^ñl5Roles6(Ì)ÌÅYj�5. �£�5Author6(A[�)�5Maintainer6(Ü¦¾¿�)� 5Copyright Holder6(xçè4�)zÁAÉújÅ,«EÉú[U+60A8]�Âç³X�AÌ,I [U+72C0]Ìh�4ÉújÅkÉ#�6. ôiD^,�¥£[U+60A8]ãúÂçAÌ,U[U+64CA]Update Rolesè�Ì�

7. ³X�l;YêgóÕConnexionsé,i�^ñÍ�^�«�>.Ì�

lAç è�[U+53E6]Í�³X�AÌé,:��è/ã�y�,÷�3;³X�¶��>:�ÌA�è;Í�³X�úa:�è,;��AÌi�p�l5Roles6(Ì)ØÌ��[U+67E5][U+95B1]úaÌ^�(p. 40)«Èµè<úa^�AÜ9�

È¶: lÍ�øçá[U+4F48]Ï,�4Í#ÌA�è»? �> ¨[U+7D55]�

3.3.7.2 B �-�Í#Ì^�

Connexions�ÊÊm¦A»¦�{èºM¸,3ÁÍ�jlh�´Í�øç z1Aî{ç è4ç�ôi[U+53E6]Í�A[�l;�Aøç z1ÁAç[U+60A8]Í�Ì,[U+60A8]a«ã;�Íf�{,5Pending6(Í#)(Figure 3.17)�×iw�l[U+60A8]Connexionsÿ4Aåêj�

21http://cnx.org/help/reference/roles/document_view




Figure 3.17: Í�Ì^�A5Pending6(Í#)�×�

�U[U+64CA]Role RequestÌ^�å^,«^ñ5Collaboration Requests6(»¦�{^�) (Fig-ure 3.18)Öt��:Öt[U+60A8]a«:

• ^��Æ[U+60A8]Aúa (Section 3.3.7.2.1: ^��Æ[U+60A8]Aúa)• [U+60A8]�áwA^��Æ[U+53E6]ÍA[�Aúa (Section 3.3.7.2.2: [U+60A8]¶áw^�)• o^� (Section 3.3.7.2.3: o^�)

Figure 3.18: 5Collaboration Requests6(»¦�{^�)Öt^ñÍ�^��Æ[U+60A8]Aúa,«�Í�^��Æ[U+53E6]ÍA[�Aúa�

3.3.7.2.1 ^��Æ[U+60A8]Aúa

ôi[U+53E6]Í�ConnexionsAA[�l;�Aøç z1êAç[U+60A8]Í�Ì,oºA[��Ü¦¾¿�� xçè4�,i�l5CollaborationRequests6(»¦�{^�)ÖtA5Request Awaiting Your Approval6(^��Æ[U+60A8]Aúa)ÜYjw�Í�óÎ�,^�>^�,�Éñl[U+60A8]N��>^�AÌÅ�AÉújÅ,/U[U+64CA]Accept�>�,^¨[U+7D55]^�,�Éñl[U+60A8]N�¨[U+7D55]^�AÌÅ�AÉújÅ,/U[U+64CA]Reject¨[U+7D55]�

È¶: ôi[U+60A8]¶ ^�[U+589E]`Í�øç z1oºxçè4�,l[U+60A8]�>^�Ï,[U+60A8]»?ÉñÖ�øçAÉújÅ«Ãñ[U+60A8]¦¶.Açúa;lÌÅA5License6(Aç)z�i,¶Í�å^ÕAça�


41

3.3.7.2.2 [U+60A8]¶áw^�

ôi[U+60A8]l[U+60A8]AÍ�øç z1Á¶�^��0[U+589E]`Ì,oºA[��Ü¦¾¿�� xçè4�,i�l5CollaborationRequests6(»¦�{^�)ÖtA5Request You Have Made6([U+60A8]¶áw^�)ÜYjw�Í�óÎ,÷�3;A[�[U+555F]¥W�[U+60A8]a«�:�1ÈÍ#A^��

3.3.7.2.3 o^�

÷\[U+60A8]¶�áwA^�,ã"h �> ¨[U+7D55],k�Øl5Collaboration Re-quests6(»¦�{^�)ÖtA5Request You Have Made � Completed6([U+60A8]¶áw^� �o)Ü�£[U+60A8]ãSD^J�.d[U+9304]é,[U+60A8]a«ç£W�

3.3.8 [U+589E]`å^ÕÍ�øç

^[U+589E]` A[ãÍ�øç4óAå^,�U[U+64CA]A[¡õêA5Links6(å^)Ç×,i�^ñ5EditLinks6(A[å^) (Figure 3.19)Öt�

Figure 3.19: 5Links6(å^)Ç×�

�5Links6(å^)Ç×,[U+60A8]a«:

• [U+589E]`�Aå^ (Section 3.3.8.1: [U+589E]`�Aå^)• A[¶5lAå^ (Section 3.3.8.2: A[¶5lAå^)• ç£Í�å^ (Section 3.3.8.3: ç£Í�å^)

:@å^a«l5Links6(å^)Ç×� �,^ñ[U+6BCF]Í�øç�å^w�l¸#A�Å2ù%Y,Èô,R�Aå^Øl5Supplemental6(R�)Çg%Y�

3.3.8.1 [U+589E]`�Aå^

^[U+589E]`Í��å^ÕÍ�øç,�®YØ[U+6B65]¤:

1. �l5Link Name6(å^çe)�É��óå^AÇ×�(»?A)




2. �:l5Module Id6(øçID)�É��óÍ�øçAA�, �l5Link URL6(å^ÿÇ)�É��óÍ�ÿÇ,«Ã#å^�Aª�ôi[U+60A8])óÍ�øçA�,[U+60A8]a«ÉñÍ�x§�3. �l5Link Type6(å^2ù)�É"U[U+64CA]ÏY¾¡,«��Y¶É�ÁÉñå^2ù�4. �l5Link Strength6(å^Äp)�É"U[U+64CA]ÏY¾¡,«��Y¶É�ÁÉñÍ��8,«Éñå^Äp;5hTÄAå^�5. �U[U+64CA]Add[U+589E]`«[U+589E]`å^�

3.3.8.2 A[¶5lAå^

ôiøç¶�74å^,åîw�lÖtAêo��Â[¶5lAå^,�®YØ[U+6B65]¤:

1. �è�5Name6(çe)�ÉAÜ¦,«��å^Ç×�2. �è�5URL6(ÿÇ)�ÉAÜ¦,«��å^ÿÇ�3. �l5Link Type6(å^2ù)�É"U[U+64CA]ÏY¾¡,«��Y¶É�ÁÉñ[U+53E6]Í�å^2ù�4. �l5Link Strength6(å^Äp)�É"U[U+64CA]ÏY¾¡,«��Y¶É�ÁÉñÍ��8,«Éñå^Äp;5hTÄAå^�5. �U[U+64CA]Update Linksè�å^«o[U+60A8]Aè��

3.3.8.3 ç£Í�å^

^ç£Í�5lAå^,�l5lAå^ØÌÁA5Delete6(ç£)z�ÉñÉújÅ,Ò¶U[U+64CA]UpdateLinksè�å^«ç£å^�

3.3.9 IÖøç

A[øç¶,[U+60A8]wµIÖøç«Éú[U+60A8]�^w�løçêA��[U+60A8]a«®YØjù�5Preview6(IÖ)Ç×B øç:

• ¿êIÖøç (Section 3.3.9.1: ¿êIÖøç)• IÖøçAÍ�ØÖx§(PDF �le) (Section 3.3.9.2: IÖøçAÍ�ØÖx§)• B è��^ (Section 3.3.9.3: B è��^)• B øç�#A8� (Section 3.3.9.4: IÖA8�)

3.3.9.1 ¿êIÖøç

^¿êB Í�øç,�®YØ[U+6B65]¤:

1. �U[U+64CA]5Preview6(IÖ)Ç×,i�^ñ5Preview6(IÖ)Öt�2. �U[U+64CA]Online Preview¿êIÖå^�:^ñøçAÍ�¿êx§,Åâ6á[U+4F48]¶øçA¿êx§�IÖ�á[U+4F48]x§/Aã¦,hIÖx§l¦¡/ã74å^�Ç×,øçÁ�Z4å^�£[U+60A8]ú^^ñé,��ÖøçÜ¦�-�£��

3. �³X[U+60A8]ë@HA5Back6(êÍ4)Ê�,«��5Preview6(IÖ)Öt�

3.3.9.2 IÖøçAÍ�ØÖx§

Í�øçAØÖx§AÅù,ã¿êx§ã¦�.F¼nh»Â,Ùº¿ê1��ØÖ1�/ã¦�^B Í�øçAØÖx§,�®YØ[U+6B65]¤:

1. �U[U+64CA]5Preview6(IÖ)Ç×,i�^ñ5Preview6(IÖ)Öt�2. �U[U+64CA]¥Print PreviewIÖØÖå^,i�w�Í�5Opening in-

dex.pdf6(¦[U+555F]index.pdf)k�jÅ�3. �³XÍ�PDFB å²u¦[U+555F][U+6A94]§,/U[U+64CA]OK¦¶,i�^ñøçAØÖx§�4. ��Ö^ñAøç�£�%å�¿?^ñ,h�h[U+60A8]úÂ�5. [U+60A8]a«³X[U+60A8]APDFë@HAØÖÉ�ØÖ.PDF[U+6A94]§�6. �ó1PDFB å²�


43

3.3.9.3 B è��^

A[Í�¶5lAøçé,[U+60A8]a«B T¶á[U+4F48]øçx§«�[U+60A8]�ÏA[x§/AF¼�^��U[U+64CA]Changesè�å^«B è��^(Figure 3.20)�£[U+60A8]^�[U+67E5]Í�ÿ�«ÏAøçòãdµ[U+60A8]�~aÌè�é,:�É�£4X�

Figure 3.20: 5Changes to6(è�)�^�

5Change To6(è�)=^ØwøçAè�,^7ÌAÃ#,«�÷\¶è�[U+6A94]§Açe,[U+589E]`A[U+6A94]§,«�½£A[U+6A94]§��U[U+64CA][U+6A94]ç«^ñè�A#�Ðy�

3.3.9.4 IÖA8�

4éÆB Í�øçAA8�hÎºjEA�^B øçAA8�,�U[U+64CA]l5Module Sta-tus6(øç[U+72C0]S)�×�A5View6(B )Çg%YASourceA8�å^,i�^ñ¶��5AT�A8��

È¶: £[U+60A8]Ù¡5Í�A8�¾é,.Ê�£4X�




3.3.10 [U+62CB]W[U+60A8]Aè�

£[U+60A8]N�iA[Aøç��uA[U+72C0]Sé,.[U+72C0]Shl[U+60A8]¦ºA[WÏ,.õÌa��áy�ô^[U+62CB]W[U+60A8]Aè�,�U[U+64CA]l5ModuleStatus6(øç[U+72C0]S)�×�A5Actions6(¥{)Çg%YADiscard[U+62CB]Wå^,øçi�C��[U+60A8]¦[U+555F]WéA[U+72C0]S�

È¶: ôiøçh�Aé�Íá[U+4F48]~,[U+60A8])óDiscardé�4AÜ¦iÈ�,øçi�oE�

3.3.11 á[U+4F48]øç

^�[U+60A8]Aøç [U+60A8]��Aè��[U+5920]³÷\0lÿìêa«B ,[U+60A8]»?iøçá[U+4F48]lConnexions��^á[U+4F48]Í�øç,�®YØ[U+6B65]¤:

1. �U[U+64CA]5Publish6(á[U+4F48])Ç×,i�^ñ5Publish Module6(á[U+4F48]øç) (Fig-ure 3.21)Öt�l[U+60A8]á[U+4F48].øçÏ,.Öt74,ñØ¶[U+60A8]1ü�

2. �l5Description of Changes6(è�[U+8AAA]é)%åjÅ��ó[U+60A8]k6øç��Ø{A#�Ðy�3. �U[U+64CA]Publishá[U+4F48],[U+60A8]k6øç��AØ{i)óÕConnexionsÜ¦É»�ª�Í�-óÜ¦É»�ª,lÿìêA÷\0ka«B .øç�

Figure 3.21: 5Publish6(á[U+4F48])Ç×�

Í��Aøç/Z4A[êAè�,Ù.l5Description of Changes6(è�[U+8AAA]é)%åjÅ�[U+60A8]»?)óÍ�Ë�,Èô5Createda new module6(m�Í��øç)�

È¶: á[U+4F48]Í�øçA¥{,ã¦6lA[§¥U[U+64CA]Save�5¥�,£[U+60A8]�5[U+60A8]Aè�é,{4[U+60A8]«�a«51[U+60A8]Ø{%çA0a« �[U+60A8]Aè��£[U+60A8]á[U+4F48]Í�øçé,q�e¡ka«lÿìê �[U+60A8]AØ{�


45

3.4 [U+589E]`<1²�b22



3.4.1 #�

Connexionsøça«^7<8ã¦2ùA<1²,.øçi�~[U+60A8]ô\a«iYØA<1²�b2ù[U+589E]`ÕÍ�øç�:

• ¿? (Section 3.4.2: ¿?)• Flash �b (Section 3.4.3: Flash �b)• �? (Section 3.4.4: �?)• Java 1ù (Section 3.4.5: Java 1ù)• �X[U+6A94]§ (Section 3.4.6: �X[U+6A94]§)• LabVIEW ¿4Z1ùñ� (Section 3.4.7: LabVIEW ¿4Z1ùñ�)

÷\a«ilÿ4�A<1²�b2ù,ka«�:³XCNXMLAmedia(1²)Ç×i3i±lConnexionsøç��[U+67E5][U+95B1]CNXMLLanguage Speci�cation(CNXML½�[U+8AAA]é)�ó61²26 Ç×AÐy,«Èµè<Ü9�*ÍA^�hµ�b»?�4Í�aXAMIME(Multipurpose Internet Mail Extension)½#2ù�MIME½#hÍ�a«�Ü¦¢)A�9½#,Èô�X �?,�~ÿjÿìòãD^"�oÍ�ASCIIÅù��[U+67E5][U+95B1]MIMETypes27 «Èµè<Ü9�.øç^7CNXML)óAÈ½,«�W�ã¦A<1²�b^ñAî�

3.4.1.1 [U+589E]`<1²Al^È¶á�

£[U+60A8]î<1²[U+589E]`Õ[U+60A8]Aøçé,�È¶YØá�:

• .øç��OñACNXMLÈ½,h¸9Ã#l.øç�³XA1²Ø�,ôi[U+60A8]i3�~�[U+60A8]Aøç�,�A[C�[U+60A8]õÌYACNXML�• [U+60A8]�î±løç�A1²�b,3type(2ù)yn»?ó�MIME2ù�Èô,ôi[U+60A8]�[U+589E]ÀÍ�¿?[U+6A94]§hPortable

Networks Graphics(.pngüy[U+6A94]ç)Åù,type2ùyn»?himage/png,3)ó��YõAÈ½:

<media type="image/png" src="mypicture.png"/>

• [U+60A8]a«³X÷\2ùA1²�b,{^WhaXAMIME2ù�• ôi[U+60A8]l[U+589E]`Í�<1²�béD^½�, �[U+60A8]ó6ÍØl.øç�AÍ��b4óA gé,�ã[U+7E6B]ConnexionsrxÄ&,[email protected]

�

• [U+60A8]a«³Xparam(1�) (Section 3.4.8: 1²2ù1�)Ç×«äj<1²�bAÉ� 1��

22This content is available online at <http://cnx.org/content/m13497/1.3/>.23"Adding Multimedia to Your Connexions Content" <http://cnx.org/content/m12660/latest/>[email protected]@cnx.org26http://cnx.org/technology/cnxml/0.5/spec/#media27http://www.ietf.org/rfc/[email protected]




3.4.2 ¿?

³XlConnexionsøç�ó�MIME2ùA¿?[U+6A94]§2ùº:

• eps - media type="application/postscript"• png - media type="image/png"• jpeg - media type="image/jpeg"• gif - media type="image/gif"

«ê�Ø/ã^7�4A2ù,÷\aXAMIME type29 2ùA¿?ka«³Xløç��^�¿?i±l[U+60A8]Aøç�,�l[U+60A8]AøçAindex.cnxml[U+6A94]§�ÖóCNXML)ó,Åâ6YØAÈ½:

<figure id="figure-01"><name>Ö¿�È</name><media type="image/png" src="envelope-taller.png"/><caption>Í�¿�A^ñ�</caption>

</figure>

media1²Ç×�Asrcyn,h¢#¿?A± u�,i3i±l[U+60A8]ú^�3w�løç�Aªj�ôi[U+60A8]¶�i[U+6A94]§ê¢Õ[U+60A8]Aøç�,yna«hÍ�[U+6A94]ç; �ôiÍ�¿?[U+6A94]§�5lÿjÿìêA3;ªj,yna«hÍ�qAURLÿÇ�êjCNXMLÈ½A`j^ñ (Figure 3.22: Ö¿�È)º:

Ö¿�È

Figure 3.22: Í�¿�A^ñ�

[U+60A8]a«³XsubfigureÇ×�¿�¿?i±l¦A�gure(Ö¿)��£[U+60A8]4¿�ó¿?,òú^i3/Øi± �êYi±é,:�Ç×£4X;^l¦Í�Ö¿�^ñ¿�¿?,�l[U+60A8]AøçAindex.cnxml[U+6A94]§�ÖóCNXMLA)ó,Åâ6YØAÈ½:

<figure id="figure-2" orient="horizontal"><subfigure id="subfigure-1"><name>Îd¿��</name><media type="image/png" src="envelope-taller.png"/><caption>½Ö¿1�

</caption></subfigure>

29http://www.duke.edu/websrv/�le-extensions.html


47

<subfigure id="subfigure-2"><name>Î³¿��</name><media type="image/png" src="envelope.png"/><caption>½Ö¿2�

</caption></subfigure>

<caption>lÍ�Ö¿�H,^ñ¿�¿?�</caption></figure>

êjCNXMLÈ½A`j^ñ (Figure 3.23)º:

(a) Îd¿�� (b) Î³¿��

Figure 3.23: lÍ�Ö¿�H,^ñ¿�¿?� (a) ½Ö¿1� (b) ½Ö¿2�

orient(jÏ)yn[U+503C]a«hhorizontal(H,) vertical(E÷),«�#x¿?ô\£&lÖ¿(�gure)��

3.4.2.1 øçA¿êx§�ØÖx§�^7A¿?

ôi[U+60A8]øç�õ¿?Ad³,ó�[U+60A8]¿êB éAd³,}£[U+60A8]ØÖ.øçé'^µ=dé;Connexions�[U+60A8]a«løç�ÖóÍ�üÀ¿?[U+6A94]§,�3Åù�d³ó�ØÖx§�D�epsÅùA¿?[U+6A94]§,h³XlConnexionsøçØÖx§�Î_AÅù�ôi[U+60A8]Aøç^7¦¿?Aeps[U+6A94]§�png[U+6A94]§;£Connexions[U+7522]yÍ�ØÖx§APDF[U+6A94]é,Connexions�³Xeps[U+6A94]§;òôil¿ê^ñøçé,�³Xpng[U+6A94]§�%Yh[U+8AAA]éô\l[U+60A8]Aøç�ºØÖx§ÖóüÀ¿?[U+6A94]§:

1. �m�[U+60A8]A¿?[U+6A94]§AÍ�epsÅùx§,:�¿?wíqoC�Ad³�2. �lindex.cnxml[U+6A94]§�Öó:�eps[U+6A94]§AÍ�media type(1²2ù))ó,l¿ê^ñA¿?[U+6A94]§)óêj�.¿?[U+6A94]§wµ4¦Açe,ò[U+6A94]çwµÃ#3[U+6A94]§2ù�Èô,image1.pngh¢¿ê³XA,òimage1.epsh¢ØÖ³XA�3. �[U+589E]èps¿?[U+6A94]§Õ.øç�

%YhD^^7ü`¿?�DACNXMLA8AÍ�È½:

<figure id='printimage'><media type='application/postscript' src='image.eps'><media type='image/png' src='image.png'/>

</media></figure>

È¶: lindex.cnxml[U+6A94]§�,ØÖ¿?(eps)A)ó»?w�l¿ê¿?(png)A)óêj;¿ê¿?A)ówµs&,«� �ól[U+53E6]Í�¿?)ó�õ�




3.4.2.2 m�Í�¿?å^ÕÍ�ÎdAx§

[U+60A8]�a«^ñÍ�¿?,�W U[U+64CA]¶^ñoÍ�Îdx§A¿?�%Yh3Ü�Ajl:

1. �m�[U+60A8]A¿?[U+6A94]§AÍ�s¿x§�2. �i�¿d³�s¿d³A¿?ÖóÕÍ�media type(1²2ù))ó,ôYØÈ½�ñ�3. �[U+589E]`�¿d³�s¿A¿?[U+6A94]§Õøç��

%Yh74Í�s¿¿?å^ÕÍ��¿x§�DACNXMLA8È½:

<figure id='thumbnail'><media type='image/png' src='TajMahal_medium.jpg'><param name='thumbnail' value='TajMahal_Thumb.jpg'/>

</media></figure>


Figure 3.24: Steve Evans30�ßV[U+59EC]vZ²AÍ?�lCreative Commons Attribution Li-censeAçaY�i�

30http://www.�ickr.com/photos/babasteve/


49

3.4.3 Flash �b

[U+60A8]a«l[U+60A8]Aøç�ÖóÍ�Flash�b,%Yh^7Í�Flash�b�DACNXMLA8È½:

<figure id='flashfig'><media type="application/x-shockwave-flash" src="flash.swf"><param name='height' value='250'/>

<param name='width' value='250'/></media>

<caption>Flash�b�È:"Welcome to Connexions"�</caption></figure>

w�l[U+60A8]øç�AFlash�b (Figure 3.25),Åâ6Í��? Í�¿?�w�Ajù�

This media object is a Flash object. Please view or download it at<�ash2.swf>

Figure 3.25: Flash�b�È:"Welcome to Connexions"�

È¶: êjÈ½h[U+9472]�lfigureÇ×�õ,a«³X¿?[U+8AAA]é�~Falsh�bA¶x,.figureÇ×/ãD^løç�^7:@1²�b�

3.4.4 �?

%Yh[U+60A8]a«^7l[U+60A8]øç�AÍ@�?2ù,[U+60A8]a«Öó:@2ù,«�3;÷\a«ÖóÕÍ�ÿ4A�?2ù�

• quicktime• mpeg

a«�:ô¦YØAA8jùi�?[U+589E]`Õ[U+60A8]Aøç:

<figure id='moviefig2'><media type="video/mpeg" src="Building_on_the_Past.mpg"><param name="width" value="450"/><param name="height" value="400"/><param name="autoplay" value="false"/>

</media><caption>Creative Commons �?:"Building on the Past",�U[U+64CA]Play(�i)¥�«¦ºB �</caption>

</figure>


This media object is a video �le. Please view or download it at<Building_on_the_Past.mpg>

Figure 3.26: Creative Commons �?:"Building on the Past",�U[U+64CA]Play(�i)¥�«¦ºB �




È¶: êjÈ½h[U+9472]�lfigureÇ×�õ,a«³X¿?[U+8AAA]é�~�?A¶x,.figureÇ×/ãD^løç�^7:@1²�b�

3.4.5 Java 1ù

a«�:ô¦YØAA8jùiJava(�T)1ù[U+589E]`Õ[U+60A8]Aøç:

<figure id="javafig"><media type="application/x-java-applet" src="PhasorDemo.class"><param name="width" value="430"/><param name="height" value="500"/>

</media><caption>Í��v�ß¿A3D¥ ,�U[U+64CA]Run(��)¥�«¦[U+555F]¥ �</caption>

</figure>


This media object is a Java applet. Please view or download it at<PhasorDemo.class>

Figure 3.27: Í��v�ß¿A3D¥ ,�U[U+64CA]Run(��)¥�«¦[U+555F]¥ �

ôiêj¥ /Z4w�,[U+60A8]a�D^£� è�Java«Ø1ùl[U+60A8]A\½ê,�Õjava.com31

YiJava«Ø1ùAT�x§�

È¶: êjÈ½h[U+9472]�lfigureÇ×�õ,a«³X¿?[U+8AAA]é�~Java Ap-pletA¶x,.figureÇ×/ãD^løç�^7:@1²�b�

3.4.6 �X[U+6A94]§

�X[U+6A94]§Èômp3�real audio��wav[U+6A94]§,a«�+�M¸ªÖóÕ[U+60A8]Aøç��^l[U+60A8]A%b�^7�X[U+6A94]§,�l[U+60A8]Aindex.cnxml%b�ê¢kwA�X[U+6A94]§�ÅâYjAA8:

<figure id='musicscale'><media type="audio/x-wav" src="chromatic_slurred.wav"/><caption>:Michael Lawrence�Dô�É"AoXX§�</caption></figure>


31http://java.com


51

This media object is an audio �le. Please view or download it at<chromatic_slurred.wav>

Figure 3.28: :Michael Lawrence�Dô�É"AoXX§�

È¶: êjÈ½h[U+9472]�lfigureÇ×�õ,a«³X¿?[U+8AAA]é�~�X[U+6A94]§A¶x,.figureÇ×/ãD^løç�^7:@1²�b�

3.4.7 LabVIEW ¿4Z1ùñ�

4ó6l[U+60A8]Aøç�^7LabVIEW¿4Z1ùñ�AóÜ9,�[U+67E5][U+95B1]Creating LabVIEWdemonstrations for Connexions32�

3.4.8 1²2ù1�

Í@<1²�bD^Í@É� 1�«C£ª^ñwu,[U+60A8]a«�:param(1�)Ç×¢OÜ9Õ<1²�b,.Ç×lmedia(1²)Ç×�,òãD^�èmedia(1²)Ç×��[U+67E5][U+95B1]CNXMLLanguage Speci�cation(CNXML½�[U+8AAA]é�)�4óparam33 Ç×AÐy,«Èµè<Ü9�%YhÍ��?(mpg)�bAparam(1�)Ç×)óAÈ½:

<media type="video/mpeg" src="testmovie.mpg"><param name="width" value="300"/><param name="height" value="300"/>

</media>

È¶: [U+60A8]wµk÷\�?�Flash�b� Java1ù #�p(height)�[U+5BEC]p(width)1�,³W�l¿ê«C�Ad³^ñ;I ³XA�p�[U+5BEC]p�ºpixels æ,lêjÈ½Á,�?^ño300pixelL«300 pixelAjÅ�

ã¦A<1²�b2ù,Ä&�kw6ã¦A1�,Í@¼A<1²�b2ù�³X�AÍ@1�È½ôY:

• Images (image/*): height, width, title, alt• Flash (application/x-shockwave-�ash): height, width, base• Video (video/*): height, width, classid, codebase, autostart• Java Applets (application/x-java-applet): height, width, code, codebase, archive• Audio (audio/*): title, volume• LabVIEW (application/x-labview): viinfo (See Creating LabVIEW demonstrations for Connexions34

for more information.)

È¶: param(1�)Ç×,Õ[U+60A8]Ã#ÖóÕXHMTL%bAÍ��bl\½þ{éA #�

32"Creating LabVIEW demonstrations for Connexions" <http://cnx.org/content/m11601/latest/>33http://cnx.org/technology/cnxml/0.5/spec/#param34"Creating LabVIEW demonstrations for Connexions" <http://cnx.org/content/m11601/latest/>




3.4.8.1 param(1�)�U�¿?

ôi[U+60A8]³X�óùAmedia(1²)Ç×«,¶Í�U�¿?^ñ,ÈôÍ�Í?w�løçAØÖx§,«1bw�l¿êx§AÍ��?;�lU�¿?A �óAmedia1²)óÏ,Öó�§¿?Aparam(1�))ó,ô¦YØÈ½�ñ:

<media type="video/mov" src="howto.mov"><param name="height" value="250" /><param name="width" value="250" /><media type="image/png" src="novideo.png />

</media>

3.5 ly§35

3.5.1 #�

Connexions�ADerive Copy(ly§)Ê�,a«�[U+60A8]k÷\¶á[U+4F48]Aøçm�Í�lynAÓ{��Í�¶5løçA§¦ºlyÓ{,�[U+60A8]k3[U+5167]M-�K�,Ò¶á[U+4F48]oº[U+60A8]ô�Aøç�Derive Copy(ly§)A[U+6B65]¤ãhÍ�»¦�{Ajù�ôi[U+60A8]ú^kÍ�¶5løçAÍ�A[�m{-�K�A[U+5167]M,a«³XSuggest Edits(m{A[)Ê��

L�: l[U+60A8]m�lyÓ{é,÷\[U+60A8]�m�AÓ{hÍ��îx§A�+¨B[U+6B65]¤�ôi~ Í¥é/¶�îAøç-�è�,[U+60A8]�~{A§iÞlp�Ö@è�A�Z�

lyÓ{hlCREATIVE COMMONSÉ»Aç��("CCPL" "Aç��")36

YÈµÕA,CX6�4ConnexionsAÜ¦�£[U+60A8]á[U+4F48]Í�ly§é,Connexionsi�ô¥[U+589E]`Í�,y[U+8AAA]é,X«Ãé�îÓ{�3A[�,:h>CREATIVECOMMONSÉ»Aç��AClnD^�

3.5.2 Xj

ly§Ê�4¿�0^AXj:

• �XÍ�¶5lAøç{ºÍ�øx,«m�Í��øç�Èô,[U+60A8]�¡�AÍ�¶5lAøç,hã[U+60A8]�^m�Aøç�4ÅâA^ì;[U+60A8]a«m�Í�ly§,£{[U+60A8]�øçAÍ�wáU�• �^m�AÍ�øçÅâ6Í�¶5lAøç,}[U+5167]M4��è�Èô,[U+60A8]¡�Í�[U+60A8]ú^³Xl[U+60A8]�z1�AÍ�¶5løç,}[U+60A8]úkÖ�øç-�Í@è�,ò[U+60A8]/Z4ç�¥K�Ö�øç�[U+60A8]ã�îA[�ã[U+7E6B],Ï;,w[U+60A8]�D^A��m{(Section 3.6)¶,�îA[�/ã¦¶[U+60A8]�,wAm{,Ùº[U+60A8]�,wAm{³øç[U+5167]M��³A³É[U+7522]y�è,òÖ/ãó�øçA�¶�[U+60A8]��[U+60A8]wµk3-��è«É�6e,Ù.[U+60A8]a«m�Í�øçAly§,Qê[U+60A8]Aè�,Ò¶á[U+4F48]o[U+60A8]ô�Aøç�

3.5.3 m�Í�ly§

l[U+60A8]AØ{/ Í�Ø{%ç�,[U+60A8]a«�øçA[�m�Í�ly§�

1. �lÜ¦É»�ª�Â537 [U+60A8]�^�~Aøç�2. �[U+589E]`.øçÕ[U+60A8]AØ{/ Ø{%ç�3. �U[U+64CA]øçÇg«¦[U+555F]øçA[��4. �l5Status6([U+72C0]S)�×�A5Actions6(¥{)ÇgYjU[U+64CA]Derive Copy

ly§,i�^ñ5Derive a Copy from6(lyÍ�§)Öt�

35This content is available online at <http://cnx.org/content/m13498/1.3/>.36http://creativecommons.org/licenses/by/2.0/37http://cnx.org/content/search?words=


53

5. �ÉñÖt%�AÉújÅ,«Î�[U+60A8]¦¶6CXContent Commons Attribution li-cense(Ü¦É»�ªAça)�[U+60A8]A�øç�

6. �U[U+64CA]Yes, Create Copy(¦¶,m�§),øçA[�i�^ñ5File6([U+6A94]§)Ç×,Øwly§;:él[U+60A8]AØ{/ Ø{%ç�,.�AøçÜ6¶m�A[U+72C0]S�

�øç��4AÜ¦ã�îøç�AÜ¦ÍøÍô;£ Ì«,Æ~Ü¦h¦A�ÌAÜ¦,£ �øç�ØwAÛ�«,�^ñ[U+60A8]oºA[��Ü¦¾¿��«�xçè4��[U+60A8]a«A[.øç�DAÜ¦�[U+6A94]§�<ôÜ¦�Ì�«�å^,ô¦[U+60A8]�m�A÷\øç�[U+60A8]a�D^,wÍ�^�«½£�îA[�,}h;��i»?^úa:ôA^�,ô¦3;÷\AÌ��£[U+60A8]á[U+4F48][U+60A8]Aly§øçé,Connexionsiô¥[U+589E]`Í�[U+8AAA]é�øç�,Ãw�îøç�A[�A,yç;.[U+8AAA]é+å^Õ�îøç,Ù.��a«B [U+60A8]Aly§�®îA�uøç�

3.6 m{A[38



Connexions42 �ASuggest Edits(m{A[)Ê�,Õ÷\Í�lConnexionsgóÛ�A0a«kÍ�øçAÜ¦¾¿�,wè�Am{��ÃAÜ¦¾¿�,hçåw�løç%�A5MaintainedBy6µØ�A0�/ãD^Í�Õ«è�Ü¦,ÙºSuggest Edits(m{A[){�køçAÜ¦¾¿�,wè�Am{[U+5167]M,/ã`jè�3Ü¦;òém{è�A0/ãD^úúÜ¦¾¿��4AÜ¦¾¿��Èµm{A[A�©,«�4Í�É�«i3AóÕÜ¦�, k3-�P��.øç[U+8AAA]éÍ�Connexions³X�ô\-�m{A[,«�Ü¦¾¿�AÉ�ô\uÜ�Ö@è��

È¶: [U+60A8]ã�l[U+60A8]�4Ü¦¾¿�ÌAøçê³XSuggest Ed-its(m{A[)Ê�,Ùº[U+60A8]¶�4�´«A[Ü¦�

3.6.1 ÏÜ¦¾¿�m{A[

Suggest Edits(m{A[)Ê�h�{AÍ�4ù,�[U+60A8]a«1ã�Í�øçAÜ¦Ü��[U+60A8]AA[a«h#�ô¡vÍ�[U+62FC]å�¾�[U+589E]`Í�å^�«��Í�ó�å, �3l^nô¦Í��m¦A[U+589E]`«ÿcøç0g�^lConnexions�kÍ�øç-�m{A[,�®YØ[U+6B65]¤:

1. �[U+67E5]Æ(Check out).øçÕÍ�Ø{/��2. �løçA[H�51.øç,-�»^Aè��:@A[a«è�%å[U+5167]M�¿?�å^�Ì� �hÆ~Ü¦�3. (¤»^)�l5Status6([U+72C0]S)�×�A5View6(B )Çg%YU[U+64CA]Changesè�å^,«^ñ[U+60A8]è�.øçAÍ��^�

4. �l5Status6([U+72C0]S)�×�A5Action6(B )Çg%YU[U+64CA]SuggestEditm{A[å^,i�w�5Suggest Edit6(m{A[)Öt�

5. �l5Description of Edits6jÅ��ó[U+60A8]��è�AÍ��~,:wµhÍ�d²êAÐy[U+8AAA]é,«�,�m{.è�A�:,:i¢�¢Ü¦¾¿��6. �U[U+64CA]Send Edits�wA[,i�w�5Manage Files6("�[U+6A94]§)Öt,Sêw�¢�¢Ü¦¾¿�AA[9&�Ü¦¾¿�4Éñç«�> P�[U+60A8]Am{�£;�[U+555F]¥m{é,;�»?k;�A¥{)óÍ�[U+8AAA]é;£[U+60A8]�[U+67E5][U+60A8]�,ÃA¶|éia« µ��

ôi[U+60A8]lA[¶ú^á[U+4F48]:�øç,5Publish module6(á[U+4F48]øç)4õi�^ñÍ�È¶á�,[U+8AAA]é[U+60A8]µÍÈµÕ«á[U+4F48].øçAÍ��x§�.4Øw[U+60A8]a«ÉñA¿�É�:m{[U+60A8]AA[¢.øçAÜ¦¾¿�, hm�9î.øçAÍ�[U+60A8]ô�A�øç�ôi[U+60A8]Éñ5Suggestyour changes6(m{[U+60A8]Aè�)É�,i�w�ôêy[U+6B65]¤3�A5Suggest Ed-its6(m{A[)Öt�ôi[U+60A8]Éñ5Create your own module6(m�[U+60A8]ô�Aøç)É�,i�w�5Derivea Copy6(lyÍ�§) (Section 3.5)Öt�

38This content is available online at <http://cnx.org/content/m13499/1.3/>.39"Suggest Edits" <http://cnx.org/content/m11817/latest/>[email protected]@cnx.org42http://cnx.org




3.6.2 �> ¨[U+7D55]m{A[

Suggest Edits(m{A[)Ê�a«hÍ�Ø�,k6[U+60A8]AÜ¦,X«�<ã¦Au� _è��m{�iã�4Í� �A\½@b4ù¢�Ü¦m{�[U+60A8]a«É`B Í��^,Ãwè�aÌ,«��-�AjÏ�£�0¢�k6[U+60A8]Í�øçAm{A[,l[U+60A8]YêgóÕConnexionséi�Èµ�©�Connexions<4åêÌ�APendingÍ#(Figure 3.29)�×i�^ñÍ�Suggested Editm{A[å^�[U+60A8]a«�:å^B è��Ùº:hm{A[,[U+60A8]�4É�a«-�³X ¨[U+7D55]�

Figure 3.29: 4Í�5Suggested Edit6(m{A[)A5Pending6(Í#)�×�

3.6.2.1 �Öm{A[

^�Ö[U+60A8]AÜ¦Am{A[,�®YØ[U+6B65]¤:

1. �l5Pending6(Í#)�×�U[U+64CA]Suggested Editm{A[å^,i�^ñ5SuggestedEdit6(m{A[)Öt�.ÖtÃw�Ï[U+60A8]AøçA�4m{A[,«�[U+60A8]¶��wA÷\m{A[�k6[U+60A8]Aøç,.ÖtØw�¢�.A[�ñU�é/�¢��A9&�«�¢�A[U+72C0]S�

2. �l5Edit6(A[)z�U[U+64CA]ViewB ,«�Öm{A[�Ötêi�^ñA[Aáf[U+5167]M(Figure 3.30),.^ñ^7ô¦©ÏÖtA¦Ü9,`ê��Õ[U+6A94]§�Æ~Ü¦�Ì�«�å^Aáf[U+5167]M�

Figure 3.30: kÍ�øçAm{A[áf[U+5167]M�

.áf[U+5167]MÃwøç��è��½£� [U+589E]`A�4[U+6A94]§�


55

3. �U[U+64CA][U+6A94]çå^«B [U+6A94]§Ü¦�÷Íç£~AåØ,l3Ej�Çd��(-)�÷Í�[U+589E]åØ,l3Ej�Çd��(+)�ñTAåØ�^ñ¿ê;eÍØlEjÇd��(-),^7�uA%å;eèØlEjÇd`�(+),^7è�A��

4. �[#[U+60A8]h�^³X3m{A[, �k3P��ôi[U+60A8]ú^³X3A[,�Õ`Çm{A[ (Sec-tion 3.6.2.2: `Çm{A[)�ôi[U+60A8]ú^P�.A[,�Õ¨[U+7D55]m{A[ (Section 3.6.2.3:¨[U+7D55]m{A[)�

3.6.2.2 `Çm{A[

^`Ç.m{A[Õ[U+60A8]AÜ¦,�®YØ[U+6B65]¤:

1. �l[U+60A8]ú^`Çè�AØ{/�Éñ,`¥�,Ø{/ÌÅ�Øwøç¶�5lAªj�[U+60A8]a«Éñ5Other6(3;),«�Ã#Í�ã¦AØ{/,Connexionsi[U+67E5]Æ.øçÕÖ�Ø{/�2. �U[U+64CA]Apply In`Ç,i�^ñ5Accept Suggested Edits6(�>m{A[)Öt�3. �l5Comments6(¶|)%åjÅ��óÍ�4ó6�>.A[A9&,«�U[U+64CA]Updateè��,Ãm{A0,l;Yê^ñ5Suggested

Edits6(m{A[)Öté,i� �.9&�øçA[Öt�^ñÍ�9&[U+8AAA]é.m{A[¶ `Ç�4. �á[U+4F48].øç�

È¶: [U+60A8]»?á[U+4F48].øç³µ3è�a«��40 ��

3.6.2.3 ¨[U+7D55]m{A[

^¨[U+7D55][U+60A8]Ü¦Am{A[,�®YØ[U+6B65]¤:

1. �U[U+64CA]Reject¨[U+7D55],i�^ñ5Reject Suggested Edits6(¨[U+7D55]m{A[)Öt�2. �l5Comments6(¶|)%åjÅ��óÍ�4ó6¨[U+7D55].A[A9&,«�U[U+64CA]Updateè��,Ãm{A0,l;Yê^ñ5Suggested

Edits6(m{A[)Öté,i� �.9&�øçA[Öt�^ñÍ�9&[U+8AAA]é.m{A[¶ ¨[U+7D55]�


Chapter 4

XML � CNXML

4.1 XML Basics1

4.1.1 What is XML?

The eXtensible Markup Language (XML) is a meta-markup language de�ned by the World Wide WebConsortium (W3C)2 . It is not strictly a markup language itself, but rather a set of rules for creatingmarkup languages. For our purposes a markup language is any language (HTML, for example) that usestags surrounding text to convey information such as content or format. CNXML3 , the markup language usedby the Connexions Project4 is an example of a language written in XML. There are many other examplesat the W3C site. Here is an example of some markup in CNXML.

Example 4.1

<para>This is a paragraph in <term>CNXML</term>. Notice that the markup

contains tags that express the meaning of the text.

</para>

<para> and </para> are the tags that enclose the text. In XML, tags are always marked by angle brackets(also known as < and >). Tags generally come in pairs. An opening tag will look like <tagname>. A closingtag will look like </tagname>, with a / preceding the tag name.

XML allows the separation of presentation from content. For example, HTML has tags such as <u>and <i>, which underline and italicize text respectively. This does not express content information, onlyformatting. XML allows you to de�ne your own language of tags to represent content. You could create a tagcalled <book> to represent book titles, and create a stylesheet (a separate formatting document), that saysthat every <book> tag should be italicized or underlined. Then when you want to change the presentationof that type of content, you just change one small part of the stylesheet. Also, if you make tags that conveythe content of the document, you can enable better searching. For example, you might look for the authorof a document by looking at the author tag.

1This content is available online at <http://cnx.org/content/m9002/2.24/>.2http://www.w3.org3http://cnx.rice.edu/cnxml4http://cnx.rice.edu


57

58 CHAPTER 4. XML � CNXML

4.1.2 Well-formed XML

XML has a few rules that apply to all of its languages, including CNXML. If a document satis�es these rules,then it is well-formed. XML documents are required to be well-formed.

• Every tag that is opened must be closed. An opening tag looks like <module> and a closing tag lookslike </module>. There is a shortcut. If your tag contains no other tags (referred to as an emptytag), then you can can type a / before the end of the opening tag and delete the closing tag. Forexample, <media> </media> can be abbreviated <media/>.

• Tags must be nested within each other. So, <b>red <i>and</i> blue</b> is �ne, but <b>red<i>and</b> blue</i>is incorrect because the <b> and <i> tags have overlapping content.

• You must put either single or double quotes around an attribute value. An attribute is some sort ofinformation that is associated with a tag and is listed inside of the tag itself. For example, <moduleid="m0001"> and <module id='m0001'> are �ne, but <module id=m0001> is incorrect.

• You can also choose to start every document with an XML declaration. If you do use the XMLdeclaration, then it has to be the very �rst thing in the �le. It cannot even be preceded by whitespace.It is not considered to be a tag. The XML declaration is as follows. <?xml version="1.0"?> Youcan also include other information such as the encoding of the document or whether the documentdepends on other �les or not.

• There must be one tag that contains all of the other tags. For example in xhtml <html> and </html>must surround all of the other tags. There are some things that are included at the top of the documentthat are not tags and that are not included with the tags. The XML declaration is an example of this.

4.1.3 Valid XML

It is possible to de�ne a set of rules that apply to all of the tags in a particular XML language. These rulescan be de�ned in a couple of di�erent ways. The most common way is to use a DTD (Document TypeDe�nition). Any document which follows all of the rules for that language is called valid. A document isnot required to be valid in order to be XML. However, it is generally a good idea.

4.1.4 Entity References

note: Entity references are no longer supported by CNXML 0.6. Instead, we suggest that youuse character references as described below (Section 4.1.5: Character References) to add specialcharacters to your module.

XML uses several characters in special ways as part of its markup, in particular the less-than symbol (<),the greater-than symbol (>), the double quotation mark ("), the apostrophe ('), and the ampersand (&).You've already seen examples of markup using the �rst four of those previously in this module. But what ifyou need to these characters in your content, and you don't want them to be treated as part of the markupby XML processors? You can use XML entity references for this purpose. The XML Speci�cation de�nesthe following �ve entity references for use in any well-formed XML document:

• & refers to an ampersand (&)• < refers to a less-than symbol (<)• > refers to a greater-than symbol (>)• " refers to a double-quote mark (")• ' refers to an apostrophe (')

Example 4.2Suppose you have a document with the following:

<para id="p1">The firm was known as Scrooge and Marley.</para>


59

you could replace 'and' with the entity reference &:

<para id="p1">The firm was known as Scrooge & Marley.</para>

All entity references outside the above �ve must be de�ned in a document type declaration, and they mayonly be used in documents that conform to that DTD. Note that an entity reference always begins with &

and ends with ;.

4.1.5 Character References

You can also use any character de�ned inUnicode in an XML document by means of character references.Unicode is a project to de�ne a unique code for every character in any human language. Unicode is veryuseful any time that you need to use a symbol that is not a part of ASCII.

Character references in XML either begin with &#, or they begin with &#x, and they end with a semicolon;. A character reference contains a representation of a Unicode code point: if it begins with &#, then itcontains a decimal representation of a Unicode code point; if it begins with &#x, then it contains a hexidecimalrepresentation of a Unicode code point.

Example 4.3The hexidecimal representation of the Unicode code point for the small 'o' with a stroke is 00F8,and the decimal representation for the same is 248. Therefore, the character references for thesmall 'o' with a stroke are ø and ø So you could write

<emphasis>The majestik møøse</emphasis>

or


or even


to get

The majestik møøse

4.2 Combining XML Languages5

XML6 allows you to create documents in custom markup languages. But what if you want to combinemarkup from multiple languages in the same document? What if there are one or more tags that exist inboth languages, but with di�erent meanings? You could, for example, have a <table> tag in HTML and

5This content is available online at <http://cnx.org/content/m10159/2.16/>.6http://www.w3.org/XML



one in a language describing o�ce furniture as well. How do you use these tags unambiguously, withoutlosing functionality?

The solution is to use an extension to XML called namespaces (See the W3C's recommendation, Names-paces in XML7 ). A namespace associates a unique global identi�er (usually a URI) with a particular set oftags and their usage rules. To declare a namespace for a particular tag, set the xmlns attribute to the valueof the unique identi�er.

You can also de�ne a namespace pre�x for use in your document. To do this, use a modi�ed version ofthe xmlns attribute. For example, you would use the attribute xmlns:foo="http://somewhere.org/foo"

to associate the pre�x foo with the namespace identi�er http://somewhere.org/foo. You can then indicatewhich tags come from that namespace by adding the appropriate pre�x to each tag. Thus, the bar tag infoo's namespace would be written as <foo:bar> and </foo:bar>.

When you use the default namespace any children of that tag lacking an explicit pre�x will be assumedto have come from the same namespace. This allows you to de�ne a default namespace for all of the childrenof a tag. This is especially useful when used on the root node, which is the outermost tag in a document.

Example 4.4For CNXML 0.6 there is only one schema. The document tag will contain the namespace for allavailable languages and will look like this:

<document xmlns="http://cnx.rice.edu/cnxml"

xmlns:md="http://cnx.rice.edu/mdml/0.4"

xmlns:bib="http://bibtexml.sf.net/"

xmlns:m="http://www.w3.org/1998/Math/MathML"

xmlns:q="http://cnx.rice.edu/qml/1.0"

id="new"

cnxml-version="0.6"

module-id="new">

4.3 The Basic CNXML8

4.3.1 Starting with CNXML

CNXML is a lightweight XML markup language for marking up educational content. The goal of CNXMLis to convey the content of the material and not a particular presentation. Connexions9 uses the ConnexionsMarkup Language (CNXML) as its primary language for storing documents. Now let's get started!

4.3.2 CNXML Tags

4.3.2.1 Document

All CNXML documents have as their root the document tag. Everything about the document including it'smetadata and content are contained within the document tag. It is important that you understand the basicstructure for a CNXML document. The structure is as follows:

Document (root tag)

• Title

7http://www.w3.org/TR/REC-xml-names/8This content is available online at <http://cnx.org/content/m9000/2.36/>.9http://cnx.org


61

• Metadata Section• Content Section

The document tag has one required attribute:

• id - a unique ID given to the document.

This is automatically assigned.

4.3.2.1.1 ID Requirements

One major di�erence between CNXML and other markup languages is the id attribute requirement. Certaintags require that you include the id attribute, but all can possess an id. The tags requiring an id are listedbelow:

• document• para• equation• list• rule• de�nition• exercise• table• div• section• sub�gure• example• footnote• problem• solution• block quotes• media• meaning• proof• list• preformat• block code• �gure• block notes

So, if you are going to use any of the above tags, be sure to add the id attribute and give it a unique 'id'.Be aware that in CNXML 0.6 ids will be generated automatically, but you are still permitted to specify youown ids if you wish.

Example 4.5Here is an example of a couple of paras containing a user generated ids.

<para id='uniqueid1'>This is an example to illustrate the use of the <code>id</code> attribute.

</para><para id='uniqueid2'>

This paragraph has a different id than the last.

</para>



note: Any tag can contain an id attribute. This is useful if you want to link to the informationcontained in a particular tag.

4.3.2.1.2 Namespaces

The document tag should also contain any namespace declarations. Namespaces (Section 4.2) allow usto easily use other mark-up languages within CNXML without having to worry about whether tag namecollision will occur. For simple documents using only CNXML, you need to include the CNXML names-pace attribute . Any additional languages need to be declared as well and should be given their ownpre�xes. For example, to associate the MathML namespace with the pre�x "m", include the following at-tribute: xmlns:m='http://www.w3.org/1998/Math/MathML'. This states that any tag with a prepended"m" will be interpreted as a MathML tag while any tag without a pre�x will be interpreted as CNXML. Thedocument tag should also contain the metadata namespace xmlns:md="http://cnx.rice.edu/mdml/0.4",the bibtex namspace xmlns:bib="http://bibtexml.sf.net/", and the question markup languagexmlns:q="http://cnx.rice.edu/qml/1.0".

Example 4.6This what the document tag should look like.





xmlns:q="http://cnx.rice.edu/qml/1.0" id="m9000" module-id="" cnxml-version="0.6">

note: Be aware that the you document id can not be the same as this example. Each modulewill have its own unique id.

4.3.2.2 Title

The title tag can be used with many CNXML tags to hold the name of its parent. This tag can onlycontain information in ASCII text or MathML. I mention it here to allow you to put in the name of themodule (since I mentioned that it was the �rst required tag in the document tag).

Example 4.7

<title>Grilling a Good Steak</title>

note: Please see the CNXML tag list in Edit-In-Place10 to see if a tag can be named.

10http://cnx.org/eip-help/tags


63

4.3.2.3 Content

Now that you have the document tag set up with an id and namespace info, the next thing to do with yourdocument is add content. By 'content' I mean the text that will make up the bulk of your document.

note: Strictly speaking the metadata should precede information about content, but we will leavethis until later.

All of this content is conveniently placed in the content tag. Every CNXML document will have one contenttag. The body of the document will be here inside the content tag.

Structural tags are the tags which are used inside of the content tag to give structure to the document.These tags are discussed below.

4.3.2.3.1 Structure Tags

Some of the structure tags are section (Section 4.3.2.3.1.2: Section), para (Section 4.3.2.3.1.1: Para), docu-ment (p. 60), and content (Section 4.3.2.3: Content).

We have already discussed the document (p. 60) and content (Section 4.3.2.3: Content) tags, so we willproceed with a short description and examples of the other other tags listed.

4.3.2.3.1.1 Para

Text can be inserted into documents by using the para tag. Each para has a required id which must beunique within the document.

Example 4.8

<para id='intro'>I have eaten many steaks in my life and none have been more satisfying

than the backyard-grill cooked steak. Maybe this is because of the

relaxing nature of drinking a beer, being outside, and lounging that

accompanies the grilling procedure. Maybe it is because of the aroma

of the grill and the beef perfectly seasoned to your taste. Either

way, this document shows how a good steak can be prepared.

</para>

4.3.2.3.1.2 Section

As often is the case in textbooks, chapters are divided into smaller sections. Because it is often necessary tosegment text for better understanding and coherence, CNXML has included a section tag.

The section tag has one required attribute, id, and a optional �rst child tag, title (Section 4.3.2.2: Title).

Example 4.9

<section id='ingredsec'><title>Ingredients</title><list> ... </list>



</section><section id='marinadesec'><title>Marinade</title><para id='marinate'> ... </para><list id='marinade'> ... </list>

<para id='tobecontinued'> ... </para></section><section id='grillingsec'><title>Grilling</title><para id='prepgrill'> ... </para><para id='grilling'> ... </para>

</section>

Obviously ellipses would be replaced by appropriate text.

4.3.2.3.2 Inline Tags

Inline tags are used to embed content and functionality inside of the structural tags. Some of the morecommonly used tags are discussed below.

4.3.2.3.2.1 Emphasis

The emphasis tag is used to emphasize text in a CNXML document where emphasis in text would be neededor desired. It is important to note that this refers to semantic emphasis and not a typeface, although manystylesheets may choose to render it visually with a di�erent typeface.

Example 4.10

<para id='intro'>I have eaten many steaks in my life and none have been more satisfying

than the backyard-grill cooked steak. Maybe this is because of the

relaxing nature of drinking a beer, being outside, and lounging that

accompanies the grilling procedure. Maybe it is because of the aroma

of the grill and the beef <emphasis>perfectly</emphasis> seasoned to

your taste. Either way, this document shows how a good steak can be

prepared.

</para>

4.3.2.3.2.2 Term

The term tag is used to mark words or phrases which are being de�ned. However, its use is con�ned toeither a para (Section 4.3.2.3.1.1: Para) or de�nition tag. The term tag has several optional attributes:

• url - a URL specifying the source or de�nition of the term.• window - contains the possible values "replace" which results in the associated url opening in the

present window, and "new" which result in the associated url opening in a new window or tab.


65

• document - the id of another Connexions module or collection.• target-id - the id of a speci�c element (such as a para or section) in the current or another Connexions

document.• resource - This reference points to a �le that is associated with the term in question. The resource

could be a pdf, text �le, or any other supplementary resource.• version - The version of a Connexions module or collection. This attribute is used in conjunction

with the document attribute.• id - A unique identi�er, whose value must begin, with a letter and contain only letters, numbers,

hyphens, underscores, colons, and/or periods (no spaces).

Example 4.11

<para id='marinade'>To ensure the best flavor possible, it is necessary to marinate the

beef. A steak <term url='http://marinade.com'>marinates</term> when

left to sit in a prepared sauce, or <term>marinade</term>, where it

will absorb the flavors of the ingredients. Marinating may take as

little as 15 minutes or as long as 6 hours and should

<emphasis>always</emphasis> be done in the refrigerator and

<emphasis>not</emphasis> at room temperature.

</para>

4.3.2.3.2.3 Note

The note tag creates a note to the reader, which could be a warning, tip, etc. There are �ve allowed typesof note: note; aside; warning; tip; important. The type of note is speci�ed by an optional type attribute.

Example 4.12

<para id='intro'>I have eaten many steaks in my life and none have been more

satisfying than the backyard-grill cooked steak. Maybe this is

because of the relaxing nature of drinking a beer, being outside,

and lounging that accompanies the grilling procedure. <notetype='warning'>Excessive drinking or fun may result in overcooked or

burned steak.</note> Maybe it is because of the aroma of the grill

and the beef <emphasis>perfectly</emphasis> seasoned to your taste.

Either way, this document shows how a good steak can be prepared.

</para>

The above markup will display as:I have eaten many steaks in my life and none have been more satisfying than the backyard-grill

cooked steak. Maybe this is because of the relaxing nature of drinking a beer, being outside, andlounging that accompanies the grilling procedure.

warning: Excessive drinking or fun may result in overcooked or burned steak.



Maybe it is because of the aroma of the grill and the beef perfectly seasoned to your taste. Eitherway, this document shows how a good steak can be prepared.

4.3.2.3.2.4 Link

The link tag is used to provide a quick link to other Connexions modules, collections or external websites.The link tag can contain the following attributes.

• strength - The Strength attribute can contain the values 1, 2, or 3 (with 3 being the strongest)specifying the relevance of the link.


present window, and "new" which result in the associated url opening in a new window or tab.• document - the id of another Connexions module or collection.• target-id - the id of a speci�c element (such as a para or section) in the current or another Connexions





The target and document attributes can be used together or alone. If both are used then you will link toa particular tag in another document. If only document is used, you will link to another document. If onlytarget is used, you will link to a particular tag within the current document.

4.3.2.3.2.5 Cite

The cite tag is used to refer to non-electronic materials within a document, primarily containing the titleof a work. Cite has several optional attributes:


present window, and "new" which result in the associated url opening in a new window or tab.• document - the id of another Connexions module or collection.• target-id - the id of a speci�c element (such as a para or section) in the current or another Connexions





4.3.2.3.2.6 Quote

The quote tag is used to denote that some text is a direct quote from some other source. The quote tag hasa display attribute which denotes whether the quote is inline or block. Quote can also contain all of theattributes associated with cite (p. 66).

Example 4.13


67

<para id='steakquote'>Everyone has an opinion on how a steak should be cooked. <quotedisplay='inline'>"A good steak should be pink in the middle and black

on the outside."</quote> Although this may sound reasonable many

remember the words of George Washington: <quote type='block'>"In any

free country a man should have the ability to purchase a nice rare

steak."</quote></para>

Everyone has an opinion on how a steak should be cooked. �"A good steak should be pink in themiddle and black on the outside."� Although this may sound reasonable many remember the wordsof George Washington:

"In any free country a man should have the ability to purchase a nice rare steak."

4.3.2.3.2.7 Foreign

The foreign tag is used to denote that a foreign word or phrase is being used. Foreign can also contain allof the attributes associated with cite (p. 66).

Example 4.14

<para id='steakquote2'>In many latin american countries steak is called <foreign>carneasada</foreign>.

</para>

In many latin american countries steak is called carne asada.

4.3.3 Document Example Code

Below is an example of what your document could look like if you included all the tags above to make adocument about making a steak.

<document id='meat'><title>Grilling a Good Steak</title>

<content>

<section id='intro'><para id='intro'>

I have eaten many steaks in my life and none have been more

satisfying than the backyard-grill cooked steak. Maybe this is

because of the relaxing nature of drinking a beer, being

outside, and lounging that accompanies the grilling procedure.

<note type='warning'>Excessive drinking or fun may result in

overcooked or burned steak.</note> Maybe it is because of the

aroma of the grill and the beef <emphasis>perfectly</emphasis>seasoned to your taste. Either way, this document shows how a



good steak can be prepared.

</para></section>

<section id='marinate_section'><para id='marinate'>

To ensure the best flavor possible, it is necessary to marinate

the beef. A steak <term>marinates</term> when left to sit in

<term>marinade</term>, or prepared sauce, where it will absorb

the flavor of the ingredients. Marinating may take as little as

15 minutes or as long as 6 hours and should

<emphasis>always</emphasis> be done in the refrigerator and

<emphasis>not</emphasis> at room temperature.

</para></section>

<section id='tobecontinued_section'><para id='tobecontinued'>

I'll be adding to this document in <link document='m9006'

>The Intermediate CNXML</link> which focuses on more

advanced CNXML tags. For more marinades see the <linkurl='http://www.2eatcab.com'>Angus Beef website</link>.Finally, a good resource is the <cite>Steak Lover's Cookbook --

William Rice</cite>.</para>

</section>

</content></document>

See how Connexions11 would render this example (Section 7.2).

4.3.4 Other Required Stu�

The �rst line in any XML �le should be the XML declaration. (Strictly speaking, this is optional,but it's a good practice to follow). The XML declaration looks like this: <?xml version="1.0"

encoding="utf-8"?> , and must not be preceeded by any blank lines or whitespace. CNXML 0.6 onlyuses one schema, so there is no need to speci�cy speci�c DTDs. Below is an example of a correct CNXML0.6 document tag containing the proper namespaces.

Example 4.15





xmlns:q="http://cnx.rice.edu/qml/1.0"

id="m9000" module-id="" cnxml-version="0.6">

11http://cnx.org


69

4.3.5 Conclusions

Remember that when composing documents it is always best to consult the CNXML Tag List12 for anyquestions regarding the exact usage of CNXML tags. For more advanced topics see The IntermediateCNXML (Section 4.4) or The Advanced CNXML (Section 4.5), which concludes the cooking lesson.

4.4 The Intermediate CNXML13

4.4.1 Example

As is often the case in textbooks, authors will include examples in the middle of a chapter or section. For thisreason CNXML provides a tag that allows an author to include examples in a document. The example tag hasa unique id attribute and can contain most tags as children, the �rst being an optional title (Section 4.3.2.2:Title). For speci�cs you should always consult the CNXML Spec14 .

Example 4.16

<example id='tboneexam'><figure id='tbonefig'><title>T-Bone Steak</title><media id="image-example" display="block" alt="A T-bone Steak."><image type='image/jpg' src='tbone.jpg'/>

</media></figure>

</example>

4.4.2 Figure

The figure tag provides the structure for creating a �gure within a document. They can contain eithertwo or more sub�gure (Section 4.4.3: Sub�gure) tags, or a single media (p. 69), table (p. 78), or code(Section 4.5.1: Code) tag.

The figure tag has two attributes:

• id - a unique ID, required• orient - de�nes how multiple sub�gure (Section 4.4.3: Sub�gure)s are to be displayed. It takes two

values, vertical or horizontal, and will default to horizontal.

The optional �rst tag of the figure tag is title (Section 4.3.2.2: Title) which is used to title a �gure.The title tag is followed by any of the tags listed above; however, the most commonly used tag is media,

which is used to include any sort of media such as images, video, music, or java applets. The media objecttags have two required attributes:

• src - the location of the displayed media

12http://cnx.org/eip-help/tags13This content is available online at <http://cnx.org/content/m9006/2.22/>.14http://cnx.rice.edu/technology/cnxml/0.5/spec



• mime-type - de�nes the type of media being displayed, which can be any valid MIME15 type.

· audio - audio/mp3, audio/wav, etc.· video - video/qt, video/mov, etc.· image - image/png, image/gif, etc.· application - application/PostScript, application/x-java-applet, etc.

The �nal tag is the optional caption which is used to add a small caption to the �gure.

Example 4.17

<figure id='tbone'><title>T-Bone Steak</title><media id="image-example" display="block" alt="A T-bone Steak.">

<image mime-type='image/jpeg' src='tbone.jpg'/></media><caption>

Upon successful completion of these documents, you should be able

to grill a steak that looks just as good!

</caption></figure>

4.4.3 Sub�gure

The subfigure tag is used when you want to include more than one media (p. 69), code (Section 4.5.1:Code) or table (p. 78) within the same �gure (Section 4.4.2: Figure).

The usage of the subfigure tag is similar to that of �gure (Section 4.4.2: Figure). It has an optional idattribute, an optional �rst child title (Section 4.3.2.2: Title) tag, a single media (p. 69), code (Section 4.5.1:Code) or table (p. 78), followed by an optional caption (p. 70).

Now the orient attribute for �gure (Section 4.4.2: Figure) becomes very important. orient lets youspecify whether the sub�gures should be displayed side-to-side or one on top of the other.

Example 4.18

<figure orient='horizontal' id='horfig'><title>Steaks</title><subfigure id='subfigtbone1'><title>T-Bone</title><media id="image-example" display="block" alt="A T-bone Steak."><image type='image/jpeg' src='tbone.jpg'/>

</media></subfigure><subfigure id='subfingnystrip1'><title>New York Strip</title><media id="image-example" display="block" alt="A NY Strip."><image mime-type='image/jpeg' src='ny_strip.gif'/>

15http://www.ietf.org/rfc/rfc1341.txt?number=1341


71

</media></subfigure><caption>

Upon successful completion of these documents, you

should be able to grill a steak that looks just as good!

</caption></figure>

Or

<figure orient='vertical' id='verfig'><title>Steaks</title><subfigure id='subfigtbone2'><title>T-Bone</title><media id="image-example" display="block" alt="A T-bone Steak."><image mime-type='image/jpeg' src='tbone.jpg'/>

</media></subfigure><subfigure id='subfig2'><title>New York Strip</title><media id="image-example" display="block" alt="A NY Strip."><image mime-type='image/jpeg' src='ny_strip.jpg'/>

</media></subfigure><caption>

Upon successful completion of these documents, you

should be able to grill a steak that looks just as good!

</caption></figure>

4.4.4 List

The list tag is used to make lists. It has two attributes:

• id - a unique ID, required• list-type - de�nes the formatting of the list. list-type takes the values bulleted (default),

enumerated, named-item or inline

The list tag has two children: title (p. 69), which is optional, and item, which is where the list informationis stored.

Example 4.19: Example List

<list id='marinade' list-type='enumerated'><title>Beer Marinade</title>



<item>pour beer into large bowl</item><item>add chili powder to taste</item><item>squeeze half lime into beer marinade</item><item>place steak in beer, let soak for 30 minutes</item>

</list>

The resulting list will look like:

Beer Marinade

1. pour beer into large bowl2. add chili powder to taste3. squeeze half lime into beer marinade4. place steak in beer, let soak for 30 minutes

Example 4.20: New List Types ExampleCNXML 0.6 gives you much more control over the list environment. Now you will be able tochoose from eight preset bullet styles as well as an option that allows you to choose your ownliteral text to serve as the bullet style. The enumerated list type now o�ers several styles, includingArabic numerals, upper and lower case alphabet characters, and also upper and lower case Romannumerals. In addition to these changes, you can now also select to have your lists follow a stepwiseprogression. In CNXML 0.6 the named-item list has been slightly altered, and is now called alabeled-item list. As you may have guessed, the change is quite intuitive. Instead of using <name>to specify the item's label, you use <label>.

Here is an example of a stepwise enumerate list:

<list id="eip-165" list-type="enumerated" number-style="arabic" class="stepwise"><title>Beer Marinade</title><item>pour beer into large bowl</item><item>add chili powder to taste</item><item>squeeze half lime into beer marinade</item><item>place steak in beer, let soak for 30 minutes</item></list>

The resulting list will look like:

Beer Marinade

Step 1: pour beer into large bowlStep 2: add chili powder to tasteStep 3: squeeze half lime into beer marinadeStep 4: place steak in beer, let soak for 30 minutes

4.4.5 Equation

The equation tag is used to set o� and number equations in CNXML documents by using ASCII text,MathML and embedded media (p. 69) to display math.

note: It is strongly encouraged, however, to use equation with MathML (Section 5.1) tags whendisplaying math.


73

4.4.5.1 ASCII Text and Images

The �rst child of equation is an optional title (Section 4.3.2.2: Title) followed by any number of media (p.69) tags.

Example 4.21

<equation id="eqn14"><title>Euler's Relation</title><media id="equation-example" display="block" alt="Euler's Relation.">

<image mime-type='image/gif' src='euler.gif' /></media>

</equation>

<equation id='eqn15'><title>Simple Arithmetic</title>

11+27=38

</equation>

This equation will display as:

Simple Arithmetic11+27=38 (4.1)

You could also write this equation using MathML:

<equation id="eqn22"><m:math>

<m:mn>11</m:mn><m:mo>+</m:mo><m:mn>27</m:mn><m:mo>=</m:mo><m:mn>38</m:mn>

</m:math></equation>

4.4.6 De�nition

The definition tag is used to de�ne a word in a CNXML document. It has a required id attribute andthree children: term (Section 4.3.2.3.2.2: Term), meaning and example (Section 4.4.1: Example). How touse de�nition is a little confusing, so don't forget to check out Example 4.22.

The �rst child tag should be term (Section 4.3.2.3.2.2: Term) which contains the word/phrase beingde�ned. It is then followed by a meaning tag which is followed by any number of example (Section 4.4.1:Example)s. This process repeats for all meanings.



Example 4.22

<definition id='tbonedef'><term>T-Bone</term><meaning>

"The T-bone steak is cut between 1 and 3 inches thick and comes

from the center section of the short loin. This steak is

characterized by its T-shape bone, has a fine-grained shell and a

small tenderloin eye,"

<cite>http://www.chophousecalgary.com/steak.html</cite>.</meaning><example id='tboneexam'><figure id='tbonefig'><title>T-Bone Steak</title><media id="image-example" display="block" alt="A T-bone Steak."><image mime-type='image/jpeg' src='tbone.jpg'/>

</media></media>

</figure></example>

</definition>

De�nition 4.1: T-Bone"The T-bone steak is cut between 1 and 3 inches thick and comes from the center section of theshort loin. This steak is characterized by its T-shape bone, has a �ne-grained shell and a smalltenderloin eye," http://www.chophousecalgary.com/steak.html.Example


75

T-Bone Steak

Figure 4.1

4.4.7 Rule

The rule tag is used to insert a rule, such as a theorem, axiom, or rule of thumb, into a cnxml document.It has two attributes:

• id - required, unique ID• type - required, speci�cies the type of rule (e.g. theorem, axiom, rule of thumb, etc.)

It may also have an optional title (Section 4.3.2.2: Title) and it must have one or more statement (Sec-tion 4.4.7.1: Statement) tags and zero or more proof (Section 4.4.7.2: Proof) or example (Section 4.4.1:Example) tags.

4.4.7.1 Statement

The statement tag is used inside a rule tag and de�nes the statement of the rule. It has an optional idattribute, which, like all IDs, must be unique. It also has two children, para (Section 4.3.2.3.1.1: Para) andequation (Section 4.4.5: Equation).



4.4.7.2 Proof

The proof tag is used inside the rule tag and marks the proof of the rule. It has an optional id attributeand may contain another rule, para (Section 4.3.2.3.1.1: Para), equation (Section 4.4.5: Equation), �gure(Section 4.4.2: Figure), or list tag.

4.4.7.3 Using rule

Example 4.23

<rule id='murph' type='law'><title>Murphy's Law</title><statement><para id='murphp1'>

If there are two or more ways to do something, and one of those

ways can result in a catastrophe, then someone will do it.

</para></statement><proof><para id='murphp2'>

Edward A. Murphy, Jr. was one of the engineers on the

rocket-sled experiments that were done by the U.S. Air Force in

1949 to test human acceleration tolerances (USAF project

MX981). One experiment involved a set of 16 accelerometers

mounted to different parts of the subject's body. There were two

ways each sensor could be glued to its mount, and somebody

methodically installed all 16 the wrong way around. Murphy then

made the original form of his pronouncement, which the test

subject (Major John Paul Stapp) quoted at a news conference a

few days later

<cite>http://www.lylemariam.com/murphy.htm</cite>.</para>

</proof></rule>

Law 4.1: Murphy's LawIf there are two or more ways to do something, and one of those ways can result in a catastrophe,

then someone will do it.Proof:Edward A. Murphy, Jr. was one of the engineers on the rocket-sled experiments that were doneby the U.S. Air Force in 1949 to test human acceleration tolerances (USAF project MX981). Oneexperiment involved a set of 16 accelerometers mounted to di�erent parts of the subject's body.There were two ways each sensor could be glued to its mount, and somebody methodically in-stalled all 16 the wrong way around. Murphy then made the original form of his pronouncement,which the test subject (Major John Paul Stapp) quoted at a news conference a few days laterhttp://www.lylemariam.com/murphy.htm.


77

4.4.8 Finishing Remarks

Thanks for making it through another tutorial. I'm sure that you still want to know more so here's a linkto The Advanced CNXML (Section 4.5).

4.5 The Advanced CNXML16

4.5.1 Code

The code tag is used to insert example computer output/input as either inline text within a paragraph oras a block of text. To see which tags it may contain or be inside, consult the CNXML Spec17 . The code

tag has a display attribute with two possible values.

• inline (default) - used to specify code that is inline.• block - used to specify code that should be in a separate block of text.

Example 4.24

<para id='copy'>In a unix terminal the command to copy a file is <codedisplay='inline'>cp original copy</code>.

</para>

In a unix terminal the command to copy a �le is cp original copy

4.5.2 Exercise

The exercise tag provides a tag for authors to add practice problems into their documents. The exercisetag has a required id attribute and has two child tags, problem and solution.

To create more complex answers, such as multiple-choice, multiple-response, ordered-response, and text-response questions, QML (Questions Markup Language) may used in place of the problem and solution tags.For more information, please see the information about QML18 .

Example 4.25

<exercise id='grilltest'><problem><para id='grilltestp1'>

For food safety, a steak should be cooked to a minimum

temperature of what?

</para></problem><solution><para id='sol1p1'>

16This content is available online at <http://cnx.org/content/m9007/2.24/>.17http://cnx.rice.edu/technology/cnxml/0.5/spec18http://cnx.rice.edu/qml/intro/qml.xml



160° F or until the juices run clear and the meat is no

longer pink.

</para></solution>

</exercise>

ProblemFor food safety, a steak should be cooked to a minimum temperature of what?

Solution160 ◦ F or until the juices run clear and the meat is no longer pink

4.5.3 CALS Table

CNXML uses the industry standard CALS Table Model19 for including tables into CNXML documents.Provided below is a brief description of the CALS tags, their attributes, and children (along with a helpfulexample (Table 4.1: Steak Cooking Temperatures)). For a more complete description of the CALS Tableconsult the CALS Table Spec20 .

4.5.3.1 table

The table tag marks the beginning of a table. It has an optional �rst child of title (Section 4.3.2.2: Title)and must contain one or more tgroup (p. 78) tags. The table tag also has many attributes, to �nd outmore information consult the CALS Table Spec21 .

4.5.3.2 tgroup

The tgroup tag marks the beginning of a new portion of a table (p. 78). It has a required attribute cols

which is the number of columns in the tgroup. Its children tags are zero, one, or more colspec (p. 78) orspanspec (p. 78), zero or one thead (p. 78) or tfoot (p. 79), and one tbody (p. 79) tag.

4.5.3.3 colspec

The colspec tag is an empty tag that speci�cies the column of a table (p. 78) or entrytbl (p. 79). Thenames and numbers speci�ed as attributes are used for referencing by other tags.

4.5.3.4 spanspec

The spanspec tag is an empty tag that identi�es a horizontal span of columns and associated attributesthat can subsequently be referenced by its spanname for repeated use in entry (p. 79) or entrytbl (p. 79) indi�erent rows (p. 79).

4.5.3.5 thead

The thead tag identi�es the heading row (p. 79) of a tgroup (p. 78) or entrytbl (p. 79). The thead tag canhave zero, one, or more colspec (p. 78) tags and one or more row (p. 79).

19http://www.oasis-open.org/specs/a502.htm20http://www.oasis-open.org/specs/a502.htm21http://www.oasis-open.org/specs/a502.htm


79

4.5.3.6 tfoot

The tfoot tag identi�es the rows (p. 79) of footer information that are displayed after the tbody (p. 79).The tfoot tag can have zero, one, or more colspec (p. 78) tags and one or more row (p. 79).

4.5.3.7 tbody

The tbody tag identi�es the body of a tgroup (p. 78) or entrytbl (p. 79). The tbody tag must have one ormore row (p. 79) tags.

4.5.3.8 row

The row tag identi�es the row of information in a thead (p. 78), tbody (p. 79), or tfoot (p. 79). The row

tag must have one or more entry (p. 79) or entrytbl (p. 79).

4.5.3.9 entrytbl

The entrytbl tag takes the place of an entry (p. 79), but �ts into a single row (p. 79) of tbody (p. 79) ina tgroup (p. 78). The content model is the same as that of a tgroup (p. 78) except that tfoot (p. 79) isommitted and entrytbl is self-excluding. Its children tags are zero, one, or more colspec (p. 78) or spanspec(p. 78), zero or one thead (p. 78) or tfoot (p. 79), and one tbody (p. 79) tag.

4.5.3.10 entry

The entry tag identi�es an entry in a row (p. 79). The entry tag contains ASCII text and zero, one,or many cite (Section 4.3.2.3.2.5: Cite), term (Section 4.3.2.3.2.2: Term), cnxn, link, code, emphasis (Sec-tion 4.3.2.3.2.1: Emphasis), or media (p. 69).

4.5.3.11 Using CALS Tables

It might sound a little confusing but I think that the best way to understand a table is to look at Example 4.26.For more information, consult the CALS Table Spec22 or the CNXML Spec23 .

Example 4.26

<table id='grilltemp' frame='all'><title>Steak Cooking Temperatures</title><tgroup cols='2' colsep='1' rowsep='1'><thead><row><entry>Temperature (°F)</entry><entry>Description</entry>

</row></thead><tbody><row><entry align='center'>140</entry><entry align='center'>Rare</entry>

</row><row>

22http://www.oasis-open.org/specs/a502.htm23http://cnx.rice.edu/technology/cnxml/0.5/spec



<entry align='center'>150</entry><entry align='center'>Medium Rare</entry>

</row><row><entry align='center'>160</entry><entry align='center'>Medium</entry>

</row><row><entry align='center'>165</entry><entry align='center'>Medium Well</entry>

</row><row><entry align='center'>170</entry><entry align='center'>Well</entry>

</row></tbody>

</tgroup></table>

Steak Cooking Temperatures

Temperature ( ◦F) Description

140 Rare

150 Medium Rare

160 Medium

165 Medium Well

170 Well

Table 4.1

4.5.4 Conclusions

This concludes the CNXML tutorial.

4.6 CNXML Reference Extensions24

4.6.1 Introduction

As an author/editor, you will often times need a way to include additional information in a document thatdoes not actually appear in the �ow of text. This information may include a glossary, and bibliographicreferences. There are many ways to include this type of information, but for our purposes, we have chosento create a new CNXML tag named glossary, and have chosen to use an xml language called bibteXML forreferences. The two are described below. I have also included the glossary and bibteXML �le examples inthe source of this document. Scroll to the bottom of the page to see how these examples would be rendered.

24This content is available online at <http://cnx.org/content/m11215/1.8/>.


81

4.6.1.1 BibteXML

"BibteXML is a bibliography DTD for XML that expresses the content model of BibTeX, thebibliographic system for use with LaTeX. It provides conversion tools for tagging your biblio-graphic data in XML, or export it to HTML or native BibTeX syntax, saving typing time."(http://freshmeat.net/projects/bibtexml/?topic_id=87)

In plain language, this means that bibtexml is an XML version of the popular and widely accepted latexextension bibtex. One can markup references in their document using semantic tags such as author andeditor. More info will be provided below.

4.6.1.2 The 'Glossary' Tag

Often in textbooks there will be a list of de�nitions included at the end of the book. In the same way, theglossary tag will contain a list of de�nitions that will be included at the end of a module. One can link tothese de�nitions using the term tag (see Example 4.28 (Linking to De�nitions in a Glossary)).

4.6.2 Including a Glossary

It is very easy to include a glossary in your CNXML document. In the Basic CNXML Tutorial (Section 4.3)it is stated that the structure usually resembles the following:

Document

• name

• metadata(optional)• content

When one wishes to add a glossary the structure will change to match the following:

Document

• name


• glossary

Inside of the glossary tag one can add as many de�nitions as one wishes. For more information on thede�nition tag, see the CNXML 0.5 speci�cation25 .

Example 4.27: Glossary ExampleFollowing is an example of the code necessary to add a glossary with one de�nition.

<glossary><definition id='quardef'><term>quarter</term><meaning><name>Meaning Name</name>One fourth of something.</meaning><example id='def'><para id='par'>

"He cut the pie into quarters and gave all four people a

piece."

</para></example><meaning>25 cents, a quarter of a dollar.</meaning>

25http://cnx.rice.edu/technology/cnxml/0.5/spec



<example id='def2'><para id='par2'>

"The drink cost a quarter."

</para></example><example id='def3'><para id='par3'>

"She picked up a roll of quarters so that she could do

laundry."

</para></example>

</definition></glossary>

Example 4.28: Linking to De�nitions in a GlossaryOften, one will need to refer to a de�nition in the glossary. To do this, one can use the term

tag. By putting the target-id attribute in the term tag, one can link to a de�nition. Simply setthe value of the target-id attribute to the id of the de�nition in the glossary, and that term willautomatically become a link to the de�nition in the glossary. Shown below is an example of theterm tag being used to link to the de�nition in the de�nition example (Example 4.27: GlossaryExample):

<term target-id='quardef'>quarter</term>

4.6.3 Including BibteXML

It is very easy to include a bibteXML reference section in your CNXML document. In the Basic CNXMLTutorial26 it is stated that the structure usually resembles the following:

Document

• name


When one wishes to add a bibteXML reference section the structure will change to match the following:

Document

• name


• glossary

• file

note: It is possible to include either a glossary or a bibteXML �le or both. The only restrictionis that if you include both the glossary must precede the bibteXML �le.

26"Themes" <http://cnx.org/content/m0000/latest/>


83

The file tag is the root tag of the bibteXML language. Inside of the �le tag one will add other tags thatcorrespond to the di�erent type of bibliographical references. An example of a bibliography is given below:

Example 4.29: BibteXML Example

<bib:file><bib:entry id="esbensen"><bib:book><bib:author>Kim Esbensen; Tonje Midtgaard; Suzanne Schonkopf</bib:author><bib:title>Multivariate Analysis in Practice</bib:title><bib:publisher>Camo AS</bib:publisher><bib:year>1994</bib:year><bib:address>Trondheim</bib:address>

</bib:book></bib:entry>

<bib:entry id="martens.nes"><bib:book><bib:author>Harald Martens; Tormod Nas</bib:author><bib:title>Multivariate Calibration</bib:title><bib:publisher>John Wiley & Sons Ltd.</bib:publisher><bib:year>1989</bib:year><bib:address>Chichester</bib:address>

</bib:book></bib:entry>

</bib:file>

note: Each tag in the example code begins with a namespace pre�x. In the case of bibteXML,the pre�x is bib:.

Example 4.30: Linking to BibliographyYou will want to refer to an entry in the bibliography. To do this, one can use the cite tag. Byputting the target-id attribute in the cite tag, one can link to a bibliographic entry. Simply set thevalue of the target-id attribute to the id of the bib:entry, and that reference will automaticallybecome a link to the bibliographic entry. Shown below is an example of the cite tag being used tolink to the bibliography in Example 4.29 (BibteXML Example):

<cite target-id='esbensen'>Multivariate Analysis in Practice</cite>

4.6.3.1 BibteXML Tags

By looking at Example 4.29 (BibteXML Example) one can see the types of tags that are available for use inbibteXML. Below I will attempt to give a brief explanation on the use of some of the bibteXML tags. Formore information and the complete speci�cation please see BibteXML Homepage27 .

27http://bibtexml.sourceforge.net/



4.6.3.1.1 File

The file tag is the root tag of the bibteXML language. It denotes the beginning of the bibliography.ChildrenThe file tag must contain one or more entry (Section 4.6.3.1.2: Entry) tags.

4.6.3.1.2 Entry

The entry tag denotes the beginning of an individual bibliographical reference.ChildrenThe entry must contain one of the following containers:

• article• book• booklet• manual• techreport• mastersthesis• phdthesis• inbook• incollection• proceedings• inproceedings• conference• unpublished• misc

4.6.3.1.3 Containers

Each of the possible children of entry (article, book, booklet, etc.) are containers for metadata on thatspeci�c type of entry.ChildrenEvery container tag must contain a di�erent combination of bibteXML metadata tags

(Section 4.6.3.1.4: BibteXML Metadata Tags). For more information on exactly which childrena speci�c container may possess, please see the BibteXMLHomepage28 .

4.6.3.1.4 BibteXML Metadata Tags

Every child listed as a possible child of entry (Section 4.6.3.1.2: Entry) can contain metadata tags.These metadata tags are now listed.

Metadata Tag List

• address• author• booktitle• chapter• edition• editor• howpublished• institution• journal

28http://bibtexml.sourceforge.net/


85

• month• note• number• organization• pages• publisher• school• series• title• type• volume• year

ChildrenEvery metadata tag can contain unicode text.


Chapter 5

3;{ÝX½�

5.1 Content MathML1

The authoritative reference for Content MathML is Section 4 of the MathML 2.0 Speci�cation2 . The WorldWide Web Consortium (W3C) is the body that wrote the speci�cation for MathML. The text is very readableand it is easy to �nd what you are looking for. Look there for answers to questions that are not answered inthis tutorial or when you need more elaboration. This tutorial is based on MathML 2.0.

In this document, the m pre�x is used to denote tags in the MathML namespace. Thus the <apply>tag is referred to as <m:apply>. Remember all markup in the MathML namespace must be surrounded by<m:math> tags.

5.1.1 The Fundamentals of Content MathML: Applying Functions and Operators

The fundamental concept to grasp about Content MathML is that it consists of applying a series of functionsand operators to other elements. To do this, Content MathML uses pre�x notation. Pre�x notation iswhen the operator comes �rst and is followed by the operands. Here is how to write "2 plus 3".

<m:math><m:apply>

<m:plus/><m:cn>2</m:cn>

<m:cn>3</m:cn></m:apply>

</m:math>

This would display as 2 + 3.There are three types of elements in the Content MathML example shown above. First, there is the

apply tag, which indicates that an operator (or function) is about to be applied to the operands. Second,there is the function or operator to be applied. In this case the operator, plus, is being applied. Third,the operands follow the operator. In this case the operands are the numbers being added. In summary, theapply tag applies the function (which could be sin or f , etc.) or operator (which could be plus or minus,etc.) to the elements that follow it.

1This content is available online at <http://cnx.org/content/m9008/2.15/>.2http://www.w3.org/TR/MathML2/chapter4.html


87

88 CHAPTER 5. 3;{ÝX½�

5.1.1.1 Tokens

Content MathML has three tokens: ci, cn, and csymbol. A token is basically the lowest level element.The tokens denote what kind of element you are acting on. The cn tag indicates that the content of thetag is a number. The ci tag indicates that the content of the tag is an identi�er. An identi�er couldbe any variable or function; x, y, and f are examples of identi�ers. In addition, ci elements can containPresentation MathML. Tokens, especially ci and cn, are used profusely in Content MathML. Every number,variable, or function is marked by a token.

csymbol is a di�erent type of token from ci and cn. It is used to create a new object whose semantics isde�ned externally. It can contain plain text or Presentation MathML. If you �nd that you need something,such as an operator or function, that is not de�ned in Content MathML, then you can use csymbol to createit.

Both ci and csymbol can use Presentation MathML to determine how an identi�er or a new symbol willbe rendered. To learn more about Presentation MathML see Section 3 of the MathML 2.0 Speci�cation3 .For example, to denote "x with a subscript 2", where the 2 does not have a more semantic meaning, youwould use the following code.

<m:math><m:ci><m:msub><m:mi>x</m:mi><m:mn>2</m:mn>

</m:msub></m:ci>

</m:math>

This would display as x2.The ci elements have a type attribute which can be used to provide more information about the content

of the element. For example, you can declare the contents of a ci tag to be a function (type='fn'), or avector (type='vector'), or a complex number (type='complex'), as well as any number of other things.Using the type attribute helps encode the meaning of the math that you are writing.

5.1.1.2 Functions and Operators

In order to apply a function to a variable, make the function the �rst argument of an apply. The secondargument will be the variable. For example, you would use the following code to encode the meaning, "thefunction f of x". (Note that you have to include the attribute type='fn' on the ci tag denoting f .)

<m:math><m:apply><m:ci type='fn'>f</m:ci><m:ci>x</m:ci>

</m:apply></m:math>

This will display as f (x).There are also pre-de�ned functions and operators in Content MathML. For example, sine and cosine

are prede�ned. These prede�ned functions and operators are all empty tags and they directly follow theapply tag. "The sine of x" is similar to the example above.

3http://www.w3.org/TR/MathML2/chapter3.html


89

<m:math><m:apply><m:sin/><m:ci>x</m:ci>

</m:apply></m:math>

This will display as sin (x).You can �nd a more thorough description of the di�erent prede�ned functions in Chapter 4 of the MathML

speci�cation.In addition to the prede�ned functions, there are also many prede�ned operators. A few of these are

plus (for addition), minus (for subtraction), times (for multiplication), divide (for division), power (fortaking the nth-power of something), and root (for taking the nth-root of something).

Most operators expect a speci�c number of child tags. For example, the power operator expects twochildren. The �rst child is the base and the second is the value in the exponent. However, there are othertags which can take many children. For example, the plus operator merely expects one or more children. Itwill add together all of its children whether there are two or �ve. This is referred to as an n-ary operator.

Representing "the negative of a variable" and explicitly representing "the positive of a variable or number"has slightly unusual syntax. In this case you apply the plus or minus operator to the variable or number,etc., in question. The following is the code for "negative x."

<m:math><m:apply><m:minus/><m:ci>x</m:ci>

</m:apply></m:math>

This will display as −x.In contrast to representing the negative of a variable, the negative of a number may be coded as follows:

<m:math><m:cn>-1</m:cn></m:math>

This will display as −1.To create more complicated expressions, you can nest these bits of apply code within each other. You

can create arbitrarily complex expressions this way. "a times the quantity b plus c" would be written asfollows.

<m:math><m:apply><m:times/><m:ci>a</m:ci><m:apply><m:plus/><m:ci>b</m:ci><m:ci>c</m:ci>

</m:apply>



</m:apply></m:math>

This will display as a (b+ c).The eq operator is used to write equations. It is used in the same way as any other operator. That is, it

is the �rst child of an apply. It takes two (or more) children which are the two quantities that are equal toeach other. For example, "a times b plus a times c equals a times the quantity b plus c" would be writtenas shown.

<m:math><m:apply><m:eq/><m:apply><m:plus/><m:apply>

<m:times/><m:ci>a</m:ci><m:ci>b</m:ci>

</m:apply><m:apply>

<m:times/><m:ci>a</m:ci><m:ci>c</m:ci>

</m:apply></m:apply><m:apply><m:times/><m:ci>a</m:ci><m:apply>

<m:plus/><m:ci>b</m:ci><m:ci>c</m:ci>

</m:apply></m:apply>

</m:apply></m:math>

This will display as ab+ ac = a (b+ c).

5.1.2 Integrals

The operator for an integral is int. However, unlike the operators and functions discussed above, it haschildren that de�ne the independent variable that you integrate with respect to (bvar) and the intervalover which the integral is taken (use either lowlimit and uplimit, or interval, or condition). lowlimitand uplimit (which go together), interval, and condition are just three di�erent ways of denoting theintegrands. Don't forget that the bvar, lowlimit, uplimit, interval, and condition children take tokenelements as well. The following is "the integral of f of x with respect to x from 0 to b."

<m:math>


91

<m:apply><m:int/><m:bvar><m:ci>x</m:ci></m:bvar><m:lowlimit><m:cn>0</m:cn></m:lowlimit><m:uplimit><m:ci>b</m:ci></m:uplimit><m:apply><m:ci type='fn'>f</m:ci><m:ci>x</m:ci>


</m:math>

This will display as∫ b

0f (x) dx.

5.1.3 Derivatives

The derivative operator is diff. The derivative is done in much the same way as the integral. That is, youneed to de�ne a base variable (using bvar). The following is "the derivative of the function f of x, withrespect to x."

<m:math><m:apply>

<m:diff/><m:bvar><m:ci>x</m:ci>

</m:bvar><m:apply><m:ci type="fn">f</m:ci><m:ci>x</m:ci>


</m:math>

This will display as ddxf (x).

To apply a higher level derivative to a function, add a degree tag inside of the bvar tag. The degree tagwill contain the order of the derivative. The following shows "the second derivative of the function f of x,with respect to x."

<m:math><m:apply><m:diff/>

<m:bvar><m:ci>x</m:ci><m:degree><m:cn>2</m:cn></m:degree>

</m:bvar><m:apply><m:ci type="fn">f</m:ci><m:ci>x</m:ci>


</m:math>

This will display as d2

dx2 f (x).



5.1.4 Vector and Matrices

Vectors are created as a combination of other elements using the vector tag.

<m:math><m:vector>

<m:apply><m:plus/><m:ci>x</m:ci><m:ci>y</m:ci>

</m:apply><m:ci>z</m:ci><m:cn>0</m:cn>

</m:vector></m:math>

This will display as

x+ y

z

0

.Matrices are done in a similar manner. Each matrix element contains several matrixrow elements. Then

each matrixrow element contains several other elements.

<m:math><m:matrix>

<m:matrixrow><m:ci>a</m:ci><m:ci>b</m:ci><m:ci>c</m:ci>

</m:matrixrow><m:matrixrow><m:ci>d</m:ci><m:ci>e</m:ci><m:ci>f</m:ci>

</m:matrixrow><m:matrixrow><m:ci>g</m:ci><m:ci>h</m:ci><m:ci>j</m:ci>

</m:matrixrow></m:matrix>

</m:math>

This will display as

a b c

d e f

g h j

.There are also operators to take the determinant and the transpose of a matrix as well as to select

elements from within the matrix.

5.1.5 Entities

note: The use of MathML character entity references in Connexions content is deprecated.


93

MathML de�nes its own entities for many special characters used in mathematical notation. While theentity references have the advantage of being mnemonic with respect to the characters they stand for,they also entail some technical limitations, and so their use in Connexions content is deprecated. Pleaseuse the UTF-8-encoded Unicode characters themselves where possible, or, failing that, the XML Unicodecharacter references for the characters. At some time in the future, the Connexions repository system willlikely convert entity references and character references silently to the UTF-8-encoded Unicode charactersthey stand for. See 6.2.1 Unicode Character Data4 from the XML Speci�cation for more information. TheMathML speci�cation contains a list of character entities with their corresponding Unicode code points5 .

There are character picker utilities available to help you select and paste UTF-8 characters into appli-cations like Connexions. If you are running Microsoft Windows, the Windows accessory Character Mapcan help you. The "Lucida Sans Unicode" font seems to have a good selection of mathematical operatorsand special characters. Under Linux, the charmap utility and GNOME applet provide access to all Unicodecharacters.

5.1.6 Other Resources

There is a lot more that can be done with Content MathML. Especially if you are planning on writing a lotof Content MathML, it is well worth your time to take a look at the MathML speci�cation6 .

5.2 QML 1.0 tutorial7

note: This tutorial currently under revision and may contain errors or inconsistencies in its cur-rent state. If you have any questions or notice any problems with this module, please [email protected] and let us know.

This tutorial will show you how to create problemsets and write individual items, and how to embed theminto other XML documents. It is intended primarily for people involved in the Connexions Project.

5.2.1 Displaying QML

The Connexions project provides the ability to do simple response processing through stylesheets andJavaScript. Examples of QML items thus processed are available in the QML 1.0 examples9 module.

PLEASE NOTE: This response processing is intended for the student to do self-testing as he or shemoves through modules. Any student with minor technological know-how can determine the answers to thequestions by viewing the source �le. Hence, if you do not want students to have easy access to the answersto the questions, do not include them in the QML - leave the key blank and do not put information in thefeedback tags that will allow the student to determine the correct answer.

Please also note that while the current Connexions response processing can determine whether answers tosingle-response, multiple-response, and single-response questions are correct, it does not process the responsesto text-response questions (this requires high-level and very situation-speci�c software that we do not haveplans to provide at this time). Instead, it only shows the general feedback.

note: In previous versions of the CNXML language it was necessary to modify the document tagsto include the use of QML. As of CNXML 0.6 this step is no longer required, as QML is supportednatively within CNXML documents.

4http://www.w3.org/TR/2003/REC-MathML2-20031021/chapter6.html#chars.unicodechars5http://www.w3.org/TR/MathML2/bycodes.html6http://www.w3.org/TR/MathML2/7This content is available online at <http://cnx.org/content/m10138/2.11/>[email protected]"QML 1.0 examples" <http://cnx.org/content/m10139/latest/>



5.2.2 Structural overview

In QML, items (test and homework questions) are either grouped together in a problemset or are writtenindividually. Each item contains the question being asked of the user, the response options together withanswer-speci�c feedback, if any, general feedback, if any, and a key. The items can also contain hints andlinks to resources.

5.2.3 Problemsets and items

The �rst thing you need to do is decide whether your items should be grouped together in a problemset ornot. If you are writing QML with CNXML, you can only use items, and each item will go within a CNXMLexercise tag. If you have a reason to logically group your items together (e.g. they comprise a homeworkset) and you are not writing for CNXML, enclose them in a problemset. To write a problemset, all you needto do is enclose your individual items within a problemset tag. If you are writing individual items and donot have a good reason to group them together within problemsets, or you are using CNXML, write itemswithout enclosing them within a problemset tag.

5.2.4 Problemset

The problemset tag encloses one or more items, and has one optional attribute called id. If you will bemaking a number of problemsets and need to be able to reference them individually, you will want to add aunique id attribute to each of your problemsets to distinguish between them.

5.2.4.1 Example

<problemset id="homework1">

<item . . .></item>

</problemset>

5.2.5 Item

The next tag is the item tag, which contains the question, response options, and so forth. Each item tagmust contain an id attribute and a type attribute. Ideally, the id attribute should be unique; no two itemsyou write should have the same attribute. How you do this is up to you.

The type attribute determines the type of question you are asking. It must be one of the following:

• single-response• multiple-response• ordered-response• text-response

Finally, it is important to note that an item must contain one question tag. It may also contain zero ormore answer tags, and zero or one key tags. However, the existence or non-existence, as well as the contentsof these last two tags, may be slightly di�erent depending on the type of question. Items may also containone or more resource tags and hint tags, and one general feedback tag.


95

5.2.5.1 Single-response

Single-response items are items for which there is one and only one correct answer to be selected from theprovided answers. Examples are multiple-choice (select only one) and Likert scale items.

5.2.5.2 Multiple-response

Multiple-response items are items which require more than one selected response option for a correct answer.Examples are multiple-choice items where the user must select two or more responses to each item.

5.2.5.3 Ordered-response

Ordered-response items are multiple-response items for which the order of the selected response is important.An example is an item that asks the user to select the instructions for performing a procedure in their properorder.

5.2.5.4 Text-response

Text-response items are items which require a textual or numeric response. Examples are short-answerquestions and supply-the-answer math questions.

5.2.5.5 Example

An example for a single-response question:

<item id="item1" type="single-response">

<question>Are bananas a fruit or a vegetable?

</question>

<resource uri="http://bananas.com/bananas.csv" />

<answer id="fruit">.

.

</answer>

<answer id="vegetable">.

.

</answer>

<hint>Bananas grow on trees.</hint>

<feedback>Bananas are a fruit.</feedback>

<key answer="fruit" />

</item>



5.2.6 Question

The question tag contains the question you are asking of the user. It can be written in plain text, or usingmarkup from another language (such as HTML, which allows you to include pictures and graphs as well astext). Be aware that the stylesheets for the Connexions project currently only allow plain text and CNXML(with and without MathML) within question tags. If you use CNXML (with or without MathML) within aQML tag, the �rst tag must be a section tag, which may contain any of the tags a CNXML section tag isallowed to contain.

5.2.6.1 Example


</question>

5.2.7 Resource

The resource tag allows you to provide a URI attribute (�le location, web address, etc.) for a particularitem. For example, if you had the necessary software, you could use the resource tag to attach a referenceto a dataset and generate question and answer values from that dataset. At the present time, Connexionshas no software to do this, and the resource tag is ignored by our stylesheets.

It also has an optional id attribute. If you are using more than one resource for a particular item andneed to keep track of which resource is which, you will want to include an id tag.

The resource tag is an empty tag, which means you must include a slash at the end of the tag.

5.2.7.1 Example

<resource uri="http://cnx.rice.edu/datasets/dataset1.csv" id="resource1" />

5.2.8 Answer, Response, and Feedback

How you construct the answer tag, including whether you include an answer tag at all, depends on youritem-type. However, in all cases where you have an answer tag, the ID of the answer tag must not containany commas, as the key tag refers to the answer IDs separated by commas.

5.2.8.1 Single-response, multiple-response, and ordered-response

To write answer tags for single-response, multiple-response, and ordered-response items:You will want one answer tag for each response option. Each answer tag has an id, which is referenced

by the key tag, below. Preferably, the id tags should have an obvious relation to the response option. Forexample, if your response options are "London, England;" "Washington, DC;" and "Paris, France" your idattributes could be london, washington, and paris.


97

Each of your answer tags should contain a response tag and may contain a feedback tag if you wishto provide feedback speci�c to that response (general feedback goes in another tag). The response tagcontains the response option, in text or markup, and has no attributes. Be aware that the stylesheets for theConnexions project currently only allow plain text and CNXML (with or without MathML) within responsetags. If you use CNXML (with or without MathML) within a QML tag, the �rst tag must be a section tag,which may contain any of the tags a CNXML section tag is allowed to contain.

The feedback tag contains feedback to be displayed to the user upon selection of that response option.The feedback may be text or markup. The feedback tag does not have attributes for single-response,multiple-response, or ordered-response items.

5.2.8.1.1 Example for a single-response question



</question>

<resource uri="http://bananas.com/banana_dataset1.csv" />

<answer id="fruit"><response>A fruit.</response>

<feedback>Correct!</feedback></answer>

<answer id="vegetable"><response>A vegetable.</response><feedback>Incorrect.</feedback>

</answer>




</item>

5.2.8.2 Text-response items

To write answer tags for text-response items: Because text-response items do not have response options,you will have either have no answer tag (if you are not providing response feedback) or only one answertag which may contain two response-speci�c feedback tags: one for a correct response, one for an incorrectresponse.

The feedback tag containing the correct feedback should have the attribute correct="yes", and the othershould have the attribute correct="no". You may also include a general feedback tag; this is recommendedas Connexions does not have plans to provide response processing for text-response items and at the present



time only shows the general feedback for the user to compare his/her answer with. The content of thefeedback tags may be text or markup; be aware that the stylesheets for the Connexions project currentlyonly allow plain text and CNXML (with or without MathML) within question tags. If you use CNXML(with or without MathML) within a QML tag, the �rst tag must be a section tag, which may contain anyof the tags a CNXML section tag is allowed to contain.

5.2.8.2.1 Example for a text-response item

<item id="item1" type="text-response">


</question>

<resource uri="http://bananas.com/bananas2.csv" />

<answer id="fruit"><feedback correct="yes">Correct!</feedback>

<feedback correct="no">Incorrect.</feedback></answer>




</item>

5.2.9 Hint

The hint tags each contain a hint to be displayed to the user upon request. The content of the hint tags istext or markup. Be aware that the stylesheets for the Connexions project currently only allow plain text andCNXML (with or without MathML) within response tags. If you use CNXML (with or without MathML)within a QML tag, the �rst tag must be a section tag, which may contain any of the tags a CNXML sectiontag is allowed to contain. The hint tag has no attributes; it is assumed that if there are multiple hints, theywill be displayed to the user in order.

5.2.9.1 Examples



99

5.2.10 Key

The key tag contains the answer key, for items for which the answer key is included.The key tag varies slightly depending on the type of item. For single-response items, the key tag contains

an "answer" attribute which refers to the id tag of the correct answer.

5.2.10.1 Example


For multiple-response items, the answer id should refer to all the necessary response ids for a correct answer,separated by commas.

5.2.10.2 Example

<key answer="fruit,yellow" />

For ordered-response items, the response ids should be in correct order and separated by commas.

5.2.10.3 Example

<key answer="uno,dos,tres,cuatro,cinco" />

For text-response items, the key tag should have no attributes, and should contain text which will be helpfulto the program or person scoring the user's answers.

5.2.10.4 Examples

<key>One example of a correct answer is "No hay nadie

aqui."</key>

<key>3.14159</key>



5.2.11 Complete examples

5.2.11.1 Stripped-down single-response item

Here is an example of a single-response item with only a question, two answers, and a key.



</question>


</answer>

<answer id="vegetable"><response>A vegetable.</response>

</answer>


</item>

5.2.11.2 Full single-response item

Here is an example of a single-response item with all options - resource, hints, and feedback.



</question>

<resource uri="http://bananas.com/yellowbananas.csv" />


<feedback>Correct!</feedback></answer>

<answer id="vegetable"><response>A vegetable.</response><feedback>Incorrect.</feedback>

</answer>



101



</item>

5.2.11.3 Stripped-down multiple-response item

Here is an example of a multiple-response item with only a question, three answers, and a key.

<item id="item1" type="multiple-response">

<question>Bananas are (pick two):

</question>


</answer>

<answer id="vegetable"><response>A vegetable.</response>

</answer>

<answer id="yellow"><response>Yellow.</response>

</answer>


</item>

5.2.11.4 Full multiple-response item

Here is an example of the same multiple-response item with all options - resource, hints, and feedback.

<item id="item1" type="multiple-response">

<question>Bananas are (pick two):

</question>

<resource uri="http://bananas.com/bananas.csv" />




<feedback>Yes, bananas are a fruit.</feedback></answer>

<answer id="vegetable"><response>A vegetable.</response><feedback>Bananas are not a vegetable.</feedback>

</answer>

<answer id="yellow"><response>Yellow.</response>

<feedback>Yes, bananas are yellow.</feedback></answer>

<hint>Bananas grow on trees.</hint><hint>Bananas are the same color as lemons.</hint>

<feedback>Bananas are a yellow fruit.</feedback>


</item>

5.2.11.5 Stripped-down ordered-response item

Here is an example of an ordered-response item with only a question, three answers, and a key.

<item id="item1" type="ordered-response">

<question>In order to boil water, you need to do the following

(please select in the correct order):

</question>

<answer id="stove"><response>Put the pot on the stove.</response>

</answer>

<answer id="pot"><response>Put water in the pot.</response>

</answer>

<answer id="boil"><response>Wait until you see bubbles in the water.</response>

</answer>


103

<key answer="pot,stove,boil" />

</item>

5.2.11.6 Full ordered-response item

Here is an example of the same ordered-response item with all options - resource, hints, and feedback.

<item id="item1" type="ordered-response">

<question>In order to boil water, you need to do the following

(please select in the correct order):

</question>

<resource uri="www.howtoboilwater.com/instructions.csv" />

<answer id="stove"><response>Put the pot on the stove.</response><feedback>You put the pot on the stove second.</feedback>

</answer>

<answer id="pot"><response>Put water in the pot.</response><feedback>You put the water in the pot first.</feedback>

</answer>

<answer id="boil"><response>Wait until you see bubbles in the water.</response><feedback>You wait for the bubbles third.</feedback>

</answer>

<hint>The pot won't boil till there's water in it.</hint>

<feedback>First you put water in the pot, then you put the

pot on the stove, then you wait for the bubbles.</feedback>

<key answer="pot,stove,boil" />

</item>

5.2.11.7 Stripped-down text-response item

Here is an example of an ordered-response item with only a question, general feedback, and a key.




<question>What are some common tests of executive function?

</question>

<feedback>Some common tests of executive function are the

Wisconsin Card Sort Test and the Tower of Hanoi.</feedback>

<key>Wisconsin Card Sort Test, Tower of Hanoi</key>

</item>

5.2.11.8 Full text-response item

Here is an example of an ordered-response item with a resource, hints, and an answer with correct andincorrect feedback.


<question>What are some common tests of executive function?

</question>

<resource uri="www.execfunc.com/tests.csv" />

<answer><feedback correct="no">Incorrect.</feedback><feedback correct="yes">Correct.</feedback>

</answer>

<hint>Think about square states and towers.</hint>

<feedback>Some common tests of executive function are the

Wisconsin Card Sort Test and the Tower of Hanoi.</feedback>

<key>Wisconsin Card Sort Test, Tower of Hanoi</key>

</item>


Chapter 6

A[ XML

6.1 Editing CNXML with Altova's Authentic1

note: Due to changes introduced in recent versions of Altova Authentic and updates to theCNXML language with version 0.6, we are not currently able to support this method for creatingand maintaining Connexions content. We hope to be able to reintroduce support in the near future.We apologize for any inconvenience. If you have any additional questions or cannot �nd the answerto your question, please contact [email protected] and we will be happy to assist in any waywe can.

6.2 Using Mathematica to Output MathML3

warning: This module contains Connexions documentation which is out-of-date. The contentsof this module are provided here for historical purposes only and should not be consideredaccurate for the current version of the Connexions website. Please visit the help page4 for up-to-date information about the Connexions website, including support for viewing and authoringcontent and the CNXML language. If you have any additional questions or cannot �nd the answerto your question, please contact [email protected] and we will be happy to assist in any waywe can.

6.2.1 Introduction

In short, Mathematica6 is a powerful math program that can be used to manipulate, evaluate, and solvemathematical equations. One of the features new to recent versions of Mathematica is the ability to outputMathML. This includes the support of content MathML as well as presentation MathML. This documentwill show you how to use Mathematica to output content MathML to input into CNXML7 documents.

warning: This method of creating content MathML only works in Mathematica 4.2 and above.We recommend you use at least version 5.0.

1This content is available online at <http://cnx.org/content/m11160/2.18/>[email protected] content is available online at <http://cnx.org/content/m11032/2.7/>.4http://cnx.org/[email protected]://www.wolfram.com/7http://cnx.rice.edu/technology/cnxml/


105

106 CHAPTER 6. A[ XML

6.2.2 Mathml Content Notebook

I have created a simple MathML notebook that anyone can use to set up Mathematica to output contentMathML. The sample notebook is available as a download from this module8.

6.2.2.1 Using the Notebook

There are a few steps you will have to follow to use the notebook:

1. Start Mathematica2. Load the content_MathML.nb by clicking the file -> open.. menu option.3. Evaluate the notebook by clicking the Kernel -> Evaluation -> Evaluate Notebook menu option.

Evaluating the notebook actually sets the options that we need. If you do not evalute the notebook, theoptions will not be set. Once you have followed these steps and ensured that there are no errors, you canproceed to the next step.

note: This document does not have any operating-system-speci�c info. For example, there willbe no info on how to start Mathematica since this varies depending on what operating system theuser is working with.

6.2.2.2 Exporting Content Mathml

Follow the instructions below to use Mathematica palettes:

1. Open the palette by clicking the File -> Palettes-> Basic Inputmenu option. (If it is not alreadyopen on startup.)

2. Build the equation you wish to export into MathML using the palette.

Now that you have created the equation using whatever method you have chosen, it is time to exportthe equation as MathML.

1. Highlight the equation you wish to export2. Copy the equation as MathML by clicking the edit -> copy as -> MathML menu option.(This will

put the equation into a bu�er that you will not see!)3. Paste the equation in the appropriate place in your CNXML document

That's it! You now have content MathML embedded into your CNXML document.

6.2.2.3 Problems to Look Out For

There may be a few di�erences in the format of the math that comes out of Mathematica. Following is alist of possible problems to look out for. This list will be updated as problems are found.

• If you plan to have your equations numbered you will need to have the MathML inside of an equation(Section 4.4.5: Equation) tag.

• When exporting an equation that has a radical, the exported math will not use the root tag, butinstead will export math with a power. For example, if you attempt to export the square root of two,the resulting MathML will be two to the one-half power.

• You may need to delete the extraneous xmlns:mathematica and mathematica:form attributes fromthe MathML output.

If you encounter a problem contact [email protected].

8See the �le at <http://cnx.org/content/m11032/latest/content_mathml.nb>


Chapter 7

ü[U+9304]

7.1 z1MÅ1

7.1.1 QcÜ¦��

.øç�A,l6QcConnexion Tutorial and Reference (Á%Ã¨�1ü - Chi-nese)z1Á�àöÜ,«E,¶��èºëÓAÜ¦�

• OOPS (Section 7.1.2: OOPS haÌ?)• Connexions ãh OCW ? (Section 7.1.3: Connexions ãh OCW ?)

7.1.2 OOPS haÌ?

OOPS2 hOpensource Opencourseware Prototype System,Á%çeÀ�¦iùz1J �#�A[U+8AAA],:hlJ�I÷�3

Y��AÍ�J �N��[U+5920]X¦i�º8A�ú�{#��%�rxuâ�¦i©ú�Á:��,�è<A0a«�´�©ú�§J ¦éQ4e¡Á¨�J AóÎÿ�4

,�|²Á%x5 �#²Á%x6 A¨�ÿ��

©úA�´h"-��áOA�¥´,ò¦i�ô:A�´$hÿd0Å©ú³ÉAdÏÙ�lî{»´��(CreativeCommons)Y,³X�{D^�2¤«Ý�º,ËéwÜ,¦ô�Á��c�,Ia«ô:A-��A�"i�¥{,%³h¨��ÊS��i�¥{,{D�2:��c#,k Ö{kÓ0Å4�A©ú�´�¦iùz1J ¾_(Opensource Opencourseware Prototype System)7 ,N�«¦i�º8Aå²�{#,uo®Ï�ØSà�Sêz1Á%¨�AJ �:�¨�J Í¦º{hÍ%02Ó�_��ú�ç�fuA,Í�<u,��I¶�4 uô�d�»e��É,700«êAÁ³ÉjÝ0¹xÜ¨�805�z1,¶�oº�ÏÓe¡I¦T��T�A¦iùz1¨�J �k�4AxÜ1ã�u[U+8AAA],�[U+5920]4X�iô�AjÝ©úã;0�´,IhTÔA`^!BóA½J 5OOPS�DJ 6�58¢�-MITØ1SàjÝÊÊJ 6¶,OOPSSpã¯»[U+840A]ÆdSAConnexions¾_�{,N��:Connexions¾_�wáwuA©ú�´,c5Connexions

� �´©ú�m��%6(Connexions � Sharing Knowledge and Building Commu-nity),ie¡ÁdS�w�Xì�mìlConnexions,cêAz1[U+5167]M¨�oÁ%�ãäô.,:6Connexions,cAa�Xn,OOPS�U[U+76FC]»[U+5167]Á Sê�ÁDÝ³É,iúeAz1[U+5167]M�$â[U+5167]M�ó©ú,ÞÏa\ã;0�´�+Q[U+60A8]êu ,ôi[U+60A8]�4p´,a«1ã��A¨�J �}%³[U+60A8]{h��A[U+95B1]��³X:@©ú,k��u[U+8AAA]khOdA®�!N�¨�J Ao,�[U+5920]ì,è<A©ú�ñ,¢Dè<Þ��Z4X��H:@©úA0É,AX��1`:�J AxØ��À��JÀ�dSêòk4��*ÍA`Îh©ú�«ô�AjÝ�´[U+5E6B]�q�Á%e¡AoI�;� fuªI,}:hª÷æ6AoI�!

7.1.3 Connexions ãh OCW ?

lÏ<¯»t�ÏAO�a,Lucifer�é�l�iÏ<Að¿(Dallas)üö,4[U+53E6]Í�ð¿À�¹Ñ(Houston),Ö�4Í�dShRiceUniversity(3»A3dS?),^�Ö�1�,��;�A¦iùz15Connexions � �´©ú�m��%6(Connexions� Sharing Knowledge and Building Community)�lGraceAÃ¨�½�Y,¥�(2005�)dèa��[U+840A]ÆdSAConnexions¾_¦º4 eÍê�H��{A°�[U+7522]y�

1This content is available online at <http://cnx.org/content/m13505/1.2/>.2http://www.myoops.org/3http://www.fantasy.org.tw/4http://www.myoops.org/5http://www.twocw.net/6http://www.cocw.net/7http://www.myoops.org/


107

108CHAPTER 7. ü[PLEASE INSERT

\PRERENDERUNICODE{\UNICHAR{37636}} INTO PREAMBLE]

l«�ConnexionsøùA¦iù~1£Á,��[U+7522]y ÿ<JJ��A¶|,Á%��4Í@ó[U+5167]MAöq8

,ÛþAhT¶k6ConnexionsA«�/Z4[U+7522]y=~©lAB�=F�ÚÒ5«�Connexions6:bá,k6�� h4Ò:AxØ��k.�u[U+8AAA],/ãhÍb�¿Aá;Òò,£Á»<�dS�w�Xìk»Ñi;�Az19

jìlConnexions,cêAéÆ,ÖvhOOPS�µÏ<Aªj�lLucifer�Grace�Connexions¾_�0A¹"(I�?)Y,TöQ6�ConnexionsÎºl^Aó�Ã¨�×z1(Connexions

Tutorial and Reference)3course4,lConnexinosA,cêm� fu�ÚÒ-4Í�[U+4EFD]z1[U+5167]M(ó6XML)�3;l^A1üÜ¦µÍm�Á%Z,}�:vh3;OOPSxØ�a«áQ�òAªj�(�©� �[U+5427],�Ï�kÜ9grA1ù½�-håå[U+61C2][U+61C2]A,Ùº�h��BA�)ôixØ^lConnexionsê¨�z1[U+5167]M,a«�«êAz1[U+5167]M¥v�ConnexionsA{Ý�Â,�È¶î{»´(Creative

Commons)Ac�,a«1ü3ÁÍ�øç5ly§63module4�ôiÁxØl��ConnexionsAéÆ �÷\A g,+Q��Íf»¦uÃ�¶|,[U+60A8]�a«÷�ÏConnexions,wpw¶|�ÙºConnexionshÍ�a«�÷\0góê¥A[ÊmA,c,a«ç�z1A^ì,a«¢�<1²Ü¦ê¥,a«iz1[U+5167]M"oPDF[U+6A94]§ØÖYu,��,�«3ú�/�wX/i¤ôAd�ôi[U+60A8]hdSÊA Á³SúÀ6ÕK°�úÀ, �ôi[U+60A8]hÍ�Sê�¾�AÍ�³¨ �, �ôi[U+60A8]hÍ�ÉµAú[U+95C6] ��Ø,[U+60A8]ka«lConnexionsêõAd[U+60A8]Az1$â[U+5167]M;6Õ6ôi[U+60A8]hÍ�{e�Í�áée Í�Sy,{^[U+60A8]4[U+503C]µ�0êã�SSAªj,kai[U+60A8]A©úlConnexionsêãde�´�òConnexions3ÁAÍ��h"-

ª³ÉA©úÃ�,:hConnexionsX4AÎ´�Connexions¾_�hÍ�áOÁA¾_,;�4<î�A°�,;��é��[U+8AAA]ConnexionsA³X�ÂlÍu-

�4<�®,6Õ;�C¶Ù~!w5÷ùÁ%6AA[¡õ,«-Í[U+6B65]-�»jZ��Ï,lPDF"[U+6A94]¶AÍ@Á%åÞl!�,-43;B�êA g,�:@k4Qè<OOPSxØ�A�ó,½�;��[Á%³XêA g,�Z�b;e¡êAÁ%��T¶4�³³Am{,£[U+60A8]lConnexionsêoÍ�¨�Ø{ Ó{AéÆ,�«[U+60A8]AjùCéAãOOPSA��´� �,£��lConnexionsAdÓ{é,a«°ã[U+7E6B]«Ã��£�Èô[U+60A8]a«l[U+60A8]AConnexionsÛ�4õê¢OOOPSAó9&,ôAlvin10

�

7.2 Grilling a Good Steak11

I have eaten many steaks in my life and none have been more satisfying than the backyard-grill cookedsteak. Maybe this is because of the relaxing nature of drinking a beer, being outside, and lounging thataccompanies the grilling procedure.

warning: Excessive drinking or fun may result in overcooked or burned steak

Maybe it is because of the aroma of the grill and the beef perfectly seasoned to your taste. Either way,this module shows how a good steak can be prepared.

Before we begin to cook I have compiled a list of ingredients.

Ingredients

• Salt• Fresh ground pepper• Lime• Beer• Chili powder• T-Bone steak

To ensure the best �avor possible, it is necessary to marinate the beef �rst. A steak marinates whenleft to sit in marinade, or prepared sauce, where it will absorb the �avor of the ingredients. Marinatingmay take as little as 15 minutes or as long as 6 hours and should always be done in the refrigerator andnot at room temperature.

Instructions

1. pour beer into large bowl2. add chili powder to tase3. squeeze half lime into beer marinade4. place steak in beer, let soak for 30 minutes

8http://forum.fantasy.org.tw/viewtopic.php?t=120659http://cnx.org/content/browse_course_institutions

10http://cnx.org/member_pro�le/alvin11This content is available online at <http://cnx.org/content/m10275/2.6/>.


109

I'll be adding to this module in The Intermediate CNXML (Section 4.4) which focuses on more advancedCNXML tags. For more marinades see the Angus Beef website12 . Finally, a good resource is the SteakLover's Cookbook � William Rice.

7.3 Grilling a Better Steak13

I have eaten many steaks in my life and none have been more satisfying than the backyard-grill cookedsteak. Maybe this is because of the relaxing nature of drinking a beer, being outside, and lounging thataccompanies the grilling procedure. Maybe it is because of the aroma of the grill and the beef perfectlyseasoned to your taste. Either way, this module shows how a good steak can be prepared.

7.3.1 Ingredients


Ingredients

• Salt• Fresh ground pepper• Lime• Beer• Chili powder• T-Bone steak

7.3.2 Marinade

To ensure the best �avor possible, it is necessary to marinate the beef. A steak marinates when left to sitin marinade, or prepared sauce, where it will absorb the �avor of the ingredients. Marinating may take aslittle as 15 minutes or as long as 6 hours and should always be done in the refrigerator and not at roomtemperature.

Marinade

1. pour beer into large bowl2. add chili powder to tase3. squeeze half lime into beer marinade4. place steak in beer, let soak for 30 minutes

12http://www.2eatcab.com13This content is available online at <http://cnx.org/content/m10278/2.9/>.




T-Bone Steak

Figure 7.1: Upon successful completion of these modules, you should be able to grill a steak that looksjust as good!


111

Steaks

(a) T-Bone (b) New York Strip





Steaks

(a) T-Bone

(b) New York Strip



113

How to grill the steak will be covered in The Advanced CNXML (Section 4.5). For more marinades see theAngus Beef website14 . Finally, a good resource is the Steak Lover's Cookbook � William Rice; Paperback.

7.4 Grilling the Best Steak15

I have eaten many steaks in my life and none have been more satisfying than the backyard-grill cookedsteak. Maybe this is because of the relaxing nature of drinking a beer, being outside, and lounging thataccompanies the grilling procedure. Maybe it is because of the aroma of the grill and the beef perfectlyseasoned to your taste. Either way, this module shows how a good steak can be prepared.

Steaks

(a) T-Bone (b) New York Strip


7.4.1 Ingredients


Ingredients

• Salt• Fresh ground pepper• Lime• Beer





• Chili powder• T-Bone

De�nition 7.1: T-Bone"The T-bone steak is cut between 1 and 3 inches thick and comes from the center section of theshort loin. This steak is characterized by its T-shape bone, has a �ne-grained shell and a smalltenderloin eye," http://www.chophousecalgary.com/steak.html.

7.4.2 Marinade

To ensure the best �avor possible, it is necessary to marinate the beef. A steak marinates when left to sitin a prepared sauce, or marinade, where it will absorb the �avors of the ingredients. Marinating may takeas little as 15 minutes or as long as 6 hours and should always be done in the refrigerator and not at roomtemperature.

Marinade

1. pour beer into large bowl2. add chili powder to taste3. squeeze half lime into beer marinade4. place steak in beer, let soak for 30 minutes5. before grilling rub salt and pepper onto steak

7.4.3 Grilling

Grilling is pretty easy. After having heated the coals or igniting the grill, start cooking the meat. I wouldrecommend periodically checking the meat and when you start to see it being cooked on top, �ip it over.Then, wait until fully cooked. Below you will �nd a table of cooking temperatures. Please note the safetywarning at the bottom.

Temperature(F) Description

140 Rare

150 Medium Rare

160 Medium

165 Medium Well

170 Well

Table 7.1

Remember that for safety's sake, always cook your steak to 160 F or until meat is no longer pink.

7.4.4 Rounding O� the Experience

The experience of grilling a steak in your own back yard is part of what makes the home cooked steak soenjoyable. It is necessary to cook in the evening as it is getting cool and to enjoy your beverage of choice.Finally, one of the best ways to enjoy a steak is in the company of your friends.

To make sure that you were paying attention to my tutorial, I've included a one question exam:

Exercise 7.4.1 (Solution on p. 118.)

For food safety, a steak should be cooked to a minimum temperature of what?


115

For more marinades see the Angus Beef website16 . Finally, a good resource is the Steak Lover's Cookbook� William Rice; Paperback.

7.5 Example module for use of cnxml/mathml tags17

A paragraph is the place for text. You can also include vocabulary terms.

note: Do not use <emphasis> for vocabulary terms.

There are two ways to present de�nitions - using the glossary to de�ne the term as above or using thedefinition tag within the text.

De�nition 7.2: problem1. a question raised for inquiry, consideration, or solution; a proposition in mathematics or physicsstating something to be done2. an intricate unsettled question; a source of perplexity, distress, or vexation; di�culty in under-standing or acceptingSee Also: enigma, puzzle

7.5.1 Section Name

A document can have sections, however they are not required.

7.5.1.1 Subsection Name

Sections can have subsections. You can include quotes in paragraphs.

The seasons alter: hoary-headed frosts Fall in the fresh lap of the crimson rose, And on oldHiems thin and icy crown An odorous chaplet of sweet summer buds Is, as in mockery, set. Thespring, the summer, The childing autumn, angry winter, change Their wonted liveries, and themazed world, By their increase, now knows not which is which. - William Shakespeare; A

Midsummer Night's Dream[?]

You can also denote words from another language, such as biological genus and species, E.coli, or the southernGerman greeting, GruÿGott.

Paragraphs can contain many other tags such as lists and �gures. Figure 7.5 (Optional Figure Name)shows how a �gure will display in our system.





Optional Figure Name

Figure 7.5: The caption of the �gure would be here.

There are four di�erent options for list. One type of list is a named-item list.

List name

�rst name - description of �rst itemsecond name - description of second itemthird name - description of third itemfourth name - description of fourth item

See the CNXML-0.5 Spec18 for more information regarding list types.

Example 7.1: Optional Name of ExampleHere is where you would put an example that relates to what the previous paragraphs werediscussing. In an example, you can include any tags that are allowed in any other paragraphincluding tables (see Table 7.2: Temperatures in 5 cities on 11/16/2002).

Temperatures in 5 cities on 11/16/2002

City Degrees Fahrenheit Degrees Centigrade

Houston 54 12.22

Chicago 37 2.78

Minneapolis 31 -0.56

Miami 78 25.56

Phoenix 70 21.11

Mean 54.000 12.22

Median 54.000 12.22

Variance 330.00 18.166

SD 101.852 10.092

Table 7.2

18http://cnx.rice.edu/cnxml/0.5/spec/


117

In the connexions system, it is important to use frame="all" with the table tag andcolsep="1" rowsep="1" with the tbody tag to properly display the table in the print system.

If you would like a block of material to display exactly as you type it, you can use <code type='block'>;as you would when discussing computer programming.

� syms t

� laplace(exp(t))

ans = 1/(s-1)

� laplace(t*exp(-t))

ans = 1/(s+1>^2

You can also include math in your document. Math can be displayed in three ways in our system: inline,block, or numbered equations. Here are examples of an inline variable, x, and an inline equation, 0 < x < π.Math that you want set apart from the text can be numbered when in an equation tag or simply set apart.

limitn→∞

‖ xn − x ‖= 0

optional equation name

P (f) =∫∞−∞ p (t) e−(i2πft)dt

=∫∆

0e−(i2πft)dt

= 1−(i2πf)

(e−(i2πf∆) − 1

) (7.1)

See our discussion of Content MathML (Section 5.1) for a more basic discussion of math. See also ourMathML Extensions page19 for more csymbol options.

Theorem 7.1: Pythagorean TheoremFor a right triangle with legs a and b and hypotenuse c,

a2 + b2 = c2

Proof:The proof would go here.

Exercise 7.5.1 (Solution on p. 118.)

What is a composite number?

19http://bunker.ece.rice.edu:8080/mntb/wikis/mathml/CSymbol




Solutions to Exercises in Chapter 7

Solution to Exercise 7.4.1 (p. 114)160 F or until the juices run clear and the meat is no longer pinkSolution to Exercise 7.5.1 (p. 117)A composite number n is a positive integer, n > 1, which is not prime.


GLOSSARY 119

Glossary

P problem

1. a question raised for inquiry,consideration, or solution; a propositionin mathematics or physics statingsomething to be done

2. an intricate unsettled question; a sourceof perplexity, distress, or vexation;di�culty in understanding or accepting

Q quarter

1. Meaning NameOne fourth of something.

Example: "He cut the pie into quartersand gave all four people a piece."

2. 25 cents, a quarter of a dollar.

Example: "The drink cost a quarter."

Example: "She picked up a roll ofquarters so that she could do laundry."

T T-Bone

"The T-bone steak is cut between 1 and 3inches thick and comes from the centersection of the short loin. This steak ischaracterized by its T-shape bone, has a�ne-grained shell and a small tenderloineye,"http://www.chophousecalgary.com/steak.html.

T-Bone

"The T-bone steak is cut between 1 and 3inches thick and comes from the centersection of the short loin. This steak ischaracterized by its T-shape bone, has a�ne-grained shell and a small tenderloineye,"http://www.chophousecalgary.com/steak.html.

Example:

T-Bone Steak

This is an unsupported media type. To view, pleasesee http://cnx.org/content/m9006/latest/

Figure 4.1

V vocabulary term

A word or phrase being de�ned in thetext. A more complete de�nition with anexample could be placed here in theglossary.


120 BIBLIOGRAPHY


Bibliography

[1] Harald Martens; Tormod Nas. Multivariate Calibration. John Wiley & Sons Ltd., Chichester, 1989.

[2] Kim Esbensen; Tonje Midtgaard; Suzanne Schonkopf. Multivariate Analysis in Practice. Camo AS,Trondheim, 1994.

[3] William Shakespeare. A midsummer night's dream. In Alfred Harbage, editor, William Shakespeare:

The Complete Works, chapter 2.1, pages lines 107�114. The Viking Press, 1969.


121

122 INDEX

Index of Keywords and Terms

Keywords are listed by the section with that keyword (page numbers are in parentheses). Keywordsdo not necessarily appear in the text of the page. They are merely associated with that section. Ex.apples, � 1.1 (1) Terms are referenced by the page they appear on. Ex. apples, 1

. .cnxml, 36

A alternate, � 3.4(45)Altova, � 6.1(105)annotation, � 1.3(7)annotations, � 2.1(13)apply, � 5.1(87)attribute, � 4.1(57), 58audio, � 3.4(45)authentic, 32, � 6.1(105)author, � 1.1(1)

B beef, � 7.2(108)bibtexml, � 4.6(80)browser, � 2.1(13)bug, � 1.1(1), � 1.2(7)

C caption, � 4.4(69)categories, � 4.5(77)category, � 4.5(77)character references, 59Chinese, � 7.1(107)ci, � 5.1(87), 88cn, � 5.1(87), 88CNXML, � 4.3(60), � 4.4(69), � 6.1(105),� 7.3(109), � 7.4(113), � 7.5(115)cnxml example, � 7.2(108)cnxml.sps, � 6.1(105)codeblock, � 4.4(69)codeline, � 4.4(69)collaborate, � 3.6(53)Connexions, � 2.1(13), � 4.3(60), � 7.1(107)connexions project, � 1.1(1)content, � 3.3(29), � 4.3(60)Content CommonsÜ¦É»�ª, 8content mathml, � 5.1(87), � 6.2(105)Content Section, 61copy, � 3.5(52)course, � 3.2(22)course composer, � 3.2(22)Courseview, � 2.1(13)csymbol, � 5.1(87), 88

D de�nition, � 4.5(77), � 4.6(80)derivative, � 3.5(52)derive, � 3.5(52)di�erentiation, � 5.1(87)discussion, � 1.4(10)document, � 4.3(60)DTD, 58, � 4.2(59)

E edit, � 6.1(105)editing, � 3.3(29), � 6.1(105)elem, � 4.5(77)empty tag, 58, 78empty tags, 88enigma, 115entity, � 4.1(57)entity references, 58equation, � 4.4(69)error, � 1.2(7)error message�¾9&, 7example, � 4.5(77)exercise, � 4.5(77)

F �gure, � 4.4(69)�ash, � 3.4(45)forum, � 1.4(10)function, � 5.1(87)

G general information, � 1.1(1)glossary, � 4.6(80)grilling, � 7.2(108), � 7.3(109), � 7.4(113)group, � 3.2(22), � 4.5(77)

H home page, � 1.1(1)

I identi�er, 88image, � 3.4(45)instructor, � 1.1(1)integration, � 5.1(87)

J java applet, � 3.4(45)

L learning assessment, � 5.2(93)locate, � 1.3(7)


INDEX 123

log in, � 1.1(1)

M marinade, 108, 109, 114marinates, 108, 109, 114markup, � 4.3(60)markup language, 57mathematica, � 6.2(105)mathml, � 5.1(87), � 6.2(105), � 7.5(115)matrix, � 5.1(87)meaning, � 4.5(77)media, � 4.4(69)message, � 1.4(10)meta-markup language, 57metadata, � 3.3(29)Metadata Section, 61metadataÆ~Ü¦, 10module, � 3.2(22), � 3.5(52)modules, � 3.3(29)movie, � 3.4(45)mpeg, � 3.4(45)multimedia, � 3.4(45)multimedia object, � 3.4(45)music, � 3.4(45)

N n-ary operator, 89namespace, � 4.2(59), � 4.3(60), 62namespace pre�x, 60namespaces, 60nesting, � 4.1(57)notes, � 1.3(7)

O omission, � 7.1(107)operator, � 5.1(87)

P patch, � 3.6(53)pre�x, � 5.1(87)Pre�x notation, 87problem, � 4.5(77), 115proof, � 4.5(77)puzzle, 115

Q qml, � 5.2(93)questions markup language, � 5.2(93)quicktime, � 3.4(45)

R real audio, � 3.4(45)

report, � 1.1(1)roadmap, � 2.1(13)role, � 3.3(29)root node, 60rule, � 4.5(77)

S section, � 4.4(69)snapshot, � 3.5(52)solution, � 4.5(77)sounds, � 3.4(45)statement, � 4.5(77)steak, � 7.2(108), � 7.3(109), � 7.4(113)student, � 1.1(1), � 1.3(7)style�Å, 10sub�gure, � 4.4(69)suggest edits, � 3.6(53)supplement, � 7.1(107)

T T-Bone, 74, 114table, � 4.5(77)tag, � 4.3(60)Tags, 57task, � 1.2(7)term, � 4.5(77)Title, 60token, � 5.1(87), 88tutorial, � 2.1(13), � 3.2(22), � 4.2(59),� 5.2(93), � 7.3(109), � 7.4(113)

U unicode, � 4.1(57), 59

V valid, � 4.1(57), 58vector, � 5.1(87)view, � 1.3(7)vocabulary terms, 115

W well-formed, � 4.1(57), 58

X xml, � 4.1(57), 57, � 4.2(59), � 4.3(60)XML declaration, 58xmlspy, 32, � 6.1(105)

g gó, 5

Q Qc, � 7.1(107)

� �¾, 7


124 ATTRIBUTIONS

Attributions

Collection: Connexions Tutorial and Reference (Á%Ã¨�1ü - Chinese)Edited by: Brent Hendricks, Adan Galvan, Mark Husband, Wei-Cheng WongURL: http://cnx.org/content/col10340/1.2/License: http://creativecommons.org/licenses/by/2.0/

Module: "Introduction to Connexions (Á%[U+8AAA]é - Chinese)"Used here as: "Connexions ó�"By: Mark Husband, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13477/1.3/Pages: 1-6Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Introduction to ConnexionsBy: Mark HusbandURL: http://cnx.org/content/m10884/2.22/

Module: "Reporting a Connexions Bug (Á%[U+8AAA]é - Chinese)"Used here as: "`¨ Connexions �¾9&"By: Mark Husband, Wei-Cheng WongURL: http://cnx.org/content/m13478/1.4/Page: 7Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Reporting a Connexions BugBy: Mark HusbandURL: http://cnx.org/content/m11836/1.4/

Module: "Viewing Connexions Content (Á%[U+8AAA]é - Chinese)"Used here as: "B Connexions Ü¦"By: Mark Husband, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13480/1.3/Pages: 7-10Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Viewing Connexions ContentBy: Mark HusbandURL: http://cnx.org/content/m11837/1.9/

Module: "Connexions Discussion Forums (Á%[U+8AAA]é - Chinese)"Used here as: "Connexions ¿ê� "By: Mark Husband, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13481/1.3/Pages: 10-11Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Connexions Discussion ForumsBy: Mark HusbandURL: http://cnx.org/content/m12613/1.1/


ATTRIBUTIONS 125

Module: "Roadmap Tutorial (Á%[U+8AAA]é - Chinese)"Used here as: "ì�¿Ã¨"By: Elizabeth Bartmess, Mark Husband, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13479/1.3/Page: 13Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Roadmap TutorialBy: Elizabeth Bartmess, Mark HusbandURL: http://cnx.org/content/m10338/2.21/

Module: "Work Areas (Á%[U+8AAA]é - Chinese)"Used here as: "Ø{�É"By: Mark Husband, Adan Galvan, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13482/1.3/Pages: 15-22Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Work AreasBy: Mark Husband, Adan GalvanURL: http://cnx.org/content/m10885/2.20/

Module: "How to Use the Course Composer (Á%[U+8AAA]é - Chinese)"Used here as: "ô\³Xz1A[�"By: Sarah Coppin, Mark Husband, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13489/1.3/Pages: 22-29Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: How to Use the Course ComposerBy: Sarah Coppin, Mark HusbandURL: http://cnx.org/content/m10288/2.19/

Module: "Editing Modules (Á%[U+8AAA]é - Chinese)"Used here as: "A[øç"By: Mark Husband, Adan Galvan, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13493/1.3/Pages: 29-44Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Editing ModulesBy: Mark Husband, Adan GalvanURL: http://cnx.org/content/m10887/2.23/


126 ATTRIBUTIONS

Module: "Adding Multimedia to Your Connexions Content (Á%[U+8AAA]é - Chinese)"Used here as: "[U+589E]`<1²�b"By: Adan Galvan, Mark Husband, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13497/1.3/Pages: 45-52Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Adding Multimedia to Your Connexions ContentBy: Adan Galvan, Mark HusbandURL: http://cnx.org/content/m12660/1.5/

Module: "Derived Copy (Á%[U+8AAA]é - Chinese)"Used here as: "ly§"By: Mark Husband, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13498/1.3/Pages: 52-53Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Derived CopyBy: Mark HusbandURL: http://cnx.org/content/m11804/1.5/

Module: "Suggest Edits (Á%[U+8AAA]é - Chinese)"Used here as: "m{A["By: Mark Husband, Wei-Cheng Wong, ConnexionsURL: http://cnx.org/content/m13499/1.3/Pages: 53-55Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/Based on: Suggest EditsBy: Mark HusbandURL: http://cnx.org/content/m11817/1.6/

Module: "XML Basics"By: Connexions, Sarah Coppin, Brent Hendricks, Chuck BeardenURL: http://cnx.org/content/m9002/2.24/Pages: 57-59Copyright: Connexions, Sarah Coppin, Brent Hendricks, Chuck BeardenLicense: http://creativecommons.org/licenses/by/1.0

Module: "Combining XML Languages"By: Sarah Coppin, Brent Hendricks, ConnexionsURL: http://cnx.org/content/m10159/2.16/Pages: 59-60Copyright: Sarah Coppin, Brent HendricksLicense: http://creativecommons.org/licenses/by/1.0

Module: "The Basic CNXML"By: Ricardo Radaelli-Sanchez, Brent Hendricks, ConnexionsURL: http://cnx.org/content/m9000/2.36/Pages: 60-69Copyright: Ricardo Radaelli-SanchezLicense: http://creativecommons.org/licenses/by/1.0


ATTRIBUTIONS 127

Module: "The Intermediate CNXML"By: Ricardo Radaelli-Sanchez, ConnexionsURL: http://cnx.org/content/m9006/2.22/Pages: 69-77Copyright: Ricardo Radaelli-SanchezLicense: http://creativecommons.org/licenses/by/1.0

Module: "The Advanced CNXML"By: Ricardo Radaelli-Sanchez, ConnexionsURL: http://cnx.org/content/m9007/2.24/Pages: 77-80Copyright: Ricardo Radaelli-SanchezLicense: http://creativecommons.org/licenses/by/1.0

Module: "CNXML Reference Extensions"By: Adan GalvanURL: http://cnx.org/content/m11215/1.8/Pages: 80-85Copyright: Adan GalvanLicense: http://creativecommons.org/licenses/by/1.0

Module: "Content MathML"By: Sarah Coppin, Brent HendricksURL: http://cnx.org/content/m9008/2.15/Pages: 87-93Copyright: Sarah Coppin, Brent HendricksLicense: http://creativecommons.org/licenses/by/1.0

Module: "QML 1.0 tutorial"By: Elizabeth Bartmess, ConnexionsURL: http://cnx.org/content/m10138/2.11/Pages: 93-104Copyright: Elizabeth BartmessLicense: http://creativecommons.org/licenses/by/3.0/

Module: "Editing CNXML with Altova's Authentic"By: Adan Galvan, Brent Hendricks, Mark Husband, ConnexionsURL: http://cnx.org/content/m11160/2.18/Page: 105Copyright: Adan Galvan, Brent Hendricks, Mark HusbandLicense: http://creativecommons.org/licenses/by/1.0

Module: "Using Mathematica to Output MathML"By: Adan Galvan, ConnexionsURL: http://cnx.org/content/m11032/2.7/Pages: 105-106Copyright: Adan GalvanLicense: http://creativecommons.org/licenses/by/1.0


128 ATTRIBUTIONS

Module: "Supplement in Connexions Chinese Course (Connexions MÅ)"Used here as: "z1MÅ"By: Wei-Cheng WongURL: http://cnx.org/content/m13505/1.2/Pages: 107-108Copyright: Wei-Cheng WongLicense: http://creativecommons.org/licenses/by/2.0/

Module: "Grilling a Good Steak"By: Sarah Coppin, Ricardo Radaelli-SanchezURL: http://cnx.org/content/m10275/2.6/Pages: 108-109Copyright: Sarah Coppin, Ricardo Radaelli-SanchezLicense: http://creativecommons.org/licenses/by/1.0

Module: "Grilling a Better Steak"By: Sarah Coppin, Ricardo Radaelli-SanchezURL: http://cnx.org/content/m10278/2.9/Pages: 109-113Copyright: Sarah Coppin, Ricardo Radaelli-SanchezLicense: http://creativecommons.org/licenses/by/1.0

Module: "Grilling the Best Steak"By: Sarah CoppinURL: http://cnx.org/content/m10281/2.7/Pages: 113-115Copyright: Sarah CoppinLicense: http://creativecommons.org/licenses/by/1.0

Module: "Example module for use of cnxml/mathml tags"By: Charlet ReedstromURL: http://cnx.org/content/m11216/1.3/Pages: 115-117Copyright: Charlet ReedstromLicense: http://creativecommons.org/licenses/by/1.0


Connexions Tutorial and Reference (Á%Ã¨�1ü - Chinese)Connexions Ã¨�1üm¦Á%xz1�(Chinese tutorial and reference materials for getting started withConnexions.)

About ConnexionsSince 1999, Connexions has been pioneering a global system where anyone can create course materials andmake them fully accessible and easily reusable free of charge. We are a Web-based authoring, teaching andlearning environment open to anyone interested in education, including students, teachers, professors andlifelong learners. We connect ideas and facilitate educational communities.

Connexions's modular, interactive courses are in use worldwide by universities, community colleges, K-12schools, distance learners, and lifelong learners. Connexions materials are in many languages, includingEnglish, Spanish, Chinese, Japanese, Italian, Vietnamese, French, Portuguese, and Thai. Connexions is partof an exciting new information distribution system that allows for Print on Demand Books. Connexionshas partnered with innovative on-demand publisher QOOP to accelerate the delivery of printed coursematerials and textbooks into classrooms worldwide at lower prices than traditional academic publishers.

Connexions Tutorial and Reference Á Ã 1 ü - Chinese)

Documents

Transcript of Connexions Tutorial and Reference Á Ã 1 ü - Chinese)