Christian's point is key. The absolute hardest problem to solve is where to anchor semantic information so that others can contribute to it easily, because his project requires lots of microcontributions (cf. Nielsen's Reinventing Discovery) Right now, by lack of a better place, it is put in sage. According to me, this is a sensible short term solution, step 1 if you want. Step 2 is that the LMFDB starts to do the same thing putting semantic information on empty classes and methods. Step 3 is that we find a better way, armed with two use cases. I don't think we are ready to go to step 3 yet. Paul
Paul-Olivier Dehaye SNF Professor of Mathematics University of Zurich skype: lokami_lokami (preferred) phone: +41 76 407 57 96 chat: pauloliv...@gmail.com twitter: podehaye freenode irc: pdehaye On Wed, May 28, 2014 at 4:37 PM, Christian Stump <christian.st...@gmail.com>wrote: > > Ceterum censeo: Please do not put too much semantic into an attribute of > > the map. It will be a burden for the map, will cost memory, and will be > > difficult to search. > > I would personally really like to get semantic information about maps > implemented in Sage. This starts with automated concatenating maps, > and does not even end with information about a map in the Journal of > Applied Nonsense. I am sure you have reasons to vote for a centralized > system where to store such information. But how am I then convincing > someone knowing that information to add that information there? What I > like about a local system (preferably accompanying the code of the > very method) is that it makes it easy for the person having > information about a specific map to provide that information. > > Of course, that information must be organized to be searchable > properly. But I don't see a problem there beside conventional namings. > > -- > You received this message because you are subscribed to the Google Groups > "sage-combinat-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-combinat-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-combinat-de...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-combinat-devel. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
