n170201
nfoWare
nfoNote
SemFix:
Semantic Text Prefix
Diary & Job Jar
|
|
n170201
nfoWare
nfoNote |
0.00 2017-02-18 -10:05 -0800 |
Status |
Date |
Description |
|
| 2017-02-18 | n170201/n170201c: Make permalink section/paragraph labelings. | ||
| 2017-02-18 | n170201c: We also have, as sources, #!, ASN.1 object-identifiers pointing to specifications, namespace identifiers, XML processing instructions, and HTTP capability negotiation. That also means that there needs to be a standard way to resolve conflicts (e.g., talking about an XML document, as a prefix on a Zip (?!), etc. | ||
| 2017-02-18 | n170201c: Consider combinations of prefixes and the ordering that matters. This may require continuations to be distinct from new introductions. | ||
| 2017-02-18 | n170201c: Consider Alternative prefix combinations beside "#?", "<!", etc. These will apply in plaintexts and in cases of Literate formatting. | ||
| 2013-11-10 | There needs to be a way to deal with texts and language-oriented features (especially with Unicode and BiDi) without having to boil the ocean. There are scaling and starting out considerations. This is all about managing generalization along with the worst that can possibly work. The conflict is around not wanting to ever obsolete previous material. Versioning will help going up-level, but down-level may be a problem unless defaults for handling unrecognized features are carefully established. [dh:2017-02-18 Some of these qualities are relevant for SemFix, not just UpDown where this was first raised.] | ||
| 2013-11-08 | It is very desirable to allow embedded markup in limited ways, mainly for setting styles around segments (oh, oh, start and end tags?), and for [La]Tex formulas. The problem is there being too much LaTeX. There needs to be some way to constrain this and allow some sort of control, perhaps in parameterization of the level the LUD appears in. This has to default out in some tidy way also. [dh:2017-02-18 This is not something that SemFix deals with, but SemFix might be valuable in company with these cases.] | ||
| 2013-11-08 | In targeting scripting languages, an enclosure might be executable lead to rendering in dynamic form. There is some line not to cross here, even though it might be closer to Simple Federated Wiki. There is an SFW application, perhaps, as well as under node.js. It is interesting to consider whether Frugal/Miser could play here. [dh:2017-02-18 This consideration applies to the use of SemFix on an embedded text in a Literate UpDown and other use inside of a program code / literate commentary. It also means that I have even more application cases for this, and it is useful to have some basic structure so I can use it in those contexts as early as possible. It is important to not be reinventing TeX and Literate Programming this way.] | ||
| 2013-11-08 | For SemFix, there is a consideration for defaults when something is not understood. It should simply be without processing apart from any (default) formatting might apply for literal (unrecognized) material. There should not be error codes/markup that intrude on treading of the material. There is some sort of principle or pattern about this. Also, the default formatting might be determined by the processor used to render and there might be logs about it all, marginal flags, etc. This is also important when bootstrapping a format, since there may be things that will not be understood downlevel in various implementation. MCE can apply here in some sense. [dh:2017-02-18 Applied to SemFix from UpDown] | ||
| 2013-11-08 | For the SemFix #? I need to differentiate between the program to run and what the file format is. There is also more involving file-name extensions, Open With cases, etc. There may need to be external cases, such as association MIME Types by some means. We may need to be careful and stick with simple extensional stuff. There is also the small issue of versioning the SemFix scheme itself. [dh:2017-02-18 Applied to SemFix from thinking about UpDown.] | ||
| done 2017-02-18 |
2017-02-15 | Add ClustrMap to n170201 and n170201c. | |
| done 2017-02-18 |
2017-02-15 |
|
|
| done 2017-02-18 |
2017-02-15 | Create prototype/placeholder pages for this folio: n170201, n170201a, n170201b, n170201c | |
| done 2017-02-18 |
2017-02-15 |
Create this page ready for recording Diary & Job Jar items of this nfoNote. |
|
created 2017-02-18-08:46 -0800 |
