All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Siemens <Simon.Siemens@arcor.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] are bluetooth specs no longer freely available?
Date: Fri, 15 Sep 2006 10:33:16 +0200	[thread overview]
Message-ID: <450A654C.4000401@arcor.de> (raw)
In-Reply-To: <1158227325.28902.38.camel@localhost>

Thanks for the link, Marcel. I didn't find it. But what about the
Generic Access Profile. Many other profiles refer to it, but I can't
find it in the list. Did it become obsolete or has there been a name
change? The JSR-82 (Java Bluetooth API) refers to it as well.

Thanks, Simon



Marcel Holtmann schrieb:
> Hi Albert,
>
>   
>> As I've done in the past, last week I tried downloading a copy of the
>> specs from http://www.bluetooth.org/spec and found that I'm no longer
>> allowed to do so.
>>
>> In the past, I've registered an individual level acccount on the
>> website, which then let me download most of the specs and profiles. 
>>
>> Now, it says:
>>
>> The document you requested requires you to be a member of the group
>> Adopters
>>
>> Although Adopter membership is free, apparently only incorporated
>> entities are allowed membership.  So it seems that individuals are not
>> able to download the specs from the bluetooth.org website...
>>
>> Can anyone else confirm this?  I tried filling in the contact form on
>> the bluetooth website, but don't expect a response (never get one)
>>     
>
> they are changing so many stuff, but Bluetooth is no longer a really
> open specification. You have to be an adopter to participate and that
> they killed the individual membership is totally stupid. They basically
> kicked out all Universities and students from access to early drafts of
> upcoming specifications. For the adopted specification you can use this
> link to download them:
>
> http://www.bluetooth.com/Bluetooth/Learn/Technology/Specifications/
>
> A small tip from my side. Keep all your old specifications, because they
> tend to remove access to old specifications if a new one has been
> released. So it is impossible to compare a new version to the old
> version of a specification. If you have products complying to the old
> specification, this is useful. Some changes are not obvious or they have
> been forgotten to mention in the new version.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>   

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-09-15  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  6:13 [Bluez-devel] are bluetooth specs no longer freely available? Albert Huang
2006-09-14  9:48 ` Marcel Holtmann
2006-09-15  8:33   ` Simon Siemens [this message]
2006-09-15  9:41     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=450A654C.4000401@arcor.de \
    --to=simon.siemens@arcor.de \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.