<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="xslt.xsl"?>
<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:foaf="http://xmlns.com/foaf/0.1/"
    xmlns:wot="http://xmlns.com/wot/0.1/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:owl="http://www.w3.org/2002/07/owl#"
    xmlns:dcterm="http://purl.org/dc/terms/"
    xmlns:cc="http://web.resource.org/cc/" 
    xml:base="http://schema.menow.org/">


<owl:Ontology rdf:about="" dc:title="MeNow">
<dc:description rdf:parseType="Literal" xmlns="http://www.w3.org/1999/xhtml">
<p>The motivation for the MeNow schema is to be able to describe a variety of aspects of the current status of someone, either online or off, in a way that the data can be easily aggregated or retrieved. This schema allows the definition of a variety of terms that would be common in many applications: describing the current book you are reading, music you are listening to, mood you are in, and more.</p>
<p>The use of the schema is designed to be easy to use for one-time status, or to describe a series of Statuses in a single document. Each document can contain an associated dc:date in order to describe the time when it was current, so that multiple sets of MeNow data can be included in the same document. Some examples of usage of menow data:</p>
<pre>
&lt;foaf:Person&gt;
    &lt;menow:hasStatus&gt;&lt;menow:Status&gt;
        &lt;dc:date&gt;...&lt;/dc:date&gt;
        &lt;menow:located&gt;&lt;geo:Point&gt;
            &lt;geo:lat /&gt;
            &lt;geo:long /&gt;
        &lt;/geo:Point&gt;&lt;/menow:located&gt;
        &lt;menow:reading&gt;
            A Hitchhiker's Guide to the Galaxy
        &lt;/menow:reading&gt;
         &lt;menow:workingOn&gt;&lt;foaf:Project&gt;
            &lt;dc:title&gt;MeNow&lt;/dc:title&gt;
        &lt;/foaf:Project&gt;&lt;/menow:workingOn&gt;
    &lt;/menow:Status&gt;&lt;/menow:hasStatus&gt;
&lt;/foaf:Person&gt;

======

&lt;menow:Status rdf:ID="crschmidt_status_1091583839"&gt;
    &lt;menow:isWith&gt;
        &lt;foaf:Person&gt;
            &lt;foaf:nick&gt;Jessica&lt;/foaf:nick&gt;
        &lt;/foaf:Person&gt;
    &lt;/menow:isWith&gt;
&lt;/menow:Status&gt;

&lt;foaf:Person&gt;
    &lt;menow:hasStatus rdf:resource="#crschmidt_status_1091583839" /&gt;
&lt;/foaf:Person&gt;

======

&lt;menow:Status&gt;
    &lt;foaf:primaryTopic&gt;&lt;foaf:Person&gt;
        &lt;foaf:nick&gt;crschmidt&lt;/foaf:nick&gt;
    &lt;/foaf:Person&gt;&lt;/foaf:primaryTopic&gt;
&lt;/menow:Status&gt;

======

&lt;menow:Status&gt;
    &lt;!-- This actually happened. --&gt;
    &lt;foaf:primaryTopic&gt;&lt;foaf:Person&gt;
        &lt;foaf:mbox_sha1sum&gt;bbff51a6d70630daafe242c186a6e27fda3e99c7&lt;/foaf:mbox_sha1sum&gt;
    &lt;/foaf:Person&gt;&lt;/foaf:primaryTopic&gt;
    &lt;dc:date&gt;2004-08-04T02:21:35Z&lt;/dc:date&gt;
    &lt;menow:writing&gt;&lt;foaf:Document&gt;
        &lt;dc:title&gt;menow.examples.txt&lt;/dc:title&gt;
    &lt;/foaf:Document&gt;&lt;/menow:writing&gt;
    &lt;menow:isWith&gt;&lt;foaf:Person&gt;
        &lt;foaf:name&gt;Jessica Allan&lt;/foaf:name&gt;
    &lt;/foaf:Person&gt;&lt;/menow:isWith&gt;
    &lt;menow:listeningTo&gt;Air Conditioner....&lt;/menow:listeningTo&gt;
    &lt;menow:browsing rdf:resource="http://crschmidt.net/" /&gt;
    &lt;menow:webcamDepiction rdf:resource="http://crschmidt.net/camera.jpg" /&gt;
&lt;/menow:Status&gt;

</pre>

