Git Product home page Git Product logo

Comments (3)

zkgeiselmann avatar zkgeiselmann commented on August 12, 2024 1

I added a Zenodo Identifier for our description to the wikidata page.
Does this look alright?

from mardiroadmap.

zkgeiselmann avatar zkgeiselmann commented on August 12, 2024 1

While adding our Identifiers to the individual Wikidata entries for the Johnson solids, I have noticed an inconsistency.
J1 is a square pyramid, and as a Johnson solid, it has constant edge lengths. In the context of Johnson solids, this last statement is usually omitted.

Wikidata has two competing entries:

  1. https://www.wikidata.org/wiki/Q1075704 A square pyramid without further constraints, so the edge length is not necessarily constant, however Norman Johnson is stated as the "discoverer" of this object.
  2. https://www.wikidata.org/wiki/Q17370383 A square pyramid with equilateral triangle sides. This has very little data to it, much of which has been added by me, but at the moment classified as a Johnson solid.

Clearly the second one is a Johnson solid and the first one is not necessarily. However the pentagonal pyramid https://www.wikidata.org/wiki/Q1154713 is also classified as a Jonson without specifying the constant edge length (there are more such examples), so using the second entry is inconsistent with the other examples.

I would like to state that the first square pyramid is a Johnson solid under the condition that its edge lengths are constant, but I can't find out whether this is possible in Wikidata (if so this could also be done for the other examples). I would also like to remove Norman Johnson as its discoverer (possibly also for some other Johnson solids, because pyramids have been known for much longer).

If this is not possible I am unsure how to proceed. Do I make the second entry a subclass of the first and repeat this process for similar Johnson solids?

from mardiroadmap.

Daniel-Mietchen avatar Daniel-Mietchen commented on August 12, 2024

@lkastner @zkgeiselmann It took me a bit to get into the matter, but now I think I can respond to your points:

While adding our Identifiers to the individual Wikidata entries for the Johnson solids, I have noticed an inconsistency. J1 is a square pyramid, and as a Johnson solid, it has constant edge lengths. In the context of Johnson solids, this last statement is usually omitted.

Wikidata has two competing entries:

1. https://www.wikidata.org/wiki/Q1075704 A square pyramid without further constraints, so the edge length is not necessarily constant, however Norman Johnson is stated as the "discoverer" of this object.

2. https://www.wikidata.org/wiki/Q17370383 A square pyramid with equilateral triangle sides. This has very little data to it, much of which has been added by me, but at the moment classified as a Johnson solid.

Clearly the second one is a Johnson solid and the first one is not necessarily.

Indeed.

However the pentagonal pyramid https://www.wikidata.org/wiki/Q1154713 is also classified as a Jonson without specifying the constant edge length (there are more such examples), so using the second entry is inconsistent with the other examples.

I would like to state that the first square pyramid is a Johnson solid under the condition that its edge lengths are constant, but I can't find out whether this is possible in Wikidata (if so this could also be done for the other examples).

I don't think this is currently possible that way, but I have started a discussion to get some input from others.

I would also like to remove Norman Johnson as its discoverer

Done.

(possibly also for some other Johnson solids, because pyramids have been known for much longer).

Yes, feel free to go ahead and adjust as necessary.

If this is not possible I am unsure how to proceed. Do I make the second entry a subclass of the first

Yes.

and repeat this process for similar Johnson solids?

Yes. I think this would be the way to go for now. If the discussion brings up another option, we can reconsider.

If you keep working on this, maybe this query — or variants of it — can be helpful to keep an overview.

from mardiroadmap.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.