<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE rdf:RDF [
   <!ENTITY sv  "http://www.senselogic.se/2006/10/26/sitevision#" >
   ]>

<!--
Example RDF file that can be imported into a SiteVision installation using the import tool.

The format is based on common RDF vocabularies such as RSS, RSS Content, and Dublin Core. Some SiteVision-specific
extensions are specified using the SiteVision namespace.

See comments below for specific details.

(Note that accepted RDF format in the future might differ between Sitevision versions. Latest version of 
 this example document can be found at Sitevision's documentation website - http://documentation.senselogic.se.)
-->
<rdf:RDF
   xmlns="&sv;"
   xmlns:sv="&sv;"
   xml:base="&sv;"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:rss="http://purl.org/rss/1.0/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/">

   <!-- A channel represents a folder, archive or page in SiteVision that already exists, and where the pages should be created under.
        "dc:identifier" is used to locate which folder, archive or page to use. Make sure to either specify both a proper hostname and id, or the short id of the page.
        The articles or pages to be created should be enumerated using "rss:items" 
        
        "rdf:resource" is a identifier for a resource that is further defined in an rss:item later on (rdf:resource is matched to rdf:about on rss:item). 
        This identifier will be saved the by the Sitevision server when doing an import so the identifier can be used for subsequent import updates.
        To ensure that the identifier actually is unique (on importing server) it is strongly recommended that you always use some kind of namespace/prefix.
   -->
   <rss:channel dc:identifier="http://localhost/3.7119907f1085211398f7fff285.html">
      <rss:items>
         <rdf:Seq>
            <rdf:li rdf:resource="myimportingapp:examples:article1"/>
         </rdf:Seq>
      </rss:items>
   </rss:channel>

   <!-- An item represents a page that either exists (if "dc:identifier" is specified) or which should be created by the import service.

        If a page is created the following properties are mandatory:
          * sv:template is used to specify, by name, which template to use. 

        The following properties may be used when creating/updating pages:
          * sv:force - whether or not an existing page that has been manually changed should be updated. Defaults to true.
                       When false: Information will be overwritten only if modified date is equal to (or less than) creation date for actual object.
                           If no modified date is supplied the creation date will be used (i.e "info not modified since creation"). 
          * dc:title - name of page
          * sv:hidden - whether the page should be hidden
          * sv:indexable - whether the page should be indexed
          * dc:created - date of creation
          * dc:creator - user that created the page
          * dc:modified - modified date
          * dc:available - when the page becomes available. If in the future then it will be published at that time
          * dc:publisher - the users that published the page
          * dc:valid - when the page becomes unavailable. If it is in the future then it will be unpublished at that time. 
                       If it is in the past the resource will not be published at all.

        Format of dates: yyyy-MM-dd mm:hh:ss, where time is optional (yyyy-MM-dd). Examples: "2006-10-26 10:34:00" and "2006-10-26". 
        If date properties are omitted todays date ("now") will be used, except for the valid date which will be left blank, i.e. it will never be unpublished.
        If force attribute is used and has a false value ("Don't overwrite") and no modified date is supplied, the creation date will be used as modified date.

        Users will be looked up by username (cn attribute). 
        Other attributes can be used if they are specified in the following way: mail=someuser@somecompany.com
        If omitted, the system user will be used

        Custom metadata values can be updated by matching the name of the metadata with the local XML name in the RDF, ignoring case. Schemas will be removed
        from the name in SiteVision before comparison. If, for example, the SiteVision metadata is named "DC.Description" it can be updated
        by adding the RDF predicate "dc:description", since the local name "description" of the RDF data matches the local name of the SiteVision 
        metadata ("Description"), ignoring case. NOTE! Ensure that name of existing metadata only appears once on the resource. If multiple metadata definitions 
        with the same name are used the name matching is indefinite. Most commonly the first occurance is used, but that is nothing you ever should rely on.
        Currently the following metadata types are supported:
          * Text
          * Multiple values. The content in RDF must be a comma-separated ("a,b") string of the values to be selected.
          * Text portlet. The content in RDF will be injected into the portlet tied to the metadata definition. The style of any currently available text will be reused. 
                          Single line breaks (<br />) in text will break text and double line breaks (<br /><br />) will create a paragraph in the portlet.
          * Date. Format must be as stated above (or a format matching the custom date pattern that the the metadata definition is configured to use).
    -->
   <rss:item rdf:about="myimportingapp:examples:article1" dc:title="Some page" sv:template="Nyhetsmall" sv:force="false" sv:hidden="false" sv:indexable="true">
      <!-- 
         Properties
      -->
      <dc:created>2006-10-01</dc:created>
      <dc:creator>magnus</dc:creator>
      <dc:modified>2006-10-05</dc:modified>
      <dc:available>2006-10-10 15:30:00</dc:available>
      <dc:publisher>mail=magnus.lovgren@senselogic.se</dc:publisher>
      <dc:valid>2008-12-10</dc:valid>

      <!-- 
         Custom metadata 
      -->
      <!-- Text metadata -->
      <dc:description>This is a page</dc:description>
      
      <!-- Multi-value metadata -->
      <dc:subject>foo,bar</dc:subject>
      
      <!-- User metadata -->
      <sv:editor>calle</sv:editor>

      <!-- 
         HTML content of page. 
      -->
      <!-- Portlets will be created in the content area specified by dc:title. If no dc:title is specified, portlets will be created in the first content area.
           Currently text, image, and table portlets are supported. Image references will resolved against images on the page first, then images in the image repository 
           on the site. Links will be resolved to real SiteVision pages if possible.
           Links using filenames of files on the page will be resolved properly.
      -->
      <sv:content rdf:parseType="Resource">
         <dc:title>Center column</dc:title>
         <content:encoded>
            <![CDATA[
               <img alt="Logo" src="Mallar/senselogic.png" />
               <p>What a <em>beautiful</em> <a href="/moduldemo.html">day</a>!</p> 
               <img src="logo.jpg" />
             ]]>
         </content:encoded>
      </sv:content>

      <!-- Layouts will be generated for each div element with a layout attribute ("vertical" or "horizontal") in HTML content.
           If a name attribute exists, it will be used as the name of the layout.
           A layout can also be given a named site decoration or a style. If a div has both (decoration AND style), the style will be ignored.
           If you add an anchor link as the first element of a div tag with content, the name of the anchor will be used as the name of the subsequent portlet to be created.
      -->
      <sv:content rdf:parseType="Resource">
         <dc:title>Right column</dc:title>
         <content:encoded>
            <![CDATA[
               <h2 title="Main header">Welcome</h2>
               <img alt="Flower" src="Vykort/blad.jpg" />
               <div layout="horizontal" decoration="Info box" name="Info">
                  <div>
                    <a name="A text" />
                    <p>What a <em>beautiful</em> <a href="/moduldemo.html">day</a>!</p>
                  </div>
                  <div><a name="A table" />
                  <table summary="This is an example table">
                    <caption>A caption</caption>
                    <tr>
                      <th>A header</th><th>Another header</th>
                    </tr>
                    <tr>
                      <td>A cell</td><td style="text-align: right">Another cell</td>
                    </tr>
                  </table>
                  </div>
                  <div layout="vertical" name="Image" style="margin: 10px; border: thin solid black">
                     <img src="testfil.jpg" />
                     <div>Test<p>Foo</p></div>
                  </div>
               </div>
             ]]>
         </content:encoded>
      </sv:content>

      <!-- Note. All subsequent text content (i.e. not a table or image) is placed in the same text portlet by default.
               If you want to alter this behaviour you can use the generator element. If it has a value that starts with "SiteVision"
               it will always create a new portlet if a div is followed by an anchor.
      -->
      <sv:content rdf:parseType="Resource">
         <sv:generator>SiteVision</sv:generator>
         <dc:title>Footer area</dc:title>
         <content:encoded>
            <![CDATA[
                <div><a name="A footer text" />
                    <p>This is a text</p>
                </div>
                <div><a name="Another footer text" />
                    <p>This is another text</p>
                </div>
             ]]>
         </content:encoded>
      </sv:content>

      <!--
         Specifies what files to create and store on the page 
      -->
      <sv:files>
         <rdf:Seq>
            <rdf:li>
               <sv:file
                  rdf:about="http://www.skatteverket.se/download/18.dfe345a107ebcc9baf80008699/200215.pdf">
                  <dc:title>skv.pdf</dc:title>
               </sv:file>
            </rdf:li>
         </rdf:Seq>
      </sv:files>

      <!-- 
         Specifies what images to create and store on the page 
      -->
      <sv:images>
         <rdf:Seq>
            <rdf:li>
               <sv:file rdf:about="http://www.senselogic.se/images/18.2f85b5f110c3d24f3468000114/senselogic.jpg">
                  <dc:title>logo.jpg</dc:title>
               </sv:file>
            </rdf:li>
         </rdf:Seq>
      </sv:images>

   </rss:item>


   <!--
           This will create the page "anotherpage1" under the existing page corresponding to the path "moduldemo.html" on the site with hostname "localhost"
   -->
   <rss:channel dc:identifier="http://localhost/moduldemo.html">
      <rss:items>
         <rdf:Seq>
            <rdf:li rdf:resource="myimportingapp:examples:anotherpage1"/>
         </rdf:Seq>
      </rss:items>
   </rss:channel>

   <rss:item rdf:about="myimportingapp:examples:anotherpage1" dc:title="Another page!" sv:template="Nyhetsmall" sv:hidden="false" sv:indexable="true">

      <sv:content rdf:parseType="Resource">
         <dc:title>Center column</dc:title>
         <content:encoded>
            <![CDATA[
            <h2>This is a header</h2>
            <p class="gronxfetxnormal">What a <em>beautiful</em> <a href="/moduldemo.html">day</a>!</p> 
            <img src="logo.jpg" /> <br />
            Here you can <a href="skv.pdf">download</a> a document.]]>
         </content:encoded>
      </sv:content>

      <sv:files>
         <rdf:Seq>
            <rdf:li>
               <sv:file
                  rdf:about="http://www.skatteverket.se/download/18.dfe345a107ebcc9baf80008699/200215.pdf">
                  <dc:title>skv.pdf</dc:title>
               </sv:file>
            </rdf:li>
         </rdf:Seq>
      </sv:files>

      <sv:images>
         <rdf:Seq>
            <rdf:li>
               <sv:file
                  rdf:about="http://www.senselogic.se/images/18.2f85b5f110c3d24f3468000114/senselogic.jpg">
                  <dc:title>logo.jpg</dc:title>
               </sv:file>
            </rdf:li>
         </rdf:Seq>
      </sv:images>
      
   </rss:item>
   
</rdf:RDF>