</dc:description>
</owl:Ontology>
<cc:Work rdf:about=""/>
<rdf:Description rdf:about="">


    <!-- !!! kpreid: these descriptions could use improvement -->
    <dc:title xml:lang="en">MeNow: A vocabulary for defining often changing variables in FOAF</dc:title>
    <dc:date>2005-01-18T01:27Z</dc:date>
    <dc:description xml:lang="en">
      This document describes a vocabulary defining the "current status" of a foaf:Agent.
    </dc:description>
    <owl:imports rdf:resource="http://www.w3.org/2000/01/rdf-schema"/>
    <owl:imports rdf:resource="http://www.w3.org/2002/07/owl"/>
    <dc:identifier>http://schema.menow.org/</dc:identifier>
    <dcterm:isVersionOf rdf:resource="http://schema.menow.org/"/>
    
    <dc:creator>Joel De Gan</dc:creator>
	<dc:contributor>Joel De Gan</dc:contributor>
    <foaf:maker rdf:nodeID="joeldg"/>
    <dc:contributor>Christopher Schmidt</dc:contributor>
    <foaf:maker rdf:nodeID="crschmidt"/>
    <dc:contributor>Michael Zeltner</dc:contributor>
    <foaf:maker rdf:nodeID="eaon"/>
    <dc:contributor>Kevin Reid</dc:contributor>
    <foaf:maker rdf:nodeID="kpreid"/>
    <dc:contributor>B.K. Delong</dc:contributor>
    <foaf:maker rdf:nodeID="bkdelong"/>
    <dc:rights>Copyright 2004 Joel De Gan, Some Rights Reserved</dc:rights>  
    <!--   crschmidt: This wasn't right to begin with cause Joel has it liscensed under CC 
       kpreid: um, it's still his copyright. that's how he CAN define the license for it. 
       crschmidt: oh, right, I guess I was thinking of "all rights reserved", which it's not. I think. To be honest, I think he just put the stuff in there to be complete - I'll ask him what he thinks about rights/licensing in a bit.
       kpreid: there should be a textual reference to CC in dc:rights I think
       -->

    <dcterm:hasFormat><rdf:Description rdf:about="http://schema.menow.org/">
        <dc:format><dcterm:IMT>
            <rdf:value>text/html</rdf:value>
            <rdfs:label xml:lang="en">HTML</rdfs:label>
        </dcterm:IMT></dc:format>
    </rdf:Description></dcterm:hasFormat>
    
    <dcterm:hasFormat><rdf:Description rdf:about="http://schema.menow.org/#menow.rdf">
        <dc:format><dcterm:IMT>
            <rdf:value>application/rdf+xml</rdf:value>
            <rdfs:label xml:lang="en">RDF</rdfs:label>
        </dcterm:IMT></dc:format>
    </rdf:Description></dcterm:hasFormat>

    <cc:license rdf:resource="http://creativecommons.org/licenses/by/1.0/"/>
    <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>


    <wot:assurance rdf:resource="menow.asc" />
</rdf:Description>


<!-- - - - Contributors - - - -->


<foaf:Person rdf:nodeID="joeldg">
    <foaf:name>Joel De Gan</foaf:name>
    <foaf:mbox_sha1sum>7e7be2934eaf8e2b51210ab2642f6f77fb18ed6b</foaf:mbox_sha1sum>
    <rdfs:seeAlso rdf:resource="http://peoplesdns.com/foaf.rdf" />
</foaf:Person>

<foaf:Person rdf:nodeID="crschmidt">
    <foaf:name>Christopher Schmidt</foaf:name>
    <foaf:mbox_sha1sum>bbff51a6d70630daafe242c186a6e27fda3e99c7</foaf:mbox_sha1sum>
    <rdfs:seeAlso rdf:resource="http://crschmidt.net/foaf.rdf" />
</foaf:Person>

<foaf:Person rdf:nodeID="bkdelong">
    <foaf:name>B.K. DeLong</foaf:name>
    <foaf:mbox_sha1sum>8245a9033a84bff4904f931c3c3bea7336a8935</foaf:mbox_sha1sum>
    <rdfs:seeAlso rdf:resource="http://www.brain-stream.com/xml/foaf.rdf" />
</foaf:Person>

