This is a silly problem that is taking up too much of my time. It's
probably got an easy answer, so I might as well ask it. Writing these
things out often helps.

Both Issuezilla and JIRA allow one to add attachments to a bug.
There's not much space to add information to the attachment as one
posts it, so the attachment seems to be a o

(1) Is the attachment a post,

a baetle:Issue, sioc:Container;
sioc:contains
[ is testRep.xml> ;
a sioc:Post;
dc:title "testRep.xml attachment";
sioc:author ;
xxx:mimetype "text/xml";
dc:created "2004-01-23";
xxx:filesize 22435;
xxx:filename "testRep.xml";
]
.

Here there is the danger of a confusion arising between the
person posting the file, and the author of the file.

(2) or is it the attachment to the Post?

a baetle:Issue, sioc:Container;
sioc:contains
[ is ;
a sioc:Post;
dc:title "testRep.xml attachment";
sioc:author ;
sioc:attachement
[ is testRep.xml>;
xxx:mimetype "text/xml";
dc:created "2004-01-23";
xxx:filesize 22435;
xxx:filename "testRep.xml";
];
]
.

btw, What relations are recommended for xxx:mimetype,
xxx:filesize and xxx:filename ?

(3) Or should I think of the Issue itself as a Post, so that it can
have attachments?

a baetle:Issue, sioc:Container, sioc:Post;
sioc:attachment
[ is testRep.xml>;
xxx:mimetype "text/xml";
dc:created "2004-01-23";
xxx:filesize 22435;
xxx:filename "testRep.xml";
sioc:author ;
];
.

In (3) we loose the information of who made the post, as we do in (1).
So I suppose (2) wins out, even though it is more complicated.
But I may have forgotten other options.

Henry

Home page: http://bblfish.net/
Sun Blog: http://blogs.sun.com/bblfish/
Foaf name: http://bblfish.net/people/henry/card#me

Home page: http://bblfish.net/
Sun Blog: http://blogs.sun.com/bblfish/
Foaf name: http://bblfish.net/people/henry/card#me

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---