Dave, Thanks a lot, that looks very helpful even if it was just for some of the major vendors.
Note <rdf:RDF xmlns:mms=" http://www.openmobilealliance.org/tech/profiles/MMS/ccppschema-20050301-MMS1.2#"; xmlns:prf=" http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20070511#"; xmlns:pss6="http://www.3gpp.org/profiles/PSS/ccppschema-PSS6#"; xmlns:pss5=" http://www.3gpp.org/profiles/PSS/ccppschema-PSS5#"; xmlns:rdf=" http://www.w3.org/1999/02/22-rdf-syntax-ns#";> <http://wap.samsungmobile.com/uaprof/SM-N900W8.xml#><rdf:Description rdf:ID ="DeviceProfile"> <http://wap.samsungmobile.com/uaprof/SM-N900W8.xml#> <!-- Hardware Platform Description --> <prf:component> <http://wap.samsungmobile.com/uaprof/SM-N900W8.xml#>< rdf:Description rdf:ID="HardwarePlatform"> <http://wap.samsungmobile.com/uaprof/SM-N900W8.xml#><rdf:type rdf:resource=" http://www.openmobilealliance.org/tech/profiles/UAPROF/ccppschema-20070511#HardwarePlatform "/> <!-- Vendor/model --> Clearly shows, the Open Mobile Alliance was defining some of those. As it did with other attributes, especially extended vocabularies in the W3C DDR Spec (like all these "is_nokia", etc.;-) We are not meeting at ARM this time but next week's JCP F2F in San Jose will be close to ARM's office. Zach Shelby represents ARM in some OMA working groups like Device Management or M2M. I've been contacted by OMA a few times about membership (which I don't need myself and Apache probably is or was a member) so through some of these contacts I might be able to find out, if OMA still has a wider stock of such information (since they helped define it, see the headers) and if it was possible for us to access them to gather more device information. P.s.: As for Bertrand's question changing the format more drastically or maintaining more than 1 repository could also be much easier if some of the data was updated automatically, at least via some batch process. Werner On Mon, Jan 5, 2015 at 3:16 PM, Dave Olsen <[email protected]> wrote: > Volkan- > > If all you're looking for is actual device characteristics provided by a > manufacturer (as opposed to what a browser might tell you) you can also use > the UAProf data. For Samsung you can use: > > http://wap.samsungmobile.com/uaprof/[DEVICEMODEL].xml > > For example: > > http://wap.samsungmobile.com/uaprof/SM-N900W8.xml > > I think that will get you at least some of the data you require. Might be > helpful to review that spec with the group before automating the process > but at least it's something that could be automated. > > > On Fri, Jan 2, 2015 at 11:12 AM, Volkan Yazıcı <[email protected]> > wrote: > > > Yes, please do so. > > I will see what I can do... > > > > On Fri, Jan 2, 2015 at 5:00 PM, Reza Naghibi > > <[email protected] > > > wrote: > > > > > Volkan, I probably should have taken a look earlier, but each device > > needs > > > it own JIRA and entry. For example: > > > > > > https://issues.apache.org/jira/browse/DMAP-97 > > > > > > > > > You have this as Samsung SM-N series. But when I look at the > user-agents, > > > I see the following models: > > > > > > SM-N7502, SM-N7505, SM-N9007, SM-N900W8 > > > > > > > > > So what we can do is treat these tickets as parents. We then have to > look > > > at the all different models in the series and: > > > > > > 1) Check if they are already in the DDR > > > 2) If not, create a sub task for the model, put in the user agent and > the > > > specs > > > > > > As for the specs, just search google. For example: 'SM-N7502 specs': > > > > > > http://www.gsmarena.com/samsung_galaxy_note_3_neo_duos-6015.php > > > > > > > > > Once that is done, we can add them to the DDR. > > > > > > I can help with this. I think if we each take a series, we can kind of > > > divide and conquer. Just send me a message and I should be able to > > assign a > > > series to you so no one else takes it. And then we just have to work > our > > > way thru the lists. > > > > > > From: Volkan Yazıcı <[email protected]> > > > To: "[email protected]" <[email protected]> > > > Sent: Friday, January 2, 2015 4:23 AM > > > Subject: Collecting Specs for UAs > > > > > > Hi all, > > > > > > The entire UA collection tickets (DMAP-94, 95, 96, 97, 98, 100, 102) I > > have > > > submitted to JIRA are being marked as NeedsSpec, which is fine. In the > > > explanation, I am being told that I need to collect the following > > > properties for each UA: > > > > > > - id > > > - vendor > > > - model > > > - marketing name > > > - resolution-x > > > - resolution-y > > > - pixel-density-ppi > > > - release-year > > > - default-os > > > - hardware > > > > > > I have some questions regarding these properties: > > > > > > - How other people collect this sort of information? Is there a > certain > > > set of steps that I can follow? I was considering writing a crawler > on > > > top > > > of a web-based proprietary UA resolver, would that be ok considering > > the > > > licensing issues? > > > - Is there scheme am I supposed to follow for the *id* attribute? Or > > > something descriptive would be just fine? > > > - *resolution-x/y* means the width and height of the screen in > pixels, > > > right? > > > - How do we calculate *pixel-density-ppi*? > > > > > > Best. > > > > > > > > > > > > > > > > > > -- > > http://dmolsen.com >