<foaf:Person rdf:nodeID="kpreid">
    <foaf:name>Kevin Reid</foaf:name>
    <foaf:homepage rdf:resource="http://homepage.mac.com/kpreid/"/>
    <rdfs:seeAlso rdf:resource="http://homepage.mac.com/kpreid/foaf.xml"/>
    <foaf:mbox_sha1sum>38e5d56e3ea275dcb1692b0912aa752f72b35483</foaf:mbox_sha1sum>
    <foaf:mbox_sha1sum>a679c0ccb519491b5d207c31b4af8115c2711a47</foaf:mbox_sha1sum>
    <foaf:mbox_sha1sum>6c72954328f6b8127c8833fe719caa249ac71f2d</foaf:mbox_sha1sum>
</foaf:Person>
  
<foaf:Person rdf:nodeID="eaon">
    <foaf:name>Michael Zeltner</foaf:name>
    <foaf:mbox_sha1sum>c82bc464697d812369ae9a35b4a9742fffbb38d9</foaf:mbox_sha1sum>
    <foaf:mbox_sha1sum>8b3a481a55f590367e1ce00128c5d30142cea83c</foaf:mbox_sha1sum>
    <rdfs:seeAlso rdf:resource="http://zine.niij.org/data/foaf" />
</foaf:Person>


<!-- - - - License information - - - -->



<cc:License rdf:about="http://creativecommons.org/licenses/by/1.0/">
    <cc:permits rdf:resource="http://web.resource.org/cc/Reproduction"/>
    <cc:permits rdf:resource="http://web.resource.org/cc/Distribution"/>
    <cc:requires rdf:resource="http://web.resource.org/cc/Notice"/>
    <cc:requires rdf:resource="http://web.resource.org/cc/Attribution"/>
    <cc:permits rdf:resource="http://web.resource.org/cc/DerivativeWorks"/>
</cc:License>



<!-- - - - Beginning of actual schema - - - -->



<rdfs:Class rdf:about="http://schema.menow.org/#Status">
    <rdfs:label xml:lang="en">status</rdfs:label>
    <rdfs:comment xml:lang="en">An RDF document describing a situation of a foaf:Agent at a particular time.</rdfs:comment>
    <rdfs:comment xml:lang="en" rdf:parseType="Literal"><div xmlns="http://www.w3.org/1999/xhtml">
      <p>An RDF document describing a situation of a foaf:Agent at a particular time.</p>
          
      <p>The person should be specified using the property <code>http://xmlns.com/foaf/0.1/primaryTopic</code>.</p>
    
      <p>The associated time should be specified using the property <code>http://purl.org/dc/elements/1.1/date</code>.</p>
        
      <p>An textual status description, such as IM services offer, should be specified using the property <code>http://purl.org/dc/elements/1.1/description</code>.</p>
    </div></rdfs:comment>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
    
    <!-- For automatic detection of the expected-to-be-common mistake of using Status properties on a foaf:Agent: -->
    <owl:disjointWith rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
</rdfs:Class>


<!-- 
    A Status represents the person's current state at a particular time. Therefore, the following properties have a domain of Status, not foaf:Agent.
-->

<rdf:Property rdf:about="http://schema.menow.org/#hasStatus">
    <rdfs:label xml:lang="en">has Status</rdfs:label>
    <rdfs:comment xml:lang="en">A way to link an Agent and a menow:Status</rdfs:comment>
    <rdfs:domain rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
    <rdfs:range rdf:resource="http://schema.menow.org/#Status" />
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#isWith">
    <rdfs:label xml:lang="en">isWith</rdfs:label>
    <rdfs:comment xml:lang="en">A person is with.</rdfs:comment>
    <rdfs:domain rdf:resource="http://schema.menow.org/#Status"/>
    <rdfs:range rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>
<!-- Example usage:
    <Status>
        <isWith><foaf:Person /></isWith>
    </Status>
-->


<rdf:Property rdf:about="http://schema.menow.org/#moodString">
    <rdfs:label xml:lang="en">mood string</rdfs:label>
    <rdfs:comment xml:lang="en">A descriptor of someone's mood.</rdfs:comment>
    <rdfs:domain rdf:resource="http://schema.menow.org/#Status"/>
    <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal" />
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#located">
    <rdfs:label xml:lang="en">located</rdfs:label>
    <rdfs:comment xml:lang="en">A descriptor of someone's location.</rdfs:comment>
    <rdfs:domain rdf:resource="http://schema.menow.org/#Status"/>
    <rdfs:range rdf:resource="http://www.w3.org/2003/01/geo/wgs84_pos#SpatialThing" rdfs:label="Spatial Thing"/>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>



