Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
Government Math

Should Salesforce's Tableau Be Granted a Patent On 'Visualizing Hierarchical Data'? 44

Long-time Slashdot reader theodp says America's Patent and Trademark Office (USPTO) has granted a patent to Tableau (Salesforce's visual analytics platform) — for a patent covering "Data Processing For Visualizing Hierarchical Data": "A provided data model may include a tree specification that declares parent-child relationships between objects in the data model. In response to a query associated with objects in the data model: employing the parent-child relationships to determine a tree that includes parent objects and child objects from the objects based on the parent-child relationships; determining a root object based on the query and the tree; traversing the tree from the root object to visit the child objects in the tree; determining partial results based on characteristics of the visited child objects such that the partial results are stored in an intermediate table; and providing a response to the query that includes values based on the intermediate table and the partial results."

A set of 15 simple drawings is provided to support the legal and tech gobbledygook of the invention claims. A person can have a manager, Tableau explains in Figures 5-6 of its accompanying drawings, and that manager can also manage and be managed by other people. Not only that, Tableau illustrates in Figures 7-10 that computers can be used to count how many people report to a manager. How does this magic work, you ask? Well, you "generate [a] tree" [Fig. 13] and "traverse a tree" [Fig. 15], Tableau explains. But wait, there's more — you can also display the people who report to a manager in multi-level or nested pie charts (aka Sunburst charts), Tableau demonstrates in Fig. 11.

Interestingly, Tableau released a "pre-Beta" Sunburst chart type in late April 2023 but yanked it at the end of June 2023 (others have long-supported Sunburst charts, including Plotly). So, do you think Tableau should be awarded a patent in 2025 on a concept that has roots in circa-1921 Sunburst charts and tree algorithms taught to first-year CS students in circa-1975 Data Structures courses?

Should Salesforce's Tableau Be Granted a Patent On 'Visualizing Hierarchical Data'?

