Math-Net Professional Personal Homepage Application Profile 1.0 Reference Description

editedBy:

Math -Net TAB

created: 2002-10-17
modified: 2002-11-13
modified: 2002-12-09

next/current version: http://www.iwi-iuk.org/material/RDF/1.1/profile/MNPerson/


isRequiredBy:
http://www.iwi-iuk.org/material/RDF/1.1/profile/MNPerson/mnperson.rdf

requires:
http://www.iwi-i uk.org/material/RDF/1.1/Schema/Class/
http://ww w.iwi-iuk.org/material/RDF/1.1/scheme/Type/

conformant:
MMMP Version 2.1

references:
PERSONA MATHEMATICA

MetaData: http://www.iwi-iuk.org/material/RDF/1.1/profile/MNPerson/index.rdf
MD Visualization: http://www.iwi-iuk.org/material/RDF/1.1/profile/MNPerson/index.html.rdf.png


This Reference Description explains about MetaData for Professional Personal Homepages ready for use with PERSONA MATHEMATICA.
http://www.iwi-iuk.org/material/ RDF/1.1/profile/ MNPerson/mnperson.rdf provides RDF/XML code for use.

The logical structure of the MetaData for a test HomePage can be read from a graph representation.
There is also a sample implementation using linking from XHTML. The embedding method of MMMP Version 2.1 will be changed to linking in Version 2.2.

For the description of a given preprint the variables in this reference description have to be replaced by concrete URLs or by text.

All MetaData entries are optional and repeatable.

A conformant tool for generation is MMMP Version 2.1. MMMP V2.1 embeds the MetaData in XHTML.



Math-Net Professional Personal Homepage MetaData package



<?xml version="1.0" encoding="E"?>
<rdf:RDF
       xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
       xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
       xmlns:dc="http://purl.org/dc/elements/1.1/"
       xmlns:dct="http://purl.org/dc/terms/"
       xmlns:mn="http://www.iwi-iuk.org/material/RDF/1.1/Schema/Class/mn#"
       xmlns:mnst="http://www.iwi-iuk.org/material/RDF/1.1/descriptor/#"
       xmlns:vCard="http://www.w3.org/2001/vcard-rdf/3.0#">

RDF/XML namespace header. Encoding by default is UTF-8. Other choices are possible, but must be given explicitly.




<mn:PersonalHomePage rdf:about="X_0"
  dc:rights=
  "These personal data may not be used for any commercial 
   purpose or incorporated in mailing lists without written 
   permission of the person identified by these data as creator. 
   They are free for use by information and communication services of 
   learned societies."
 dc:title="Professional Personal Homepage of X_1 X_2 X_3"
 dc:description="Personal and professional data of X_1 X_2 X_3 as a member of Faculty/Staff of X_7; X_8">
  
  <dct:modified>
   <dct:W3CDTF rdf:value="YYYY-MM-DD" rdfs:label="DD Month YYYY"/>
  </dct:modified>


This piece of MetaData declares the current resource as a professional personal homepage.
In an instance X_0 has to be substituted with the URL of the homepage.
The rights disclaimer is fixed text.
Title and short description are composed from MetaData detailed below from personal and organizational data. Literal prasetype is choosen for internationalization issues.
The last modification date of the homepage in format YYYY-MM-DD should be recalled as label with the name of the month in plain English.



The following sections provide MetaData for the person.



<dc:creator>
   <mn:Person            
                            vCard:FN="X_1 X_2 X_3"
                            rdfs:label="X_1 X_2 X_3"
                            vCard:EMAIL="X_4"
                            vCard:TITLE="X_5">
        <vCard:N>
         <rdf:Description 
                             vCard:Family="X_3"
                             vCard:Given=X_2"
                             vCard:Prefix="X_1"/>
        </vCard:N>
        <vCard:PHOTO rdf:resource="X_6"/>
        <vCard:ORG>
          <rdf:Description vCard:Orgname="X_7">
           <vCard:Orgunit>
             <rdf:Seq>
              <rdf:li>
               <rdf:Description rdfs:label="X_8">
               <dc:identifier>
                  <mn:MathNetPage rdf:about="X_9"/>
               </dc:identifier>
               </rdf:Description>
             </rdf:li>
           </rdf:Seq>
         </vCard:Orgunit>
         </rdf:Description>
        </vCard:ORG> 
        <vCard:ADR>
          <rdf:Description 
                              vCard:Street="X_10"
                              vCard:Locality="X_11"
                              vCard:Pcode="X_12"
                              vCard:Country="X_13"/>
        </vCard:ADR>
        <vCard:ROLE>
         <rdf:Bag rdf:_1="X_14"/>
        </vCard:ROLE>
        <vCard:TEL>
         <vCard:voice rdf:value="X_15"/>
        </vCard:TEL>
        <vCard:TEL>
         <vCard:fax rdf:value="X_16"/>
        </vCard:TEL>