<rdf:Property rdf:about="http://schema.menow.org/#accessing">
    <!-- kpreid: needs a better name -->
    <!-- eaon: what should that do? -->
    <!-- crschmidt: just a property for the grouping of Reading/Browsing/etc., I guess? -->
    <!-- kpreid: right. they're essentially the same concepts -->
    <rdfs:label xml:lang="en">accessing</rdfs:label>
    <rdfs:comment xml:lang="en">A resource you are accessing. A superproperty over reading/browsing, useful in cases where those terms don't fit exactly.</rdfs:comment>
    <rdfs:comment xml:lang="en">Any resource which one is viewing/reading/browsing/playing with/(editing?).</rdfs:comment>
    <rdfs:domain rdf:resource="http://schema.menow.org/#Status"/>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#listeningTo">
    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#accessing"/>
    <rdfs:label xml:lang="en">listeningTo</rdfs:label>
    <rdfs:comment xml:lang="en">Current song being listened to</rdfs:comment>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#reading">
    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#accessing"/>
    <rdfs:label xml:lang="en">reading</rdfs:label>
    <rdfs:comment xml:lang="en">A book or resource you are reading.</rdfs:comment>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#browsing">

    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#accessing" />
    <rdfs:label xml:lang="en">browsing</rdfs:label>
    <rdfs:comment xml:lang="en">A web page you are browsing.</rdfs:comment>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#writing">
    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#accessing"/>
    <rdfs:label xml:lang="en">writing</rdfs:label>
    <rdfs:comment xml:lang="en">Something you're writing.</rdfs:comment>
    <!-- crschmidt: is there a good way to represent examples in the comment, or is that inappropriate?-->
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#workingOn">

    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#accessing" />
    <rdfs:label xml:lang="en">working on</rdfs:label>
    <rdfs:comment xml:lang="en">A project you are working on.</rdfs:comment>
    <rdfs:range rdf:resource="http://xmlns.com/foaf/0.1/Project"/>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>    
    <!-- Details of a project are outside the scope of this vocabulary. See FOAF and DOAP.-->
</rdf:Property>


<rdf:Property rdf:about="http://schema.menow.org/#snapshot">
    <rdfs:label xml:lang="en">snapshot</rdfs:label>
    <!-- ??? should the comment say that the image must be somehow associated with the person? -->
    <rdfs:comment xml:lang="en">A superclass for images that were created on the date of this Status: mobile images, camera images, etc.</rdfs:comment>
    <rdfs:domain rdf:resource="http://schema.menow.org/#Status"/>
    <rdfs:range rdf:resource="http://xmlns.com/foaf/0.1/Image"/>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#depictionThen">
    <!-- ??? good label? <rdfs:label xml:lang="en"></rdfs:label> -->
    <rdfs:comment xml:lang="en">An image which depicts the person. Not necessarily direct photo/video.</rdfs:comment>

    <!-- kpreid: I think foaf:depiction is sufficiently general that this is OK, and it might be useful. -->
    <rdfs:subPropertyOf rdf:resource="http://xmlns.com/foaf/0.1/depiction" />

    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#snapshot" />
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>


<rdf:Property rdf:about="http://schema.menow.org/#depictionNow">
    <!-- ??? good label? <rdfs:label xml:lang="en"></rdfs:label> -->
    <rdfs:comment xml:lang="en">A superclass for images or video streams that, as of the date of this Status, depict the person, but may not in the future.</rdfs:comment>
    <rdfs:domain rdf:resource="http://schema.menow.org/#Status"/>
    <rdfs:range rdf:resource="http://xmlns.com/foaf/0.1/Image"/>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#webcamDepiction">
    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#depictionNow" />
    <rdfs:label xml:lang="en">webcam</rdfs:label>
    <rdfs:comment xml:lang="en">A regularly updated photographic image or video stream which depicted the person at the date of this Status.</rdfs:comment>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>

<rdf:Property rdf:about="http://schema.menow.org/#icon">
    <!-- kpreid: good idea?
         eaon: emoticon? like the stuff you have for blogs? current mood? 
         crschmidt: we used to have statusIcon, so you'd have your little "away" dude, but this is different than that ... this is a lot like what LJ uses foaf:logo for, since foaf:img nor foaf:depiction apply. I'm just not sure if it's a "meNow" thing, since it's pretty stable?
         kpreid: i see people change their icon all the time on AIM ...
         eaon: i used to switch quite often ...
         crschmidt: alright, sounds good to me then. 
         kpreid: I see this as "use this property IF you use your user icon this way" 
         crschmidt: better to be complete than sorry later when you can't represent your data
    -->
    
    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#snapshot" />
    <rdfs:label xml:lang="en">current icon</rdfs:label>
    <rdfs:comment xml:lang="en">An icon chosen by the user to represent themselves, as in AIM buddy icons, LiveJournal user pictures, etc. The URL must refer to the icon as of the date of this Status, not a changing one.</rdfs:comment>

    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property> 

