Subpage under development, new version coming soon!
Subject: [update] XML interface
Terrion to
All
The new changes will need an update of the XML interface, so I think this is a good place to discuss about which improvements could be made:
- History data: we need a way to access to historical results of leagues and cups, including NTs and Champions Cup
- Transfers and transfer announcements: we need a way to access the players skills when they are public through the web
- Training data: a way to know what did the user train (not just a guess like now) and whether every player received the training or not (sometimes it's impossible to know if the player is injured)
- Up to date data: we need updated results once the matches have been played
- NT controlled: in the user info, so I don't have to access all the NTs to know if a specific user is managing any NT. Besides, currently there is no way to know which team controls a determined user. Maybe create a user-[login].xml with this info?
- Read only access: maybe it would be nice that the users could provide a "read only" permission access password to external tools. Also ignore the CORS policy in this case
- JSON instead of XML: to reduce the traffic
(edited)
- History data: we need a way to access to historical results of leagues and cups, including NTs and Champions Cup
- Transfers and transfer announcements: we need a way to access the players skills when they are public through the web
- Training data: a way to know what did the user train (not just a guess like now) and whether every player received the training or not (sometimes it's impossible to know if the player is injured)
- Up to date data: we need updated results once the matches have been played
- NT controlled: in the user info, so I don't have to access all the NTs to know if a specific user is managing any NT. Besides, currently there is no way to know which team controls a determined user. Maybe create a user-[login].xml with this info?
- Read only access: maybe it would be nice that the users could provide a "read only" permission access password to external tools. Also ignore the CORS policy in this case
- JSON instead of XML: to reduce the traffic
(edited)
I hope sokker to be done so we do not need third part apps but till than +1000 especially for history data
I completely agree with the suggestion of Terrion. And I hope a state-of-the-art api-service will be established before the new layout is published. This could prevent a long shutdown of current sokker-tools including my https://www.sokker-manager.net website.
The thing is: Right now my website highly relies on parsing the html-code of sokker.org. Html-parsing is currently the only way to get near-time data not only for collecting all the latest transfers but also for publishing the new standings and promotion/-relegation-forecasts directly after the matches end. If out of the blue sokker.org came up with a new layout, basically all my website's features would be broken.
My suggestion: Please create a contemporary webapi-service, which provides json as a data-format. And please give us developers the chance to adapt our web-apps, tools and plugins ahead of time, so that we can avoid an annoying interruption of our services!
(edited)
The thing is: Right now my website highly relies on parsing the html-code of sokker.org. Html-parsing is currently the only way to get near-time data not only for collecting all the latest transfers but also for publishing the new standings and promotion/-relegation-forecasts directly after the matches end. If out of the blue sokker.org came up with a new layout, basically all my website's features would be broken.
My suggestion: Please create a contemporary webapi-service, which provides json as a data-format. And please give us developers the chance to adapt our web-apps, tools and plugins ahead of time, so that we can avoid an annoying interruption of our services!
(edited)
+1 because:
thanks to Terrion´s tactic editor SETE and training monitor Sokker Asistente,
thanks to Ramonymous transfer comparison tool https://www.sokker-manager.net
and also thanks to Kryminator`s browser addon SkUnk,
more than 10% of sokker population in Germany (perhaps more than 50%, but for sure I know about 10%) have more fun with sokker, because of the sites and the tools I mentioned above.
By the way, a reminder about some old official sokker news:
"We have made accessible a new method of fetching data from the Sokker server based on XML. This will mainly interest developers of Sokker-related software.
Here you will find more information: http://online.sokker.org/xmlinfo.php "
(from Dec. 2016, see post on Forum Sokker International (en) »[news] XML Data Improvements )
Now I adresss to developers Raoul und Mekene:
Dear developers, please recognize the importancy of these sites and tools and give asap following answer:
.
(edited)
Such managers as Terrion or ramonymous are valuable players in this game. With their request I am completely for it!
The developers should offer the data of current transfers and league matches in real time in xml or another format, and definitely before the new layout comes!
+1
The developers should offer the data of current transfers and league matches in real time in xml or another format, and definitely before the new layout comes!
+1
To be honest SkUnk doesnt need XMLs, it operates completely on standard sokker page, no XML API use at all.
Although, I sometimes use that API in some scripts to get some data (like for example - how many players in every country has YS).
Although, I sometimes use that API in some scripts to get some data (like for example - how many players in every country has YS).
Yes Kryminator and SkUnk's transfer comparison tool (the $ icon) could work again, with the help of https://www.sokker-manager.net.
That's why I mentioned your tool and that's why I expect +1 from you too.
That's why I mentioned your tool and that's why I expect +1 from you too.
It would be a shame if pages like those of ramonymous would no longer work. As long as many people benefit from such extensions or websites, they should be supported urgently!
(edited)
(edited)
it operates completely on standard sokker page
very sensible to any layout/content page updates ^^ Good lord Sokker was not update since.... :-)
anyway,
+1 XML interface (+ Json data for the js guys in da place)
very sensible to any layout/content page updates ^^ Good lord Sokker was not update since.... :-)
anyway,
+1 XML interface (+ Json data for the js guys in da place)
Such managers as Terrion or ramonymous are valuable players in this game. With their request I am completely for it!
The developers should offer the data of current transfers and league matches in real time in xml or another format, and definitely before the new layout comes!
+1 :-)
The developers should offer the data of current transfers and league matches in real time in xml or another format, and definitely before the new layout comes!
+1 :-)
I hope sokker to be done so we do not need third part apps but till than +1000 especially for history data
Actually this is the right way. No need for the XML data at all if its all in the game :-)
btw. using JSON instead of XML would save some traffic ;-)
Actually this is the right way. No need for the XML data at all if its all in the game :-)
btw. using JSON instead of XML would save some traffic ;-)
very sensible to any layout/content page updates ^^ Good lord Sokker was not update since.... :-)
geez, it's because it perform scripts directly on sokker page and it cannot be done other way
how could it show all logos or show flag to send info to NTDB using XML API?
it does not gather any data, it does not need to send request for team/player data because team/player-related scripts are executed on team/player page so all data is accessible directly (except some minor functions like league statistics) and those are mostly scripts for enhancing UX, not for any data-processing things
geez, it's because it perform scripts directly on sokker page and it cannot be done other way
how could it show all logos or show flag to send info to NTDB using XML API?
it does not gather any data, it does not need to send request for team/player data because team/player-related scripts are executed on team/player page so all data is accessible directly (except some minor functions like league statistics) and those are mostly scripts for enhancing UX, not for any data-processing things
so what your the point?
We need to deal with data even with user-script (parsing pages); data api (in json) would be a great benefice for js-script because when the ui/page change parsing data is broken, : then dev and ALL users need to update their scripts.
If you want to improve the UI it's great ! But not for many other tools...
For example, our french database dont need the NTDB "flag", we don't, and adding skills is juts one part of the job : all NTDBs need massive "visible" data update that user-scripts can't do.
We need to deal with data even with user-script (parsing pages); data api (in json) would be a great benefice for js-script because when the ui/page change parsing data is broken, : then dev and ALL users need to update their scripts.
If you want to improve the UI it's great ! But not for many other tools...
For example, our french database dont need the NTDB "flag", we don't, and adding skills is juts one part of the job : all NTDBs need massive "visible" data update that user-scripts can't do.
so what your the point?
I am just saying that my extension cannot operate other way and not using API (be it in XML format or JSON or any other) is the way to go for it, and it had to be adapted to layout changes manually, that's the way these things works.
You simply said in Your previous post like its behavior was wrong while it is right.
I am just saying that my extension cannot operate other way and not using API (be it in XML format or JSON or any other) is the way to go for it, and it had to be adapted to layout changes manually, that's the way these things works.
You simply said in Your previous post like its behavior was wrong while it is right.