Re: [ontology-summit] Question about the Summit hashtag

[Mike Bennett <mbennett@xxxxxxxxxxxxxx>]

It’s also worth noting (though this won’t affect us) that if you have an account name with the same text as a hashtag, then this never shows up in Twitter’s “trending topics” feed.

 

However I doubt ontology will trend any time soon ;)

 

(h) #ontsummit might work?

 

Mike

 

--

Mike Bennett

Head of Semantics and Standards

EDM Council

Tel: +44 20 7917 9522

Cell: +44 7721 420 730

www.edmcouncil.org

Semantics Repository: www.hypercube.co.uk/edmcouncil

 

From: ontology-summit-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Amanda Vizedom
Sent: Wednesday, May 08, 2013 2:30 PM
To: Ontology Summit 2013 discussion
Subject: Re: [ontology-summit] Question about the Summit hashtag

 

It did get used a bit, at least by me, on tweets and on some Google+ posts. But it is too long, as we discussed. Some others have use #ontologysummit without the year.

 

I think it is well worth thinking about a new tag for next year, or even now. Since I've made noise about this a few times, I'll take a minute here to lay out why anyone would care what tag we have, and some considerations:

 

1) As a classifier-collector, a good hashtag is something you can search on, on the web in general, on twitter, on Google+, anywhere that uses hashtags, and find all the stuff that various people have posted on the hashtag topic.  This works only if your hashtag is fairly unique; otherwise the relevant posts get drowned out in noise from others using the same tag. If this were the only consideration, #ontologysummit2013 would be fine. #OS is terrible - very noisy. Some things might vary by year, depending on whether an event repeats, or might clash but be at different times of year so not overlap in the feeds (e.g., you find unrelated stuff if you search on #OS2012, but there is nothing on #OS2013)

 

2. As an update mechanism, a tag shouldn't be too noisy (not too many other people use the same tag to mean something else, and it should be made well-known. In an interface like twitter (or a multi-source social media aggregator) people will "follow" the hashtags they are interested in. That's like a subscription, so you can get real-time updates of what people are posting on the topic. There are really two different levels of following, though.

Level 1: following something (generally an account) so that it shows up in your general stream. You'll get everything, but you might not see it because it's mixed in with everything else.

Level 2: following something (an account or a tag or a complex search) so that it shows up separately, and you can make sure to see most or all of it if you want to. 

For a specific event, series, or specialized topic community that people really care about, they are more likely to use level 2. For example, if they use an multi-column social media aggregator, they will add a column (possibly just for the time period around an event) to the interface showing just tweets with that hashtag, account, or search). 

You'll see this for almost any major conference. For examples from our near-industry neighbors, check out #iswc2013, #semtechbiz, #lodlam (linked open data for libraries archives and museums). This works for them because people find out about the hashtags at/before the conferences and follow. Some series have dropped the dates (as with semtechbiz) that they used to use, because last year's conference and this year's, since they aren't being tweeted at the same time! Then regular attendees know where to look year to year for the relevant information

 

3. As a pivot for peoples' attention, a tag should be non-generic but short.  Lots of people already follow broader topic hashtags they are interested in. For example #ontology #semanticweb #lod (that's linkedopendata). For the most part, people do not read every single post on these, but check recent postings regularly. One way to call people's attention to a specific event that is relevant to a topic is to use the event hashtag *and* one or more general hashtags. The summit is in the position where this is needed. People who aren't already participating *might* see tweets marked #ontologysummit2013 if it comes from someone whose tweets they follow closely. They are more likely to see it if it is double marked with hashtags they care about, such as #ontology #semantictechnology #interoperability.... If they see enough double-tagged with an event and stuff they care about, they are more likely to wonder what the event is and click through. This consideration pushes for shorter tags, because you have to say something interesting enough for anyone to care, include a link to click through on, and get multiple tags in, within 144 characters. 

 

So, overall, the tag doesn't have to be self-explanatory or completely unique, but it should fairly unique to cut down noise, and short to allow multiple tagging.

 