<rdf:Property rdf:about="http://schema.menow.org/#statusIcon">
    <rdfs:subPropertyOf rdf:resource="http://schema.menow.org/#icon" />
    <!-- This can't be a subproperty of menow:status, because menow:status takes literals. -->
    <rdfs:label xml:lang="en">status icon</rdfs:label>
    <rdfs:comment xml:lang="en">A visual depiction of current status.</rdfs:comment>
    <rdfs:isDefinedBy rdf:resource="http://schema.menow.org/"/>
</rdf:Property>


</rdf:RDF>

<!-- - - - Archived discussion only below this point - - - -->


    <!-- crschmidt: Silly me, I wasn't paying enough attention :) -->
    <!-- eaon: what about doap? -->
    <!-- kpreid: Isn't DOAP orthogonal? I haven't looked at it but wouldn't it just be longer-time-than-MeNow properties of a foaf:Project? -->
    <!-- eaon: you mean this is basically used for mini-projects? -->
    <!-- kpreid: no, I mean that this would be used to specify *which* project but not stuff about the project - that's long term data for FOAF/DOAP/etc. -->
    <!-- eaon: true - let me have a look -->

    <!-- eaon: there is http://usefulinc.com/ns/doap#Project -->
    <!-- kpreid: is it subPropertyOf foaf:Project? or vice versa?  -->
    <!-- eaon: yes:     <rdfs:subClassOf rdf:resource="http://xmlns.com/wordnet/1.6/Project" />
<rdfs:subClassOf rdf:resource="http://xmlns.com/foaf/0.1/Project" /> -->
    <!-- kpreid: ok, let's just say that rdfs makes everything magically work :) -->
<!-- eaon: what about cyc? :] -->
    <!-- kpreid: what about it? -->
    <!-- eaon: well, thats quite complicated to explain in a few words, but wordnet defines words, and cyc describes microtheories -->
    <!-- kpreid: yes, but why do we^H^Hthis schema need to care about what cyc does or doesn't? -->
    <!-- eaon: well, it's the 'do we want a bit more meaningful content' question imo -->
    <!-- kpreid: I don't understand - if someone wants to use Cyc properties to describe their MeNow or Project they can do that, no? Why does it matter to the definition of this schema? Or are you suggesting that we use different approaches based on looking at how Cyc does things? -->
    <!-- eaon: it's to late and i'm quite dead but i'll try to explain, hehe, let me think a bit -->
    <!-- crschmidt: I've never really understood CYC, so. :) -->
    <!-- eaon: instead of explaining words, they're defining the meaning of it and attaching a word to it - some words in wordnet can't be mapped to something else in another language - this would better be possible with it though -->
    <!-- kpreid: Yes. I understand that about Cyc and WordNet. What I want to know is, why do we care for purposes of *designing this schema*? -->
    <!-- crschmidt: I'm pretty sure we don't, because all we're providing is an rdf:resource or something similar to link to project information. The same way that foaf:currentProject is. -->
    <!-- kpreid: Right. WRT the above contrast, we're more like Cyc than Wordnet right? Wordnet is explicitly about structuring English words. -->
    <!-- crschmidt: menow:workingOn is really something along the lines of foaf:currentProject -->
    <!-- kpreid: Right. It's the meNow equivalent. Should they be named the same? I think that would be confusing. and 'working on' sounds like a current activity, vs 'this is one of my currentProjects' -->
    <!-- crschmidt: right, I completely agree. I don't like reusing property names/labels in other schemas -->
    <!-- kpreid: shall we delete all of the above? :) -->
    <!-- crschmidt: Save comments, I think. I'll dump them out when I pass it on to Joel, I'd like to keep reasoning around, just for historical sake - we don't have a historical version, I don't think, unlike a wiki. -->
    <!-- kpreid: Right. Keep these comments, Maybe reformat them to a description rather than a discussion (and the discussion will be much harder to follow without knowing who wrote what), like c2 wiki theoretically does. ThreadMode -> 'normal' pages -->
    <!-- eaon: we need live svn integration! :P no seriously, getting it away is fine for everyone i think -->
    <!-- crschmidt: that exists, with subethawiki - - http://cpan.uwinnipeg.ca/module/Kwiki::Edit::SubEtha -->
    
    <!-- kpreid: OK if i add names to all the discussion comments? -->
    <!-- eaon: and foaf information :) -->
    <!-- fine by me  - crschmidt is fine for me -->
    <!-- kpreid: Green, what short name would you like? -kpreid -->
    <!-- eaon: i'm eaon -->    
    
    <!-- kpreid: How about we still do it inline but all share the same < ! - - - - >? 
    crschmidt: Sounds good to me. I'm just lazy :)
    eaon: bah, i'm off soon anyway ... it's 1:42 am here 
    -->
