Comments (6)
Could be convenient in some cases. Just one thing though. Many properties of spaces can be deduced from other properties via theorems. We don't want to lose that ability, as it's one of the nice features of pi-base, allowing to eliminate duplication in that way. If space X is listed as having property A, and a theorem has A implying B, we still need B. One asserted trait per file may be what makes this work currently?
(And not directly related, but I think there are quite a few traits files that could actually be removed and deduced instead.)
from data.
This proposal would replace the files spaces/Sx/properties/Pm.md
and spaces/Sx/properites/Pn.md
with the following header metadata in spaces/Sx/README.md
(which I'd further lobby to rename to spaces/Sx.md
):
properties:
- id: Pm
value: [true|false]
- id: Pn
value: [true|false]
Then all the current reference metadata and supporting content written each property's markdown file would be incorporated into the main spaces/Sx/README.md
(or spaces/Sx.md
) file. This better mirrors the pattern of properties/Py.md
and theorems/Tz.md
files, and should make editing much more streamlined. Particularly in the case of #134 where I have a single reference that defends every asserted property.
This should not change the behavior of automatically deduced properties. We still need to provide tooling to find redundant properties.
from data.
Are you proposing this only for the cases of properties whose justification is entirely contained in the reference mentioned at this top level that defines the space itself, and we would keep the previous scheme for cases where more explanations are provided or different references are used specifically for different properties?
Also I assume the search capabilities by properties would not be affected?
from data.
Ah, let me amend this.
properties:
- id: Pm
value: [true|false]
refs:
- mathse: 123456
- id: Pn
value: [true|false]
refs:
- jstor: 123456
So each assertion should have a reference or two. Then either any further elaboration goes in the main README for the space itself, or we could consider an extra note: "hello world \(x^2+y^2\)"
attribute on each property item that contains the content currently stored in the space/property pair markdown file.
from data.
N.B. I'm not proposing any difference in the front-end viewer; it would have essentially the same capabilities (search, automatic deduction, etc). But this would make most contributions significantly more streamlined.
from data.
I am starting to like this idea. For deploying/testing this, we could:
- do a first pass at a change in the infrastructure to support both old and new scheme
- pick a representative space X with multiple property files with a variety of things like proofs, comments we want to preserve, etc
- introduce a parallel space "TEST X" using the new scheme
- see the result and compare how spaces X and TEST X look like in the front end viewer
- tweak/iterate as necessary until we are satisfied with the result
from data.
Related Issues (20)
- Add Michael Line HOT 1
- Examples of Hausdorff non-regular P-spaces which are and aren't Urysohn HOT 3
- Variants of compactly generated spaces HOT 20
- Tracking issue for redundant theorems HOT 3
- Hey doofus, here's a property you're missing
- Temporary added workflow for merging contributions HOT 3
- Citing the pi-Base HOT 3
- edit math.stackexchange posts linking to pi-base HOT 3
- Add open long line HOT 2
- Import the Boolean Spaces machine HOT 2
- Merge S50 into S27 HOT 3
- Example of door space HOT 5
- Ostaszewski space HOT 5
- Example of Totally Separated Λ Metrizable Λ ¬Zero Dimensional HOT 2
- Properties independent of ZFC HOT 1
- Euclidean subspace property
- T107 improvement HOT 13
- Selection principles; Fortissimo spaces HOT 9
- Variations on the Frechet-Urysohn property
- Mysior plane HOT 17
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from data.