X_1 will be substituted with name prefixes in instance data,
X_2 with the given name(s) (when there is more than one use a whitespace as separator),
X_3 with the family name (when there is more than one part use whitespace as separator),
X_4 with an e-mail address (when there is more than one repeat the field),
X_5 with the title of the profession,
X_6 with a URL of a personal photo (when there is more than one photo repeat the field),
X_7 with the name of the University (or other Organization) the person in question is emploid with,
X_8 with the name of the Department (as Identifier X_9 use the URL of it's Math-Net Page). When there is need to further detail the description of organizational units amend the list, but only with names of subunits.
X_10 will be substituted in instance data with street name and number of the smallest subunit mentioned,
X_11 with the name of the city it's located in,
X_12 with the postal code,
X_13 with the name of the country.
X_14 in instance data gives an unordered list of specific professional tasks of the person in question,
X_15 will be substituted by international telefon number,
X_16 by international fax number most suitable for the person.



The following piece of MetaData links the person with information about hers/his professional activities.



    <dct:isReferencedBy>
       <mnst:Articles rdf:about="Y_1"/>
    </dct:isReferencedBy>
    <dct:isReferencedBy>
       <mnst:Preprints rdf:about="Y_2"/>
    </dct:isReferencedBy>
    <dct:isReferencedBy>   
       <mnst:CourseInformationAndMaterials rdf:about="Y_3"/>
    </dct:isReferencedBy>
    <dct:isReferencedBy>    
       <mnst:ResearchGroups rdf:about="Y_4"/>
    </dct:isReferencedBy>
    <dct:isReferencedBy>
       <mnst:Projects rdf:about="Y_5"/>
    </dct:isReferencedBy>
    <dct:isReferencedBy>   
       <mnst:ClassSchedules rdf:about="Y_6"/>
    </dct:isReferencedBy>

In instance data Y_1 will represent a resource with information about refereed articles (co-)authored by the person,
Y_2 comes with (information about) hers/his preprints,
Y_3 is for course information and materials provided by the person,
Y_4 for (information about) research group(s) the person is involved with,
Y_5 for (information about) projects the person is involved with,
Y_6 for hers/his class schedules.



The next two entries provide search URLs for the preprints/ refereed articles in MPRESS and Zentralblatt. A typical MetaData creation tool will generate those automatically from the personal data already given.



   <dct:isReferencedBy>
      <mn:MPRESS rdf:about="Z_1"/>
   </dct:isReferencedBy> 
   <dct:isReferencedBy>
     <mn:ZblMath rdf:about="Z_2"/>
   </dct:isReferencedBy>



In the next section the mathematical interests of the person are classified by means of MSC2000



   <dc:subject>
       <mn:MSC2000 rdf:value="W_1" rdfs:label="W_2"/>
   </dc:subject>


The value W_1 is the classification code,
W_2 the caption of W_1.
When there is more than one entry matching the construction should be repeated.



Interests may be described also using PACS, ACM or ZDM classification codes. It would be desirable to have these schemes available in the same way as MSC2000, but currently a slightly less expressive way of coding has to be used



   <dc:subject>
      <mn:Descriptor rdf:value="V_1">
        <rdfs:isDefinedBy rdf:resource="http://publish.aps.org/PACS/pacsgen.html"/>
      </mn:Descriptor>
   </dc:subject>
   <dc:subject>
       <mn:Descriptor rdf:value="V_2">
         <rdfs:isDefinedBy rdf:resource="http://www.acm.org/class/1998/"/>
       </mn:Descriptor>
   </dc:subject>
   <dc:subject>
       <mn:Descriptor rdf:value="V_3">
         <rdfs:isDefinedBy rdf:resource="http://www.mathematik.uni-osnabrueck.de/projects/zdm/"/>
       </mn:Descriptor> 
   </dc:subject>


V_1 represents a PACS code,
V_2 an ACM code, and
V_3 an ZDM code.
When there is more than one entry matching the corresponding construction should be repeated.



Additional items of interest of the person can be given in form of uncontrolled keywords and -phrases.



    <dc:subject>
     <rdf:Bag rdf:_1="V_4"/>
    </dc:subject>

V_4 is a keyword or key phrase.
When there is more than one entry matching the bag should be extended.



A text with a description of the person can be linked within the same file via:



  <dc:description rdf:resource="#mission"/>



The MetaData section on the person and the homepage syntactically closes with:


 
     </mn:Person>
   </dc:creator>
 </mn:PersonalHomePage>



The next section formally aligns the use of Descriptors with the Math-Net Type Scheme.



<mnst:Descriptor rdf:about="http://www.iwi-iuk.org/material/RDF/1.1/descriptor/#ResearchGroups" 
  rdf:value="information about research groups"/>

<mnst:Descriptor rdf:about="http://www.iwi-iuk.org/material/RDF/1.1/descriptor/#Preprints"
  rdf:value="information about preprints"/>

<mnst:Descriptor rdf:about="http://www.iwi-iuk.org/material/RDF/1.1/descriptor/#Articles"
  rdf:value="information about refereed articles"/>

<mnst:Descriptor rdf:about="http://www.iwi-iuk.org/material/RDF/1.1/descriptor/#Projects"
  rdf:value="information about projects"/>


<mnst:Descriptor rdf:about="http://www.iwi-iuk.org/material/RDF/1.1/descriptor/#ClassSchedules"
  rdf:value="information about lectures"/>

<mnst:Descriptor 
  rdf:about="http://www.iwi-iuk.org/material/RDF/1.1/descriptor/#CourseInformationAndMaterials"
  rdf:value="information about courses and materials"/>



At the place the mission is given the following code has to wrap the text:



  <rdf:Description rdf:ID="mission">
   <rdf:value rdf:parseType="Literal" xml:lang="x">
    Text of mission statement in language x 
   </rdf:value>
  </rdf:Description>
</rdf:RDF>



IWI Logo Math-Net Logo Valid XHTML 1.0!