<!-- Using attributes instead of elements would prevent us from specifiying xml:lang.



On repeated rdfs:isDefinedBy:
  crschmidt: isn't this part of the subPropertyof? 
  kpreid: no, for example if we defined a subPropertyOf something in a different namespace ... 
  crschmidt: oh, got it.
  




     <foaf:Person foaf:nick="kpreid" menow:status="food"/> 
     eaon: :D good idea ;) brb
      
     kpreid: oops, I just typed that in and made a mistake.
    crschmidt: is there a better solution? :/ I don't want to have two of everything, but at the same time, I want to be able to tie these things together. I could remove the domain, I suppose? That way it could go with either? 
kpreid: NO. the domain i think will be essential to making this work usefully. BUT: we do this:
  MeNow...> <owl:disjointWith rdf:resource="http://xmlns.com/foaf/0.1/Person"/> - that way programs can tell we made a mistake. I've pasted that in above.
      crschmidt: (Excuse the slowness of my connection, damn dsl ;))
      crschmidt: It's times like these that I wish that we could specify two domains: either person or MeNow, because that way we could allow things like that. But Dual Domains are intersections, not unions, as far as I understand it.
      kpreid: Right. I think there's some support for union classes in OWL, but I also hear that it's nasty on software trying to handle it. I think we should stick with explicit MeNows. We'd like hypothetical reasoning software to be able to make interesting conclusions from this data without taking so long that it's been obsoleted. :)
      crschmidt: Okay. There is, of course, a way to do what you want to do relatively easily, but still, not as all attributes I don't think.
      crschmidt: <MeNow status="food"><foaf:primaryTopic><foaf:Person foaf:nick="crschmidt" /></foaf:primaryTopic></MeNow> <- does that work? 
      kpreid: yes, with proper striping :)
      crschmidt: right. I wonder if it's worth it to add something specific to meNow, or does primaryTopic fill this role?
    kpreid: I think primaryTopic should work just fine. 
    [a MeNow; status  "food" ] . 
    kpreid: [a foaf:Person; is foaf:primaryTopic of [a menow:MeNow; menow:status "food" ] ] .
    kpreid: "is x of" is N3 for reversing subject/object syntactically.
    crschmidt: cool. This whole "RDF not just being XML" thing is actually quite useful ;)
    eaon: rdf/xml is really suboptimal :P n3 is really nice ;)
    crschmidt: but it's what most people get used to to start, as it's really a lot easier to understand than n3. :p at least, for me.
    kpreid: the nice thing about rdf/xml is if you need to write a parser, you can use an XML parser as a base instead of having to write parsing for quoted strings, brackets, etc, all of n3
    eaon: right it's easier to understand but also easier to understand in a wrong way... i have confused so so so many things before i started to learn n-triples and n3... but thats not the topic here! :D
    crschmidt: what, we're supposed to be menow:workingOn "menow"? :)
    kpreid: ok to move this to archive?
    crschmidt: sure.






     kpreid: Proposal: rename menow:status to menow:statusDescription. 
     crschmidt: actually... why exactly? I just agreed because i was distracted :)
     kpreid: or... we could have menow:status [a menow:Status; foaf:depiction ...image..; dc:description ...status string...]
     kpreid: why? for parallells with statusIcon. because a string isn't really your status.
     crschmidt: I like the idea of a class for status, so that all the aspects of status could be tied together.
    kpreid: but: it's horribly verbose. least in rdf-xml, relatively. hsm.
    kpreid: foaf has foaf:interest and foaf:topic_interest, where the first is a shorthand for "the foaf:topic of the resource is what i'm interested in". we could take that approach, but then...enh. dunno.
    kpreid: I think for this kind of app, getting the model near exactly right is very important.
    crschmidt: I'm just not sure what exactly the right model is ;) I think in this case though, that verbosity should not be a downside to anything. Just because it takes a lot of <> <><> to say is not really a bad thing - I'd rather give people the options than anything else.
    eaon: a class would the "right" way, or at least one that is more right - the description is really something that fits more into dc: and same for the depiction (shouldn't be in foaf imo :P)
    kpreid: WAIT WAIT WAIT WAIT!
    kpreid: i'm not sure about this status class thing: isn't the *whole MeNow* a kind of status info?
    crschmidt: true enough, heh :) It's time based, and describes a vareity of aspects, but you're right that the whole thing is supposed to describe status.
    kpreid: I just think that having a menow:Status container would be redundant. they happen to be named similarly, but that is i think mostly coincidence not the data model. so let's leave things as they are except for the renaming. 
    crschmidt: Right. it doesn't serve any purpose other than to replace the MeNow class.
    eaon: agreed... so what about having menow:Status instead of menow:MeNow ?
    kpreid: *vague handwaving* I like MeNow as conveying "properties about me, just [now] rather than [forever]", whereas Status seems to imply a Different Kind Of thing.
    kpreid: proposal: rename MeNow to Status, delete status/statusDescription and have people use dc:description instead. Opinions? 
     eaon: thats what i meant :)
    kpreid: Ok, implementing...
    crschmidt: ehh... I guess that sounds right. I'm just so used to calling it "menow" :)
    eaon: i love that session guys :D
    kpreid: all done. see the comment just below the class definition of Status telling you about what non-MeNow properties you should use. it really ought to be outside of the XML-comments though. I wonder if XHTML as rdf:parseType="Literal" in a rdfs:comment would be ok, so that we can do paragraphs.
    eaon: i always saw the parseType stuff as very weird... i mean, just as an example: rss 1.0 :/ but the description is used there in a wrong way anyway...
    kpreid: but isn't this exactly what it's for? we're writing our rdfs:comment, just in a more structured data type.
    crschmidt: I just asked in #rdfig: 
        20:36:22 < crschmidt> Is it possible to use XHTML in <rdfs:comment> by using parseType="literal"?
        20:37:07 < crschmidt> Will tools understand that? is it suggested/not suggested?
        20:37:18 < mortenf> most tools will expect plain text
    kpreid: ask if tools will *choke* on it, or just fail to get the comment. most people interested will be reading normal HTML docs or the schema source directly, not schema via some RDF tool. the question is: will a pT="Literal" make the rest of our schema unreadable?
    crschmidt: It will, apparently, most likely simply dump out the unescaped HTML - it will not make the schema unreadable.
  kpreid: Well, then, it should be ok to use Literal. And we'll encourage tool developers to improve their tools this way. :)
  crschmidt: Improvement of tools++ ;)
