Oh. I should have mentioned how I see this being able to relate to vcards. There is an rdf ontology for vcards on SchemaWeb [1]. It is a little odd because it assigns names, addresses and other properties to vcards instead of to people. But it would be easy to
add a property from a foaf:Person to a vcard named vcard, that would then contain all that info, something like
_someEntry --- isa ---> <atom:Entry>
|----------author---> _somePerson ---isa-------><atom:Person>
| |------------isa-------><foaf:Person>
... |-----atom:name-------->"John Doe"^^xsd:String
|-----atom:email-------><mailto:[EMAIL PROTECTED]>
|-----foaf:gender------>"male"^^xsd:String
|----foaf:aimChatID---->"aim:johndoe"^^xsd:String
|----xxx:vcard--------->_avcard ---isa----><vcard:vCard>
|---vcard:familyName-->"Doe"
...
If you draw me a diagram as above with a good vcard ontology that you like, I'll go through the process of step by step showing how one can get to an atom xml format
from first principles.
Henry Story
[1] http://www.schemaweb.info/schema/SchemaDetails.aspx?id=215
On 4 Jan 2005, at 16:06, Henry Story wrote:
I think that the simplicity of atom:Person is fine. I have not checked this out carefully, but it should be possible to map it quite easily to foaf:Agent[1]. If one specified the following mappings:
- atom:Person is a subclass of foaf:Agent
- atom:uri is a super property of foaf:weblog
- atom:email is the sub property as foaf:mbox
then we can have an atom segment represented in triples as
_someEntry --- isa ---> <atom:Entry>
|----------author---> _somePerson ---isa-------><atom:Person>
| |------------isa-------><foaf:Person>
... |-----atom:name-------->"John Doe"^^xsd:String
|-----atom:email-------><mailto:[EMAIL PROTECTED]>
|-----foaf:gender------>"male"^^xsd:String
|----foaf:aimChatID---->"aim:johndoe"^^xsd:String
so I think this translates into the following Atom xml
<entry> .... <author> <name>John Doe</name> <email>[EMAIL PROTECTED]</email> <foaf:gender>male</foaf:gender> <foaf:aimChatID>aim:johndoe</foaf:aimChatID> </author> .... </entry>
In fact there is a little hitch in the mapping between atom:email and foaf:mbox that I have just noticed. foaf:mbox has as object a mailto uri. Perhaps this would be a good idea for a improvement to the spec?
Henry Story
[1] http://xmlns.com/foaf/0.1/#term_Agent (In fact I think that we should use Agent instead of Person, as it is quite possible that robots, or multi-person organizations be creating blog entries or feeds.
On 4 Jan 2005, at 15:03, Brett Lindsley wrote:
A while ago I wrote a Pace (but I can't seem to find it, maybe I didn't finish
it, it was a while ago...) on using a vCard for the Person. vCards are pretty
common and have some XML formats that would fit in to the current spec.
Any interest?
Brett Lindsley, Motorola Labs
Martin Duerst wrote:
I was asking myself the same questions when I was recently reading the atom format spec.
Regards, Martin.
At 18:39 05/01/04, Henry Story wrote:
>
>I was just looking closely at the atom:Person class [1] and found some
>pretty arbitrary limitations:
> - why should a Person only have one e-mail address?
> - why should a Person only have one associated url?
>
>It seems to me that one should follow the principle: only impose
>limitations that are proven to be necessary. Here they seem both
>unnecessary and counterintuitive.
>
>Henry
>
>[1]
>http://ietf.levkowetz.com/drafts/atompub/format/draft-ietf-atompub- format-03.txt
>