(a) #ontologysummit20**   is really too long, and the date doesn't really win any extra clarity, since feeds are by nature time-ordered.

 

(c) #os  and even #os20** are too noisy, especially the first. There is also an account with that second name. It tweets in arabic, though, which I don't read, so I've no idea what it is about.

 

If we drop the date,

 

(b) #ontologysummit is better, and a few people used it this year. Still, can we make it shorter for more multi-tagging?

 

All of these alternatives appear to be unused.

(d) #ontosummit 

(e) #ontosum

(f) #ontologysum

(g) #ontsum

 

(h) ?

 

 

Also: It might not be a bad idea also to get the *account* @ontologysummit -- that can be long without using tweet characters, and  could be used to tweet official stuff and serve as a pivot from whatever hashtag is used to more info, via that account profile.

 

My 2 cents,

 

Amanda

 

 

 

 

 

 

 

 

On Wed, May 8, 2013 at 12:47 PM, Peter Yim <peter.yim@xxxxxxxx> wrote:

Thank you, Gary. Glad you asked, Marc. ...


Marc & All,


Yes, we did set up the hash tag #OntologySummit2013 (ref.
http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013#nid3J1Y ).

Anyhow, ...

* that doesn't get used much (if at all) ... maybe it's the culture of
this community (which started way before tweets or even social media
existed)

* we don't show up in the blogosphere much, either, but you can see
some of that listed under:
http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013#nid3J1W

* if you (or for that matter, anyone) is putting anything about the
OntologySummit or the Summit Communique on the web or in any
publication, please make sure you send me a link, so I can include
that in the abovementioned section (or, even better, post that
yourself there.)

* there have been recommendations that we use a shorter hashtag ...
what do people think?


Thanks & regards. =ppy
--


On Wed, May 8, 2013 at 8:00 AM, Halpern,Marc <Marc.Halpern@xxxxxxxxxxx> wrote:
> Thanks.
>
>
> Marc Halpern, P.E., Ph.D.
> Vice President, Research
> Manufacturing Advisory Services
> Engineering, R&D, Product Lifecycle Management
> Direct: (Tel) 1-203-316-6894
> (Fax) 1 866 785 2967
> (email) marc.halpern@xxxxxxxxxxx
>
> "A pessimist sees the difficulty in every opportunity; an optimist sees the
> opportunity in every difficulty."
>
> -Winston Churchill


> From: ontology-summit-bounces@xxxxxxxxxxxxxxxx
> [mailto:ontology-summit-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Gary
> Berg-Cross
> Sent: Wednesday, May 08, 2013 10:27 AM
> To: Ontology Summit 2013 discussion
> Subject: Re: [ontology-summit] Question
>
>
> I believe it was #ontologysummit2013
>
>
> Gary Berg-Cross, Ph.D.
>
> gbergcross@xxxxxxxxx
> http://ontolog.cim3.net/cgi-bin/wiki.pl?GaryBergCross
> NSF INTEROP Project
> http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0955816
> SOCoP Executive Secretary
> Knowledge Strategies
> Potomac, MD
> 240-426-0770


> On Wed, May 8, 2013 at 10:22 AM, Halpern,Marc <Marc.Halpern@xxxxxxxxxxx>
> wrote:
>
> Is there a twitter “hash” tag for the group?
>
>
> Marc Halpern, P.E., Ph.D.
> Vice President, Research
> Manufacturing Advisory Services
> Engineering, R&D, Product Lifecycle Management
> Direct: (Tel) 1-203-316-6894
> (Fax) 1 866 785 2967
> (email) marc.halpern@xxxxxxxxxxx
>
> "A pessimist sees the difficulty in every opportunity; an optimist sees the
> opportunity in every difficulty."
>
> -Winston Churchill

_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
Community Portal: http://ontolog.cim3.net/wiki/

 

_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/   
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/  
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013  
Community Portal: http://ontolog.cim3.net/wiki/     (01)