kpreid: OK, doing it (see above)
eaon: can we provide something like a summary that would be normally the comment in a heading or something? would that make sense?
crschmidt: I don't think we can have multiple ways of making comments: I suppose there is some kind of way of seq+bag or something like that, but I highly doubt tools that ... 
kpreid: rdfs:comment could be used twice.
crschmidt: yeah, that makes sense. I wonder what tools do in that case. (My code would probably just grab the first one ;))
eaon: i always forget basic things about rdf... so true :D 
kpreid: done.
crschmidt: I think that this will serve as an effective starting point for everything that menow needs to do. Little things can still come in later, but it seems that we've got a basic schema set up.
kpreid: Yeah. Let's move the comments out of the way and review what we've got.




On renaming camImage:
      kpreid: do we want 'cam' in this name? self-portrait implies image and Status implies current - what about things that are images in some sense but not from cameras?
      crschmidt: Before, we were using camImage for "webcam image." But I'm not sure if that was a good idea or not, it was just what we were using :)
      eaon: i'd go without the cam - gives you a bit more flexibility but doesn't throw away too much semantics - i mean, there aren't *that* many webcam users out there...
      crschmidt: me, me! http://crschmidt.net/nowhere.php ;) But yeah, I understand what you're saying
      kpreid: ok to delete this? we've split this into webcamSelfPortrait so this issue should be ok
      crschmidt: Sure.




EOF -->

