Facts:

1. Yes that's why we need ThreadsML and are here in the first place.
2. The Wiki lives as a breathing, seething beast. Feel free to throw away all of it and start over (at least the page I created - for the purposes of the web site getting fleshed out.)

3. It's gonna take one session of just reading through everything - to get a synonymous trail going. There's nothing we can do about that.
4. Buono fortuna.

< replied-to message removed by QT >

woe...woe is me...this referred-to-message-removing is *really*
annoying. I'm losing track of threads. Also, not being able to change the subject line...lost, adrift in a sea of mails. I want my metadata back.

Also, could changes to the wiki, or a notifier of such, be posted to the list. I'm offline a lot of the time at the moment, and can't keep up with distributed conversations. (Therein find a use case for
ThreadsML)

Anyway, yes, I'll load the old faithful and see what I can tap out for the good Doctor...

In the sense of:

"who's doing what?"

"why is it such a hodge podge?"

"am I missing something here?"

or

"what am I supposed to do?"

Consider all that crap fodder and source material. I tried going through recent posts - culling what seemed like juicy tid-bits - to me.
But step back, take a deep drag on that infamous pipe of yours and just do your thang. :-) Please.

Give us some words that:
 - explains what the goals of ThreadsML are
 - what we've come up with so far (may want to check with Steve Y on that)
 - what work is in progress
 - what we can expect as far as a roadmap
 - you know - all that "marketing stuff that humans need" kind of communication stuff..........

And then send that to the good, kind Dr. Weinberger.

:-)

Maybe we can even get Paolo to create a good logo for us.

:-)

- Marc

< replied-to message removed by QT >

I have editor access there... wassup with that page?

On Wednesday, May 28, 2003, at 17:40 Europe/Stockholm, QT - Marc Canter wrote:

>
< replied-to message removed by QT >

Dudes,

Does anybody know anybody at Syndic8?

http://www.syndic8.com/feedinfo.php?FeedID=26156

- Marc

No idea - I'll ask on rss-dev...

< replied-to message removed by QT >

How well (and how) does the use of foaf elements for dc:creator and dc:contributor interoperate with existing RSS readers?

I've put the strawman on the Wiki as "ThreadsVocabulary", please hack away :
http://www.quicktopic.com/cgi-bin/thwiki.pl?ThreadsVocabulary

On Sunday, May 25, 2003, at 03:28 Europe/Stockholm, QT - Jay F wrote:
> --QT-------------------------------------------------------------
> Note: replies go to the entire group (see below)
> -----------------------------------------------------------------
>
>> can you think of a better name for tdb:threadHead ?
>
> I think "head", to many people, suggests "header". However, it
> probably would suggest the right meaning to everyone who has
> worked with CVS.
> threadBegin is the other one I like a lot.

thread:firstPost

Obvious... :-)

> can you think of a better name for tdb:threadHead ?

I think "head", to many people, suggests "header". However, it probably would suggest the right meaning to everyone who has worked with CVS.

I was thinking of: threadStart.

This came to mind because, in online forums / discussion moderation, it is common to see "topic started by . . ." or, as on QuickTopic, "start a new topic".

Here are some other possibilities:

threadBegin
threadBirth
threadEnter
threadInception
threadKickoff
threadOrigin

threadBegin is the other one I like a lot.

OK - so I guess I'll just keep trying, and use the validator to test with........

- Marc "arrows in the back" Canter

< replied-to message removed by QT >

> Right, both are optional--either one or both could be used, so:
>
> (optional) I am part of a thread that starts at: some-uri
> (optional) I am responding to (my parent is): another-uri

The second is covered by tbd:parent(s)

The first - can you think of a better name for tdb:threadHead ?

Cheers,
Danny.

> Sablotron XSLT transformation error on line 7: XML parser error
> 4: not well-formed (invalid token).

> Is there supposed to be something else in there I'm missing?
> What gives?

I tried it at the W3C's RDF validator

http://www.w3.org/RDF/Validator/


from the URL, it fails (IOException while reading URI at character 249 using encoding null.)

copy & pasting the source, it works.

My guess is there's a junk EOF character or something crept in. Weird.
> P.S. THEN I'm gonna ask you how to add names to my "trusted
> network".

First you'll need a little black book and some invisible ink...

Edited by author 05-24-2003 04:09 PM
In reply to Danny's comment in /m235:

>I hadn't thought of identifying the head of the thread, but
> for the branch idea I guess that's what would be
> happening. In fact both parts could be optional - "I am
> the head of a new thread". Yep, I reckon this is worth pursuing.

Right, both are optional--either one or both could be used, so:

(optional) I am part of a thread that starts at: some-uri
(optional) I am responding to (my parent is): another-uri

Hey Danny - thanks for the FOAF bookmarklet.

Since I know FOAF is not directly related to this list, however this issue is relevant to the acceptance and pickup of ANY standard (such as ThreadsML) I'm gonna use this list reply to ask:

"why do I get this error code?"

Error
Unable to parse FoaF (http://blogs.it/0100198/gems/FOAF.rdf).

Sablotron XSLT transformation error on line 7: XML parser error 4: not well-formed (invalid token).

=======================

???????????????

If you look at my FOAF.rdf file - it looks fine to my naked eye. That's what FOAFmatic gave me.

http://blogs.it/0100198/gems/FOAF.rdf

Is there supposed to be something else in there I'm missing? What gives?

- Marc

P.S. THEN I'm gonna ask you how to add names to my "trusted network".



< replied-to message removed by QT >

> > I know, early on in this dicussion, RSS was definitely a
> context
> > in which threads were imagined. But, I am asking:
> >
> > Is ThreadsML (at least, phase 1) really just the "threads
> module
> > of RSS"?
>
> Pretty much, but only in that RSS 1.0 is a major vocabulary of
> RDF. I'd go further, though, and say it's a profile too.

Can I add that it will also be an ontology (just don't tell Shelley!).
> Mandating use of the dc elements is absolutely key.

+1.

Cheers,
Danny.