Comments Filter:
  • by rta ( 559125 ) on Sunday September 28, 2025 @03:41AM (#65687956)

    or is that just when someone sues over it ?

  • by OrangAsm ( 678078 )
    See subject
  • No (Score:4, Insightful)

    by sizzlinkitty ( 1199479 ) on Sunday September 28, 2025 @03:44AM (#65687960)

    Our patent system is broken beyond repair, you shouldn't be able to patent anything short of revolutionary. The answer is NO and Tableau is a cancer.

    • You can't really decide the bare like that. Instead remove the problem of corporation yielding a way too powerfull arsenal of patents: Patents can only be owned by an entity owning that single patent, using it to gain as many royalties as possible, fairly for all actors. If a company gets a patent they have to establish a separate company handling it, and themselves pay royalties to that company. They can't control that company and that way use the granted, exclusively rights to extent their monopoly, but i
    • Although I agree that this chart type shouldn't be patentable, I don't agree with the "revolutionary" yardstick.

      This patent should have been disallowed due to prior art. Org charts have been around for decades.

      As for "revolutionary," nearly all inventions ever, are incremental, not revolutionary. The humble farm windmill, for example, has a long history of innovation, adding features that do things like turning it sideways in high winds to keep it from being destroyed in storms. We only think of it as munda

  • Without knowing the claims (at the very least), only dumb people can tell whether the patent should've been awarded...
    • https://patents.google.com/pat... [google.com] It's above my pay grade, but seems to be a UI patent? A system designed to render a collapsable tree on a server and present it to the user's computing device which might be VR with Haptics.
    • PDF version [jumpshare.com]. Their diagrams of a computer are outdated, including BIOS.

      The claims are extremely detailed, which is what I would do if I were required to get a patent for work: make it so detailed that their is no prior art, and no one will likely ever do the same configuration again.
      • by Entrope ( 68843 )

        I'm not going to look at the claims because that's a good way to treble damages (by committing "willful infringement"), but adding details should not be sufficient. The threshold for patentability isn't doing something for the first time, but doing something novel and not taught by prior art. Detailed claims aren't needed for that unless prior art teaches so much as to suggest that the present invention was taught by the prior art.

        • If your claim says:

          A device that has A and B and C and D and E and F

          Add enough letters and the patent is unique. It also becomes easy for other people to avoid violating the patent.

          I'm not going to look at the claims because that's a good way to treble damages (by committing "willful infringement"),

          You're just being lazy, merely hearing the title is enough, see for explanation: https://www.dority-manning.com... [dority-manning.com]

          • by Entrope ( 68843 )

            Adding "and F (and ...)" isn't sufficient to escape prior art. There needs to be something more to establish that it wasn't an application that could be deduced by a practitioner with ordinary skill in the art based on knowledge of any prior art.

            And speaking of lazy, maybe you want to find some source that (a) mentions merely knowing the title of a patent and/or (b) isn't about summary judgment in favor of a defense on willful infringement.

            • Adding "and F (and ...)" isn't sufficient to escape prior art.

              Obviously it was enough for this patent.

              And speaking of lazy, maybe you want to find some source that (a) mentions merely knowing the title of a patent and/or (b) isn't about summary judgment in favor of a defense on willful infringement.

              You're more at risk of willful infringement than I am. I read the patent, so I know how to avoid infringing the patent. You, on the other hand, put in writing that you refuse to read it, although have some idea of what is in it. If you're doing anything related to "visualizing hierarchical data," then avoiding reading the patent isn't going to help you. Living in Europe might help you.

              • by Entrope ( 68843 )

                You're more at risk of willful infringement than I am.

                This is exactly as true as your earlier claims that "You're just being lazy, merely hearing the title is enough, see for explanation" -- namely, totally false.

          • It also becomes easy for other people to avoid violating the patent.

            The way patents work is that an applications has letters A, B, C, D, E, and F in order to get the patent. Then the patent holder sues anyone who does A, B, C, D, E, or F; in any combination. Then they argue that not all elements need to be present at the same time to constitute patent infringement. And then, if they lose, they suffer no consequences aside from the money they put into the suit. And then they write that off as a business expense.

            That this piece of shit was even considered for submission is an

            • by ceoyoyo ( 59147 )

              I don't think it's corrupt. It's lazy. Patent examiners are overworked and are probably aware that what they do doesn't really matter. They're prone to rubber stamp things because it's ultimately up to a court anyway.

            • ... to patent the process of bullshitting the USPTO with heaps of prior art that they can't be bothered to wade through?

      • by ceoyoyo ( 59147 )

        I'm not sure why you say that. The claims are very broad, as they are in most patents. Patent claims arent "all of these things" they're "any of these things" with some limited (lol) hierarchical relationships as specified.

        Usually the way it goes is that the actual person who made the thing gets to explain it to a lawyer and the lawyer draws up claims that vaguely resemble their impression of the thing in the broadest possible terms. Broad terms let you intimidate and maybe actually sue the largest variety

    • Slashdot has a long and glorious history of both not understanding how patents work and not RTFA. The combination of the two leads to posts like this, where everyone starts yelling about how stupid a patent is based just on the abstract.

      On the other hand, I did look at the claims, and, well, it does seem pretty stupid. The independent claims don't actually have much more than what's in the abstract. The file history might be interesting, but not enough for me to bother digging though it.
    • by theodp ( 442580 )

      Data Processing For Visualizing Hierarchical Data [google.com] Here you go - hopefully got the access rights correct this time!

  • I cannot think of a better application for Betteridge’s Law of Headlines.
  • So, do you think Tableau should be awarded a patent in 2025 on a concept that has roots in circa-1921 Sunburst charts and tree algorithms taught to first-year CS students in circa-1975 Data Structures courses?

    It's likely Tableau's founders learned this stuff when they were taking their CS intro courses at Stanford [wikipedia.org] in the first place.

  • by VaccinesCauseAdults ( 7114361 ) on Sunday September 28, 2025 @03:59AM (#65687980)

    1. Antiquity and the Middle Ages – Early Outlines

    • Aristotle (4th c. BCE): Aristotle’s logical works (the Categories, Topics, Posterior Analytics) introduced hierarchical classification of concepts (e.g., genus species subspecies). These were not indented trees in the modern typographic sense, but were often rendered in later commentaries as branching diagrams or stepwise lists.
    • Porphyry’s Isagoge (3rd c. CE): Introduced the “Tree of Porphyry” (Arbor Porphyriana), a famous diagram of how genera divide into species. Medieval manuscripts frequently depicted it as a literal tree or as a branching hierarchy. This is probably the earliest “tree hierarchy” diagram in Western tradition.

    2. Medieval and Scholastic Outlines (12th–15th centuries)

    • Scholastic manuscripts used outline formats with nested structures, marked by letters (A, B, C), numerals (I, II, III), or alternating systems (I.1.a).
    • Example: Peter Lombard’s Sentences (12th c.) and Thomas Aquinas’s Summa Theologica (13th c.) are organized into major parts, questions, articles, objections replies. Manuscripts often show them as indented or cascading lists, essentially early outline trees.

    3. Early Printed Encyclopedias and Tables of Contents

    • 16th century encyclopedias and legal codices began using tables of contents that were hierarchical, with indentation or stepped numerals.
    • Example: Conrad Gesner’s Bibliotheca Universalis (1545) and Historia Animalium (1551–58) used hierarchical subject divisions, sometimes visually tabulated.
    • Legal codes (e.g., Corpus Juris Civilis, rediscovered 11th c. and printed 16th c.) were also structured hierarchically with books titles chapters sections.

    4. Early Modern Systems

    • Francis Bacon’s Advancement of Learning (1605): explicitly presented a tree of knowledge divided into disciplines and subdisciplines, often printed with indentation.
    • Diderot & d’Alembert’s Encyclopédie (1751): had a famous “tree of knowledge” diagram based on Bacon, with branches into philosophy, theology, sciences, arts.

    5. Library Classification Systems

    • Dewey Decimal Classification (1876): Explicitly hierarchical in decimal notation. Not typically indented in early catalogs, but by design it’s a tree structure (e.g., 500 510 516).
    • Library of Congress Classification (1897 onward): Used an alphanumeric hierarchy with indentation in catalogs.

    TL;DR – Earliest Examples

    • Tree of Porphyry (3rd c. CE): first explicit hierarchical tree diagram.
    • Scholastic outlines (12th–13th c.): earliest indented/nested list format in manuscripts.
    • Early printed encyclopedias & legal codes (16th c.): hierarchical tables of contents.
    • Dewey Decimal System (1876): modern numeric hierarchy for catalogs.
  • There is obviously prior art, so it's not patentable. Since we are seeing more and more of these malicious attempts to patent common practices, I would propose that the patent authority can issue penalties for it. Like, let them issue a fine up to 5 percent of the business' turnover of something for really egregious behaviour like this. Make them feel it.

    As it is now, there is no reason not to try, which is kinda ridiculous.

    • by PPH ( 736903 )

      There is obviously prior art, so it's not patentable.

      Too late:

      Patent and Trademark Office (USPTO) has granted

      Patent clerks used to be smart [wordpress.com] and familiar with the state of the art. Not so much anymore, I guess.

  • by msauve ( 701917 ) on Sunday September 28, 2025 @05:31AM (#65688032)
    There should be no software patents.
  • by Mirnotoriety ( 10462951 ) on Sunday September 28, 2025 @06:44AM (#65688054)
    Patent Application: Revolutionary Bread Browning Solution (a.k.a. Toast)

    Abstract: This groundbreaking invention tackles the age-old crisis of bread being too soft, too edible, and frankly too boring. By blasting bread with weaponized levels of heat until it cries out in crispy anguish, this system produces what humanity calls "toast." Said toast can then be smeared with salted fats, sticky fruits, or whichever condiment is least expired in one’s fridge. The invention supersedes all prior methods of “leaving bread near fire and hoping for the best.”
  • I worked for this one company for 13 years and started from the ground up. Later on I was asked to be a part of 3 teams that were to compete in an internal design contest for visualizing hierarchical data. As a part of this internal development team our goal was to reduce the labor needed in the process by adding a visual component to the correlations. This allowed an anyone to quickly investigate an item further to verify the data points accuracy. It was simple and elegant, I was so proud of my design. In

  • by frdmfghtr ( 603968 ) on Sunday September 28, 2025 @07:17AM (#65688078)

    It's called an "org chart."

    Oh wait this is an org chart "with a computer."

    What am I missing here?

  • â¦On a computer

    Patent granted.

  • for real, they want control of the directory! this is b u l l s h i t.

  • Just like a million or more of others, who have done the same, I have personally, singlehandedly used the same exact principles and techniques to construct in a dynamic manner, not only visual representations of parent/child relationships as visual trees, but created entire systems that relied on these concepts for both, reporting and control.

    I am absolutely capable of displaying my work, results of my work, people using result of my work, my work used in production on daily basis. I built a retail managem

  • "So, do you think Tableau should be awarded a patent in 2025 on a concept that has roots in circa-1921 Sunburst charts and tree algorithms taught to first-year CS students in circa-1975 Data Structures courses?"

    Absolutely, as long as they also accept my patenting the letter "e" and my groundbreaking idea of "making things hotter or colder by using electricity".

    Pay me, bitches!!

  • This is one of those "practitioner skilled in the art" kind of things. We've had SQL and UML for ages that use and visualize parent-child relationships. Once you know them, this is an obvious application for making queries about the relationships. Given how ubiquitous trees of various kinds are, I doubt their specific implementation is particularly novel.

He who is content with his lot probably has a lot.

Working...