tag:blogger.com,1999:blog-70192123585136810562024-03-13T23:33:24.599-07:00Digital Spelunk 42A Web-Based Tech NotebookAnonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.comBlogger143125tag:blogger.com,1999:blog-7019212358513681056.post-17872395297862150842015-10-28T03:54:00.002-07:002015-10-28T03:54:39.064-07:00On Discovering the Wonders of Stack Machines in Contemporary Software Architectures<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgS6i6cBv5XMaZuO3NoCDhM6CwpH1x4KFRzjNsYYNsHvbC1_0TTdrdSz3jneMGtPFBfi_l13Enx63VjOHH2M5-CvYB9Cz1LV10uVEYuxDoLoeRNEPNWzYmDQb7I1b5UlN1Lpv7VZr6v5OI/s1600/Screenshot+from+2015-10-28+03-39-05.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="179" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgS6i6cBv5XMaZuO3NoCDhM6CwpH1x4KFRzjNsYYNsHvbC1_0TTdrdSz3jneMGtPFBfi_l13Enx63VjOHH2M5-CvYB9Cz1LV10uVEYuxDoLoeRNEPNWzYmDQb7I1b5UlN1Lpv7VZr6v5OI/s320/Screenshot+from+2015-10-28+03-39-05.png" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">FreeBSD PMake : make -dv</td></tr>
</tbody></table>
<br />Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-40713962467060130932015-10-19T22:04:00.000-07:002015-10-19T22:49:20.871-07:00The Day When the HPAN Open Book Project BeganIntro humor: Wondering if it may be possible to develop a dedicated web browser submodule in an FPGA circuit for a single-board computer. This question, of course, entails a short review of resources on the Web and about the SysV shared memory (SHM) architecture, such as implemented in the FreeBSD operating system -- in short synopsis, because CORBA CDR and applications of SysV SHM in inter-process communications onto a single physical machine architecture. This article will resume another topic, shortly.<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEha9HVi899mCf-blO5NCZMP09jfYMsQ-lQzNe2ev-8h4z5IoIM-X6YxoT9xsT6UGp_sbla4ul1FEYoAHlec3a_rEs1V0CSkwyrkbhWhxP54dnGhTVMkZUpGetOK6LFvN_onxotFABCuqcQ/s1600/Screenshot+from+2015-10-19+20-45-39.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="179" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEha9HVi899mCf-blO5NCZMP09jfYMsQ-lQzNe2ev-8h4z5IoIM-X6YxoT9xsT6UGp_sbla4ul1FEYoAHlec3a_rEs1V0CSkwyrkbhWhxP54dnGhTVMkZUpGetOK6LFvN_onxotFABCuqcQ/s320/Screenshot+from+2015-10-19+20-45-39.png" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Gecko + Firefox at 131.74% WCPU</td></tr>
</tbody></table>
This morning, there was a certain announcement published on Twitter, as with regards to a certain discovery likewise published by the <a href="http://www.snf.ch/">Swiss National Science Foundation</a> (<a href="http://www.snf.ch/">SNF</a>), <i>viz a viz</i>: <a href="http://www.snf.ch/en/researchinFocus/newsroom/Pages/news-151019-press-release-new-electronic-component-replace-flash-storage.aspx"><b><i>A new electronic component to replace flash storage</i></b></a>. In the original article that I had seen mentioned about the news, at the Twitter social microblog service -- <i>viz a viz</i>, <a href="http://www.newelectronics.co.uk/electronics-news/swiss-researchers-have-created-a-memristor-with-three-stable-resistive-states/108563/"><i>Swiss researchers have created a memristor with three stable resistive states</i></a> (newelectronics) -- the research is attributed to researchers at <a href="https://www.ethz.ch/en.html">ETH Zürich</a>. In some regards, juxtaposed to ETH's web site, the article published at the SNF's web site might seem overall more informative about the scientific development of the discovery. A short search for "memsistor" at the ETH web site does not reveal any search results.<br />
<br />
In both articles -- the first, published at the SNF web site, and the second, published at the newelectronics web site (UK) -- in both articles, the discovery is referenced as in a context of reprogrammable memory-oriented storage. <br />
<br />
Of course, it would be a short semantic leap from such a topic, to a topic of solid state device (SSD) storage modules -- as, in applications, SSD modules serving as certainly a common feature of mobile computing appliances, of contemporary "Rack mount" server architectures, and sometimes also in laptop computing architectures. The repercussions of a new three-state method for data encoding within reprogrammable memory-oriented storage, it could be profound simply in the storage manufacturing industry.<br />
<br />
What struck me about the article: The discovery essentially describes a three-state mode of logical voltage analysis -- principally, as a matter distinct to the contemporary "Tri-state" voltage analysis, that as with regards to "voltage high", and "voltage low" states, and a mysterious "high-impedance" state of a discrete electrical circuit, in a design-oriented view -- that rather, the discovery introduces a mode of logic in which a whole new unit of measure of information is required, the "Trit", a three-state <i>bit-like</i> unit of measure for information.<br />
<br />
Considering -- albeit, in a manner of broadly foreshortened synopsis -- considering the broad range of conventions developed, to the contemporary "State of the Art", developed as with regards to discrete<i> binary</i> states of logic, in a manner of a <i>binary</i> voltage-state model of discrete circuit analysis, the "Trit" -- in its applications -- along with the corresponding <i>memsistor</i> technology developed -- it would seem, jointly developed -- by ETH Zürich and the Swedish National Science Foundation, these could substantially affect the very nature of electrical circuit design, as primarily of circuits implementing a conventional <i>binary voltage-state model</i> in circuit design.<br />
<br />
It might seem like onl;y a small item of news, a mere quantum of popular press in a very large information space of the contemporary Webs. It is, potentially, a discovery of momentous significance -- significant not only in with regards to prospective designs of computer hardware, but furthermore significant as in regards to the essential nature of logical/mathematical models applied in circuit analysis and circuit design.<br />
<br />
The author of this web log article being, perhaps, something of a "Rogue scholar," maybe it could seem convenient therefore that the author is in any ways of a disposition to be able to observe the significance of the discovery. Not as if to attribute it to any manner of any manner of a national stack of industrial laurels, however. The discovery is profound.<br />
<br />
Focusing about some topics as commonly referenced with regards to mathematics developed of the contemporary electrical sciences, to the contemporary "State of the art" in electronics -- voltage, current, resistivity, "and so on" -- considering that any new development of the "State of the Art" must necessarily proceed from a number of previous developments in the "State of the Art", it may be possible to develop at least an estimation of how a "Trinary logic" could be applied in circuit design. The author of this article -- perhaps, stretching a little far, semantically -- the author of this article estimates that it could serve to introduce a manner of a spherical model of mathematical analysis of electrical circuits.<br />
<br />
Short of delving into a very visual illustration: Conventional electromagnetic waverforms can be rendered -- as in a voltage analysis -- rendered for a time-series presentation on a Euclidean space of coordinate (t,E) for t representing time, E representing voltage, and the Euclidean coordinate space being presented in as a rectangular coordinate plane. In an alternate model for voltage analysis over time, E can be rendered as a polar radius, t as a polar azimuth, and the continuous voltage waveform illustrated -- whether instantaneoiusly, or in in a computationally interactive manner -- illustrated as in a projection onto a polar coordinate plane.<br />
<br />
Albeit -- the author sifting through his own thesis, presently -- the discovery at ETH/SNF does not itself introduce any new measure of fundamental electrical information. It does not any add new -- so to speak -- any new greek letters to the formula of Ohm''s Law. Thus, it might not seem sufficient to introduce so much as an "iota" of a <i>third vector element</i> -- pun intended -- to the (r, theta), or (E, t) analysis of voltage over time. Thus, perhaps it may not be immediately representative of any new manner of spherical model of anything, <i>per se</i>. Simply, the guesstimate -- so to speak -- as towards a <i>spherical space</i> for analysis of electrical systems, it might derive only of the author's own small effort for estimating a "plane" for a "third state", in a <i>trinary voltage</i> model -- assuming there is a plane on which a <i>binary voltage waveform</i> may be rendered -- which there is, as to a presentation in terms of <i>voltage</i> and <i>time,</i> not so much immediately in terms of the conventional <i>binary logical voltage</i> model, such that is extended -- as in an orthogonal, if not transitive manner -- such a binary model originally being extended to a concept of <i>binary voltage analysis</i>, principally extended to a concept of an <i>information content</i> in and of <i>voltage states</i>, in a direct current (DC) circuit.<br />
<br />
The discovery of an application for a <i>trinary logic</i> in a "real world" electrical system -- as towards an estimate of potential applications, simply -- it may most certainly entail a consideration of what a voltage state "Means," in a circuit. <br />
<br />
Beyond the perhaps simple analysis of a polar state of voltage -- as with regards to theoretical "Electron surplus" and "Electron deficit" states, in a charge-oriented/kinetic theory of circuits -- albeit, the polarity of a charge source, as may be a property of and in a continuous, alternating current flow, it might not seem to be immediately "Factored in" to a discrete logical model of circuits. In a shorter phrasing: Polarity may not typically occur as a concern, in digital circuit design. Logical circuits typically operate on direct current -- ideally, as with no reversal of <i>current polarity</i> occurring, in a logical circuit.<br />
<br />
Considering the "high/"low" or "on/off" state of a discrete signal in a DC circuit as it being a single, discrete <i>state</i> or <i>quality </i>representative of the DC voltage of the discrete signal -- as onto any single voltage-level model, whether of industiral conventions in Transistor Transistor Logic (TTL), or conventional CMOS logic, or in any of the newer low-power logics typically found in applications of mobile appliances -- perhaps it could seem to greatly complicate the manufacturers' responsibilities for circuit design, if as to introduce a trinary <i>voltage state</i> model. <b>That it could -- in ways -- that it could positively affect the overall "Information bandwidth" of circuits</b>, perhaps that might be sufficient as to retain the manufacturers' attention to the topic.<br />
<br />
If a unit of information may be measured as in a <i>base three </i>or <i>trinary </i>model of voltage states (E_0,E_1,E_2), the third logical state of the <i>trinary model</i> would not immediately "fit in" with either of the TTL or CMOS voltage state models. E_2 would need to be defined with an "acceptable voltage range" , as much as E_0 and E_1 are presently defined of to an "Acceptable voltage range" in the present TTL and CMOS models.<br />
<br />
This is all diverging, although, from the author's own novel project idea of making "A thing" out of the geometry model in the Common Lisp Interface Manager (CLIM), seconded with an applciation of the Garnet KR subsystem for a design of an algebraic system ... and supported with a project the author of this article now denotes as the "Open Book" project, manageably a project developed under the Hardpan Tech label. The project has existed for only a half of a day, and it is already at full momentum ....<br />
<br />
Perhaps, more "Updates" will "Follow," soon.<br />
<br />
In albeit a simple sense, the discovery may introduce a new manner of meaning about analysis and design of information-carrying circuits -- such that could be, as a category of circuits, juxtaposed to so many mechanical work-producing circuits as may be applied in in electrical mechatronic systems, as well as photo-electrical circuits, such that may be applied in any typically non-central manner, in solar-electrical generator systems.<br />
<br />
The author will resume an imitation of a decorative potted plant, presently.Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-87096882109769430032015-10-17T16:01:00.001-07:002015-10-17T16:58:01.905-07:00Late Announcement of a Fork of CLORB, and Documentation Design, a CTags-to-DITA Model, and a Concept of Security Policies for Common LispOn reviewing a set of notes I've begun developing as towards producing an unambiguous outline of concepts as applied with regards to material sciences and computing, then in considering a possibility of developing a modeling service in extending of the topical outline of the article with models of tangible computing machine designs -- in no radical estimation of concepts of intellectual property, simply focusing on a modeling view, this morning -- I've returned to a fork of <a href="http://clorb.sourceforge.net/">CLORB</a> that I had created at GitHub, presently named <a href="https://github.com/hpan-open/feldspar-dnet-corba">hpan-dnet-corba</a>. The name of the fork is derived of the name of the <i>Hardpan Tech</i> projects set, as well as a concept of a <i>distributed data network</i>. Presently, I am fairly certain that the repository will be renamed. I believe that I may be fairly certain that this will not interfere with anyone's present work, in regards to software development -- the repository at GitHub, in its present state, has not been forked, starred, or "Watched". Neither have I been able to proceed to any immediate development of the codebase in the repository -- so far, directing my attention to other projects. Of course, GitHub will automatically forward any URLs on event of repository name change.<br />
<br />
On reviewing the codebase of the CLORB fork, this afternoon, not firstly considering any of the immediate "TO DO" items -- for instance, to ensure that CLORB will apply a portable sockets interface, such as usocket, a portable threading interface of some kind to be determined, to the project, and a portable operating systems interface such as osicat, then to proceed to update the CLORB baseline for the latest edition of CORBA, as well as to develop an implementation of the CORBA Component Model (CCM) in Common Lisp, to include services for component assembly and component activation, moreover in a manner as may be compatible onto component definitions not written in Common Lisp, however compiled to any single object file format -- my most immediate concern, superficial though it may be, is that I do not want to "Get lost in the codebase."<br />
<br />
Of course, that would not be "All of the project," either, as far as updating the fork I've begun of the CLORB codebase. Likewise, I would like to develop a set of Common Lisp metclasses for reflective modeling of the IDL definitions that will be implemented with the codebase. This, I am certain, would be relatively easy to develop, with a small modification of the IDL compiler, onto a specific namespace syntax for IDL in Common Lisp, and a compatible definition of object services for Interface Repository reflection in CORBA. This extension would depart from the traditional IDL binding for Lisp onto CORBA -- incorporating some functionality available in a Common Lisp dialect, so far as may be available of Common Lisp implementations including an implementation of the Metaobjet Protocol (MOP) as MOP representing an implementation, transitively, of the Common Lisp Object System (CLOS).<br />
<br />
Furthermore, I would like to develop a concept of a manner of "Specialized dispatching" of Common Lisp method definitions -- if definitively possible -- such as for implementing an instance of a definition of an object method A operating on a parameter B, within an arbitrary class C i.e C::A(B), such that the method definition is translated to a method A having a lambda list with specializers (C B) in Common Lisp. For instances in which A is not specialized onto any class D, then its unique application in C may be collapsible to a specialization onto B. Of course, if A would later be defined with a specialization onto any class D, then its implementation should need to be "Un-collapsed" to allow for dispatching onto both C and D. This, of course, might entail an unconventional extension onto a MOP implementaiton, itself, but it could be developed as to be portable onto MOP. Considering that any possible "Un-collapsing" would be performed at component load time, it may be minimally expensive as in regards to computational resources, while allowing -- ideally -- for something of an optimization in regards to runtime method dispatching. A to whether any further "Dispatch collapsing could be performed ... but this should all be proceeded by an in-depth study of the respective MOP implementation. Presently, though I may wish to assume that a MOP implementation is already implemented to its optimal semantic and procedural effectiveness for standard method dispatching in Common Lisp, but the nature of the conventional IDL-to-Lisp binding -- I think -- may seem to suggest that an <i>even more optimal</i> model may be possible. Not as if to split bits over a matter of byte sequencing, I think it represents a useful goal for a CORBA implementation.<br />
<br />
So far as with regards to a concern of object modeling, there could seem to be an irony -- that here I am beginning to consider to "Put the wheels to the road," in a manner of speaking, to proceed now about CORBA development in Common Lisp, and to proceed as towards a purpose of developing a no doubt intellectual property-agreeable model repository service ... and yet that I may be unable to develop a model for this project until having produced this project to such a point as in which it would be applicable in a modeling service, or either, in perusing the codebase manually.<br />
<br />
So, there is an exit condition from the semantic loop of that concern -- namely, as to read the source code. Again, though, I am at the concern to not "Get lost in the source code."<br />
<br />
In extending of a concept of "reading the source code", of course I would also want to begin to develop a comprehensive reference about the source code, namely in a documentation format external to the source code. Personally, I would not prefer to develop such a manner of reference if with an HTTP virtual filesystem service intervening, in which a local filesystem service may be sufficient.<br />
<br />
There's a side note about the reStructuredText (RST) format that could seem apropos, inasmuch -- RST offering a certain number of syntactic features effectively extending of the set of markup types available in the Markdown format. With GitHub providing instantaneous RST-to-HTML translation, and though it may not be the most computationally efficient process to not write the documentation originally in HTML format and publish it likewise in HTML format, but text-oriented markup formats may typically be more succinct than HTML, and would probably be more "Friendly" to editors not familiar with an XML format. <br />
<br />
Alternately, it may be feasible to develop a DITA formatted <i>topic repository</i> about the original CLORB codebase, then to update the same topic respository with any later notes as may be added onto any reference elements generated in the immediate Lisp-to-DITA translation. Thus, as this is not an enterprise project, and it does not have an enterprise management base to manage it by, but with it representing nearly an enterprise scale of endeavor -- in a small manner, as it might seem -- it can be approached functionally and manageably, to so much as document the existing CLORB codebase, even if in a manner as that the documentation may be <i>intermediate to</i> any updates of the codebase.<br />
<br />
Of course, to keep the documentation synchronized with any changes to the source code, it would need an attention to both of the documentation and the source code, as if simultaneously, and throughout the duration of any updates to the source code. <br />
<br />
Much of the documentation might be generated, initially, with an application of CTags -- if not of an extensional tool, such as <a href="http://ctags.sourceforge.net/"><i>Exuberant CTags</i></a> -- then with an application of a transformation model for generating documentation from a <i>set </i>of<i> templates</i>, such as may be applied to the <i>tags lists</i> generated by the respective CTags implementation. Such a procedure, of course, could be performed onto any single language supported by the respective CTags implementation, given any suitable set of document templates. It might not be in all ways analogous to <a href="http://lxr.sourceforge.net/en/index.php">LXR</a> or <a href="http://www.stack.nl/~dimitri/doxygen/">Doxygen</a>, though accomplishing a result in some ways similar to Doxygen -- namely, a structured reference about source code forms -- though ideally, producing documentation files in a structural format resembling the Common Lisp Hyperspec, such that may include -- by default -- the contents of any available <i>documentation strings</i>, and such that may be extended, potentially, with source code references -- and a corresponding URI transformation -- in a manner analogous to LXR.<br />
<br />
Thus, it might produce not so much of an IDE-like web-based presentation for linked source code review, rather producing a sort of "Skeleton" -- 'tis the season -- for support of <i>documentation authoring</i> onto an existing codebase. It would not presume to provide a complete set of documentation files, but merely a skeletal documentations structure -- such that could then be edited by software developers, such as to add any documentary information that would not otherwise be available, immediately, in the source code. In a sense, it would may as to provide a manner of a <i>source code annotation</i> service, but with the annotations contained in documentation files, not directly in the source code.<br />
<br />
In regards to a design of a template model for application in such a manner of a documentation skeleton generator tool, it might be beneficial if the documentation and templates may be maintained -- in some ways -- separately, with a semantic linking model as to ensure that the documentation may be automatically "Linted" for compatibility across any changes to the source code -- "Actively linted," moreover, such that if an object is renamed in the source code, its documentation will be renamed, and if removed, then its documentation removed, and if any new features would be added, that a new documentation stub would be added for each feature.<br />
<br />
Speaking of <i>features</i>, in a context of Common Lisp, some <i>features</i> may be difficult to "Parse for," however -- the Common Lisp <i>feature</i> syntax itself, for instance, such as "#+quux or "#-quux" or any more complex expressions such as "#-(and quux (not quo))". Perhaps it may be in no small sense of coincidence, if such expressions might -- in ways -- might resemble something like a C preprocessor syntax, moreover being evaluated in a manner -- namely, at the nearest approximation of "Compile time" in any Lisp reader/evaluator procedure -- then in a manner analogous to how a C toolchain evaluates a C preprocessor directive, but minus any analogy of of macro syntax and evaluation. In a sense, it is like the Common Lisp read/eval/print loop (REPL) applies a preprocessor in the reader component, intermediate to a computational evaluation of forms read by the reader, then any printing of return values or stream output values as may result of the evaluation. It might seem, in some ways, "More tidy," but a whole lot less common than the langauge's name might seem to imply.<br />
<br />
So, together with such a short sidebar about <i>tool stacks</i> in C, continuing ... the documentation system, if it can update the documentation files in parallel to any updates observed of the source code itself -- maybe it could be presented to market as a manner of a "Smart" documentation system, but aside to so many concerns of marketing -- if not updating the documentation tree in response to any changes in actual definitions of compiled objects, then as long as any "Manually written" documentation is maintained in a manner separate to any "Generated structural" documentation, the "Manually written" documentation can be presented for update, corresponding to any change in the structural definition of an object.<br />
<br />
It might seem computationally frivolous, perhaps, to propose to keep a documentation tree simultaneously linked with an object system, and the object system's source code and documentation tree both mapped onto a filesystem managed under a Software Change and Configuration Management (SCCM) service. It's certainly a small toss from the CTags-parser paradigm, but it may be only a small toss inasmuch. The most computationally expensive aspect of such a feature, it may be in simply monitoring any source code file for changes, then detecting which definitions a change applies to, then processing the documentation about those definitions such as to reflect the change in the source code -- likewise, maintaining a manner of a table between object definitions and source forms, such that if a compiled definition is replaced with a new definition, the developer may be presented with a set of convenient, if not in ways pedantic options for modifying the documentation about the original definition.<br />
<br />
Of course, considering that an object's definition, in a compiled form, may not be so much "Changed" in its compiled data, as much as "Replaced" with a newly defined object of compiled data, it would certainly need some implementation-specific modifications to implement this albeit <i>ad hoc</i> proposal, in full -- that the software system could be programmed to detect a change in the definition of a named object, and if maintaining a definition-source state about the name of the object (as some Common Lisp implementations may, at developer option), that the detected change could be noted in the software's program system, then followed with a query to the developer by some manner of an interactive prompt.<br />
<br />
Towards developing a programmed security model onto Common Lisp, the very fact that a Common Lisp implementation may allow any item of code to redefine any existing item of code -- sometimes, as optionally filtered with "Package locks" -- we must assume that all of the software code having been evaluated by a Common Lisp implementation is instantaneously trusted, moreover that not any software will be evaluated that is not trusted -- an oblique sense of "Trust", by no means programmatically defined. Perhaps the security policy model defined in Java could seem to be of some particular relevance, at that, short of any <i>ad hoc</i> and distinctly <i>not code related</i> approaches to ensuring a manner of discrete security of software code and program data.<br />
<br />
By no means will this project represent any manner of trivial convenience. Even in the simple effort of developing so much as a design for a documentation system, it somewhat apparent that there may be some "Lower level concerns" -- such as that the Common Lisp language development ... may be behind in a few updates, as with regards to the "State of the art" in commercial software development, quite candidly. Though Common Lisp is a computationally comprehensive programming language, but if Common Lisp may be applied within a secure, trusted commercial communication system -- firstly, we may wish to consider, each, our own integrity as to how much it is a<i> trusted</i> programming language, juxtaposed to any programming language as may provide a distinct level of <i>security policy definition</i> and of <i>security policy enforcement</i>, ostensibly with such <i>security policy features</i> being applied throughout commercial software systems.<br />
<br />
The author of this article is not one to place any chips on the table, before an analysis of such a concern.<br />
<br />
It may be not as if Common Lisp was vastly behind other programming language -- short of anything in regards to "Warm fuzzy" marketing -- but the <i>security policy </i>issue, it may be approached perhaps without any too broad sweeping changes to any single Common Lisp implementation.<br />
<br />
So, but there was a discussion about documentation, in this article -- albeit, an in many ways breeezy, verbose discussion -- an in-all-ways a rhetorical discusssion, likewise lacking any great presentation of detail. This article describes a manner of a semantic model for working with documentation and source code, in parallel. This article does not go to great lengths for a description of the DITA format, or XML Stylesheets, or the Document Object Model .<br />
<br />
Presently, this article returns to the original topic, of generating documentation from CTags files. The topic of IDE-to-source-code-to-object-definition linking should be approached with a manner of a later demonstration, but first there would need to be an IDE compatible to the demonstration. Secondly, the topic of how-to-prevent-unwanted-object-redefinition-scalably-and-well could be approached of any much more detailed analysis.<br />
<br />
Towards a manner of an event-oriented model in regards to definitions in Common Lisp programs, appending a few <i>ad hoc</i> notes:<br />
<ul>
<li>Types of Program Objects, "Program Top Level"</li>
<ul>
<li>Variable Definitions</li>
<li>Type Definitions</li>
<li>Class Definitions</li>
<ul>
<li>Structure Class Definitions</li>
<li>Condition Type Definitions</li>
<li>Standard Class Definitions</li>
</ul>
<li>Functions</li>
<ul>
<li>Standard Functions</li>
<li>Funcallable Instances</li>
<li>Generic Functions</li>
</ul>
<li>Method Definitions </li>
<li>Macros </li>
<li>Special Operators</li>
<li>Packages </li>
<li>System Definitions</li>
<li>Declarations</li>
<ul>
<li>FTYPE Declarations</li>
<li>Type Declarations onto Variables</li>
</ul>
<li>Closures and Closure Environments</li>
<ul>
<li>Concept: Null lexical environment, i.e. global environment, as an effective "Top level closure" </li>
<li>Concept: Redefining a lexically scoped object defined in a non-global environment, A-OK ?</li>
<li>Concept: Redefining a 'special' scoped object defined in a non-global environment, A-OK ?</li>
</ul>
</ul>
</ul>
<ul>
<li>Events</li>
<ul>
<li>Event: Program Object Definition</li>
<ul>
<li>Instance: One of Defvar, Defparameter, Defconstant</li>
<li>Instance: LET </li>
<li>Instance: Defclass, or related CLOS, MOP protocol procedures</li>
<li>Instance: Defun</li>
<li>Instance: Defgeneric</li>
<li>Instance: Defmethod </li>
<li>Instance: Defpackage</li>
<li>Instance: Defsystem or similar</li>
</ul>
<li>Event: Program Object Redefinition</li>
<ul>
<li>Instance: SETF <special object="" program=""> <setf-data> </setf-data></special></li>
<li>Instance: SETQ <special variable=""></special></li>
<li>Instance: Object definition onto a previously defined object</li>
<ul>
<li>Re-DEFCONSTANT: Implementation-specific handling [exists]</li>
</ul>
</ul>
<li>Event: Program Object Definition Shadowing</li>
<ul>
<li>Not expressly 'redefinition', more entailed of both <i>closure definition</i> and component <i>program object definition</i> </li>
<li>Synopsis: a lexical scope is defined in which a program object defined in which a new definition is created, in a manner as to effectively shadowed a definition previously created -- a definition furthermore bound to a single name for the definition's program object type -- in a containing lexical scope</li>
<li>May be a part of a shadow => redefine procedure</li>
<li>May or may not be approached "Maliciously"</li>
<li>May produce unintended side-effects in software programs, e.g. if *STANDARD-OUTPUT* is shadowed as to pipe all data through a digital wormhole to an alternate universe</li>
</ul>
</ul>
<ul>
<li>Event: Program Object Deletion</li>
<ul>
<li>Note: Though defining a top-level interface for garbage collection, Common Lisp (CLtL2) does not define any single 'finalize', 'delete' or 'free' procedure, such as could be applied for dereferencing and deallocating objects manually</li>
<li>Instance: makunbound <symbolically-named-program-object> (global symbol table)</symbolically-named-program-object></li>
<ul>
<li>Note: Whether or not this would actually result in the deletion of the program object, or merely in the "Un-binding" of the program object to any single symbolic name, may be implementation-dependent</li>
</ul>
<li>Instance: fmakunbound <named-function> (local function table) </named-function></li>
<ul>
<li>Does not affect immediately any compiled, inline functions in which contexts the respective functions are compiled inline</li>
</ul>
</ul>
</ul>
</ul>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-68417467992049388022015-10-16T15:48:00.000-07:002015-10-16T22:48:20.626-07:00Toolchains in a Key of C<div dir="ltr">
In developing a lively, component-oriented view of software development -- allegorically, as beginning from a location of "the ground," towards a limit of "upwards" -- it may be logically reasonable to begin with a component, "The Toolchain." Not as if to propose any singular, <i>ad hoc</i> definition of a concept of a topic so broad as <i>toolchain</i>s -- and in this single article, as such -- theoretically, a definition of "The Toolchain" begins with a definition of "The operating system." In the present State of the Art, that would likely entail one of: Linux, any single BSD -- for instance, FreeBSD, NetBSD, OpenBSD, or any BSD happily derived from either of those three "Main BSDs" -- or OS X, or Microsoft Windows.</div>
<br />
<div dir="ltr">
Proceeding in a rough estimate along a timeline going backwards in relation to present time, previously the State of the Art would have also included Beos, NeXT, MS-DOS, IBM-DOS, CP/M, the Lisp Machines of yore, and any number of UNIXes whose development in any way chronologically parallels the same timeline. The Industry has had its trends, for a number of years, before Social Networking web log networks ever became such a popular topic as today, a topic how much for advertisers, Social Networking networkers, and the more of the social networking service user community. If assuming that we may say that the present State of the Art is the only State of the Art that has ever existed, in all known time, we might likewise be assuming as if life proceeds without a sense of historical context. Though that could be quite a trendy way to not view history, perhaps it may be understood that the present State of the Art has developed only of the previous State of the Art, at any moment of time. If we may leave aside so many stylistic brand names and endeavor to consider how the present State of the Art has developed, perhaps we can learn more of the present State of the Art, if not of any estimable "Future" State of the Art, by studying any works of the previous State of the Art. If that does not tire us fully, perhaps it may begin to seem that not all of the State of the Art may have developed as if only along any single linear chronological trend. Thus, even as if to analyze the architecture of an operating system comprising any manner of an obvious element of the present State of the Art, there may be a whole lot of "Previous work" available, such that may serve to inform the present discussion -- as even of so many discrete encodings of program codes onto punch cards, and applications of Teletype machines for other than radio telecommunications, and any trends marking the evolution of terrestrial semiconductor manufacturing methods. The State of the Art, clearly, being a material domain, though not exclusively of any single material vocation -- not even as if singularly of the many works of marketing, of works of media ever apparently seeking to draw a social attention in one way or another across the present State of the Art, if not furthermore to direct the viewer's attention to any single commercial product -- perhaps it cannot all be said to derive back to a material physics and a corresponding mathematics ever developed of any possibly more intuitive laboratory.</div>
<br />
<div dir="ltr">
Inasmuch, it might not be said that all of the State of the Art derives back to knowledge, or knowledge deriving back to language, or everything under the sun deriving back to a simple concept of communications. Such naive theses, though presenting any manner of an immediate sense of perspective, may seem difficult to prove, to any detail, logically and at scale. Perhaps not all of the universe is merely a mote in the eye of a grand, benevolent narcissist, but it would seem that much of the known universe derives, at least, to a sense of information.</div>
<br />
<div dir="ltr">
So, if we are to begin at toolchains, it might be expedient to skip ahead past the estimable origin of the physical universe, to leap a little ways across the evolutions of mineral mining and tool production techniques, to take a long way around the events of empires, piracy, and war, and hop on up to the present day, in which all operating systems may appear to be constructed of C or a programming language deriving of C, in terms of syntax, semantics, and evaluation procedures. The subtle leaning of Java over to anything like a Lisp -- even so far as of the <i>lambda</i> nomenclature of the Java programming language, edition 8 -- this might be ignored simply as an aberrant trend, nothing whatsoever arcing around to another method of systems design, nothing in any ways suggesting anyone had constructed any microprocessors either wrongly or in way merely keeping up with the industry's state at any point in time. Surely, every microprocessor must have an Arithmetic and Logic Unit, and every OS must be constructed of C or a dialect of C ... except for those that are not.</div>
<br />
<div dir="ltr">
So, then -- taking some liberty to try to construct a light-hearted point of view of this thesis -- we may begin with the present state of the art in C toolchains.</div>
<br />
<div dir="ltr">
...and the author will return to this thesis, shortly, with a reference to the K&R book, section 4.11, and no further aside about a story by -- estimably -- a satirist writing by the name, Ayn Rand.</div>
<br />
<div dir="ltr">
For wont of expedience, this article will resume the discussion not at the development of the first C dialect, in 1971 [<a href="http://www.catb.org/esr/writings/taoup/html/index.html">Raymond2003</a>], and neither of an analysis of any market trends, ahead to which the GNU C Compiler Collection (GCC) first addressed the GNU Public License (GPL) to a Patents Industry, thirdly leaving aside any analysis of the complex interleavings of the LLVM toolchain and non-BSD operating systems including OS X and Android, lastly to an immediate, albeit in ways <i>ad hoc</i> overview about a generic model of a C toolchain, as to include -- in the albeit <i>naive</i> model -- a C preprocessor, a C compiler, and a C linker, such that the linker produces -- in a procedure of processibg certain intermediate compiled object files produced by the C compiler -- producing a loadable binary object file, such as may be later evaluated by an operating system, whether evaluated as a "runnable" software program having any single main() routine as its entry point for its launching as a software program, or evaluated as a library file for linking with other binary object files. This generic model may be difficult to describe to any detail, for how it may serve as model if the components of any single toolchain, with the addition of any more specialized and toolchain-specific components, abd an aside to address compiler components such as may produce an intermediate or loadable object file, from a source code language not C.</div>
<br />
<div dir="ltr">
Of course, as well as those components of a C toolchain -- the preprocessor, the compiler, and the linker -- there is also the inevitable Makefile implementation, such that provides instructions to an operating system for how to "Put the pieces together" to any point of program evaluation, in producing evaluable programs. A Makefile interpreter, in some regards, might be cast in a metaphor of a mechanical chef.</div>
<br />
<div dir="ltr">
Aside to the C toolchain, of course there are software programs that may -- in ways -- resemble a Makefile interpreter, such as the Ant program, in a Java toolchain, or the inimitable ASDF, in a Common Lisp toolchain, as of the present state of the art in Common Lisp system definition utilities. The author's novel thesis that all of these toolchains could be -- theoretically -- translated into a Common Lisp interpreter, it might seem too novel to be obviously relevant to the State of the Art. For all of the UNIX architecture developed in C, furthermore, it might not either be fortuitous to abandon such architecture for a Lisp Machine, if without making a comprehensive study of the exiting work.</div>
<br />
<div dir="ltr">
Of course, not all of UNIX is implemented in C. In fact, the FreeBSD operating system uses a bit of Forth in its bootloader. Ever, there are these novel things that so impede a linear introduction of the State of the Art. Forth being a language as much allied to a concept of stack machines as is the Lisp implementation described in the AI Memo 514, in which the authors propose to develop a microprocessor absent an ALU, as well as proposing an implementation of Lisp, in how far absent to the going trends of CISC microprocessor designs, of industry at the time -- to the author's best understanding of such features of the State of the Art -- well so, but now we have C, C preprocessor langauge, Makefiles, and Forth, as well as anything else that may be compiled to a binary loadable object file, insofar as source code languages -- with a note in regards to intermediate object file formats, and loadable object file formats.</div>
<br />
<div dir="ltr">
The author has read that there are criticisms of Lisp syntax. The author fails to understand, How can this be? Is it too far unlike the linguistic sandwich bar of the modern toolchain? Could it be, perhaps, too far unlike a CISC language?</div>
<br />
<div dir="ltr">
On top of -- or, in another way <i>below to</i> -- C, of course there is the syntax of any single assembler. Below the assembler, in a similar arc, any individual Instruction Set Architecture.</div>
<br />
<div dir="ltr">
Not as though to begin a Lisp Advocacy thesis forthright, ironically there's something like an assembler defined in one Common Lisp implementation named CMU Common Lisp, the low-level compiler VOP framework of CMUCL being then inherited by Steel Bank Common Lisp (SBCL), with SBCL being originally a fork of CMUCL. How this may seem to parallel an evolution of a BSD operating system -- moreover that CMUCL's architecture may seem, in some certain ways, curiously BSD-like -- but it might not seem to contribute an obvious whole lot(TM) to the State of the Art, Immediately Today(TM) to make any too lengthy dissertation of such topics of systems evolution, and well would the author go out of depth to speculate of the similarity. No myth, no magic, perhaps an independent operating system can be developed out of Common Lisp, once more, but there is a dearthy lot of existing work to observe, if not to study, in UNIX systems.</div>
<br />
<div dir="ltr">
Perhaps the author has begun to mistake this English language for Makefile syntax, if not merely a disposable lexicon. Of course, BPMN might be far more succinct, visually -- if not more likewise difficult to reproduce if discarded -- to describe a thesis topic or a recipe.</div>
<br />
<div dir="ltr">
And so, the author must take another aside, with a glib and/or drab nod to the works of the grand satirists in literature. This article has now breezed across the whole C toolchain, topically, and here it is not even August yet.<br />
<br />
<i><b>Ed. Note: </b></i>This article may be reviewed, at some later time, towards clarifications about compiler architectures, including: The nature of "Intermediate" compiled object files (e.g. *.s) whether present in C compilers, C++ compilers, or otherwise; the role of the assembler, in the procedures of the compiler.</div>
<br />
<div dir="ltr">
Before commencing to present the <i>hot topic</i> of the evening's article – as of a simple illustration of <i>two ways to produce object files</i>, each of a popular though by no means <i>industry-dominant</i> programming language, and as such, to produce object files as <i>without an immediate application of a C compiler</i> – the author should take care to define, initially, what the term,<i> object </i><i>file</i>, may denote – as in how the term may be defined, at least in a context of the media object comprising this single article, if not also of how the term may be encountered of other literature.<br />
<br />
In a metaphor to granola … <i>non</i>. This thesis shall presently disembark to a discussion of machine architectures, focusing primarily about microprocessor architectures, specifically Intel, MIPS, and ARM microprocessors. This representing an adventurous aspect of the evening's thesis, a food with a suitable proportion of complex carbohydrates may be recommended … if not a draught of the evening's coffee, along with.</div>
<div dir="ltr">
<br />
<br />
<b><i>This intermission brought to you in a format of lyrical music</i></b></div>
<div dir="ltr">
</div>
<iframe allowfullscreen="" frameborder="0" height="315" src="https://www.youtube.com/embed/JItQ4Kg5Zy8" width="420"></iframe>
<br />
<br />
[Article will resume momentarily]<br />
<br />
<b><i>Ed. note:</i></b> For some intents and purposes, the Executable and Linkable Format (ELF) may seem to be "Enough to know about", as with regards to object files produced by compiler toolchains on UNIX platforms -- at least, so far as up until a point of actually developing a compiler [TO DO: FINALIZE ARTICLE] (<a href="http://www.evernote.com/l/AepnrqwgquVLgJeK7v2Y5vFf_Q2L_2_U6eg/">NOTES</a>)<br />
<br />
<b><i>Ed. note:</i></b> Though the Embeddable Common Lisp (ECL) Common Lisp implementation can be applied to produce object files, it is not without applying a C compiler as an intermediary component. Thus, the comment -- in the previous -- as if it was possible to generate an object file with ECL does not hold. Neither might it hold as if LuaJIT was not applying a C compiler, itself, in producing object files for the respective machine of its application. As stated in the previous article, the "Hot topic" of the evening might seem to be a "Dud," in such regards.<br />
<br />
<b><i>Ed. note:</i></b> With regards to how ECL and LuaJIT may be applied with the LLVM toolchain, such a study may be addressed at a later time.<br />
<br />
<b><i>Ed. note: </i></b>Follow up with documentation about ctags, etags, Exuberant CTags, and llvm-clang ETags/CTags, as with regards to source code modeling and review. See also: Doxygen; UML; SysML; MARTE<br />
<br />
<b><i>Ed. note:</i></b> The goal of this article was to develop a singular overview about compiler toolchains, as with regards to (1) how a compiler toolchain is applied as a component of an operating system; (2) how a compiler toolchain extends of any single microcontroller's supported instruction set architectures (e.g. amd64, SSE2, MMX; on GPU microcotrollers, lastly, CUDA). Beyond such a description of existing work, in contemporary operating systems design, perhaps it may seem frivolous to endeavor to assert that a <i>reproducably usable</i> operating system may be constructed for contemporary microcontrollers, and without an application of a C toolchain.Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-78628566383254182372015-10-16T07:28:00.001-07:002015-10-16T08:22:42.474-07:00DevOps Servers - Jenkins or DIY?In developing a small concept of producing a DevOps server for the environment of a single Small Office/Home Office (SOHO) network, in the past couple of days I've reviewing a concept of installing <i><a href="http://gitblit.com/">Gitblit</a></i>, <a href="https://jspwiki.apache.org/"><i>JSPWiki</i></a>, <a href="https://roller.apache.org/"><i>Roller</i></a>, and <i><a href="http://activiti.org/">Activiti</a></i>, as web services, then to develop a minimalist web-based portal front-end for integrating those individual web service components into a single "User experience". These components would be installed, originally, to one of my old laptops, it serving a dual-purpose role as an old laptop retained of my own purchase -- now a manner of a sentimental artifact, sure -- presently applied as a FreeBSD server on a SOHO Local Area Network (LAN).<br />
<br />
The local web-type services, of course, would not be the only features of the same server's <i>Service mix</i>, as it would also publish a Git service from within a FreeBSD sandbox. The Git service, of course, could be published from a sandbox maintained in a manner separate from the host's web server sandbox -- that, as with a small amount of software to provide a filesystem bridge, between the two -- both sandboxes operating on the same computing machine, however, with both being procedural isolated from the "Sandbox controller" server. Even in so much as a design for such application of the FreeBSD sandbox, i.e jails framework, it might already represent a manner of a component-oriented software service design, though it is not yet in every ways a detailed software service design.<br />
<br />
I've favored this design, due to its minimalist nature and its development singularly in the Java programming language. I'd begun the design, after reading a comment -- from 2012 -- by James Gosling, a positive comment about <i><a href="http://gitblit.com/">Gitblit</a></i> [<a href="http://nighthacks.com/roller/jag/entry/benjamin_arrives_in_australia">Gosling2012PapaMau</a>] Of course, a positive comment by one of the original developers of the Java programming language may seem to <i>carry</i> for <i>some mileage</i>.<br />
<br />
In my own small software design work, proceeding from a review of the <i><a href="http://gitblit.com/">Gitblit</a> </i>web services component<i>,</i> I'd even developed a clever name for the design, a DevOps portal design for my own LAN, but such that should be scaleable beyond the "Single use" -- naming the design, "Glister," after an artifact of the Heritage Universe, a series of science fiction books written by a physicist, Charles Sheffield. In a context of the story of the Heritage Universe books, Glister is an Artifact that appears early in the story. In a context of a SOHO network, Glister has been -- thus far -- simply an easy-to-remember name for a single service design. As I've developed a substantial amount of writing about the design, in my Evernote notebooks, it is not a design I would want to abandon hastily.<br />
<br />
The design of the Glister DevOps server, in some ways, it mirrors the design of the <a href="http://www.emforge.net/"><i>EmForge</i> Portal</a>. In a manner, both designs would introduce a Business Process Management (BPM) component to the conventional <i>service mix</i> of a wiki, web log, issue tracking, and web-based source code review service -- as also seen, with some slight differences, in Edgewall's <i><a href="http://trac.edgewall.org/">Trac</a></i>, different at least in regards to the implementation of each service of the respective <i>service mix</i>. Of course, <i><a href="http://trac.edgewall.org/">Trac</a></i> favors the Subversion change management service, as does <a href="http://www.emforge.net/"><i>EmForge</i></a> -- whereas Glister would apply Git, with a <i><a href="http://gitblit.com/">Gitblit</a></i> web interface providing a light-weight localized service for immediate web-based source code review. <br />
<br />
Of course, the issue tracking feature might not seem as apparent as the novel "Other features" of the architecture. <br />
<br />
In the Glister portal, <i><a href="http://activiti.org/">Activiti </a></i>would provide a BPM management interface. Thus, it may seem to effectively mirror the the BPM component of <a href="http://www.emforge.net/"><i>EmForge</i></a>.<br />
<br />
Considering that the "Issue tracking" features of the Glister architecture may seem -- in ways -- very much obscured of the novelty of some of the other components of the architecture, perhaps the "Issue tracking" service could not be the main "Selling point", if it would be presented as all of a "Free beer" model.* Regardless, I've estimated that it may be relatively easy to develop an issue-tracking front-end for <i><a href="http://activiti.org/">Activiti</a></i> -- whether to emulate <i><a href="https://www.bugzilla.org/">Bugzilla</a></i>, <i><a href="https://www.bestpractical.com/rt/">Request Tracker</a></i>, <i><a href="https://www.gnu.org/software/gnats/">GNATS</a></i>, or any other normative issue tracking service -- such that would be developed, originally, for issue tracking about individual Ports, such as available on the <a href="https://www.freebsd.org/"><i>FreeBSD</i></a> operating system and such as would be installed to an individual SOHO network. <br />
<br />
Though I am not inclined to present it as if it was any manner of a "Zero-Sum Free Beer Return" process -- and well would such a process be a novelty, in itself, of all the spontaneous things -- I suppose that I could try to market it is as so, whatever I may eventually be able to develop of the Glister server baseline. Not as if to exploit "Free Beer," it is already a small effort at making use of a small number of existing software components, in developing a manner of an immediately "New" component -- so far, as to develop a "New", and in-some-ways "Unique" service design, then as to proceed towards an effort in producing and maintaining that design in its implementation, there in regards to some terms of real software integration, and documentation, and software distribution, and issue tracking. Maybe it would not seem immediately "Fun," in such a perspective.<br />
<br />
I notice, presently, that the <a href="https://jenkins-ci.org/"><i>Jenkins</i></a> server -- such that I may wish to denote as it being an <i>alternative to</i> an independent design of a DevOps server, such as Glister proposes to implement, and such as is implemented of <a href="http://www.emforge.net/"><i>EmForge</i></a> -- that the <a href="https://jenkins-ci.org/"><i>Jenkins</i></a> server has recently found an application in the FreeBSD project. If it is a project trusted by the FreeBSD project, and if it may serve a role in mitigating my own development burden, and as I may happen to personally trust the OS distributed by the FreeBSD project, in a far ways, thus I've begun to consider applying <a href="https://jenkins-ci.org/"><i>Jenkins</i></a>, albeit then to an effect of by-in-large abandoning the Glister service design.<br />
<br />
Though the Glister service design, in its exact and present composition, has not existed for any long period of time -- this specific design has been in development for all of a couple of days, now -- I'd thought it might serve as a manner of a "Go-getter" project, though, as well as a nice minimalist design for a convenient web service on a local area network (LAN). The note about <i><a href="http://gitblit.com/">Gitblit</a></i>, I'd thought<i>, </i>it had seemed<i> </i>to convey so much of the original goodwill that was ever demonstrated of the Java developer community, at least as in the duration up to which the Sun Microsystems company -- the original "Shop" in developing Java -- was acquired by Oracle. <br />
<br />
Whereas the latter corporate institution, Oracle, may -- in some manners of a metaphor onto science fiction -- that the Oracle company might seem to resemble an archetype much like the character of CLU in the TRON: Legacy universe, and though perhaps I'm the only person seeing it as so, but in no ambiguous terms: I miss the goodwill of the original Java developer community. That a programming language such as was originally developed to an effect of a <i>web browser plug-in</i> -- with regards to so much as the <i>Java applet</i> origins of the Java programming language -- that a single programming language, as such, has weathered all the tides of Enterprise trends and gone so far as to find an application in an embedded/mechatronic architecture presently continuing an expedition to Mars? Who could have expected such an outcome of a Java applet programming language? <br />
<br />
In any linear, even <i>post hoc</i> analysis, how could such a thing have become? and what has been lost of the goodwill of the original Sun Microsystems developer community, in the years since the acquisition by Oracle? Moreover, how much of the original brainpower of Sun, in effect, had "Jumped off the ship" once the Oracle acquisition was finalized? and today, does Oracle still try to discredit the nature of free/open source software engineering, but that may be where they could find any of the staff that left Oracle? Have we not learned anything of this process, as yet?<br />
<i><br /></i>Towards considering how the Glister service design might <i>scale</i> beyond a context of an individual LAN, it may be -- in that context -- that I might wish to entrust the <a href="https://jenkins-ci.org/"><i>Jenkins</i></a> web services as for those web services to not only present a novel web-facing interface, but also ... but no, it may be simply the novelty of its web-facing interface that would draw my own attention more to Jenkins, as any alternative to the minimalistic design of the Glister service mix.<br />
<br />
Candidly, I am a little worried about installing <a href="https://jenkins-ci.org/"><i>Jenkins</i></a> on my own SOHO LAN, as -- even with its full free/open source codebase -- I do not know if it is such a kitchen sink I may actually need to install. Not to discredit its component-oriented design, though I am in any ways nonplussed by its marketing. I do not know if a <a href="https://jenkins-ci.org/"><i>Jenkins</i></a> instance would actually "Do much" on my LAN, except if it may represent something of a novelty -- and yet, would the Glister design be any less so? If it may be any less of a novelty, and if it may be any more of a producible gain -- to my own manners of personal perspective -- but even if it may need "A lot more welding," as to "Put the thing together," for the "Thing" being a "DIY" component-oriented design of a lightweight DevOps server, maybe it's not too far past the sunset of Sun.<br />
<br />
Personally, I think that a design strategy of <i>"Everything and the kitchen sink"</i> would not be ideal for a design of a light-duty/low-usage software service for an independent network services environment. Thus, personally, I've begun to "shy away from" so many <i>Java Enterprise Kitchen Sink Portal</i> architectures and the <i>kitchen sink style</i> of DevOps services, likewise, in considering any "Forward" designs for network services and -- in that context -- also web services.<br />
<br />
I wouldn't want to seem too hasty in abandoning the concept of applying <a href="https://jenkins-ci.org/"><i>Jenkins</i></a>, immediately. No sales lost of it, I would prefer to resume the Glister service design, and to keep my design table "Lightweight."<br />
<br />
* The phrase resounds, even of free/open source software component systems: <i>Caveat Emptor</i>Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-32253278209998663002015-10-13T09:52:00.003-07:002015-10-13T13:27:48.106-07:00Why Open Source Operating Systems: Commercial-Free Developer Support and Technical DocumentationPerhaps one of the greater draws about software development with free/open source operating systems -- such as GNU/Linux, FreeBSD, Open Solaris, or the most of the Google Android and Samsung Tizen platforms -- perhaps, one of the greater draws may be found of a simple estimate of technical <i>developer support</i>, such as might be estimated to be in <i>greater abundance</i> of and about free/open source operating systems. Although -- candidly -- the developer support resources available of free/open source operating systems may not seem to be as <i>heavily marketed</i> as with commercially licensed, closed-source operating systems -- such as of the Microsoft commercial presence behind the <a href="https://msdn.microsoft.com/">Microsoft Developer Network</a> (MSDN), or the Oracle presence now backing the Solaris operating system, Solaris being originally a Sun Microsystems product -- but with a certain amount of attention and of simple resourcefulness, it may be possible to locate and to utilize some many of the resources as may be available for developer support about free/open source operating systems.<br>
<br>
<u><b>Developer Support in Free/Open Source Operating Systems</b></u><br>
<br>
Towards developing a manner of a <i>topical overview</i> about <i>developer support resources</i> as may be available about <i>free/open source operating systems</i>, a simple outline:<br>
<ul>
<li>Documentation</li>
<ul>
<li>Tutorial Documentation</li>
<li>Reference Documentation</li>
<li>Software Distribution Service Data</li>
</ul>
<li>Software Development Support Tools</li>
<ul>
<li>Compiler Toolchains</li>
<li>Integrated Development Environments</li>
<li>Developer Utilities</li>
<li>DevOps Tools</li>
<ul>
<li>Software Configuration and Change Management (SCCM) Tools, as a subset of Software Distribution Support Tools </li>
<li>Build Automation Tools</li>
<li>Software Distribution Utilities</li>
<li>Issue Tracking Systems</li>
<li>Whiteboard Tools</li>
</ul>
</ul>
<li>Developer Forums</li>
<ul>
<li>Mailing Lists</li>
<li>Bulletin Boards</li>
<li>Social Networking</li>
</ul>
<li> Source Code</li>
</ul>
It would be beyond the scope of this simple article, to develop any manner of a comprehensive reference manual about these topics. In so far as of the simple process of developing an outline of these topics, there -- in itself -- could be an outline towards beginning to develop a reference manual, as such. The <i>media</i> and <i>format</i> of such a reference manual, however -- secondly, the <i>topical scope</i> of such a reference manual -- may be behooved of some specific consideration.<br>
<br>
<u><b>Reference Documentation - Towards the Core of Software and Systems Literacy</b></u><br>
<br>
In regards to reference formats and reference media, the author of this article can denote a small number of topics offhand -- variably of media types and media distribution services<br>
<ul>
<li><b>Wiki</b> </li>
<ul>
<li>Context: referring to the formal <a href="http://www.wikipedia.org/">Wikipedia</a> model and the original <a href="http://c2.com/cgi/wiki">C2 wiki</a></li>
</ul>
<ul>
<li>Concept: Web-based topical discussions</li>
<li>Contents:</li>
<ul>
<li>Wiki Pages, formatted as HTML</li>
<li>Topical Taxonomies, representative of wiki page linking structures </li>
</ul>
<li>Availability: Public Internet, typically</li>
<li>Corresponding Concepts</li>
<ul>
<li>Bibliographies </li>
<li>Resource References</li>
<li>Web-Oriented Peer Review</li>
<ul>
<li>See also: Wikipedia - Articles - 'Talk' Section</li>
</ul>
</ul>
</ul>
<li><b>Project Reference Documentation</b></li>
<ul>
<li>Concept: Reference documentation developed of single projects</li>
<li>Availability: Variable</li>
</ul>
<li><b>TeX Info</b></li>
<ul>
<li>Concept: Narrative and Technical Reference Documentation</li>
<li>Availability: Typically available via shell command line, <span style="font-family: "Courier New",Courier,monospace;">'info'</span> shell command, such as may be available on any single operating system; may be available in alternate media formats (PDF, HTML)</li>
</ul>
<li><b>Manual Pages</b></li>
<ul>
<li>Concept: Technical Reference Documentation</li>
<li>Availability: Typically available via shell command line, <span style="font-family: "Courier New",Courier,monospace;">'man'</span> and <span style="font-family: "Courier New",Courier,monospace;">'apropos'</span> shell commands; may be available in alternate media formats</li>
</ul>
<li><b>Academic Dissertations</b></li>
<ul>
<li>Concept: Philosophical Overviews and In-Depth Studies of Technical Topics</li>
<li>Availability: Variable</li>
</ul>
<li><b>Technical Journals</b></li>
<ul>
<li>Concept: Market Information and Technical Overviews</li>
<li>Availability: Journal publishers; libraries </li>
</ul>
<li><b>Tech Books</b></li>
<ul>
<li>Concept: Friendly <i>overview</i> literature about technical topics</li>
<li>Availability: Books sellers; book services; libraries</li>
</ul>
<li> <b>Tech Encyclopedias</b></li>
<ul>
<li>Concept: Topical reference surveys about technical topics</li>
<li>Availability: Books sellers; book services; libraries</li>
</ul>
</ul>
<br>
<br>
<u><b>Introducing DITA, Obliquely</b></u> <br>
<br>
Towards a manner of applications of a single reference documentation format, it may be possible to develop an application of the Darwin Information Typing Architecture (DITA) in a context of any one or more of those topical categories. DITA is a standard format for technical documentation, standardized in publications from OASIS [<a href="http://docs.oasis-open.org/dita/v1.2/spec/DITA1.2-spec.html">DITA 1.2</a>]. In a simple estimate, it may seem that DITA may be most often applied for developing documentation about products of individual commercial enterprise institutions. However, DITA may find an application furthermore in documentation about free/open source products. DITA may be juxtaposed, functionally, to the DocBook technical documentation format [<a href="http://www.docbook.org/">DocBook.org</a>]<br>
<br>
<br>
<b>Web to DITA - XSLT and Semantic Wikis</b><br>
<br>
With regards to a Wiki as a manner of a reference model, it may be difficult to represent all of the depth and meaning of DITA markup within a Wiki markup language. Certainly, <i>some of</i> the DITA schema bears a close resemblance to HTML -- such as with regards to DITA <i>inline</i> markup elements broadly for specifying an <i>italics</i>, <i>bold</i>, or <i>underline</i> markup, and DITA structural markup elements for <i>ordered lists</i> and <i>itemized lists</i>, juxtaposed to any functionally similar markup elements in HTML. Such "HTML-like" elements in DITA might be easily transformed both <i>to</i> and <i>from</i> any conventional, typically HTML-oriented <i>Wiki markup language</i>.<br>
<br>
The more <i>semantically specialized</i> DITA elements may not seem meaningful in a <i>Web Media</i> model, until having been processed, mecahnically -- as in a publication process proceeding from <i>DITA source code</i> to <i>web presentation</i> -- processed with such as an XML Stylesheet Language Transformation (XSLT). Conversely, if to transform a Wiki markup into any of the more semantically specialized DITA markup elements -- as in a process proceeding from <i>Web-based Wiki</i> to <i>DITA source code</i>, in any manner of a converse directionality juxtaposed to a DITA-to-Web process<i> --</i> in order to transform Wiki content to DITA content, it may be feasible to begin with a <i>semantically specialized Wiki markup</i>, such as may be available of the Semantic MediaWiki [<a href="https://semantic-mediawiki.org/wiki/Help:Editing">Help:Editing - Semantic MediaWiki]</a>. Of course -- as like in order for Wiki editors to become editorially familiar with a semantically specialized Wiki markup language -- there may be an additional burden for documentation, if not training, in applications of a semantic wiki markup.<br>
<br>
If it may be feasible to develop a "Round trip" DITA-to-Wiki publication model, clearly there are some "Existing works," such as may be adapted to lend, functionally, to a DITA-to-Web and a Wiki-to-DITA publication process – a DITA-to-Wiki process being functionally subsumed of a DITA-to-Web process, in an application of XML stylesheets for transforming DITA markup into a semantic Wiki markup, and a procedural system for publishing the generated Wiki markup, juxtaposed to any more media-centric (HTML, PDF, EPUB) DITA-to-Web publication model. <br>
<br>
(Ed. Note: The following section of this article's text was originally edited with the Blogger web-based editor, in the Firefox web browser -- in Firefox' distribution on the Android platform. Presently returning to the desktop web browser, the author of this article will endeavor to study the availability of <a href="https://apps.wordpress.org/">Wordpress mobile apps</a>, as perhaps Wordpress may be more well supported than Blogger's Google-based blogging experience, on Anrdoid)<br>
<br>
<u><b>DITA Markup - Presence in Free/Open Source Software Projects</b></u><br>
<br>
<ul>
<li>DITA Open Toolkit </li>
<li> …</li>
</ul>
<br>
<i>The author of this simple blog article, presently, will return to a study of software development tools</i>Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-68872915332813305062015-10-11T08:57:00.000-07:002015-10-11T12:46:58.613-07:00Installing Debian 8.2 as a VirtualBox Virtual Guest in FreeBSD 10.2-STABLE <b>Synopsis: </b>In order to run the Mendeley and Evernote<i> desktop</i> applications on my FreeBSD laptop -- short of endeavoring to develop a <i>port</i> for each of those, as onto the Centos 6 (C6) Linux emulation layer, in FreeBSD -- previously, I'd installed Microsoft Windows 7 into a VirtualBox <i>virtual guest machine</i>, from a Microsoft <i>DreamSpark</i> installer disk. In a sense, it's "Worked," so far -- as after completing all of the OS installation process, OS update process, and software installation processes onto the <i>virtual guest machine</i> -- "Worked," though, in such that I now have a Microsoft Windows 7 <i>virtual guest machine</i> available for running Microsoft Windows software via VirtualBox on my FreeBSD laptop, but considering the substantial <i>hardware footprint</i> of Microsoft Windows -- as in regards to Microsoft Windows' utilization of system <i>memory</i> and <i>processor</i> resources, whether or not such <i>hardware resources</i> are utilized via a VirtualBox <i>virtual guest machine</i> -- I've estimated that it may be more effective to install Mendeley and Evernote into a Linux virtual guest machine. With those applications installed into a Linux <i>virtual guest machine</i>, and with the Linux operating system (OS) of that virtual guest machine being <i>tuneable</i> as a Linux operating system, I estimate that it may be overall a more effective way to utilize the Mendeley and Evernote desktop applications ultimately on my FreeBSD laptop -- more effective, juxtaposed to the Mendeley and Evernote desktop applications being installed to the, may one say, the <i>more indulgently designed</i> operating system that is Microsoft Windows 7. <br />
<br />
Thus, I've downloaded the Debian net installer CD -- using the BitTorrent P2P distribution for downloading the Debian net installer CD, then applying the ctorrent command-line BitTorrent application on my FreeBSD laptop. After some small effort for resolving an initial issue at installation time, I've now installed Debian into a VirtualBox virtual guest machine, on my FreeBSD laptop. Of course, this being a learning experience -- and although the style in which I write about this learning experience may not seem like "Normal English" to some readers' estimations -- I've considered that it may be useful to record some of my own technical observations from this learning experience, specifically of installing Debian 8.2 from the amd64 <i>netinst CD</i>.<br />
<br />
Firstly, as in order to so much complete the installation, I've configured the VirtualBox <i>virutal guest machine</i> such that the <i>virtual guest machine</i> would utilize the VirtualBox ICH9 CPU emulation -- juxtaposed to the VirtualBox PIIX3 CPU emulation. When the <i>virtual guest machine</i> was configured, originally, to use the PIIX3 CPU emulation, the installation would "Freeze", reproducibly -- furthermore, always "Freezing" at a specific time, such as when installing the 'passwd' utility during the Debian installer process. My not being immediately predisposed to <i>bug track</i> that specific issue, I've sought a workaround, and have found a workaround of the issue.<br />
<br />
Simply, in the graphical configuration panel for the VirtualBox <i>virtual guest machine</i> for the Debian installation -- specifically, in the <i>virtual guest machine</i> <i>'System'</i> configuration panel, <i>'Motherboard'</i> configuration tab -- I've selected the ICH9 <i>Chipset</i> <i>emulation</i> instead of the PIIX3 <i>Chipset</i> <i>emulation.</i> Once making that single change to the configuration for the <i>virtual guest machine</i>, I was able to complete the Debian installation. (<b><i>Ed. Note:</i></b> Of course, this configuration change could also be made in applying the 'vboxmanage' shell command, as may be installed with the VirtualBox OSE port on FreeBSD hosts. The VirtualBox manual describes the 'vboxmanage' shell command, at depth)<br />
<br />
In order to create something of a minimalist desktop, in the Debian <i>virtual guest machine</i>, I'd selected the XFCE desktop at installation time. Furthermore, I'd deselected the <i>print server</i> <i>installation task</i>, at that time -- thus limiting the amount of software that the installer would install in the <i>virtual guest machine</i>, before "First boot".<br />
<br />
Of course, the Debian <i>virtual guest machine</i> will be applied, on my FreeBSD laptop, not as if for creating a stand-alone virtual desktop environment of the Debian installation. Rather, ,the Debian <i>virtual guest machine</i> will be applied as to provide some <i>desktop application services</i>, such that may then be presented on the FreeBSD desktop via the VirtualBox "Seamless" display integration -- such that it will then be possible to use the Evernote and Mendeley desktop applications, without those applications being installed immediately to the FreeBSD laptop's root filesystem.<br />
<br />
At "First boot," with the newly created Debian <i>virtual guest machine, </i>I installed the Debian package <span style="font-family: "Courier New",Courier,monospace;">virtualbox-guest-dkms</span>. To install the Debian package, I used <i>aptitude</i> package manager application on Debian. The selection is illustrated on an XFCE desktop, in the following screenshot.<br />
<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUV9kKxJPmH9kZ7FVosgaLesRXlFhgSfwG_wVbpmtmjcDgYoGq0i7a-55uqUbCaEkwJvO3ghm052FcUWcEPzWxjpFAsV5U-iEAvHzHlifaWOR3JBkV-p9qnK72e6NVbl0FXkPmJ-Nzg6A/s1600/CorvidCube_1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="240" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUV9kKxJPmH9kZ7FVosgaLesRXlFhgSfwG_wVbpmtmjcDgYoGq0i7a-55uqUbCaEkwJvO3ghm052FcUWcEPzWxjpFAsV5U-iEAvHzHlifaWOR3JBkV-p9qnK72e6NVbl0FXkPmJ-Nzg6A/s320/CorvidCube_1.png" width="320" /></a></div>
<br />
<br />
<br />
After installing the <span style="font-family: "Courier New",Courier,monospace;">virtualbox-guest-dkms</span> package, I've then rebooted the Debian installation within the virtual guest machine. Following the reboot, the Debian installation can now utilize the VirtualBox <i>Seamless</i> display mode. Effectively, this allows for a close visual integration of desktop applications running directly in the Debian virtual guest machine, in a manner of visual integration with the FreeBSD desktop -- at which desktop, I've been applying the Cinnamon desktop environment. <br />
<br />
Of course, the installation is not as <i>functionally seamless</i> as much as it may seem <i>visually seamless</i>, at least by the time of "Second boot". At time of "Second boot," I can't help but notice that the <i>virtual host machine's</i> mouse pointer is not actually producing <i>input events</i> to the desktop in the <i>virtual guest machine</i>. The host machine's mouse pointer then <i>appearing to make</i> a manner of <i>geometry events</i>, in the <i>virtual guest machine</i> -- at least, from how it seems, with the desktop of the <i>virtual guest machine</i> being displayed within a VirtualBox window on the <i>virtual host machine</i>. It may be that the <i>virtual guest machine</i> is not receiving any input from the host machine's mouse pointer, in the "Second boot" <br />
<br />
At "Second boot," the desktop of the <i>virtual guest machine</i> has become unresponsive to the mouse pointer of the <i>virtual host machine --</i> perhaps it may be something to do with the APIC implementation in the <i>virtual guest machine</i>, as I've not seen any such issue with the Microsoft Windows <i>virtual guest machine</i> I've installed on the same <i>host machine</i>. In retrospect, the "Unresponsive" state of the <i>host machine's</i> mouse pointer may have actually preceded the switch into <i>Seamless mode</i> in the display of the virtual guest machine. Perhaps it may be "Cleared up" with a simple reconfiguration of the respective VirtualBox <i>virtual guest machine</i>.<br />
<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTRGqSvmKsCZNCi5xsYUhFbwqFsmAL_A46scH2MLJ4HajhVWCFcccCRnKMnYhNrDAvIAowFygG-a7wcljuir9AVENZ8wOFYOU-mi0s2aBvbjKEYCtCL0jDJzZQw-23uGCYtA5mA2xKV9c/s1600/Screenshot+from+2015-10-11+08-27-09.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="179" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTRGqSvmKsCZNCi5xsYUhFbwqFsmAL_A46scH2MLJ4HajhVWCFcccCRnKMnYhNrDAvIAowFygG-a7wcljuir9AVENZ8wOFYOU-mi0s2aBvbjKEYCtCL0jDJzZQw-23uGCYtA5mA2xKV9c/s320/Screenshot+from+2015-10-11+08-27-09.png" width="320" /></a></div>
<br />
<br />
<br />
After shutting down the <i>virtual guest machine</i> in its minimal "Second boot" configuration, I've now reconfigured the <i>virtual guest machine</i> -- as such, within the host operating system -- such as to apply the original PIIX3 <i>Chipset</i> <i>emulation</i> within the <i>virtual guest machine.</i> Subsequently, I've booted to "Third boot." In a simple commentary, it may seem that the ICH9 <i>Chipset</i> <i>emulation</i> was sufficient for application at installation time, but that it's not working out as well, for application at normal desktop runtime. With the PIIX3 <i>Chipset</i> <i>emulation </i>again selected, then at "Third boot" of the <i>virtual guest machine,</i> again I'm able to use the host mouse pointer within the <i>virtual guest machine</i>.<br />
<br />
The screenshot, above, illustrates the VirtualBox <i>seamless</i> desktop integration, with Debian 8.2 running in a VirtualBox <i>virtual guest</i> machine, and the VirtualBox <i>virtualization services</i> then running on a FreeBSD host. On the FreeBSD host, I'm applying the Cinnamon desktop environment. In the <i>virtual guest machine</i> -- presently -- I'm applying the LXDE desktop environment. Though I'm considering to deactivate the desktop environment, entirely -- albeit, then to a loss of "Window switching" behaviors in the virtual guest machine -- personally, I think LXDE is a nice "Starting point" for interacting with the virtual guest machine via a desktop/menu graphical interface. <br />
<br />
As illustrated in the previous screenshot, when the VirtualBox <i>virtual guest machine</i>'s display window is active on the <i>virtual host</i> desktop environment, and the <i>virtual guest machine</i> display window is configured for VirtualBox <i>Seamless </i>display mode,<i> </i>then the host machine displays the LXDE desktop environment effectively as a layer on top of the host machine's desktop. Visually, the effect is as if the Debian LXDE installation was running immediately within the Cinnamon desktop on FreeBSD. (<i>Ed. note: </i>Effectively, that is a characteristic of the functional configuration, moreover, with the LXDE desktop running within VirtualBox -- the VirtualBox virutalization services then providing a manner of a "Middle services layer" in running the Debian <i>virtual guest</i> <i>machine</i>, and VirtualBox running within a desktop on a FreeBSD host.)<br />
<br />
There are a number of optimizations that may serve to produce an optimally running virtual desktop environment, of a Linux installation in VirtualBox -- for instance, to adjust the "clock" timer in the Linux kernel configuration to a value that may be more optimal than the default value, such as for running a Linux desktop within a VirtualBox <i>virtual guest machine</i>. Furthermore, it may be advisable to disable the screensaver in the <i>virtual guest machine</i>. To any further detail, such optimizations will be left as an exercise for another article. <br />
<br />
By time of "Fourth boot," hopefully my own simple CorvidCube will have the Evernote and Mendeley desktop applications installed. Presently, perhaps it's an -- albeit wordy -- "Howto" towards a configuration of a sort of <i>meta-development environment</i> on a desktop PC.<br />
<br />
<i><b>Ed. Note:</b></i> As it turns out, the Evernote desktop application is not available for Linux platforms. Mendeley is, though [<a href="https://www.mendeley.com/download-mendeley-desktop/">Download Mendeley Desktop for Linux</a>]. Bibliography, and so on....Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-55806483349010849972015-10-08T14:37:00.002-07:002015-10-08T14:48:59.742-07:00Towards a Concept of Source Code Management - Android - Licensing, Repo, and RepositoriesEd. note: The following article is written with an assumption that a thesis thoughtfully juxtaposing the BSD and GPL licenses is already available, thus that the author's own perspective <i>that the BSD license is "More free" than the GPL -- </i>that this can be assumed to be a concept already familiar to an arbitrary reader.<br />
<br />
Ed. note: The following article will not present a juxtaposition of <i>marketing</i> and <i>propaganda</i>. The philosophical similarity of such concepts may be left for another time.<br />
<br />
Ed. note: The following article will not endeavor to address the ZMOT marketing strategy as published of any singularly advertising-oriented commercial agencies.<br />
<br />
Google Android -- as a mobile operating system certainly "more open" than iOS, if not measurably "More fun" than QNX, in any arbitrary measure of statistical popularity -- it being an operating system, it has a source code. It being an operating system based on the Linux kernel, of course it's an operating system extending of a GPL licensed work, moreover. Software licensing not being <i>per se</i> a time-locked concept, it may be a relevant concept even when it is not <i>per se</i> a popular concept. Thus, the author proposes to write about the concept, even in writing in a populist Internet media.<br />
<br />
Though the GPL license clearly does not limit the popularity of marketing about the Android platform, but as the GPL's licensing limitations representing a manner of a legal concept, and Google being a gargantuan company, it certainly may not be the veritable <i>poisoned apple in the varnish</i>, if it may be something that Google surely would have addressed, already, to all legal extents, already -- such as would be apparent of Google Android <i>source code</i> distribution and Google Android <i>binary application</i> distribution. <br />
<br />
So much as any non-GPL'd applciations may be defined as <i>linking to</i> the Linux Kernel in the Android platform -- that, of course, would not be "On Google," rather "On" the responsibilities of Android application developers. Sure, Google facilitates distribution of non-GPL'd applications for Android, with the Android App Store -- and sure, it may be difficult, if it is not altogether impossible for a software industry to thrive under a <i>toxic licensing strategy</i> such as, to some theories, the GPL represents. So far as estimating any possible risk of Android application development, with non-GPL's applications, "The industry" perhaps seems to "Look away" from analyzing the exact terms of the GPL license and its implications for applications development and public applications distribution on GPL'd platforms. Individual software vendors may not be at <i>such liberty</i>.<br />
<br />
A thorough study of licenses applied in the Google Android source code -- such a study being, no doubt, a non-trivial thing to develop -- may not be immediately forthcoming of this singular article, though proposed of this article, momentarily.<br />
<br />
A study about source code management practices applied with regards to the Android operating system -- as a study that <i>should be</i> preceded with a study about software licensing, as in regards to terms and practices of software licensing in regards to software development and software distribution -- a study about <i>source code management</i>, itself as <i>a topic</i>, may need not begin with any manner of a review of <i>marketing propaganda</i>.<br />
<br />
Of course, Android is designed to be compiled with GNU LibC and GNU Make [<a href="https://source.android.com/source/requirements.html">requirements</a>]. There's a certain alignment between Java Development Kit (JDK) versions and Android versions, moreover<br />
<br />
<center>
<table border="1">
<thead>
<tr>
<th>Android OS Version(s)</th>
<th>JDK Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>"Cupcake" .. "Froyo"</td>
<td>JDK Release 5</td>
</tr>
<tr>
<td>"Gingerbread" .. "Kitkat"</td>
<td>JDK Release 6</td>
</tr>
<tr>
<td>"Jellybean" ..</td>
<td>JDK Release 7</td>
</tr>
</tbody></table>
</center>
<br />
The Android Open Source Project (AOSP) applies <i>Git</i> as a software change and configuration management tool. Thus, the AOSP source code repositories may be presented as <i>changeset management</i> repositories -- of which, there are no few [<a href="https://android.googlesource.com/">android Git repositories</a>]<br />
<br />
As though in a manner similar to the Google Chromium project, the Google Android Open Source Project applies -- as extending of the Git changeset model -- a custom development tool, named <i>repo</i>. <br />
<br />
... a central managing repository of which is represented in the <a href="https://android.googlesource.com/platform/manifest/"><i>platform/manifest</i> repository</a> of the Google AOSP.<br />
<br />
<i>Repo</i> <i>may</i> provide a manner of a service for coordinating Git <i>changeset branches</i> among individual Git repositories published of the Google AOSP. The <a href="https://android.googlesource.com/platform/manifest/"><i>platform/manifest</i> repository</a> itself is organized with a number of changeset <i>branches</i> and changeset <i>tags</i>, each representing -- no doubt -- a specific <i>application target</i> for the Android platform, as in regards to platform development and software distribution services. The Android <a href="https://source.android.com/source/requirements.html"><i>Downloading and Building</i></a> guide, for instance, recommends a branch named <span style="font-family: "Courier New",Courier,monospace;">'android-4.0.1_r1'</span>, such that -- certainly -- would represent a version 4.0.1 release of the Android operating system, essentially as <i>upstream</i> to any vendor-specific additions to the operating system.<br />
<br />
Clearly, a topic of <i>Changeset Management</i> with the Android platform may seem to become to something of a geometric expansion, as with regards to analysis of <i>software repositories</i>, <i>software sources</i>,<i> software destinations</i>, and <i>provenance </i>as in a manner of <i>software platform analysis</i>. So far as that the <i>Repo</i> tool can be applied for accessing Android source code, there is a guide about it online.<br />
<br />
Candidly, so, it may not be all of a <i>trivial</i> process to develop a "match" between any single <i>vendor release</i> of the Android operating system, in matching to any single <i>upstream</i> Android open source release -- or, in a logical inverse of such relation, traversing the <i>Android OS distribution chain</i> from any single Android open source release to any number of individual vendor releases. <br /><br /> Beginning with changeset branch <span style="font-family: "Courier New",Courier,monospace;">'android-4.0.1_r1'</span> in the AOSP <a href="https://android.googlesource.com/platform/manifest/"><i>platform/manifest</i> repository</a> [<a href="https://android.googlesource.com/platform/manifest/+/refs/heads/android-4.0.1_r1">AOSP</a>] ... after a short 'Git clone', perhaps the contents of the repository would then be readily available for expert perusal.<br />
<i><br /></i>
<i>This author will presently take a short break, while mustering up to understand Android.</i>Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-61173649712873758802015-09-29T10:24:00.001-07:002015-10-08T13:48:04.109-07:00Customer Support at Five Minutes to Mark Zero <div dir="ltr">
Customer support services – there's a certain topic for the modern Web? With no lengthy thesis about business process management, stakeholder analysis, or theories of culture, or of community and narratives, customer support is a topic that the author of this article is in some ways well familiar with. So far as the topic ever finds a context in free/open source software (FOSS) systems, maybe it could be to a broad definition of a sense of <i>customership</i>, with no too exacting definition of a concept of <i>commercial services</i>. </div>
<div dir="ltr">
The Debian concept of a <i>social contract</i>, as sometimes denoted with regards to a concept of FOSS systems development, it may seem to represent all of a <i>constructive</i>, if not <i>novel</i>, if not in all ways a <i>naively idealistic</i> concept with regards to <i>social</i> <i>ethics</i> in practices of software and systems engineering. Whether or not it may seem to represent any sole, guiding principle in the work of developing FOSS systems, the Debian Social Contract may at least serve to represent a great, higher ideal, towards consideration of a social aspect of software and systems deveolopment – a sense of principle, towards a social regards in software and systems engineering – without specific delineation of a sense of institutions, in wordly material endeavor. In the contemporary, multiply connected universe, it may seem to be a concept in some ways strained, however, strained of so many narrowly globalist, nationalist, and more narrowly exclusive – if not naively exclusive, to denote such concepts in a manner of far understatement – irrationally exclusive narratives, such that become to no apparent gain in so many agendas' real world representations – no gain anywhere and much of destruction, of the apparently non-sane objectives of a radically populist riot state – the near ends of things, as demonstrated in Ukraine and elsewhere. What social contract may hold, of such a world?</div>
<div dir="ltr">
How can anyone propose to develop software, in such a world, if the <i>global</i> <i>customership</i> may include representatives of an army of murderous, radical thugs? The <i>coy</i> – may one call it coy? The coy manipulation of news as if to suit a narrow, naive, if not fundamentally anti-humane narrative – as represented in Ukraine, and elswehere, sometimes even to a point <i>where those whom may seem to imagine themselves controlling the chaos</i> would literally boast of their delusional affronts to the very nature of humanity – how is that even a trend, of any social climate? and yet, it has occurred in some of the very real world.</div>
<div dir="ltr">
There is certainly a lot of <i>human nature</i> such that any single social contract may not immediately serve to address, of any human endeavor. In that a social contract may serve as to establish any sense of a guiding principle, vocationally – but not to be preoccupied of worldly vocations. The author of this article very well wishes that everyone may enjoy a solitude like of Thoreau's reflections at Walden Pond – even for a short time in life, to reflect apart to material vocations – but how may a scholar maintain his hut, if the scholar would be forever about to make an idle thesis of an idle place? </div>
<div dir="ltr">
Apart to any radical social environments online or in the broader material world, what manner of a reflection may be found of broader life? What consideration developed, thence, of any material nature undespoiled as of the material debauchery so deeply criticized by Thoreau? and on return to a radically materialistic community, what to? To depart, thence to make a candid appraisal of radical materialism, may it be? What some social climates resemble, in the world – <i>hell</i> is a word for it. Albeit, it is a word denoting a concept not introduced of any single social contract. An analysis of <i>hell</i>, as a concept – but such a vocation has already been approached by Dante and Virgil. Notably, Dante's own travels had not ended at <i>Inferno</i>, that Dante literally went through hell for Beatrice.</div>
<div dir="ltr">
So, why does anyone try to make any kind of an <i>ad hominem</i> bias about software? An anthropologist's study of a sense of <i>cultutural identity</i> could be apropos, if there were not so many innately fratricidal cultural identities afoot in the world. The toxic agendas of an innately fratricidal radicalism – how does anyone set about to offer any of a sense of incentive to such a thing? If there is no incentive ever so much as imagined of it, then how does it continue? May there may be some people fundamentally aloof to the aims of a radical community? How, then, to mend hell on earth?</div>
<div dir="ltr">
It might not be in any single social contract, not even in the smallest of <i>fine print</i>.</div>
<div dir="ltr">
So, there being possibly more to life than as any single social or vocational contract may encompass, of itself, there is probably a consistent value of literacy – though it have the scholar situated squarely in hell, apace, if to follow the path of Dante Aligheri. The radical <i>Inferno</i>, the enterprise <i>Purgatorio</i> – and is there not any astronomical <i>Paradisio</i>, in this one scholar's poor knockoff of the <i>Divine Comedy?</i></div>
<div dir="ltr">
What social contract is there, and what society, if the world is all a mass of debauched individualism? </div>
<div dir="ltr">
What customership, if we are all set about to prove a fallacy of social "Darwinism"?</div>
<div dir="ltr">
What institutions, and what a profound aloofness of what self-serving potentates of merely political festooning, in any place much needing of a rational and authentically conscientious leadership?</div>
<div dir="ltr">
What has the world brought itself to, in these years? What fortune, to be alive in such a time? And how much of the world forever glib, aloof to all the furthest immoral depths to which any society in the contemporary world has yet plunged itself? Would one ask such a question, though, and the question be answered by all the more of a news of a cruel debauchery in the world? </div>
<div dir="ltr">
That, and an odd theme of socialism's implicit dysfunction – there may be a guiding light that occurs, even in a social Purgatory, if not moreover in an intellectual hell of a world gone squarely off of any natural, rotational axis, if not in a world seeming to be actively trying to herald a global Armageddon?</div>
<div dir="ltr">
For all the news that a commercial journalism has not reported of – again, this topic is not addressed of a social contract. </div>
<div dir="ltr">
There may be limits to the validity of a social contract, as much as there are limits to the literal scope of a social contract. There may be limits to a sense of imagination, moreover, none too well aided of a <i>trauma reporting</i> – and the human imagination stretched to a point of breaking, if anyone tries to leverage a propaganda of an atrocity made in real human actions, in the world.</div>
<div dir="ltr">
For all the real traumas occuring of a crisis, and for all the social aloofnesss of the materialistic world, what kind of a stakeholder analysis can bear the reality of it – of the world as people have made it to be, in where are the worst possible designs demonstrated of real human actions? Does all the world then need a coroner's wit, to extrapolate any manner of a sense of society?</div>
<div dir="ltr">
What if <i>material aloofness</i> is a part of the real problems, in the very real world? Would such a possibility ever be addressed of a social contract on the part of any material society? May a society imagine itself too successful to give a damn?</div>
<div dir="ltr">
What if?</div>
<div dir="ltr">
And if in such a social world, what to say about customer support?</div>
<div dir="ltr">
This thesis has arrived at its end.</div>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-54930115321316213942015-09-28T13:17:00.001-07:002015-09-28T15:56:04.188-07:00Android, FreeBSD, and the Golden Ticket Demistyfied <blockquote>
<b><i>"We don't support FreeBSD officially, so you'll have to run you custom Android Studio built from source."</i></b><br />
<div style="text-align: right;">
— [<a href="https://code.google.com/p/android/issues/detail?id=173413#c9">source</a>]</div>
</blockquote>
With regards to applying FreeBSD as a desktop operating system, the author of this article may presently endeavor to "Skip ahead" from recounting an initial installation of FreeBSD onto an HP Pavilion PC's EFI architecture -- with a small configuration in the laptop's EFI boot-time processes, FreeBSD boots, more easily so than on the author's own older MBR/BIOS-style laptop. The author is presently running the Cinnamon desktop, augmented with an installation of Microsoft Windows 7 in VirtualBox. Although the Pavilion PC's hardware isn't completely supported in FreeBSD 10.1, but it's sufficient to maintain a usable desktop with FreeBSD -- no clutter, no advertisements, nothing but plain computing with the FreeBSD brand of UNIX.<br />
<br />
It's theoretically possible, certainly, to develop a DITA topic repository as for the interest of presenting documentation to FreeBSD users and FreeBSD developers, in a centrally organized manner. Such a topic repository -- it might much resemble a Wiki, in style, though more centrally managed, such as <i>viz a viz</i> <a href="http://foldoc.org/">FOLDOC</a> -- it might not be a light feat to undertake, however. Of course, there's already the <a href="http://wiki.freebsd.org/">FreeBSD Wiki</a>, the <a href="https://www.freebsd.org/doc/handbook/">FreeBSD Handbook</a>, and the FreeBSD manual pages, all available as immediate documentation about components of the FreeBSD kernel, the FreeBSD base system, and ports available in FreeBSD. So much as in assuming that a manner of technical documentation may be of some assistance, in developing FreeBSD, the author of this article wishes to assume furthermore that a topic-oriented manner of documentation -- as may be developed onto a DITA format -- may be of some use for developing unambiguous documentation with regards to applications of FreeBSD. Of course, if there may be some disagreements about exact topical labeling and depth of overall content, maybe it would be only a "Paper project," after all.<br />
<br />
So, while the author of this article considers that it may be useful to write more documentation about FreeBSD, but the "Central DITA topic repository" model, as an idea, it may not seem as immediately feasible as much as it may seem immediately ideal to an overview of FreeBSD. Instead, the short and no doubt in-a-populist-light "Odd" notes at this web log may have to be sufficient, for developing so much as a stub of "New" documentation.<br />
<br />
What's to denote, "Newly" about the Android operating system? It's an operating system applying a Linux kernel -- different to other UNIX operating systems, and different to even the Linux desktop operating systems, in some ways. The Android Operating System features some components developed by the Google Android project, some of which components are distributed individually in the Google Play Services package for Android. No doubt, Google is the primary commercial institution developing the Android platform, but there is some development support available from individual vendors and developer institutions, furthermore, such as with Samsung.<br />
<br />
The Android operating system may be meaningfully contrasted to any number of other mobile operating systems, such a BlackBerry 10 and its QNX baseline, or iOS mobile. The Android operating system, in itself, is not all of the Google Play Android App Store, but certainly there's to one of the primary incentives to develop with Android -- as towards any possibility of developing an income from software development, moreover in software development applied onto the Android platform. Of course, as with many things, a topic of Android development may not stay forever contained of its own definition -- entailing, naturally, concepts such as of build automation, software distribution, and later issue tracking. <br />
<br />
The author of this article would not propose to raise a barn about Android, without first denoting that someone shall have to shovel out the stalls -- as in a metaphor onto Farmville, if not a metaphor to actual farming -- albeit, at some risk of trivializing the interactions with Android users, in the metaphor, perhaps moreover a risk of trivializing any nature of farming. Android users being individual persons, there's certainly much that can be said as to how provide effective customer support in the Android marketplace.<br />
<br />
It might seem to be of a different kind of media than of a typical commercial support counter, but -- in being fully aware of the shovel and the stall, so to speak -- it may remain a manageable endeavor, to provide customer support even to any very demanding customership in the Android marketplace.<br />
<br />
One chooses one's metaphors carefully, when choosing a metaphor with a bit of pith to it.<br />
<br />
Could it be, then, a glimmer of the much sought after "Golden ticket," that it is possible to develop an Android application on the FreeBSD platform? It may not be the entry pass to all of Willy Wonka's own private theme park, but perhaps it may be worth a sincere synopsis at least.<br />
<br />
<br />
[Article Draft Nr. 1]<br />
<br />
Outline for Article Drafts Nr 2+ : Resources<br />
<ul>
<li>Library (Literal)</li>
<ul>
<li>Safari Books Online [<a href="http://safaribooksonline.com/">www</a>] (fee-based service)</li>
<li>Google </li>
</ul>
<li>Baseline Support</li>
<ul>
<li>Java [<a href="https://www.freebsd.org/java/">info</a>]</li>
<li>Linux Emulation [info] </li>
<li>USB [<a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/usb.html">info</a>]</li>
<li>If YouTrack: </li>
<ul>
<li>HTTP Server - Apache HTTPD, Nginx, or other</li>
<li>Java Servlet Engine - Tomcat, Jetty, or other</li>
<ul>
<li>See also: <a href="https://wiki.freebsd.org/AppserverJailsHOWTO">Appserver Jails Howto</a></li>
</ul>
</ul>
</ul>
<li>Android Developer Tools</li>
<ul>
<li>ADB [<a href="http://www.freshports.org/devel/android-tools-adb/">port</a>]</li>
<li>Fastboot [<a href="http://www.androidcentral.com/android-z-what-fastboot">info</a>] [<a href="http://www.freshports.org/devel/android-tools-fastboot/">port</a>]</li>
<li>Simpleperf [<a href="http://www.freshports.org/devel/android-tools-simpleperf/">port</a>]</li>
<li>Android SDK [<a href="https://android-review.googlesource.com/#/c/100271/">patch</a>]</li>
<ul>
<li>Bundled with Android Studio</li>
<li>Available separately for ADT and other toolchain applications</li>
</ul>
<li>Android NDK [?]</li>
<ul>
<li>May not be needed for all Android development projects</li>
<li>Linux emulation (?) </li>
</ul>
<li>Vendor-Specific Developer Support - Android Developers</li>
<ul>
<li><a href="http://developer.samsung.com/home.do">via Samsung</a></li>
<li><a href="http://developer.lge.com/main/Intro.dev">via LG</a></li>
<li><a href="http://www.htcdev.com/">via HTC</a></li>
<li>... </li>
</ul>
</ul>
<li>Documentation Tools </li>
<ul>
<li>Emacs</li>
<li>DITA Open Toolkit</li>
<li>DocBook </li>
</ul>
<li>IDE Integration for Android Development</li>
<ul>
<li>Android Studio</li>
<ul>
<li>See also: Android SDK </li>
</ul>
<li>Android Developer Tools (ADT) and Eclipse IDE</li>
<ul>
<li>See also: Android SDK </li>
</ul>
<li>Emacs (??????) </li>
</ul>
<li>Android Emulators</li>
<ul>
<li>QEMU [<a href="https://wiki.freebsd.org/qemu">info</a>] [<a href="https://wiki.freebsd.org/QemuUserModeHowTo">more info</a>]</li>
<ul>
<li>See also: virt-manager [<a href="http://www.slideshare.net/CraigRodrigues1/libvirt-bhyve">info</a>] [<a href="http://www.freshports.org/deskutils/virt-manager/">port</a>]</li>
</ul>
<li>... </li>
</ul>
<li>Build Automation </li>
<ul>
<li>Gradle [<a href="http://www.freshports.org/devel/gradle/">port</a>]</li>
<li>Ant [<a href="http://www.freshports.org/devel/apache-ant/">port</a>]</li>
</ul>
<li>Network DevOps</li>
<ul>
<li>Code Signing and Distribution </li>
<li>Continuous Integration</li>
<ul>
<li>Jenkins</li>
<li>Travis CI</li>
<li>... </li>
</ul>
<li>Change Management</li>
<ul>
<li>Git</li>
<li>SVN</li>
</ul>
</ul>
<ul>
<li>Issue Tracking</li>
<ul>
<li>Trac [<a href="http://www.freshports.org/www/trac/">port</a>]</li>
<li>Request Tracker [<a href="http://requesttracker.wikia.com/wiki/FreeBSDInstallGuide">info</a>] [<a href="http://www.freshports.org/www/rt38">port - expired</a>]</li>
<li>YouTrack [<a href="https://www.jetbrains.com/youtrack/">info</a>] [<a href="https://gist.github.com/drfill/7228217">rc.d script</a>]</li>
</ul>
</ul>
</ul>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-42934030459744182822015-09-28T11:52:00.001-07:002015-09-28T11:52:24.449-07:00Calculating with CORBA – A Showy Prognostication Of Rational Numbers, Computations, and Communications in Application Systems<p dir="ltr">Reading over <a href="http://dsp42.blogspot.com/2014/10/a-synopsis-at-length-onto-decimal.html">an embarrasingly obtuse description</a> that I had written, one day in another place, about a software system that I was referring to as <a href="https://github.com/MetaCommunity/igneous-math">igneous-math</a>, I would like to denote henceforward that the article was much of an effort to describe a simple sense of novelty about the 'ratio' type as implemented in Common Lisp. Without immediately producing a study of IEEE standards for representing <i>floating point decimal </i>values in computing systems, and without any lengthy sidebar as to comment to a concept of <i>fixed point</i> arithmetic as developed in Forth, I recall that my initial thesis had centered on the very limits of finite <i>data registers</i> in computational machines. </p>
<p dir="ltr">In the following article, the author will endeavor again to circumnavigate any specific consideration with regards to computing, instead to focus about some concepts of commumications as developed with regards to CORBA.</p>
<p dir="ltr">Assuming a fixed-size data register, in any single numeric computation – whether of a 24 bit, 32 bit, 64 bit, or other bit length of numeric encoding – any <i>number</i> may be represented in a <i>precision</i> bounded by the size of the <i>data register</i> in which the <i>number</i> is <i>encoded</i>.</p>
<p dir="ltr">This article will not go at length to juxtapose different methods of discrete digital encoding of numeric values, as whether for encoding of natural numbers, signed integers, unsigned integers, fixed point decimal numeric values, floating point decimal values, numeric ratios, or complex numbers. Excepting the field of <i>ratios</i> and the field of <i>complex numbers</i>, each other of those topics may be referenced immediately onto the Common Data Representation (CDR) format as standardized in specifications about the Common Object Request Broker Architecture (CORBA). Though that may not serve as to describe such topics in any manner of a comprehensive detail, but as to reference these topics onto CDR encoding, perhaps it may at least serve as to provide a common point of reference – in regards to numeric computing – principally orthogonal to an implementation of any single programming language or programming architecture. </p>
<p dir="ltr">The CORBA specifications, as publicly described in core specifications documents and as extended in any number of supplemental specifications documents published by the Object Management Group (OMG), moreover as pragmatically <i>augmented</i> with domain-specific case studies described in any discrete number of documents in or outside of the OMG specifications set, moreover as implemented in any number of instances of <i>development tools</i>, then as applied in any singular set of software products – broadly, CORBA provides a platform-agnostc framework for applications, such as may be developed to extend of any number of fundamental CORBA object services – as in regards to developing software components such that may interact via CORBA object services, at an applications layer and – as on a TCP/IP network – may employ methodologies of <i>transport semantics</i> at <i>session</i> (cf. SECIOP) and <i>presentation</i> (cf. ZIOP) layers, as in regards to a view of networked applications projected onto a conventional seven layer model of TCP/IP networking. </p>
<p dir="ltr">In such a context, CORBA serves to provide a single, standardized, <i>baseline</i> object service architecture, such as may be augmented in applications of supplemental CORBA object service specifications. </p>
<p dir="ltr">In regards to applications utilizing CORBA IIOP – IIOP being the Internet Inter-ORB Protocol, principally an extension of the Generalized Inter-ORB Protocol (GIOP) –  applications may apply the Common Data Representation (CDR) format for <i>stream encoding</i> of data values, such as may be reversibly <i>encoded</i> and subsequently <i>decoded</i> onto <i>protocol</i> <i>request</i> sockets and <i>protocol response</i> sockets in a context of CORBA IIOP.</p>
<p dir="ltr">Short of an orthogonal concern with regards to encoding of <i>object references</i>, the CDR encoding format provides for an encoding of atomic, primitive numeric values – an encoding standardized essentially onto stream objects, principally in a manner independent of any single microcontroller implementation, but however dependent on a streams-oriented communications media. Though perhaps the CORBA architecture may serve to encapsulate much of the nature of the <i>stream based</i> encoding of data values in IIOP, but inasmuch as that an IIOP application utilizes TCP sockets for its implementation, the IIOP implementation therefore utilizes a stream based encoding. Whether GIOP may be extended, alternately, as to develop any more <i>computationally limited</i> encoding – such as perhaps to develop an encoding for protocol data values onto an I²C bus, as may be for application within a light-duty parallel computing framework, or alternately, as to develop an encoding method for GIOP onto shared memory segments within a process model of any single operating system – the CDR encoding onto IIOP serves to provide a standard encoding for atomic data values, moreover CDR providing a basis for encoding of object references and any number of application-specific data values, in CORBA applications.</p>
<p dir="ltr">Thus, as towards developing a platform-agnostic view of applications of computing machines, it may be fortuitious to make reference to the CORBA architecture – even in so limited a regards as in reference to the CDR encoding for primitive numeric values. </p>
<p dir="ltr">Concerning the CDR encoding for any single data value onto a communication stream, the CDR encoding may be observed as being compatible with so many machine-specific encoding methods for encoding of data values onto finite memory registers, data values as may likewise transmitted across finite processor bus channels within any single computing machine. Certainly, the communications of a data value – as within a CORBA application framework – would not cease at the transmittal of the data value to or from an IIOP application socket. </p>
<p dir="ltr">Towards a perspective of an implementation of CORBA, the CORBA implementation's own concerns – with regards to communication services – might not extend much further than as to provide an interface for <i>encoding</i> and <i>decoding</i> of data values onto CORBA data channels, in a manner however orchestrated with CORBA object adapters. The <i>trope</i> as that CORBA is for application in regards to <i>middleware</i> services – aside to any suggestion, to which the author may take some exception, as if CORBA was <i>not</i> <i>trendy, any more</i> – it does not serve to say much, at all, as to how a computing machine may apply any single data value, once a data value is transmitted over a CORBA object services network. Naturally, CORBA is a feature of a communications domain. In a manner of a domain-oriented view, CORBA dovetails with a domain of computer operating systems and a domain of microcontroller design, furthermore – as inasmuch as that a microcontroller provides computing services to an operating system, and as that an operating system may be applied as to provide computing services to a CORBA application.</p>
<p dir="ltr">How, then, is UNIX not relevant to CORBA applications? </p>
<p dir="ltr">The author of this article being how immediately preoccupied of developing a thesis with regards to the Common Lisp programming language, the FreeBSD operating system, and the potential for applications of CORBA in networked computing,  but perhaps it may seem as though the author is simply distracted of some few archaic trends in the social universe. The author would not propose to suggest any too narrowly deterministic model of such a thesis, whether or not is may be easily proved to be of a computationally sound and comprehensive architecture for computing in any arbitrary networked systems environment. Common Lisp has perhaps not been a great favorite for applications programming, however it may momentarily serves an academic end, as in a manner of thesis development. It might be estimated, moreover, that most theses developed about Common Lisp would be developed, likewise, as theses about concepts of <i>artificial intelligence</i> – logically, with regards to theses describing of applications of logic in mathematics and in computing systems. Perhaps it has not been since the 1970s and 1980s that Common Lisp development was shaped of microprocessor development. Across the popular <i>AI Winter</i> of the era, but perhaps the <i>old scrolls</i> have not all been lost to the shifting ice of the populist glacier.</p>
<p dir="ltr">As though lost in the library of historic record – but AI Memo 514 is certainly no manner of a <i>Cardiff giant</i>. If it may be a memo of an academia in which the plain logic of microprocessor design was paramount – but perhaps the contemporary computing market may seem all preoccupied of so many novel products of contemporary microprocessor manufacture, if not of applications of the newest high-speed microcontrollers and software designs in all the novel, new commercial systems. In regards to how so many novel, new toys are applied to present any manner of noise to contemporary engineering trades, but if it may be simply a manifestation of a lot of marketing fluff atop a lot of repetitive iterations in social development, how novel is a simple endeavor to disembark of the sollubrious consumerism and recover whatever remains of the sciences aside the grand industrial merry-go-round? </p>
<p dir="ltr">It might seem as if it was only a metaphor of a brass ring, a token, a trinket grabbed in a singular merry-go-round's long spin? Is it to a metaphor of a trophy, then, ere it is returned to the vendor's brass ring dispensor? If there is not a metaphysics of such a commercial mechanics, perhaps Whitehead's thesis really ever was disproved? May the circus resume, fortwith, if there is no more of a meaning beyond so many singular objects of materialism.</p>
<p dir="ltr">Before returning to this thesis, the author denotes a concept of <i>pi</i> in which <i>pi</i> is calculated as a <i>ratio.</i> </p>
<p dir="ltr">Though perhaps not all definitions of <i>number</i> would include <i>ratio</i> as a <i>type of number</i>, but as for that a <i>ratio</i> may be defined as a type of <i>rational number</i>, it may be a <i>type of number</i> of some relevance for application in computations onto other types of <i>rational number</i>. Sure, then, between concerns of <i>computation</i> and of <i>measurement</i>, some variance in <i>measurment</i> may entail some of a variance in <i>computation</i>. In regards to variance of physical measurements in physical systems, and considering as that a discrete measurement – a <i>measurement</i> of any estimable <i>precision</i> – may be applied in a computational model, applied as towards calculating any <i>intermediate numeric values</i> as may be, lastly, applied in a physical analysis or physical design of a system, and though it may seem practically naive to assume a <i>perfect measurement</i> may be provided to any computational system, but insomuch as that a computational system may produce a predictable set of consequent computations, as given a known set of initial measurements and a discrete formula for calculations, a computational system should not itself be assumed to operate at variance of any set of initial measurment values.</p>
<p dir="ltr">If there may seem to be a commercial novelty of the Common Lisp functions, 'rational' and 'rationalize', those two functions alone may be applird as a computational entry point – of each, seperately so – to perform all intermediate calculations within a computing machine as in calculations with rational numbers. There may be, in that, likewise a <i>toss of the hat </i>with regards to fixed-point numeric calculations in Forth. Perhaps it may be said as to "Go further," moreover, that any immediately fixed-point numeric value may be converted to a ratio numeric value, as to conduct any subsequent calculations wholly onto rational numbers, whether or not producing a decimal number for numeric denotation as a consequent value.</p>
<p dir="ltr">It is not unprecedented: That a computing machine may usefully produce calculations deriving of rational numbers. In an immediate manner, a computer of a finite memory may not actually contain an irrational number, except that an irrational number is encoded of rational quantities. A concept of <i>irrational number</i> should not be removed from numbee theory, of course! It is <i>simply not</i> a concept occurring in computations within finine memory spaces.</p>
<p dir="ltr">It is not to merely make a drab show, therefore, if a rational number may be calculated as <i>estimating</i> a built-in <i>decimal</i> value of <i>pi</i> to a rational numeric constant. Such a constant, rational value may be applied intermediate computations wholly onto rational numbers. The rational numbers computer may only need convert any decimal input values into a ratio format, then to produce a decimal representation – to any single consequent precision – of any numbers calculated finally of the rational computation.</p>
<p dir="ltr">Of course, this does not indicate any trivial methodology for rational numeric computations onto transcendental functions. So far as that the triginometric transcendental functions may be derived of a rational estimate of pi, as on a <i>unit circle</i>, there may be a channel for computations with rational numbers in those transndental functions. The author, regrettably, is not as immediately familiar with calculations of Euler's constant.</p>
<p dir="ltr">Towards a representation of <i>ratio</i> numeric values and <i>complex</i> numeric values – no mere <i>propaganda,</i> the Common Lisp type system providing definitions of such numeric types, in computing – of course, it may be a trivial affair, to define an IDL module, an IDL interface, and finally an IDL data type in which a platform-agnostic definition of each of the <i>ratio</i> or of <i>complex number</i> numeric types may be provided, in a computing system. That being denoted as towards a consideration of a <i>transport level encoding</i> of numeric values, but it may not seem to say an immediate bunch as towards an algorithmic, if not functional view of computing</p>
<p dir="ltr">This article, presently, returns to a thesis about CORBA.</p>
<p dir="ltr">Of course, CORBA IDL itself is not the <i>computing</i> element of a <i>CORBA system</i>. Inasmuch as that an implementation of a CORBA IDL <i>module</i> may be developed in an application programming language, then applied within an <i>object adapters</i> system, CORBA IDL may serve something of a complete, modular role in regards to communications among computing systems. This article has denoted, albeit somewhat obliquely, the CDR encoding for data values in an IIOP framework. Likewise, as in regards to the subclauses of the CORBA core specifications as in which CDR and IIOP are described, it may be said to amount to a much of a description of a <i>platform-agnostic communications model</i>, such as is defined in a manner for application within a broader, platform-agnostic object services framework as may be denoted, broadly: CORBA.</p>
<p dir="ltr">May it be, then, as if to limit the potential applications of CORBA frameworks, if the computational features of CORBA systems may not often be found as described in so much of specific detail as of the CORBA communications model itself? One may wish to speculate as to how the platform-agnostic nature of CORBA specifications may seem to effectively obfuscate any single CORBA implementations from immediate duplication without limits of immediate licensing agreements. In some regards, such a coincidence could be quite fortuitous, overall. Inasmuch as CORBA may find an application in defense systems, such applications should probably not be danced out for any idle opportunism, however any CORBA applications may be momentarily denoted of a popular discourse. However analogously, if CORBA may be estimated as to find applications in some of social infrastructure systems – such that may seem however estimably <i>possible,</i> as in consideration of specifications defining platform-agnostic applications of CORBA in telecommunications systems – but this says almost nothing with regards to any manner of actual computing systems. Not to offend the reader with the author's own simple obtuseness: A <i>communications specification</i> is not a <i>microprocessor,</i> just as much as a pie plate is not a peach pie.</p>
<p dir="ltr">Sure, a discrete number of peaches may be applied in preparing any discrete number of peach pies, at any estimable formula of efficiency and other results. Analogously, the CORBA specifications are not either like recipes for microcontroller applications. (<b><i>Ed. note: </i></b>There should be a cute metaphor to Hexbugs(R), here. Though it might seem to startle a reader, if juxtaposed to the fantastic, fictional <i>Replicators</i> of the Stagate SG-1 universe, in science fiction literature, but the metaphor of a microchip-sized automoton of a bounding character, outside of any too far Arachnid-like species of science fiction creature, the simple ant-like Hexbug Nano(R), as a metaphor, could be apropos.)</p>
<p dir="ltr">So, a student of computing might feel in some ways stymied of the communications-oriented CORBA specifications. The proverbial magic of CORBA may not be insomuch in the proverbial network chatter of a CORBA object system.</p>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-8352610123625806212015-09-27T20:48:00.002-07:002015-09-28T07:21:45.163-07:00Thoughts - Nomenclature and TaxonomyAs a topic that I've found some concern about: Even in so much as
developing my own set of notes at Evernote -- and marking such notes in
any ways meaningfully, with labeled tags -- I've begun to develop a sort
of an <i>ad hoc</i> taxonomy about a number of concepts in computing.<br />
<br />
Though I've not lately been refreshing my own study of the bibliography
of taxonomy, it's a topic that I'm aware of as it existing, with
potential applications in a number of theoretical contexts, including: <i>Topic Maps</i>,
as in reference to the XTM topic maps format and Ontopia; the Simple
Knowledge Organization System (SKOS), as in reference to RDF, RDF
Schema, and the Web Ontology Language (OWL); the Darwin Information
Typing Architecture (DITA) as in reference to types of DITA <i>topic</i> elements. In an applications sense, I've observed that a concept of <i>taxonomy</i>
may be relevant in regards to web services for content curation, web
content annotation, and web content development, as in reference to both
of Evernote and Diigo. <br />
<br />
Both of Evernote and Diigo
allow for annotation of web content. Evernote might seem to provide
something more of a container view of web content, juxtaposed to Diigo.
Diigo might seem to be more readily usable, at desktop PCs, for web
content annotation. Evernote and Diigo both provide services towards content development – Diigo, with Diigo outliners, and Evernote with Evernote articles. <br />
<br />
Focusing on the "Content tagging" features of each of Evernote and Diigo -- with a momentary reference to the original <i>Annotea </i>project
of the World Wide Web Consortium (W3C) -- Evernote allows for
hierarchical organization of content tags. This evening, I've noticed
one simple example in which that occurs to a particular highlight:
Annotating a concept of <i>instruction set architecture, </i>as of any
of a Complex Instruction Set Computing (CISC), Reduced Instruction Set
Computing (RISC) or other species of instruction set architecture
developed into a tangible microcontroller platform. Orthogonally,
there's a concept of <i>instruction set architecture</i> denoted in MARTE 1.1.<br />
<br />
To denote each of a concept of CISC and a concept of RISC as being subsumed by a concept of <i>instruction set architecture</i>,
it may not seem all of ideally like a perfect taxonomy, but I think it
suffices for my own personal notes, in my own Evernote notebooks. That there
are any number of instruction set architectures that may not be immediately denoted as either CISC or RISC architectures, there's a whole
history of computing that was developed before those terms became <i>en vogue</i>. Some of the literature of the earlier computing might seem particularly clear in developing concepts as with regards to logical microcontroller design, moreover.<br />
<br />
I think,
the classification of CISC and RISC concepts as being subsumed by a
concept of an <i>instruction set architecture</i>, it provides both of a
semantically meaningful construction and a flexible construct allowing
for later description of instruction set architectures, such as may not be
immediately identified as either CISC or RISC architectures -- however anyone may
endeavor to define exact limits to a definition of either of those
concepts, as implemented in any single, tangible microprocessor.<br />
<br />
Of
course, a concept of RISC and of CISC may likewise be subsumed of a
concept of microprocessor architecture -- as by way of a concept of
instruction set architecture.<br />
<br />
This article -- which I had wanted to write, originally, about taxonomy -- it is, by now, also an article about concepts of <i>instruction set architecture</i>.
The reader might notice that this article, moreover, is absent of any
cross references to a Wiki. That's not to snub the WIki editor
community, simply the reader may Google any number of these concepts.
Personally, I think that my own study is better served with my own
application of Evernote, Diigo, and towards a DITA model for content
development, not to lead too much into any singular Wiki narrative. <br />
<br />
This
web log I keep, I think this is just a forum to be a little more chatty
about some concepts, essentially outside of any specific social
channels, online. I've been trolled, here, exactly once -- therefore,
would expect anything similar again. Though I've yet to be trolled here
any more than once, I now understand I must understand that I may be
trolled, here, at any time. So, I'm naturally going to be a little more
edgy-terse in writing at this, my tech web log -- might learn to be more
cheerfully natured about the overall "Troll potential" of this
supposedly anonymous Internet, though in no immediate sense of warmth
for trolling. It sure makes it difficult to write about any cheerful
concepts, here. I've a sense, that's by no means "Only Online," either.
However momentarily flexible the Internet media might seem, of course,
any single page with a comment section might become an instant forum for
mud-slinging. <br />
<br />
Why is anyone so <i>ad hominem</i>
online? I honestly cannot imagine. I'm not one to escalate or deter
anyone's own fantastic ideas, as such, either. Does that make me an easy
target, online, or just a subtle observer of semantics, though? So
sure, maybe sometimes I draw fire from an Internet troll. Big loss, huh?<br />
<br />
<br />
Further
than defining a correlation between a concept of CISC architectures,
and a concept of RISC architectures, with both concepts being subsumed
of a concept of Instruction Set Architectures -- and this, being
represented simply in a set of Evernote 'tags' -- that concept then
being subsumed of a concept of Microprocessor Architecture, I notice
that all of these concepts may seem to fit well in an overall taxonomy
of nomenclature about computing. My being a student not so much of the
nomenclature as much as of concepts denoted of the nomenclature, in
computing, I wouldn't want to be tedious about nomenclature. I think,
it's an idea towards keeping so much as my own webliography well
organized -- not to say of any broader sense of bibliography, and how to
integrate a bibliography system, and Evernote, and Diigo.<br />
<br />
Of
course, in thinking furthermore of developing a topic repository model
onto DITA, I'm not thinking anything "Like FOLDOC", as FOLDOC is far too
friendly a media for such a serious demeanor as I think I must have to
keep, in most of communications immediately in the modern world online.
Sometimes, I can't help but have an impression that some lot of the
readership might be just waiting to reach out and take a swipe at
something -- judging only by previous experiences, no more wishful
thinking from me for how people apparently are, online.<br />
<br />
FOLDOC
publishes a number of reference pages, itself, mostly in a colloquial
reference. It's a manner of a topic-oriented reference base, about
computing, alternate to Wikipedia.<br />
<br />
So, there's already
FOLDOC, no rush to develop any excess of an additional topic repository
about contemporary concepts in computing -- any repository about
information science, the physical sciences, mathematics, logic, and
marketing, and anything else that may be defined about computing, including: Concepts of human-computer or human-machine interface design (HCI or HMI, respectively), HCI/HMI accessibility, or plain novelty.<br />
<br />
<a href="http://foldoc.org/">FOLDOC </a>exists, great thing.Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-61236363673289934562015-09-27T07:40:00.001-07:002015-09-27T16:58:07.508-07:00Concerning Android App Identities as Represented in the Android OS<div dir="ltr">
One of the challenges facing the development of an integrated bibliography system on the Android platform, simply, arrives of the Android OS' app UID/GID model, moreover Android's application of the Linux filesystems permission model – in any ways augmented, as some documentation may denote, augmented with a mandatory access control (MAC) application extending of SE Linux, in light of the albeit not formally adopted POSIX 1003.1e i.e "POSIX 1e" draft, in Android KitKat and other Android release branches. POSIX 1e finds application in Linux, furthermore, with the Linux process capabilities implementation. Analogously, in the FreeBSD operating system, POSIX 1e find application in the FreeBSD MAC implementation and in the Capsicum implementation.<br />
<br /></div>
<div dir="ltr">
Not as if to abjectly criticize the Google Android project – the app/filesystem permissions model in KitKat being of some notable inconvenience for file storage to SD card media, in Android platforms – there is probably a logic to the changes made with regards to these features, in Android 4 i.e "Kit Kat" and other Android release branches. (<i><b>Ed note:</b></i> cf. Android <i>Content Providers</i> [AndrDeveloperST]) Whatever ways in which the MAC model may be involved in the issue, it may seem to center primarily about app UID specification – the issue of the inonvenience for platform users, as with regards to files that must be accessed with multiple Android apps on a single Android appliance – whether or not specifically to access files stored on external SD card media, logically an orthogonal concern, orthogonal to the permissions model of a Google certified Android appliance's own on-device storage meda, there with further orthogonal reference to filesystem types (bibliography on file).<br />
<br /></div>
<div dir="ltr">
On the Android platform, app UID and GID is computed at time of app installation[AndrDeveloper]. App UID and GID information on the Android platform is not stored in the common <i>text</i> and <i>shadow</i> files under the /etc directory – common insomuch as with regards to UNIX platforms applying a POSIX and X/Open model. Rather, in one regards, UID and GID information is stored – on the Android platform – as with reference to an 'acct/uid' directory[BD2015]. (<i><b>Ed. note: </b></i>See also, the GET_ACCOUNTS <i>manifest permission</i> [AndrAPI_Mperm])<br />
<br />
<br /></div>
<div dir="ltr">
From a developer's perspective, there are application settings available for <i>sharing</i> an app's identity with an <i>existing app</i>, inasmuch as with regards to the <i>sharedUserID</i> attribute [AndrDeveloperPerms] of a single app's APK <i>manifest</i> description. The corresponding s<i>haredUserLabel</i> APK manifest field, moreover, allows for human-readable labeling of apps' shared user ID[AndrAPI_R], Albeit, the <i>sharedUserLabel</i> may be applied to an ambiguous situation – as with regards to that a <i>sharedUserLabel</i> may be specified in <i>one</i> app's APK <i>manifest</i>, but would be applied for a UID <i>shared among multiple apps</i>. This article will not further investigate how the Android OS may establish a systematic precedence to <i>shared user labels</i>, as in a conflict of differring <i>sharedUserLabel</i> specifications for a single <i>sharedUserID</i>.<br />
<br /></div>
<div dir="ltr">
In addition to the <i>sharedUserID</i> APK <i>manifest attribute</i>, the Android API defines a <i>permissionGroup</i> object type [AndrAPI_R], corresonding to a <i>'permission-group'</i> tag as may be specified in an Android APK <i>manifest</i> file[AndrAPI_RStyleable]<br />
<br /></div>
<div dir="ltr">
Referring to the reference documentation about these multiply-linked OS features, in Android, it seems there is an <i>Account Service</i> in the Android OS, specifically referencing the GET_ACCOUNTS <i>manifest permission</i> [AndrAPI_Mperm] – perhaps an <i>elusive</i> feature of the Android Operating System, the Android OS <i>Account Service</i>.<br />
<br /></div>
<div dir="ltr">
There is inquiry of a topic as with regards to storage of user account information on the Android platform. [OvOp2015] Probably, the Android OS <i>Account Service</i> may be a topic of a commonly linked reference, as with regards to APK <i>principal</i> peer identity, and UID and GID values computed at time of APK <i>install</i>. </div>
<div dir="ltr">
(<i><b>Ed. Note: </b>Or not. </i>On further study, it seems that the Android <i>Account Service</i> is rather a service for managing a user's <i>web account</i> information, centrally, on any single Android appliance.)<br /><br />Perhaps this study may be extended of, as with regards to applying Kerberos as a neteork peer authentication service on Android appliances. There is some of an existing work, with regards to implementing Kerberos services on the Android platform (bibliography on file), though perhaps nothing immediately about whether or not a network admin <i>should</i> allow authentication to a network service, e.g SSH, with a Kerberos ticket from a thin client appliance – an orthogonal topic, certainly. For web apps, of course there's OAuth/OAuth2.<br />
<br />
[Article Draft Nr. 2]<br />
<br /></div>
<div dir="ltr">
<i><b><u>Webliography</u></b></i></div>
<div dir="ltr">
<br />
[Anderson2013] <a href="http://www.all-things-android.com/content/deeper-look-android-application-permissions">http://www.all-things-android.com/content/deeper-look-android-application-permissions</a><br />
[BD2015] <a href="http://boundarydevices.com/android-security-part-1-application-signatures-permissions/">http://boundarydevices.com/android-security-part-1-application-signatures-permissions/</a><br />
[AndrDeveloperPerms] <a href="http://developer.android.com/guide/topics/security/permissions.html">http://developer.android.com/guide/topics/security/permissions.html</a><br />
[AndrAPI_R] <a href="http://developer.android.com/reference/android/R.attr.html">http://developer.android.com/reference/android/R.attr.html</a><br />
[AndrAPI_RStyleable] <a href="http://developer.android.com/reference/android/R.styleable.html#AndroidManifestPermissionGroup">http://developer.android.com/reference/android/R.styleable.html#AndroidManifestPermissionGroup</a><br />
[AndrDeveloperST] <a href="http://developer.android.com/training/articles/security-tips.html">http://developer.android.com/training/articles/security-tips.html</a><br />
[AndrAPI_Mperm] <a href="http://developer.android.com/reference/android/Manifest.permission.html">http://developer.android.com/reference/android/Manifest.permission.html</a><br />
[OvOp2015] <a href="http://android.stackexchange.com/questions/74969/where-is-user-group-id-info-stored-on-android-and-how-do-i-inerpret-it">http://android.stackexchange.com/questions/74969/where-is-user-group-id-info-stored-on-android-and-how-do-i-inerpret-it</a></div>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-59214106787896340502015-09-24T20:21:00.001-07:002015-09-24T20:21:53.331-07:00Lua - A CommentThough I've been considering to begin taking a closer look at EFL WebKit potentially for application with Common Lisp, but presently I've become somewhat distracted of the network configuration on my small LAN. Towards considering a scripting language -- alternate to SH -- for automating a time-based iterative function on the LAN gateway, I've not considered Common Lisp as an option for this application. Though I think Common Lisp has a lot to offer to systems programming, but I think it may be a little much to apply a complete Common Lisp implementation for simply automating such a function on the LAN gateway. <br />
<br />
Considering scripting languages, I'm young enough in years to remember when PERL was first becoming a popular scripting language. I remember, likewise, my own difficulty with making sense of the affability with which PERL's baroque syntax was presented, in popular discourse. Presently, I don't believe a person should ever have to indulge in any manner of intellectual gymnastics, if to understand the syntax and semantics of an interpreted programming language. I don't have any great sense of appreciation about the <i>eclectic</i> nature of PERL. Candidly, I think it's more a novelty than a necessity. I don't find it to be a particularly helpful novelty, either.<br />
<br />
So, I'm also going to take a break from so much as considering to develop any applications of Common Lisp. I'm sure Common Lisp is great for making adventures about computer science.<br />
<br />
I've glanced at the Ruby language. I've heard that Ruby is applied in Puppet Labs' <i>Puppet</i> tools. Not to rain on anyone's fair, as far as scripting languages, I'm thinking to favor Lua instead.<br />
<br />
Lua is a programming language with a few applications that I know of. The first one I've thought of, of late, has been the application of Lua in the block-oriented builder game universe of the Minetest platform. Then again, there's also the Texas Instruments N-Spire graphing calculators, which feature a Lua interpreter. Even in this era of the <i>Phablet</i> computer, I think that the N-Spire calculators are some really profound calculators. I'm impressed with their possible applications in laboratory science and in mathematics. <br />
<br />
This evening, I've also found a couple of implementations of Lua onto CORBA, and a note about a Lua scripting extension for Nginx. The latter could be of use as towards developing a manner of a "Web Social" presentation model onto Minetest, but that's in looking ahead.<br />
<br />
Searching the FreeBSD baseline packages repository, I see that there are a number of FreeBSD ports available for programming with Lua. Towards adopting Lua in integrated development environments, there's also an <i><a href="http://immerrr.github.io/lua-mode/">Lua-mode</a></i> for Emacs, and -- in the Eclipse IDE -- there's also the <i><a href="http://www.eclipse.org/ldt/">Lua Development Tools</a></i> platform, previously <a href="http://www.eclipse.org/koneki/ldt/"><i>Koneki</i></a>.<br />
<br />
There are a number of books about programming with Lua, at <a href="https://www.safaribooksonline.com/">Safari Books Online</a>. Reader's interests may vary.<br />
<br />
There are also Lua interpreters available on the Android platform.<br />
<br />
So, it should be to a great lot of fun. Why, then, am I writing a web log article instead of writing my first lines of Lua code? Is it that I am bewildered that Common Lisp, for all its Turing Completeness, still does not re-emerge any further from its <i>AI Winter</i> in Comp. Sci academia and into the commercial market? Am I perhaps a bit disconcerted by the character of same Comp Sci academia, itself, in some that I have seen of the same, and way too personally so?<br />
<br />
I think both of those are why I would like to write a while longer, before studying much more in detail about Lua -- but of such a rough time veritably on the dark side of the moon, what is there to every write usefully of it?<br />
<br />
Not a lot.Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-45320135429102663022015-09-23T14:19:00.002-07:002015-09-24T02:54:08.843-07:00Cloning WebKit in a Few Easy Steps<div>
The Git changeset repository developed by the WebKit project is not a small Git chanegset repository. In order to <b><i>Git clone</i></b> the WebKit Git repository for software development, an <i>incremental</i> <b><i>Git fetch</i></b> may be useful. </div>
<div>
<br /></div>
<div>
An intermediary <i><b>Git gc</b> </i>call may serve to optimize the Git repository clone, before the final <span style="font-family: "Courier New",Courier,monospace;">'unshallow'</span> <b><i>Git fetch</i></b> procedure.</div>
<div>
<br /></div>
<b><u><i>Example</i></u>:</b> Incremental Git clone/fetch - WebKit Git repository.<br />
<blockquote>
<pre>#!/bin/sh
WHENCE="git://git.webkit.org/WebKit.git"
WHERE="webkit"
<b>git clone</b> --depth=1 "$WHENCE" "${WHERE}"
cd $WHERE
for LIM in 100 1000 5000 10000 20000 40000 60000; do
<b>git fetch</b> --depth="$LIM"
done
<b>git gc</b> --aggressive --prune=all
exec <b>git fetch</b> --unshallow</pre>
</blockquote>
<br />
<u><b><span style="font-size: large;">Configuring Git index-pack</span></b></u><br />
<br />
The following configuration may not be ideally optimal. The following configuration settings may serve to alleviate some conditions that may otherwise cause Git index-pack to<i> fail</i> when repacking the data of WebKit source code repository.<br />
<blockquote>
<pre><b>git config</b> --global pack.deltaCacheSize 512m
<b>git config</b> --global pack.deltaCacheLimit 5000
<b>git config</b> --global pack.windowMemory 100m
<b>git config</b> --global pack.packSizeLimit 100m</pre>
</blockquote>
<br />
<b><u><span style="font-size: large;">Post-Checkout Configuration</span></u></b><br />
<br />
The WebKit Git repository is constructed effectively as a Git proxy onto the WebKit SVN repository. In order to draw changes directly from the WebKit SVN repository, the WebKit project has provided a utility shell command [<a href="https://trac.webkit.org/wiki/UsingGitWithWebKit">cross reference</a>]<br />
<blockquote>
<pre>cd ${WHENCE}
Tools/Scripts/webkit-patch setup-git-clone</pre>
</blockquote>
<br />
For developing with the EFL WebKit integration, a shell command is available as an initial dependency management utility [<a href="http://trac.webkit.org/wiki/EFLWebKit">cross reference</a>]<br />
<blockquote>
<pre>${WHENCE}/Tools/efl/install-dependencies</pre>
</blockquote>
<br />
<span style="font-size: large;"><u><b>The "See Also" Section</b></u></span><br />
<br />
Developers may wish to refer to more detailed documentation about Git
<br />
<ul>
<li><a href="https://trac.webkit.org/wiki/UsingGitWithWebKit"><i>Tips and Tricks for using Git with WebKit</i></a>. WebKit Trac <a href="https://trac.webkit.org/wiki">Wiki</a> (2013)</li>
<li>Chacon, Scott and Ben Straub. <i></i><a href="https://git-scm.com/book/en/v2"><i>Pro Git</i></a>. second edition. Apress (2014)</li>
</ul>
<br />
For further documentation about developing with the EFL integration for WebKit<br />
<ul>
<li><i><a href="http://trac.webkit.org/wiki/EFLWebKit">EFL Port of WebKit</a></i>. WebKit Trac <a href="https://trac.webkit.org/wiki">Wiki</a> (2015)</li>
<li><i><a href="https://www.enlightenment.org/docs/efl/start">EFL</a></i> Documentation. <a href="https://www.enlightenment.org/start">Englightenment Main</a></li>
<li>Haitzler, Carsten. <a href="https://www.tizen.org/events/presentations/tizen-native-display-layer-efl-architecture-and-usage"><i>Tizen Native Display Layer - EFL, Architecture and Usage</i></a> (2012)</li>
<li><a href="http://ewebkit.github.io/ewebkit-doc/ewebkit2/html/index.html">Documentation </a>for EWebkit2 (version 1.11.0)</li>
</ul>
<br />
EFL is a core feature of the Tizen framework. Additional documentation may be available about applications of EFL, with reference to Tizen<br />
<ul>
<li><a href="https://developer.tizen.org/development/guides/native-application/graphics"><i>Graphics</i></a>. Tizen Developers</li>
<li><a href="https://developer.tizen.org/development/guides/native-application/graphics/cairo"><i>Cairo</i></a>. Tizen Developers</li>
<li><a href="https://developer.tizen.org/dev-guide/2.3.0/org.tizen.native.mobile.apireference/group__Elementary__GL__Helpers.html"><i>Elementary GL Helper functions</i></a>. Tizen Native API </li>
<li>Holwerda, Thom. <a href="http://www.osnews.com/story/22503/Samsung_Sponsors_Enlightenment_EFL_Development"><i>Samsung Sponsors Enlightenment, EFL Development</i></a> (2009) </li>
</ul>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-68066025640286164552015-09-23T01:01:00.001-07:002015-09-23T11:27:15.181-07:00Towards Developing a DITA Editing Platform on FreeBSD<div dir="ltr">
Having developed a certain sense of interest with regards to writing technical documentation, I've been studying periodically about the Darwin Information Typing Architecture (DITA). There are a number of things that I would like to highlight about DITA, as in a sense of a thesis document – I've tried to collect my notes, as such, with Evernote. Thus far, I have been unable to write any single thesis document about the topic, rather developing only a series of <i>itemized lists</i> of notes, and a small bibliography.</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Presently, I think it may be as well to begin writing some <i>narrative</i> text about DITA. Although I may not feel as able to write fluidly, in a digital media – as juxtaposed to a media of graphite and paper, with clipboard, to an older style of desktop writing appliance – but it is surely easier to share a work of writing produced in a legible digital font – here juxtaposed to my own <i>cursive</i> handwriting and <i>ad hoc</i> visual layout approaches, as when writing with pencil on paper. Sure, I have begun to sketch out an idea for a more fluid style of <i>sketching</i> in a digital media, but it would need some work in regards to <i>ergonomic</i> presentation and editing of vector graphics, and therefore may depend on software not yet developed for the Common Lisp Interface Manager (CLIM). Presently, I am more preoccupied of developing a workflow towards DITA editing with free/open source software (FOSS) tools. Though I have looked at both of the XXE XML editor and OxygenXML for a DITA workflow, I would like to start writing DITA with a platform more familiar to me. Personally, I'm comfortable with Emacs and pSGML.</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
In regards to any manner of perhaps <i>esoteric</i> features of DITA – such as, DITA linking, DITA content replacement, and any broadly <i>semantic</i> qualities of DITA's <i>topic</i> element classes – it might not seem that a baseline Emacs + pSGML environment could be completely sufficient, If applied primarily as a DITA editing enviromment. The Emacs + pSGML platform, of course, can be extended with Emacs Lisp. Although Emacs, in turn, may not seem like a very rigorous programming enviromment, as when juxtaposed to the Eclipse IDE or IntelliJ IDEA platforms – both of which are developed, primarily, in the Java(R) programming language – but I think there is a manner of an <i>incentive</i> in the simple convenience of the <i>interactive,</i> functional <i>command</i> interface of Emacs + pSGML. It may seem to be enough that I might not be excessively distraught about the absence of programmatic <i>rigour</i> in the Emacs Lisp programming language, juxtaposed to Oracle's Java(R).</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
So, but in that I would not wish to develop an manner of an <i>ivory tower</i> of this concept, and I will be writing with Emacs on a FreeBSD desktop, I think it needs a a sense of a project, in itself. I propose that a FreeBSD <i>port</i> can be developed of each of: The DITA 1.2 Document Type Definition (DTD) files, there integrating with the XML entity resolver's configuration on FreeBSD; the DITA Open Toolit, likewise to be integrated with the host's XML entity resolver, moreover to be applied with the user's own ASF <i>Ant</i> configuration. If anything analogous to the Comprehensive PERL Archive Network (CPAN) may be developed, moreover, as to provide a <i>software distribution service</i> for extensions to the DITA DTDs and DITA Open Toolkit (DITA OT) XML stylesheets, perhaps such a thing may be anyhow designed onto CORBA services, moreover the CORBA Component Model (CCM), if not Java(R) and OSGi services. Of course, from an end user's perspective, that might be secondary to the availability of a FreeBSD port for each of those two existing components, respectively the DITA DTDs and DITA OT.</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Fourthly, as towards a concept of applying DITA in an open documentation system, there is a simple concept of a <i>topic repository</i> model that may be developed, in a manner of writing DITA as like for a sort of an – albeit not primarily <i>web-based</i>, and insamuch not <i>web-editable</i> – <i>Wiki-like</i> format. Though it may seem to loose something of a popular incentive, for it not being a <i>web-editable</i> format, but inasmuch as that a DITA editing platform may serve to provide a manner of editing support not easily provided altogether with a web-based <i>interface environment</i>, then perhaps there may be<i> </i>an adequate<i> </i>"<i>up side"</i> to the <i>design decision</i>, as such.</div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
Immediately, I am somewhat distracted of the tedium of making a complete <i>Git clone</i> of the WebKit source code repository – perhaps this is referred to as <i>multi-tasking.</i> It seems that the initial <i>Git </i>fetch must be run incrementally, onto that same source code repository. It's presently at <span style="font-family: "Courier New",Courier,monospace;">`--depth=20000`</span>, in no small detail. I have referenced only a couple of forum topics [<a href="http://serverfault.com/questions/158052/git-pull-times-out">Matthews 2010</a>][<a href="http://stackoverflow.com/questions/4826639/repack-of-git-repository-fails">midtiby2011</a>], to try to resolve that a complete <span style="font-family: "Courier New",Courier,monospace;">`git clone`</span> onto that source code repository has consistently has failed. Proceeding to to a <span style="font-family: "Courier New",Courier,monospace;">`git fetch`</span> at <span style="font-family: "Courier New",Courier,monospace;">`--depth=60000`</span>, the Git incremental-clone procedure succeeds, so far. <br /><br /><b><i>Ed. Note:</i></b> There's also something to write about <span style="font-family: "Courier New",Courier,monospace;">`git gc`</span></div>
<div dir="ltr">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjmKg06MDEdyIXq7mShCDrgX8CCvRmlzrKmunoIcoL6rVDh0W3V0cX_S3je5_O3NDxoQlDuBuvTzSXbBcQ9iXKHEKRqCgiL_HNbE42HA3yt2y6XwT6thN-RI8lEnP6BRPvDDBsSLg6C4Ns/s1600/Screenshot_2015-09-23-01-30-36.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"> <img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjmKg06MDEdyIXq7mShCDrgX8CCvRmlzrKmunoIcoL6rVDh0W3V0cX_S3je5_O3NDxoQlDuBuvTzSXbBcQ9iXKHEKRqCgiL_HNbE42HA3yt2y6XwT6thN-RI8lEnP6BRPvDDBsSLg6C4Ns/s320/Screenshot_2015-09-23-01-30-36.jpg" width="320" /> </a> </div>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-64738460584680700092015-09-21T10:19:00.001-07:002015-09-23T11:33:30.187-07:00To Evernote like DITA<div dir="ltr">
I wish a DITA editing tool could be as convenient to write with as <i>Evernote.</i></div>
<div dir="ltr">
<br /></div>
<div dir="ltr">
<i>Meanwhile: </i><i>
<span><span><a href="http://www.evernote.com/l/Aeo7BVTJrjpOPoebxUO75rj5VQTL2BReVSA/">FELDSPAR Model Catalog – Towards a reference manual</a> (Σ)</span></span>
<br /><br /> </i></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhIoIURj5iXXlynTZFniYj4_sGvnc8m4vl9on35GpAvFnCgMiK5y4pSZ0fojd72mkXF_vUv0YrYJbyJVhFvG62TvtXLVKBd6LJl2Z-SK0nms259HQWGQIx7ORzLv0ERil0LuKXF2Nh3y6U/s1600/Screenshot_2015-09-21-10-24-05.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"> <img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhIoIURj5iXXlynTZFniYj4_sGvnc8m4vl9on35GpAvFnCgMiK5y4pSZ0fojd72mkXF_vUv0YrYJbyJVhFvG62TvtXLVKBd6LJl2Z-SK0nms259HQWGQIx7ORzLv0ERil0LuKXF2Nh3y6U/s640/Screenshot_2015-09-21-10-24-05.jpg" /> </a> </div>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-74483626328657962242015-09-20T21:21:00.000-07:002015-09-20T21:57:13.991-07:00Introducing GRANITENET and the FELDSPAR Platform Agnostic Object System.As the author of this article being someone who has developed a distinct sense of interest about the <i>logic</i> and the existing <i>body of work</i> in regards to concepts of <i>operating systems design</i> -- moreover, a sense of interest as with regards to the effects of specific <i>design choices</i> in <i>operating systems design</i>, as of <i>design choices</i> ultimately resulting in discrete effects with regards to <i>operating system applications</i>, in any single common <i>domain</i> of <i>computing</i>, including <i>software development</i>, and effects in regards to <i>application</i><i> system maintenance</i> -- the author of this article, though for some time familiar with the Debian GNU/Linux operating system, the author of this article has lately become more a fan of the FreeBSD operating system. It is this author's candid opinion that FreeBSD presents a markedly less cluttered development environment than the GNU environment of GNU/Linux systems. Not as though to meanly criticize either the Free Software Foundation (FSF) or its supporters, the author of this article is aware that operating system distributions such as Debian GNU/Linux are systems that have evolved, over time, initially from relatively small-scale origins. Considering a conceptual paradigm in which GNU tools are developed as to be modular, moreover portable with other GNU tools, moreover in which the Linux kernel itself and applications of the Linux kernel have been shaped with developments in operating system standardization -- broadly, under a heading of a colloquial definition of UNIX systems, more specifically as under the headings of international standards such as the versions of POSIX and specifications published by the Open Group and later X/Open company, moreover as with regards to standards published by the Internet Engineering Task Force (IETF) -- the author of this article is aware that it may entail no manner of a trivial work, to develop any single, working computer system out of so many individual software components and software systems standards. Perhaps there has been a certain degree of centrally managed organization, in the development of the FreeBSD operating system -- if not, moreover, a greater degree of flexibility as with regards to distinctions of the BSD licenses, juxtaposed to the GNU Public License (GPL) or derivatives of the GPL -- such that may result in an impression -- as to the author's opinion -- that FreeBSD is a really well organized, really uncluttered operating system, moreover very easy to apply in begining software and systems development. Certainly, such an impression is aided with the availability of so many centrally managed reference documents about FreeBSD, as in regards to the FreeBSD base system and the FreeBSD kernel.<br />
<br />
The author would not wish to abridge any introduction about FreeBSD. This article, presently, is developed not insomuch as to make an in depth study of the FreeBSD operating system, but rather to begin to develop a set of concepts that the author has found occurring to the author's own sense of consideration, during applications of the FreeBSD operating system. The author has been operating a local area network (LAN) with FreeBSD on the the LAN gateway host, on the software build host, and on the author's primary notebook laptop, on the LAN, for a small number of months. The author has begun to develop a concrete concept of the configuration of the same LAN, referring to it then as GraniteLAN. In an architectural sense, GraniteLAN may be integrated moreover with hosts configured of software defined networking (SDN) services -- there under the heading GraniteSDN -- as to develop an overall systems development network -- with the full network under the heading, GRANITENET. Presently, the author does not wish to develop any length sidebar about the architecture of the GRANITENET design, or the design philosophy of the same. It's basically a concept for a scalable DevOps network, and a small office/home office (SOHO) network, such that may be utilized not only from GRAITELAN, but moreover that may be utilized from a mobile appliance not immediately connected to but configured for connection to GRANITESDN. In its architecture, GRANITENET would apply a distinct number of common UNIX networking services, such as LDAP, NFS, NIS, Kerberos, and -- furthermore -- RADIUS. Though it may seem relatively easy to write about, as such, but -- in order to develop a manageable framework of so many network services, as such, and for it to be relevant in regards to applications on contemporary operating system architectures -- it may not ultimately be as easy to "Glue together," in application of so many software components. At least, it may be easy to "Put together" the concept of GRANITENET's design -- initially, as it representing a manner of a<i> paper machine,</i> as to apply an older phrase to the matter -- as it entailing a design of an effectively multi-homed application of the FreeBSD operating system.<br />
<br />
In regards to the manageability of the design and applications of GRANITENET, of course there must be a manner of a design incentive thought to exist. The author might not believe that every reader would share the author's sense of appreciation about the logical design of each of Common Lisp the Language, 2nd Edition, and CORBA systems, furthermore the Object Management Group's concepts of Object Management Architecture and Model Driven Architecture -- moreover, the portability of systems developed onto CORBA and, separately, the portability of applications developed onto the Common Language Infrastruture (CLI), the latter as popularized of the Microsoft Dot-NET and the Xamarin and Mono platforms, furthermore as standardized onto ECMA-335.<br />
<br />
Insofar as it representing a concept of a <i>paper machine</i>, the author has certainly expended some paper and graphite, in putting together a number of offline notes about the design of GRANITENET, moreover the design of a system the author denotes as FELDSPAR. FELDSPAR would represent an application of Common Lisp, CORBA, and the Common Lisp Interface Manager, as to create a bundled application development kit of free/open source software for applications of the same software and systems components. In that regards, perhaps it might seem like overmuch of an aspiring goal -- as to apply GRANITENET in developing the FELDSPAR framework, while GRANITENET is not even completely constructed, in itself, as yet. However, in retaining a sense of focus about the logical qualities of the design of each of GRANITENET and the FELDSPAR framework, it therefore remains a manageable set of concepts, at least to the author's own sense of consideration.<br />
<br />
In beginning to describe these discrete concepts to the Internet audience, it must naturally entail a development of a literal body of documentation. Thus -- in focusing about the Darwin Information Typing Architecture (DITA) -- there is a sense of a <i>topic repository</i> model developed in the FELDSPAR<i> </i>systems design, insofar as of the present <i>paper machine</i> edition of the FELDSPAR systems design. The <i>topic repository</i> model -- in some regards, semantically -- it might resemble something of a concept like of a <i>Wiki</i>. Though a FELDSPAR <i>topic repository</i> would be published to the Web, but -- in it utilizing DITA,l in its content source model -- it would not be immediately managed "on the web". The FELDSPAR <i>Topic Repository</i> model would allow for managing the body of content of a <i>topic repository</i>, as in application of so many DITA editing tools, multimedia content development tools, and changeset management tool such as Git -- without HTTP interverning between the editor and the filesystem. As such, perhaps it may not seem to be an immediately <i>enterprise friendly</i> framework, but perhaps it may be scalable outwards from its initial <i>SOHO friendly</i> design.<br />
<br />
In beginning to document this design, in a digital format of text, the author of this article wishes to make reference -- immediately -- reference to MARTE, specifically MARTE 1.1, furthermore to make reference to the DOAP RDF schema. Surely, it may be possible to develop a great amount of <i>semantic sugar,</i> in application of such normative specifications. Presently, the author wishes to recommend a concept of <i>software platform</i>, in an abstract sense, as may be extended to subsume concepts both of <i>operating system platform</i> and of <i>toolchain architecture, </i>furthermore as to provide a sense of structure about application components commonly referred to as <i>libraries</i> -- then to include the DOAP RDF schema, as to develop a documentation framework with which software developers may be able to make consistent, ostensibly convenient reference to all points of upstream software distribution, for any single software component.<br />
<br />
Towards developing an initial <i>usage case</i> to this sense of structure in software and systems: The author of this article has begun to write a small series of notes, in the author's own Evernote notebook, as to begin to develop some normative documentation towards an application of the Enlightenment Foundation Libraries (EFL) and the EFL WebKit integration, namely towards developing an EFL <i>port</i> for the Common Lisp Interface Manager (CLIM) as well as extensions for CLIM, in regards to web appliations, such that would be developed as for application at least onto FreeBSD, Linux Desktop, Android Mobile, and Microsoft Windows Desktop operating system platforms. Perhaps it aspires as towards a comprehensive design, to be thorough in regards to development and support of operating system applications.<br />
<br />
Though the author is furthermore interested about some concepts of microcontroller design, reprogrammable computing, and the history of the infamous Lisp Machine, but perhaps it may turn out to be a manner of a fortuitous effort, to begin with regards to applications of existing microprocessor achitectures and existing operating systems, specifically beginning at the manner of a colloquial UNIX-like framework developed of the FreeBSD Project -- furthermore, as FreeBSD being extended in a small number of by-in-large domain-special FreeBSD distributions.<br />
<br />
So, that would be towards an unabridged introduction.<br />
<br />
In focusing immediately towards applications of the EFL toolkit, there is immediately a concern that occurs as with regards to illustrating the toolkit's software components and software component depencencies, as towards any single distribution of the EFL toolkit -- in a sense, as towards any single distribution of a bundled set of EFL toolkit components, whether immediately with or without the EFL WebKit integration, and finally in a distribution to any single <i>operating system platform</i>, in application of any single <i>toolchain architecture</i>. This would be essentially orthogonal to -- but, in a sense, essential to -- the development of a <i>CLIM port</i> for EFL.<br />
<br />
The author proposes to develop a model for each of the following concepts, in extending the MARTE 1.1 Profile for the UML metamodel:<br />
<ul>
<li>Concrete <i>Computer Machine Architecture</i> -- immediately, perhaps extending of the Detailed Resource Model defined in MARTE 1.1</li>
<ul>
<li>e.g. as in reference to:</li>
<ul>
<li>The FreeBSD sysctl property, <span style="font-family: "Courier New",Courier,monospace;">`hw.model`</span></li>
<li>Compiler optimizations as may be specified in FreeBSD <span style="font-family: "Courier New",Courier,monospace;">/etc/make.conf</span> and/or FreeBSD <span style="font-family: "Courier New",Courier,monospace;">/etc/src.conf</span></li>
<li><span style="font-family: inherit;">Machine architectures in Debian GNU/Linux</span></li>
<li><span style="font-family: inherit;">Machine architectures in the GNU Compiler Collection </span></li>
</ul>
</ul>
<li>Abstract <i>Software Platform</i> -- likewise, perhaps extending of the Detailed Resource Model defined in MARTE 1.1</li>
<li>Concrete <i>Operating System Platform</i></li>
<li>Concrette <i>Toolchain arhitecture</i></li>
<ul>
<li><i>e.g. </i>MINGW </li>
<ul>
<li>Subsumes: MINGW x86-64<i> </i></li>
</ul>
</ul>
<li>Abstract <i>Software Application </i>and correspondingly, Abstract <i>Software Distribution</i>, in a <i>noun</i> sense of the latter term</li>
<ul>
<li>Software Distribution/Application model on a FreeBSD operating system</li>
<li>Software Distribution/Application on a Linux operating system</li>
<ul>
<li>Software Distribution/Application on a Debian or Ubuntu GNU/Linux operating system</li>
<li>Software Distribution/Application on an Android Operating System</li>
</ul>
<li>Software Distribution/Application on a Microsoft Windows operating system</li>
</ul>
</ul>
Orthogonally, it is the author's hope that the resulting UML profile models will be compatible onto the CORBA Component Model -- such that, in a sense, may complemented with a UML profile model extending of the concept of abstract software application, if not moreover integrating a manner of a system for software distribution in regards to CORBA components, there certainly making reference to OSGi and also Maven.<br />
<br />
That being so, then how may the author propose to publish a UML profile model, in any vendor-compatible regards? The author proposes to apply Modelio, and to publish the UML profile models finally as serialized XMI. The author furthermore proposes to apply the respective UML profile models, in development of a manner of a component metadata database, there integrating the DOAP RDF schema and some manner of a web publishing model for presenting the metadata database, in any managed manner, online. The DOAP RDF integration, in itself, may entail a development of an extensional RDF schema, moreover an application of some existing tools for RDF graph modeling in Common Lisp.<br />
<br />
Of course, there is a sort of a <i>boostrapping dilemma</i>, in such design. The author proposes to address the <i>bootstrapping dilemma</i>, in -- albeit, perhaps in something of a expressly nolinear sense -- but in an overall iterative sense, however. In such a sense, the author does not propose to specify that the design of the RDF application would wait on the design of the project-oriented management information system (Project MIS). The RDF application must wait, however, for the design of the final component metadata schema.<br />
<br />
Towards such an application of RDF, the author wishes to comment towards a sense of applying Common Lisp as a <i>data system</i> feature, within a <i>data programming</i> system, there closely and comprehensively integratred with the underlying operating system. The author proposes to limit this specific design to the FreeBSD operating system, moreover to focus about a small number of individual, concrete components such as already developed as and for individual Common Lisp implementations. The goal of this aspect of the design, to the author's opinion, the goal is to support software systems development with software systems development and documentation. In such a regards, perhaps it might seem like a manner of a DevOps concept, however developed of a popularly unconventional framework<br />
<br />
The RDF application, specifically, it may be developed as to extend of an XML Schema Datatypes implementation. As in a manner across the XML Schema Datatypes Implementation, it may be integrated onto a data persistence model for RDF, there to apply a HypersonicSQL service as a data storage service.<br />
<br />
If there may be a rhetorical question, such as, "Where to begin, next?" the author prpoposes to continue with the development of the UML profile models, as denoted herein.<br />
<br />Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-19837966874741174442015-09-19T13:17:00.000-07:002015-09-23T01:28:41.488-07:00Considering Bibliography and Filesystems<div class="blogaway-section">
While <i>Git</i> clones <i>EFL WebKit</i> onto my <i>GraniteLAN,</i> there is a short while as to develop a thought towards a concept of bibliography: That in the known universe, there exists a book about <i>SysML,</i> and there exists an article towards a mathematical perspective of <i>UML</i>. A mathematical perspective of such a topic, perhaps, may be presented as towards something of a literary discussion about a sense of a philosophical and practical relevance of the <i>Metaobject Famework</i> (MOF), and the corresponding metamodels of UML and SysML as dialects of systems modeling, such as may be applied moreover towards a systems design. <br />
<br />I'll try to develop a logical model of a concept, presently, as towards developing a logical model of software components, abstractly, and of components bundled materially in the EFL WebKit changeset repository – a changeset repository stored and accessible with <i>Git</i>. <br />
<br />Preliminary to developing a <i>UML </i><i><i><i><i><i><i>modeling p</i></i></i></i></i></i><i><i><i><i><i>rofile </i></i></i></i></i>for <i>software source code</i> components, I would firstly like to share a set of notes that I've collected as with regards to bibliography. I'm afraid that it cannot be a trivial effort, however, as to begin a thesis about bibliography, forthwith. Presently, there is a matter of the bibliography for any thesis about bibliography.<br />
<br />The article – as towards a mathematical perspective of UML, in the known universe – the article, in a PDF edition of its presently unnamed publication, it is presently located in a private <i>Git</i> repository on my notebook laptop. I had moved the file to there – effectively, relocating the file from its initial on-LAN location, then stored on the internal filesystem of my own academic dashboard of a tablet computer, moving it then to the <i>FreeBSD</i> UFS filesystem on my Notebook – that procedure, as when I was trying out <i>git-annex</i> as a file synchronization tool. Not to short <i>git-annex</i> of attention, I don't believe a <i>Git</i> repository may be an ideal resource for a mobile filesystem. The 'dot-git' metadata directory of a source tree managed with <i>Git</i>, that may seem to present something of a waste of limited mobile storage space, as it is for storage of data that may not be immediately accesed by a <i>Git</i> user, outside of each individual changeset registrstion.<br />
<br />Since the time of making an initial study about <i>git-annex</i>, approximately one week ago, I've read a small amount of literature about <i>SparkleShare</i>. I wonder, now, as SparkleShare implements a manner of a virtual filesystem, may it be approached as to develop a manner of a <i>CORBA</i> filesystem service framework? <i>SpakleShare</i> is available as free/open source software, juxtaposed to <i>Dropbox</i>, <i>Box.net</i>, or similar closed source, web-oriented <i>Cloud Storage</i> services.<br />
<br />This morning, while developing an outline about networked filesystems available on <i>FreeBSD,</i> I'd read some little about <i><i>GlusterFS,</i></i> and some little more about network services available to a model of classical <i>UNIX</i> networking. Though, personally, I am not immediately decided about applying either <i>GlusterFS</i> or <i>NFS</i> on my <i>GraniteLAN,</i> this afternoon, however I'm considering both of those networked filesystem models – as towards a manner of a <i>DevOps</i> regards – for application in <i>integration testing</i> and <i>continuous availability</i> i.e software distribution, but on a local area network (LAN) only, of a custom compiled <i>FreeBSD</i> 10.2 <i>kernel</i> and <i>FreeBSD</i> 10.2 <i>base system</i> on <i>GraniteLAN</i>.<br />
<br />So. There's to a service oriented view of filesystem services – as in a manner, a view corresponding with a generic concept of "File", howwver applied as onto a concept of a "Private network." There are the <i>GlusferFS</i> and <i>NFS</i> network filesystems, and alternately, <i>SparkleShare</i> as a centralized virtual filesystem. <br />
<br />Three types of filesystem – it might be enough as with which one may develop a manner of an outline of a thesis article. There might be a concept of mathematical topology, correspondingly developed – perhaps, towards an abstraction about data and computation, and a conept about illustrating a graph of data.<br />
<br />[Draft nr. 5]<br />
<br />
<br />
Some notes about Bibliography, focusing on bibliographical tools<br />
<ul>
<li><i>Mendeley Desktop</i> (Microsoft Windows, version 1.14)</li>
<ul>
<li><b>When importing a <i>BibTeX </i>file</b>, in regards to attachments (files), <b><i>Mendeley Desktop </i>does not parse <i>relative filenames</i> as expected</b>. </li>
<ul>
<li>If an <i>attachment</i> is referenced in the BibTeX file with a relative pathname -- such as when the BibTeX file is generated with <i>Eratosthenes</i>, then as when <i>attaching </i>a document to a BibTeX entry -- the <i>attachment</i> will not be added to the user's Mendeley files, as expected. Mendeley, instead, will report as if the file does not exist. </li>
<li>A workaround exists for this unexpected software behavior: To remove the "Not found" attachment's entry, in each Mendeley bibliography entry, then to attach each file manually</li>
</ul>
<li>When saving the user's bibliographies in <i>BibTeX </i>format:</li>
<ul>
<li>Effectively, the files are <b>saved in read-only format. </b>Changes to the files will be overwritten by Mendeley Desktop</li>
<li>For a set of bibliography files saved by <i>Mendeley Desktop </i>into a directory 'bibsync', the <i>BibTeX </i>*.bib files saved within 'bibsync' will change in unexpected ways, over time</li>
<ul>
<li><b><i>Mendeley Desktop </i>does not always save the set of <i>BibTeX </i>entries in the same order of entry,</b> within each file, at each time of synchronization</li>
<ul>
<li>If the 'bibsync' directory is managed within an SCCM repository, this will result in <i>file changes</i>, though the <i>BibTeX </i>entries themselves may not have changed, in any single one.</li>
</ul>
<li> If the user has configured <i>Mendeley Desktop</i> to organize the user's bibliography attachments, as to save the files within a directory 'bibsync/files', then in each entry in 'bibsync/*.bib', <b>every attached file within 'bibsync/files'will be referenced with an absolute pathname</b> as would be generated on the filesystem or origin.</li>
<ul>
<li>This may seem to present a minor challenge, as in regards to utilizing the generated BibTeX files with services not including Mendeley Desktop -- such as when the bibliography files are synchronized into an SCCM repository, or if the bibliography files would be posted to any single web service</li>
</ul>
</ul>
</ul>
</ul>
<li>Eratosthenes (Android)</li>
<ul>
<li><a href="https://bitbucket.org/mkmatlock/eratosthenes/wiki/Home">Eratosthenes Wiki</a> [Bitbucket] </li>
<li><a href="https://bitbucket.org/mkmatlock/eratosthenes/issues?status=new&status=open">Eratosthenes Issue Tracker</a> [Bitbucket] </li>
<li>Not open source</li>
<ul>
<li>Not uncommon, on Andoid</li>
</ul>
<li>Supports bibliography formats generated with <i>JabRef</i>, <i>BibDesk</i>, and <i>Eratosthenes</i></li>
<li>Great UI</li>
<li>May be difficult to synchronize between tablet and desktop</li>
<ul>
<li>Tried: Synchronizing bibliography metadata and files, using git-annex</li>
<ul>
<li>Though git-annex has its applications, but in considering the limited filesystem storage capacity available of <i>thin client </i>mobile appliances, <b>the dot-git repository of a git-annex repository consumes storage space </b>to no great effect. This is more pronounced, perhaps, for storage of binary formatted files, such as of documents in the Adobe PDF format</li>
</ul>
<li>Unavailable, presently: GlusterFS on Android</li>
<ul>
<li>See also: <a href="http://www.cyanogenmod.org/">CynaogenMod </a></li>
</ul>
<li>Available, but with reservations: Dropbox</li>
<ul>
<li>A user's Dropbox storage is manageable via the central DropBox web site, or on filesystems with the user's central/cloud DropBox storage completely synchronized to the filesystem</li>
<li>Synchronization not obviously available for Android</li>
<li>Synchronization not manageable by the LAN administrator</li>
</ul>
<li>Unavailable, presently: Sparkleshare on Android</li>
</ul>
</ul>
</ul>
</div>
Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-37791496050397904292015-09-19T12:15:00.001-07:002015-09-20T06:45:00.756-07:00On Cloning EFL WebKit<a href="https://trac.webkit.org/wiki/EFLWebKit">EFL WebKit</a> is certainly not a small toolkit to <i>Git clone</i>, in its full <i>Git changeset</i> <i>repository</i>.<br />
<br />
At 37% of <i>changeset</i> data transmitted, the <i>repository data</i> amounts to so much of 3.41 GB, in a quantitative measure.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhj4scgq4_z7ZMEnvDXrKZxUQoFHfEs_jdR3P_qXg7IPb3HUxzAxY_-PS5MfS9XHqS_PgZ8F-HnePqPYGA-PWpWPlmvYA7mWkOOlLYIvOgwOIFJPZ_oBGO9-SQxkFXtLN1R-PTV6-VLGQg/s1600/Screenshot_EFL_Webkit_Get.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="179" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhj4scgq4_z7ZMEnvDXrKZxUQoFHfEs_jdR3P_qXg7IPb3HUxzAxY_-PS5MfS9XHqS_PgZ8F-HnePqPYGA-PWpWPlmvYA7mWkOOlLYIvOgwOIFJPZ_oBGO9-SQxkFXtLN1R-PTV6-VLGQg/s320/Screenshot_EFL_Webkit_Get.png" width="320" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">Cloning the EFL WebKit source repository - 3.4 GB at 37%</td></tr>
</tbody></table>
I'm certain there's something that can be applied to simplify its source tree, but it might need a sketch or two in UML format -- moreover, a <i>UML profile </i>for illustrating <i>inter-component dependencies</i> onto a <i>SysML</i> block diagram.<br />
<br />
Presently, it has thoroughly bogged down my network uplink, thus making this <i>web log entry</i> a little more difficult to <i>edit</i>. So, there won't be much to show here, in this article's draft nr. 1.<br />
<br />
Update: On review of the <a href="https://github.com/ewebkit/webkit/">ewebkit/webkit repository at GitHub</a>, juxtaposed to the <a href="http://trac.webkit.org/browser#trunk/">WebKit SVN repository</a> (e.g. <a href="http://trac.webkit.org/browser#trunk/Source/WebKit2/efl">Source/WebKit2/efl/</a>) it seems that there's a certain lack of synchronization with the repository a GitHub. Furtthermore, the SVN repository would be the more up-to-date source code repository, assuming a sense of trust about the "Last update" timestamps on the files. <br /><br />It may seem peculiar that the EFL WebKit developers would not keep the repository up-to-date at GitHub. Regardless, the baseline WebKit SVN repository may be preferred, or the baseline WebKit Git repository -- at which point, <a href="http://www.webkit.org/building/checkout.html">the WebKit 'checkout' documentation</a> may be relevant. As a further alternative, a Git repository may be developed as manner of a <i>changeset proxy</i> onto the SVN repository, using 'git-svn'.<br />
<br /><br />Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-87153736417876663302015-09-18T18:01:00.001-07:002015-09-19T04:07:31.975-07:00FreeBSD Base System Upgrade - How To - and a question, DITA and FreeBSD ?<a href="https://www.freebsd.org/doc/handbook/index.html">The FreeBSD Handbook</a> is a really helpful resource. It contains a lot of really well organized information -- certainly, information that may be useful for FreeBSD system developers and system maintainers -- clearly, in a format of documentation written by authentic experts about the FreeBSD <i>Kernel</i> and broader FreeBSD <i>Base System</i> -- no imitations about UNIX expertise, in the FreeBSD handbook.<br />
<br />
Towards rebuilding a FreeBSD operating system on a local area network -- such as for compiler optimizations, <i>viz a viz</i> <span style="font-family: "Courier New",Courier,monospace;">/etc/make.conf</span>, and for upgrading the operating system to a newer version, as for instance in upgrading from FreeBSD 10.1-RELEASE to 10.2-RELEASE -- there are a few references that would be useful, in the FreeBSD handbook.<br />
<br />
As to augment the existing documentation, I'd like to add a few small annotations -- to highlight a small number of concepts addressed in the conceptual <i>topic repository</i> of the FreeBSD handbook, and in an annotations sense, to add some augmentative information -- as follows<br />
<ul>
<li><i><a href="https://www.freebsd.org/doc/handbook/kernelconfig-building.html">Building and Installing a Custom Kernel</a></i> </li>
<ul>
<li>Concept: Kernel configuration</li>
<li>See also</li>
<ul>
<li>Shell command: <span style="font-family: "Courier New",Courier,monospace;">`sysctl -n kern.conftxt`</span></li>
<li><span style="font-family: inherit;">Manual page <a href="https://www.freebsd.org/cgi/man.cgi?query=config&sektion=5">config(5)</a></span></li>
</ul>
</ul>
<ul>
<li><u><i>Ed. Notes - Misc</i></u></li>
<ul>
<li>TBD: Cross-compiling the FreeBSD <i>kernel</i> (see documentation)</li>
<li>TBD: HOWTO FreeBSD Kernel Configuration GUI</li>
<ul>
<li>See also: GNU/Linux kernel - <span style="font-family: "Courier New",Courier,monospace;">`make menuconfig`</span>, <span style="font-family: "Courier New",Courier,monospace;">`make xconfig</span>`, ...</li>
</ul>
</ul>
</ul>
</ul>
<ul><ul><ul>
<li><b>TO DO:</b> Produce an index of all kernel configuration parameters noted in the FreeBSD handbook </li>
</ul>
</ul>
</ul>
<ul><ul><ul><ul>
</ul>
</ul>
</ul>
<li><i><a href="https://www.freebsd.org/doc/handbook/makeworld.html">Rebuilding World</a></i></li>
<ul>
<li>Concept: FreeBSD <i>Base System</i></li>
<li><u><i>Ed. Notes - Misc.</i></u> </li>
<ul>
<li>See also: Previous link, as with regards to FreeBSD kernel configuration </li>
<li>TBD<i>: Configurable</i> parameters of the FreeBSD <i>base system</i> build</li>
<li>TBD: FreeBSD Base System Configuration GUI</li>
<ul>
<li>See also: <a href="https://github.com/freebsd/poudriere">Poudriere</a>; <a href="http://augeas.net/">Augeas</a></li>
<li>Note: <i>Licensing terms </i>of FreeBSD <i>base system</i> components </li>
<li>Note: Concepts, <i>Licensing</i> and <i>Software Distribution</i></li>
</ul>
<li>TBD: Cross-compiling the FreeBSD <i>base system</i></li>
<li>TBD: <i>Issue tracker</i> integration</li>
<ul>
<li>See also: Debian <span style="font-family: "Courier New",Courier,monospace;">`reportbug`</span></li>
</ul>
</ul>
</ul>
<li><a href="https://www.freebsd.org/doc/handbook/small-lan.html"><i>Tracking for Multiple Machines</i></a></li>
<ul>
<li>Concept: <i>Build set</i></li>
<ul>
<li>Common features:</li>
<ul>
<li><span style="font-family: "Courier New",Courier,monospace;">make.conf</span></li>
<li><span style="font-family: "Courier New",Courier,monospace;">src.conf</span></li>
<li>networked filesystem configuration (e.g. NFS)</li>
</ul>
<li>Recommended feature:</li>
<ul>
<li><i>Test machine</i></li>
<ul>
<li>Application: <i>Integration testing</i> for compiled <i>base system</i> and <i>kernel </i></li>
</ul>
</ul>
</ul>
<ul>
<li>Optional feature:</li>
<ul>
<li>Change management shared files</li>
<li>NIS/YP - <i>see following notets</i> </li>
</ul>
</ul>
<li>Concept: <i>Toolchains</i></li>
<ul>
<li><u><i>Ed. Notes - FreeBSD Toolchain</i></u></li>
<ul>
<li>See also: Following notes about make.conf, src.conf<i> </i></li>
</ul>
</ul>
<li>Concept: <i>Networked filesystems</i></li>
<ul>
<li><i><u>Ed. Notes - Networked Filesystems</u></i></li>
<ul>
<li><i>Juxtapose to:</i> Block-level filesystems; Virtual filesystems</li>
<li>See also: Network File System Service</li>
<ul>
<li>Bill Swiggle <i>"<a href="https://www.freebsd.org/doc/handbook/network-nfs.html">Network File System (NFS)</a>"</i>. ed. <span class="authorgroup"><span class="author"><span class="firstname">Tom</span> <span class="surname">Rhodes. </span></span></span><i>FreeBSD Handbook</i></li>
<li><a href="https://www.freebsd.org/cgi/man.cgi?query=mount_nfs&sektion=8&apropos=0&manpath=FreeBSD+10.2-RELEASE"><i>mount_nfs(8)</i></a>. Manual page<i> </i></li>
</ul>
<ul>
<li>See also: Network Information Service (a.k.a YP)</li>
<ul>
<li><i>"<a href="https://www.freebsd.org/doc/handbook/network-n">Network Information System (NIS)</a>"</i>. <i>FreeBSD Handbook</i></li>
<li>Hal Stern, Ricardo Labiaga, Mike Eisler. <a href="https://www.safaribooksonline.com/library/view/managing-nfs-and/1565925106/"><i>Managing NFS and NIS, 2nd Edition</i></a>. O'Reilly (2001)</li>
</ul>
<li>See also: LDAP Directory Service</li>
<ul>
<li>Dag-Erling Smørgrav. <a href="https://www.freebsd.org/doc/en/articles/pam/"><i>Pluggable Authentication Modules</i></a></li>
<li>Toby Burress. <a href="https://www.freebsd.org/doc/en/articles/ldap-auth/index.html"><i>LDAP Authentication</i></a><i> </i></li>
</ul>
<ul>
</ul>
<ul>
</ul>
<li>See also: Certificate Authority Service</li>
<ul>
<li><a href="https://wiki.strongswan.org/projects/1/wiki/SimpleCA"><i>Setting-up a Simple CA Using the strongSwan PKI Tool</i></a>. strongSwan documentation</li>
<li><a href="https://www.zeitgeist.se/2013/11/22/strongswan-howto-create-your-own-vpn/"><i>strongSwan 5: How to create your own private VPN</i></a>. Zeitgeist. web log</li>
</ul>
<li>See also: Wireless Networking Services and WPA2-Enterprise Wireless Authentication Services</li>
<ul>
<li><span class="authorgroup"><span class="author"><span class="firstname">Marc</span> <span class="surname">Fonvieille Loader and Murray Stokely. </span></span></span><i>"<a href="https://www.freebsd.org/doc/handbook/network-wireless.html">Wireless Networking</a>"</i>. FreeBSD Handbook</li>
<li><a href="https://forums.freebsd.org/threads/howto-wpa2-enterprise-with-freeradius.28467/"><i>HOWTO: WPA2-Enterprise with FreeRadius</i></a>. FreeBSD Forums</li>
<li><i>"<a href="http://wiki.freeradius.org/guide/FAQ">FAQ</a>."</i> <i>FreeRADIUS Guide</i></li>
</ul>
<li>See also: <i>"<a href="https://www.freebsd.org/doc/handbook/network-dhcp.html">Dynamic Host Configuration Protocol (DHCP)</a>"</i>. FreeBSD Handbook </li>
<ul>
<li><i>Advice: </i>For each network client configured to obtain its IP address via DHCP, the DHCP server may be configured so as to reserve a specific IP address for each network client, as per the MAC address published of the connecting client's network interface. Each such reserved IP address may then be applied in the NFS configuration, on each NFS server and/or the NFS client.</li>
<li>Alternately, if a network is configured with static IP addressing, each IP address, network mask, and router address may be entered manually at each respective client machine.</li>
</ul>
</ul>
<li>See also: Histories of UNIX(R) </li>
<li>See also: Andrew Filesytem (AFS)</li>
<li>See also: Zettabyte Filesystem (ZFS)</li>
<li>See also: Filesystem in Userspace</li>
<ul>
<li><a href="http://fuse.sourceforge.net/"><i>FUSE: FIlesystem in Userspace</i></a>. web site<i> </i></li>
<li><i><a href="https://wiki.freebsd.org/FuseFilesystem">FUSE Module</a></i>. FreeBSD Project Wiki </li>
</ul>
<li>See also: GlusterFS</li>
<ul>
<li><i><a href="https://wiki.freebsd.org/GlusterFS">GlusterFS</a></i>. FreeBSD Project Wiki</li>
<li>Coyle, James. <a href="http://www.jamescoyle.net/how-to/471-zfs-and-glusterfs-network-storage"><i>ZFS and GlusterFS network storage</i></a></li>
<li><a href="http://www.gluster.org/"><i>Gluster</i></a>. web site</li>
<li><i><a href="http://gluster.readthedocs.org/en/latest/Quick-Start-Guide/Quickstart/">Installing GlusterFS - a Quick Start Guide</a> </i></li>
</ul>
</ul>
</ul>
</ul>
</ul>
<ul>
<li><i>Ed. Notes (add'l)</i></li>
<ul>
<li>TBD:<i> </i>Handbook-wise<i> </i>documentation about files <span style="font-family: "Courier New",Courier,monospace;">/etc/make.conf</span> and <span style="font-family: "Courier New",Courier,monospace;">/etc/src.conf</span></li>
<ul>
<li>Concept: <i>Toolchains</i> </li>
<li>Concept: <i>Machine-specific optimizations</i> </li>
<ul>
<li>e.g utilizing SSE machine instructions on later Intel architectures</li>
</ul>
<li>See also: </li>
<ul>
<li>LLVM</li>
<li>Manual pages</li>
<ul>
<li><a href="https://www.freebsd.org/cgi/man.cgi?query=make.conf&apropos=0&sektion=5&manpath=FreeBSD+10.2-RELEASE&arch=default&format=html">make.conf(5)</a></li>
<ul>
<li>Context: all system builds, including ports, kernel, and base system</li>
</ul>
<li><a href="https://www.freebsd.org/cgi/man.cgi?query=src.conf&apropos=0&sektion=5&manpath=FreeBSD+10.2-RELEASE&arch=default&format=html">src.conf(5)</a></li>
<ul>
<li>Context: kernel and base system (?) </li>
</ul>
</ul>
</ul>
<ul>
<li><span style="font-family: "Courier New",Courier,monospace;">/usr/share/examples/etc/make.conf</span></li>
<li><span style="font-family: "Courier New",Courier,monospace;">/usr/src/share/mk/bsd.cpu.mk</span></li>
</ul>
</ul>
</ul>
</ul>
<ul><ul><ul><ul><ul>
</ul>
</ul>
</ul>
</ul>
</ul>
<br />
Orthogonally: Though I cannot believe I'll ever be able to <i>sell</i> the FreeBSD project about using DITA, but it's "A thought," though.<br />
<br />
The FreeBSD Handbook, by in large, already serves as a topically focused -- and very usefully detailed -- reference manual about the FreeBSD operating system. As a<i> knowledge resource</i>, the FreeBSD handbook very much <i>"Holds its own,"</i> as furthermore a manner of a <i>reference manual.</i><br />
<br />
The Handbook is published in a format like of a set of <i>thesis documents</i> about individual components of FreeBSD. In a DITA format, each article-like section in the FreeBSD handbook could be rendered as a DITA <i>Topic</i>. That, in itself, might not exactly serve towards further development of the FreeBSD handbook. However, perhaps it might serve as an aid to users and developers, as towards a manner of extensibility about the FreeBSD handbook -- at least, then, to authors whom would be both familiar with the DITA format, and familiar with the "Internals" of FreeBSD. <br />
<br />
The overlap, in that proverbial set -- perhaps it might not seem to be any very broad kind of an overlap, <i>at least</i> outside of an<i> ideal estimate</i>, as of a hypothetical universe in which DITA is something anyone would voluntarily learn, beyond the small community of technical documentation geeks, and those of us somewhere in orbital space to the same.<br />
<br />
The FreeBSD Handbook, in its original format, is developed onto the DocBook toolchain -- a long tried and trusted toolchain for technical documents. The DocBook toolchain is comprised, essentially, of the DocBook Schema -- in any single format, such as of a Document Type Definition (DTD) or a RELAX-NG schema -- and the DocBook modular stylesheets. The DocBook stylesheets, in turn, are available in both of DSSSL format -- for application onto SGML DocBook documents -- and in XSL format, for application on to XML DocBook documents.<br />
<br />
Though there is a <i>mapping</i> -- as commonly available of the DITA Open Toolkit (DITA OT) -- for transforming DITA documents onto DocBook, but presently, there might not be an inverse mapping for DocBook onto DITA. It might be a fairly trivial matter, to <i>semantically invert</i> any much of the DITA-to-DocBook transformation module, from DITA OT, in defining a DocBook-to-DITA transformation. However, the question of whether and how that may be pragmatically <i>worth it</i> might remain to be addressed.<br />
<br />
There's a topic that the author of this article is not willing to venture to address, in any offhand regards, at the FreeBSD forums: <i>"Anyone else wants to use DITA to document FreeBSD?" </i>Though the author of this article might fancy himself to be sufficiently familiar with SGML, XML, DocBook, and DITA formats, sufficient to be able to manage such a project by himself, but the social incentive of such a matter might seem to be fairly much "In doubt," as it may seem to be fairly much "Non-trivial," as a prospective effort, in numerous independent <i>points of view</i>.<br />
<br />
In a manner of a rhetorical question: How would a "Proof of concept" be regarded, for a DITA transform of the DocBook format of the original FreeBSD Handbook?<br />
<br />
It might seem to need some kind of a "Run-up time," such a project, if it could ever be a project that might be any furthermore adopted by the FreeBSD developer community. Though the author of this article, in particular, fancies DITA to be as simple as push-button editing -- except for all of the visible markup of it -- but not everyone might quite agree.<br />
<br />
In a further juxtaposition of DITA to DocBook: In DITA, there are also the matters of <i>content inclusion</i> and seperately, of <i>linking</i>, each of which such <i>concepts</i> does not occur exactly in such a manner, in DocBook, not in exactly as it occurs in the syntax and semantics of DITA. Furthermore, in DITA, there is the topic 'class' attribute -- probably a very much interesting features, to those of us whom may be, furthermore, object oriented programming (OOP) geeks.<br />
<br />
<i>Ed. Note: </i>...and then there's something about "How to avoid arbitrary topics," as towards, orthogonally, towards a manner of <i>a Wiki model for DITA</i> or -- contrarily -- towards a centrally edited <i>topic repository</i> model for DITA <br />
<br />
It would definitely be a project applying the Java(R) programming language, to document FreeBSD with DITA. DITA OT uses ASF* <i>Ant</i>, for instance, in DITA OT's own build automation framework. ASF <i>Ant</i> is a tool developed in Java(R). Whether or not all persons editing DITA documents may prefer to use editor platforms <i>also</i> developed in Java(r) -- such as the <i>commercially licensed</i> Oxygen XML product -- and the author of this article would rather prefer to use Emacs and PSGML, candidly -- but for so much as building the finally formatted documentation, it would definitely need to use Java(R), such a project. It may be <i>at least a convenient thing</i>, then, that FreeBSD is <i>really good</i> at running Java(R) applications.**<br />
<br />
Is that enough of an incentive, in itself? Most probably, it is not. DITA is not the hottest kewlness online, and -- candidly -- all of this amounts to anything very much unlike a <i>hot rod</i> sports car view of FreeBSD. It doesn't exactly become easily to a metaphor about <a href="http://www.minetest.net/">Minetest</a>, either -- not to game around about operating systems design. This article describes some concepts of documentation, as in or towards a manner of a developer's view.<br />
<br />
<br />
* ASF: The Apache Software Foundation.<br />
<br />
** It could seem almost like a kind of Digital Magic -- the efficiency at which FreeBSD runs Java(R) applications, even on the desktop. Perhaps it's rather a matter of the operating system design in FreeBSD. Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-8879466191464768892015-09-17T09:18:00.001-07:002015-09-18T17:34:36.266-07:00On Assembling "Own Porridge"As a status update written at an exo-Twitter[1] dimension: Aside to beginning a small adventure[2] with <a href="http://www.minetest.net/">Minetest</a>* as -- so to speak -- in a <a href="https://en.wikipedia.org/wiki/Voxel">voxel</a>-blocks meta-universe -- to a fun and simple study of video games, multiplayer online game environments, and such that I refer to as <i>Maker Universe</i> game styles -- this week, I've also begun reading about the ECMA standardization of the Microsoft dot-net platform, as codified in ECMA-4356445, ECMA TR-xyzzq, and TR-3A2 -- rather, <a href="http://www.ecma-international.org/">ECMA</a> documents: <a href="http://www.ecma-international.org/publications/standards/Ecma-335.htm">ECMA-335</a>, <a href="http://www.ecma-international.org/publications/techreports/E-TR-084.htm">TR/84</a>, and <a href="http://www.ecma-international.org/publications/techreports/E-TR-089.htm">TR/89</a>. Ostensibly, all of those documents are as exactly as the titles would seem to indicate.<br />
<br />
The second part of this week's adventure -- presently, in presenting it like an adventure through CLI Land -- it begins as a lark, in a sense, as with regards to the <a href="http://www.unity3d.com/">Unity</a> framework, <a href="https://en.m.wikipedia.org/wiki/Xamarin">Xamarin</a>'s work in software and systems development, <a href="http://www.mono-project.com/">Mono</a>, and ostensibly, Common Lisp.<br />
<br />
Hypothetically, a complete implementation of the "Dot Net" framework can be developed in Common Lisp, if anyone would set about to develop such a work and to complete the work, as such. Materially, although such a hypothesis may be difficult to disprove -- and it may not be any easier to materially <i>prove</i>, as in<i> completely </i>and with<i> a proof of concept</i> in software programming -- it may seem that there are some elements with which anyone may invent a "Golden ticket for Lisp," again, commercially.<br />
<br />
So, aside to all the facets of a plain adventure, presently the author of this article has arrived at PDF page 139 (document p. 113) of ECMA-335, in which there is a convenient list of software directives as defined in the high-level assembly language of ILAsm, in the whole C#/CLI/CLR/dot-Net porridge.<br />
<br />
Porridge -- a metaphor of a fantastic social fairytale and the webs, furthermore a breakfast food of a starchy kind.<br />
<br />
Before the author of this article looses one's place of study in the same porridge, some further notes: <br />
<ul>
<li>The definition of ILAsm as a <i>high-level assembler</i></li>
<li><b>ECMA-335 Common Type System</b></li>
<ul>
<li>Juxtapose[d] to: CORBA IDL bindings</li>
<li>See also: ECMA-335 <i>Generics</i></li>
<li>See also: ECMA-335 section II.11 <i>Semantics of Classes</i>, as specifically for each type of effective meta-class</li>
<ul>
<li>Interface</li>
<li>Value Type</li>
<li>Special Type</li>
</ul>
</ul>
<li> <b>ECMA-335 Virtual Execution System</b></li>
<ul>
<li>Juxtapose[d] to: Operations of a CORBA Portable Object Adapter (POA) in application for providing any single CORBA object service</li>
</ul>
<li>Dot-net</li>
<li>C#</li>
<li>Unity Framework</li>
<li>Enligthenment Foundation Libraries (EFL)</li>
<li>Tizen</li>
<li>...</li>
</ul>
<br />
<br />
<br />
<br />
<br />
<u>Footnotes</u><br />
<br />
[1] In the <a href="http://www.twitter.com/">Twitter</a> media, all status updates are encoded at 140 or fewer Unicode Characters, with a shortened encoding for URL references<br />
<br />
[2] An adventure much in a manner as to extend of the heritage of <a href="https://www.freebsd.org/cgi/man.cgi?query=adventure&apropos=0&sektion=6&manpath=FreeBSD+10.2-RELEASE+and+Ports&arch=default&format=html">Adventure</a>, <a href="http://rickadams.org/adventure/">Colossal Caves</a>, and <a href="https://en.wikipedia.org/wiki/Zork">Zork</a>, without overmuch of <i>mature themes</i> -- aside to a <i>shout out</i> for the<i> early years</i> of Linden Labs' <a href="http://secondlife.com/">Second Life</a> (SL) universe. In such a sense, it may be rather difficult for the game universe to become polluted of excessively mature themes -- as in some "Adult only" locales in Second Life. Elsewhere, in some other voxel universes online, there are themes of simple art, <a href="http://wiki.minetest.com/wiki/Crafting">crafting</a>, and -- aside to the materials of voxel universes -- <a href="http://rubenwardy.com/minetest_modding_book/index.html">coding</a>.<br />
<br />
Sadly, much of the art has disappeared from SL -- <i>Virtual Tibet</i> included. It might not seem like overmuch a quandary, however, to a mature perspective. It would be difficult for anyone to corrupt** the <i>block-oriented</i> maker universes -- not to challenge anyone who might even consider to. There's not likely to be so much as an illusion of incentive for anyone to corrupt -- for instance -- the non-dollar-oriented <a href="https://minecraft.net/">Minecraft</a>, though one might not underestimate the depths of the imaginations of anyone whom might even consider to. <br />
<br />
* Update: After reviewing a book about the fantastic Secondlife universe, moreover considering the unlikelihood of block-oriented video games ever becoming any more popular than already, I'll probably not be continuing with any further studies about multiplayer online game universes. It sure was neat to write about such a positive idea, for a short time, however.<br />
<br />
** That's exactly the word I mean, there, if there may be any sense of ambiguity about that.Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-27501742163510237422015-08-05T21:48:00.001-07:002015-10-09T23:58:56.460-07:00Custom Build for SBCL 1.2 with Multithreading on FreeBSD 10After installing SBCL 1.2.9 from the standard baseline package for FreeBSD 10.1-RELEASE, the *features* value is as follows: <br />
<blockquote>
<code>(:ALIEN-CALLBACKS :ANSI-CL :ASH-RIGHT-VOPS :BSD :C-STACK-IS-CONTROL-STACK
:COMMON-LISP :COMPARE-AND-SWAP-VOPS :COMPLEX-FLOAT-VOPS :CYCLE-COUNTER :ELF
:FLOAT-EQL-VOPS :FREEBSD :GCC-TLS :GENCGC :IEEE-FLOATING-POINT
:INLINE-CONSTANTS :INTEGER-EQL-VOP :INTERLEAVED-RAW-SLOTS :LINKAGE-TABLE
:LITTLE-ENDIAN :MEMORY-BARRIER-VOPS :MULTIPLY-HIGH-VOPS :OS-PROVIDES-BLKSIZE-T
:OS-PROVIDES-DLADDR :OS-PROVIDES-DLOPEN :OS-PROVIDES-GETPROTOBY-R
:OS-PROVIDES-POLL :OS-PROVIDES-PUTWC :OS-PROVIDES-SUSECONDS-T
:PACKAGE-LOCAL-NICKNAMES :PRECISE-ARG-COUNT-ERROR :RAW-INSTANCE-INIT-VOPS
:SB-CORE-COMPRESSION :SB-DOC :SB-EVAL :SB-LDB :SB-PACKAGE-LOCKS :SB-QSHOW
:SB-SIMD-PACK :SB-SOURCE-LOCATIONS :SB-TEST :SB-UNICODE :SBCL
:STACK-ALLOCATABLE-CLOSURES :STACK-ALLOCATABLE-FIXED-OBJECTS
:STACK-ALLOCATABLE-LISTS :STACK-ALLOCATABLE-VECTORS
:STACK-GROWS-DOWNWARD-NOT-UPWARD :SYMBOL-INFO-VOPS :UNIX
:UNWIND-TO-FRAME-AND-CALL-VOP :X86-64)</code></blockquote>
<br />
In a a <i>custom</i> build, SBCL 1.2.14.32-ce739b6 <br />
<blockquote>
<code>(:ALIEN-CALLBACKS :ANSI-CL :ASH-RIGHT-VOPS :BSD :C-STACK-IS-CONTROL-STACK
:COMMON-LISP :COMPARE-AND-SWAP-VOPS :COMPLEX-FLOAT-VOPS :CYCLE-COUNTER :ELF
:FLOAT-EQL-VOPS :FP-AND-PC-STANDARD-SAVE :FREEBSD :GCC-TLS :GENCGC
:IEEE-FLOATING-POINT :INLINE-CONSTANTS :INTEGER-EQL-VOP :INTERLEAVED-RAW-SLOTS
:LINKAGE-TABLE :LITTLE-ENDIAN :MEMORY-BARRIER-VOPS :MULTIPLY-HIGH-VOPS
:OS-PROVIDES-BLKSIZE-T :OS-PROVIDES-DLADDR :OS-PROVIDES-DLOPEN
:OS-PROVIDES-GETPROTOBY-R :OS-PROVIDES-POLL :OS-PROVIDES-PUTWC
:OS-PROVIDES-SUSECONDS-T :PACKAGE-LOCAL-NICKNAMES :PRECISE-ARG-COUNT-ERROR
:RAW-INSTANCE-INIT-VOPS :SB-DOC :SB-EVAL :SB-FUTEX :SB-LDB :SB-PACKAGE-LOCKS
:SB-SAFEPOINT :SB-SIMD-PACK :SB-SOURCE-LOCATIONS :SB-TEST :SB-THREAD
:SB-THRUPTION :SB-UNICODE :SB-WTIMER :SB-XREF-FOR-INTERNALS :SBCL
:STACK-ALLOCATABLE-CLOSURES :STACK-ALLOCATABLE-FIXED-OBJECTS
:STACK-ALLOCATABLE-LISTS :STACK-ALLOCATABLE-VECTORS
:STACK-GROWS-DOWNWARD-NOT-UPWARD :SYMBOL-INFO-VOPS :UNIX
:UNWIND-TO-FRAME-AND-CALL-VOP :X86-64)</code></blockquote>
Difference:<br />
<blockquote>
<code>(:SB-XREF-FOR-INTERNALS :SB-WTIMER :SB-THRUPTION :SB-THREAD :SB-SAFEPOINT
:SB-FUTEX :FP-AND-PC-STANDARD-SAVE)</code>
</blockquote>
In the <i>custom</i> build, I'd enabled the <code>:SB-XREF-FOR-INTERNALS</code>
feature for purpose of debugging, the <code>:SB-WTIMER</code>, <code>:SB-THRUPTION</code>, and <code>SB-SAFEPOINT</code> features for purpose of testing, and initially just <code>:SB-THREAD</code> for multithreading. The build did not complete.<br />
<br />
Without <code>:SB-FUTEX</code> enabled, the build might fail/loop/freeze during the build's integrated testing. When the <code>:SB-FUTEX </code>feature is enabled <i>along with</i> <code>:SB-THREAD</code>, then SBCL compiles successfully on FreeBSD 10.1. <br />
<br />
#YMMV<br />
<br />
<i>Ed. Note</i>: This has since been addressed to a comment in the FreeBSD Bugzilla database, at <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199055">Issue nr. 199055</a> Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-8441337619956017982015-07-23T16:43:00.000-07:002015-07-23T16:50:15.789-07:00Towards a DITA OT Port for FreeBSD -- But First, The LarchCorresponding to a beginning of a development of a personal business plan, formally starting today, I've set aside my own edition of the [plug start] <a href="http://amzn.to/1ekudok">Samsung <i>Galaxy S 8.4</i> Tablet</a> -- an <i>Android</i> tablet -- and its seat-friendly, tabletop-friendly, all-around outdoors-friendly <a href="http://amzn.to/1TUXlT8">Griffin <i>All-Terrain</i> case</a> [plug end] -- furthermore, leaving aside the <a href="https://evernote.com/">Evernote</a> app -- likewise, to sit down at my <a href="https://www.freebsd.org/">FreeBSD</a> notebook -- for a short time -- indoors. It's a kind of a "Pivot day," in my own small, individual corner of the world. I've subscribed to <a href="https://www.safaribooksonline.com/"><i>Safari</i> Books Online</a>, and have begun to develop an ongoing books list.<br />
<br />
In beginning to read one item in that list, I've queued up what is my first book to read about the <a href="http://dita.xml.org/">Darwin Information Typing Architecture</a> (<a href="http://dita.xml.org/">DITA</a>), in my own Safari books queue, namely the text: <a href="https://www.safaribooksonline.com/library/view/dita-best-practices/9780132374323/">
<i>DITA Best Practices: A Roadmap for Writing, Editing, and Architecting in DITA</i>.</a><br />
<br />
Corresponding to that new books subscription, yesterday I'd begun developing a draft edition for another 'blog article -- that article, focusing about <a href="http://dita.xml.org/">DITA</a>, as in developing a concept of <a href="http://dita.xml.org/">DITA</a> architecture and <a href="http://dita.xml.org/">DITA</a> in applications. That was in using the <i><a href="https://play.google.com/store/apps/details?id=com.beanie.blog">Blogaway</a></i> app (<a href="https://play.google.com/store/apps/details?id=com.beanie.blogaway"><i>Pro</i> edition</a>), on my tablet. I'm afraid it may as well remain in an unpublished <i>draft</i> edition, that article. Candidly -- in no short time after I've signed up with the <a href="https://www.safaribooksonline.com/"><i>Safari</i> Books</a> subscription service and begun reading about <a href="http://dita.xml.org/">DITA</a> -- presently, it's developed from an academic pursuit into a project idea. Likewise, it's such that I'd like to share about, as a project idea.<br />
<br />
Of course, a project would not be able to take up a life of its own, in such short time. Beside the introduction that I'd tried to develop, in <i>that unpbulished 'blog </i>article<i>, </i>yesterday, but in a shorter sense of overview<i>: </i>Personally, I have some albeit limited knowledge about technical writing -- as namely with regards to a small number of document formats, such as the <a href="http://www.docbook.org/">DocBook</a> SGML DTD and <a href="http://www.docbook.org/schemas/5x.html">DocBook 5</a> RELAX NG XML schema. I'm fairly well familiar with XML, more broadly, as a markup format.<br />
<br />
Previous to yesterday, I'd read a little bit about <a href="http://dita.xml.org/">DITA</a>. In a sense, I'd thought it seemed like a kind of a <i>cheerful little ray of sunshine</i> about narrative XML documentation formats, in broad -- a topic that there might not seem to be too many <i>rays of sunshine</i> about, typically. Candidly, on reading only some little about applications of the DITA schemas -- furthermore, in my being familiar with a style of hypermedia markup conventions as developed in <a href="http://www.docbook.org/">DocBook</a> -- I was a little put-off about some of the conventions of XML syntax developed in <a href="http://dita.xml.org/">DITA</a>. Mainly, there are the syntax and semantics of <i>linking</i>, in DITA information sets -- more specifically, a small number of elements and attributes in <a href="http://dita.xml.org/">DITA</a>, such that those elements and attributes may serve to provide "hooks" for <i>content replacement</i> in <a href="http://dita.xml.org/">DITA</a> processing models, as I've now begun to understand-- in a sense, those confuse me otherwise. I think there's a substantial difference in how <a href="http://dita.xml.org/">DITA</a> develops a concept of <i>hypermedia linking</i>, contrasted to the primarily ID/IDREF oriented hypermedia linking model in <a href="http://www.docbook.org/">DocBook</a>. I don't personally find myself able to "Leave it all to the editing platform," either -- my not being able to assume any manner of an opacity about the DITA markup format -- as I'm fairly certain that I may be editing a <a href="http://dita.xml.org/">DITA</a> markup file in a console-based text editor, at some point in time.<br />
<br />
So, although those features of the <a href="http://dita.xml.org/">DITA</a> markup schemas may be such that I may find difficult to understand -- at least, at either of a <i>first</i> or <i>second approach, </i>in study -- now that I've found more of a friendly documentation about <a href="http://dita.xml.org/">DITA</a> and reviewed a couple of DITA document source trees, I'm fairly certain that I should be able to learn to proactively adapt my own hypermedia knowledge to adjust to the <a href="http://dita.xml.org/">DITA</a> document formats, even inasmuch as with regards to extending <a href="http://dita.xml.org/">DITA</a>.<br />
<br />
It's on that note, then, that I am still trying to write around the "Long leap" of the following tasks, as I can forsee in my own "Next nine yards" about <a href="http://dita.xml.org/">DITA</a>:<br />
<ol>
<li>Installing Java on my own <a href="https://www.freebsd.org/">FreeBSD</a> notebook, with work-log, notes, and documentation references correspondingly</li>
<li>Installing the <a href="http://www.dita-ot.org/">DITA Open Tooolkit</a> Tools onto the same notebook, likewise with a set of corresponding notes and references</li>
<li>Likely beginning at least a local project for creating a <a href="https://www.freebsd.org/">FreeBSD</a> port of <a href="http://www.dita-ot.org/">DITA Open Tooolkit</a>. This <i>task</i>, ultimately may entail a communication and further coordination with the <a href="https://www.freebsd.org/java/">FreeBSD Java(R) Project</a>. As such, it's nothing I may approach in any of a <i>too casual</i> regards. Not to say overmuch about my own opinions of Oracle's style in commerce or software development -- however contrasted to the <i>novel goodwill</i> style of approach, as originally developed by Sun Microsystems -- I think Oracle's left me with a little bit of a bad impression, as to Oracle's position reportedly ever disfavoring developments in free/open source software (FOSS) namely in defense-oriented projects, and perhaps Oracle's own lack of information, as such, candidly. </li>
</ol>
So, personally, I'm not a big fan about Oracle, and I'm not altogether certain if there is any broad Java developer community, any more, outside of Oracle ... and FreeBSD, and a small number of enterprise web portal projects. The vibrant community that had developed around Java, during Sun Microsystems' management of the development of the Java programming language -- would it be too naive, to draw a metaphor of <i>fracking</i>, as for how that changed when Oracle acquired Sun?<br />
<br />
The Oracle Java(R) launcher thing on Microsoft Windows 8.1 -- though it's cute, certainly -- it doesn't really change that impression, so much, not to my own point of view. Candidly, I still expect Oracle to be the monolithic corporation largely focused about a database platform, such that I've -- for a long time -- estimated of Oracle as a company. I don't think it makes any less of an Atlas-like shadow, with Oracle having acquired Sun. With Oracle now having demonstrated their own obvious lack of information with regards to FOSS and defense systems software, I might wish to trust Oracle to be moreover a <i>Blind Atlas</i> -- very worrisome, I think, worrisome if Oracle would set about to "Make New The Things."<br />
<br />
So, knowing of a particular manner of a corporate monolith as such, looming up a little ways northward in California, and with some much of a knowledge of a broader world, I'm afraid I'm unable to join in the local Cool Team Parties. Even in avoiding any manner of a too locale-centric manner of a perspective about software development, but it still kind of "Creeps me out," about Java(R), if Oracle is really all the Enterprise as may I candidly estimate it to be.<br />
<br />
If it may be possible to limit one's owns views to a sense of plainer principles, however -- inasmuch, to not make overmuch of a consideration as with regards to superstitions -- sure, Oracle might not be all of the scarily opaque commercial software institution that I might think of it as. Focusing if simply on the ongoing free/open source licensing of any products previously developed or adopted by Sun Microsystems -- such as Berkeley DB, for instance, in its free/open source licensing options -- there's a matter of software licensing, orthogonal to any company's own apparently political positions with regards to software development models.<br />
<br />
Thus, there's a foot I can find, in my own sense of knowledge about software now licensed by Oracle -- a foot, at which I may be able to disembark from my own concerns with regards to Oracle's policies. If it could seem as though Oracle could become such as, "Like <i>Old Microsoft</i>, but a thousand times worse," there's what I'm worried about. Regardless, the free/open source licensed by Oracle as free/open source software, that much of software might endure any such shift -- as much as of any free/open software licensed originally by Sun Microsystems.<br />
<br />
So, in something of a sense of an organizational view, maybe the goodwill "Vibe" that Sun developed could be just enough that it may endure even the acquisition by Oracle -- however far any developers and managers who would've been the parties directly developing such goodwill, and about a programming language moreover, however far "The Java Original Team" in and beyond Sun, may have been put off and away from Oracle. <br />
<br />
If I'd thought as though the film TRON: Legacy may have been all of a metaphor about Apple, perhaps it could as well be a film interpreted as if about any other Silicon Valley empire of an enterprise -- Oracle, perhaps as like a CLU character nearly making Java break out so much that it would break apart?<br />
<br />
I don't find myself able to ignore the apparent social implications of Sun's acquisition by Oracle -- it seeming even more worrisome, after Oracle tried to toss some mud to the US DoD, as denoted in an article once reported to Slashdot, mud as if about free open source software. The "Old Microsoft 2.o?" theme, thusly, it began in my own simple point of view about Oracle.<br />
<br />
Clearly, Oracle "Owns" Java(R) as a trademark, today, but -- not even after the acquisition of Sun -- Oracle certainly does not own <i>the history of</i> the Java programming language. Thus, there's a broader sense of context, and nothing radical, about <i>not looking too far</i> into <i>the Oracle</i>.<br />
<br />
So, maybe there's any plan for Java integration in LLVM. I'll have some research to develop, before I myself may develop any further work about Java(R) on a FreeBSD(R) operating system. <i>The Brand Wars not begun again, they have not.</i>Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0tag:blogger.com,1999:blog-7019212358513681056.post-73845009868211680462015-07-17T17:34:00.000-07:002015-07-18T19:59:25.959-07:00Towards a Multiply-Linked List model for Storage and Retrieval of Trie Structures {S,P,O}<div class="blogaway-section"><p><b><i>Ed. Note:</i></b><i> Clearly, this web log format does not serve to present an ideal format for presentation of mathematical notations. The syntax of the following article may be difficult to read. It should be reformatted, subsequently, to something more immediately legible in its web-facing presentation.</i><br/>
<br/>Earlier this month, I'd begun developing a UML model for a graph-oriented application system, namely after a matter of small confusion with regards to differing board support information about the Cryptotronix CryptoCape circuit board. The design, as such, began to by-in-large diverge from the original concern as with regards to <i>logical</i> and <i>physical modeling</i> of electrical systems. It's become, it rather seems, a design for albeit a simplistic manner of graph-oriented application framework, extending of a FreeBSD operating system<br/>
<br/>As one of the core features in that design -- as yet, the design as such being represented in a <i>by in large</i> incomplete and unpublished document, but here might be a start of some of a literate documentation about it -- the design features a sort of a simple, abstract binary tree model for storage of <i>trie</i> formatted data, as of -- in a manner or description logics -- a data format {S,P,O} for resources S and O being, respectively, a <i>subject</i> and an <i>object</i> joined of a predicate P. This format, of course, is by in large influenced of the design of the Resource Description Framework (RDF). <br/>
<br/>The abstract binary tree model proposed in the same presently unpublished design, the same tree model, in its format, is essentially of a generic format like so: {{S,P}, {P,O}} <br/>
<br/>In a sense, perhaps it may seem like an arbitrary design concept, as here it would not be immediately correlated to any logical or mathematical models as with regards to data structures and computing. Of course, the author is at least vaguely familiar with a generic, diadic format of assembler instructions.  The original design, itself, may be much like unto a cafe placemat sketch but produced in UML format.<br/>
<br/>Of course, the design may evolve over time -- much to the author's own sense of uncertainty, as to whether or not to publish the initial design resource, presently. Essentially, it's a multi-layered design -- developing some of a service-oriented view, in parallel to a design for a simple graph information service, in a manner focusing on CORBA and some of a network security model. In each essential layer, however, the design is by in large conceptually naive, and not as yet completely developed to any single proof of concept. In some of a view of  a competitive software development community, it could seem like the design is far too much of a ripe manner of chum for a sharkey web, thus it's presently unpublished.<br/>
<br/>The storage of the {{S,P}, {P,O}} model would, itself, be one feature to address of the design -- here unnamed -- in any implementation.  The generic model does not, in itself, provide any detail as to how it  may be best implemented. Broadly, and albeit without any sense of a single usage case, an application could maintain exactly three tables, of each of A={S,P}, B={P,O} and M={A,B}.<br/>
<br/>Each of A,B, and M, hypothetically, could be implemented as a sequence value -- in Common Lisp, optionally an adjustable array -- each contained within some sort of an encapsulating object -- in an abstract sense representing each of A, B, and M as a table each implemented with a vector. In addition to each of the binary object values in each relation A,B, and M, the implementation may suffix a numeric index value onto each respective table -- thus, A' = {S,P, N_A}, B' = {P, O, N_B}, M' = {N_A, N_B, N_M}. <br/>
<br/>In something of a list-oriented approach, alternately, each of the tables may be given an index value N — fig. 1<br/>
<br/>A" = {S, P, N_B, N_A} // Including N_B in A"<br/>
B" = {P, O, N_M, N_B} // Including N_M in B". Redundant 'P'<br/>
M" = {N_A, N_B, N_M} // The "End" relation<br/>
<br/>Thus, in constructing any complete {S,P,O} relation for any S, any row of B" could be retrieved in beginning at a row in A", and any row in M" from a row in B", in such an implementation. This suggest a manner of a <i>singularly linked list</i>.<br/>
<br/>In refactoring the design into a doubly-linked list model, A" and M" may be retained — the refernce to P, made exactly once in A" — thusly, fig. 2<br/>
<br/>A" = {S, P, N_B, N_A} <br/>
B"' = {N_A, O, N_B} <br/>
M" = {N_A, N_B, N_M}<br/>
<br/>In that design, M" would be essentially redundant, though allowing perhaps for an {S,P,O} to be referenced as a unique object independent of A" and B"'.<br/>
<br/>In a more normally list-oriented design, towards a manner of a single-linked list — fig. 3<br/>
<br/>A"" = {S, N_B, N_A}<br/>
B"" = {P, N_M, N_B}<br/>
M"" = {O, N_M}<br/>
<br/>Towards a manner of a multiply linked list — fig. 4<br/>
<br/>A""' = {S, N_B, N_M, N_A}<br/>
B""' = {P, N_M, N_A, N_B}<br/>
M""' = {O, N_A, N_B, N_M}<br/>
<br/>Once the initial design is refactored onto a list-like data model -- as reminiscent of the (CAR,CDR) semantics of lists in Common Lisp -- then the design begins to assume a sense of applicable normalcy. For an application system, the {A""', B""', M""'} model might represent a manner of a most effective baseline data model design, it allowing for a search for any of {S,P}, {P,O}, {S,O}, and {S,P,O} sequences, essentially without any further data structure definitions in the table itself. <br/>
<br/>In developing a manner of a meta-semantic view of the last table design, in the previous: Essentially, it describes a model in which regards — fig. 5<br/>
<br/>Given: {M_1,.. M_N}<br/>
Define tables {M_1, M_N} ...<br/>
* as that each table M will be defined with N+1 columns<br/>
* such that in any row n of a a table M: an index value N will be defined in the row, such that N = n<br/>
*  furthermore, in any row n of a a table M: Each of {M_a, .. M_b} will be referenced, for a != n, b != n<br/>
<br/>This meta-semantic model allows for indexing and search across all elements of any single set type structure S = {M_1, ... M_Nx}  <br/>
<br/>So, it's probably as well that the original design document has not yet been published. To resolve the original design document of all its distinct naivete in design, the design document itself should need to be suffixed with so many considerations of the technical qualities of any single implementation, it may serve to render the original design document essentially obsolete. <br/>
<br/>Not as though to leave it to collect dust for all eternity, here's the first textual design document about an as-yet unpublushed, graphical model of a graph OS.<br/>
<br/>Continuing this article as from a description of generic data structures, towards a concept about application, it may be noted that the table structure described in fig. 4 may be initialized from any set of trie structures {S, P, O}. Some of the columns in the table would be populated not of data values represented in the original input structures, but rather as to provide for a small number of "Procedural shortcuts" for optimization of searches onto each table  of {S,P,O}.<br/>
<br/>Of course, once the table as illustrated in fig. 4 would be initialized of any single table of {S, P, O} if any single update would be made as effectively onto any row N of the original table, then any number of additional data stuctures — such as would be created during the table's initialization — would likewise need to be updated, specifically for any changes in reference across any single, original {S ,P, O} data structure. <br/>
<br/>Perhaps towards a more structurally modular design of the tabular model illustrated in fig. 4, the supplemental reference fields as added to fig. 3, in this design, may be essentially separated such as to create one additional table structure, removed of redundant refences  — thus, fig. 6<br/>
<br/>A_x = {S, N_B, N_A}<br/>
B_x = {P, N_M, N_B}<br/>
M_x = {O, N_M}<br/>
C_x = {N_M, N_A} // {O,S} in {S,P,O}<br/>
<br/>The supplemental table, C,  need not include <i>row index</i> values. That table would not provide original reference values, but would be maintaintained as for purpose of optimization of supplememtal searches across direct {S,O} references in the table of {S,P,O}. For searches singularly onto {P,O} in {S,P,O,} the table B_x may be queried. For searches singularly onto {S,P}, the table A_x provides a sufficient set of data fields.<br/>
<br/>Certainly, fig. 6 may serve to present an optimal table structure, at least across the set of table structures described in fig. 1 through fig. 4 and fig. 6.<br/>
<br/>In the methodology of storage/reference encoding illustrated as in fig. 6,  a <i>table group</i> structure is illustrated. This may be juxtaposed to a singular table structure, such as may be implemented onto an SQL relational database -- fig. 7<br/>
<br/>N_a = {S, P, O ,N_N}<br/>
<br/>In the <i>table group</i> methodology for storage/reference encoding, structural data field elements are stored independent of other elements. This <i>table group</i> methodology may be more closely analogous to data structures within a Common Lisp implementation, juxtaposed to data structures of a conventional SQL relational database implementation.<br/>
<br/>In a manner of further refining the table group illustrated in fig. 6, the tables A, B, and C may be removed of cross reference values, then applied only for storage and identity of data values for each element of {S, P, O}. Data references as of {S,P}, {P,O}, and {O,S} would all be stored in separate tables, independent of the individual data object tables -- fig. 8<br/>
<br/>A_y = {S, N_A}<br/>
B_y = {P, N_B}<br/>
M_y = {O, N_M}<br/>
C_y = {N_M, N_A} <br/>
D_y = {N_A, N_B}<br/>
E_y = {N_B, N_M}<br/>
<br/>The author has, to now, assumed it would be a known axiom that each of the N_fum <i>row index</i> values, in each table, would be an unsigned integer value unique in the respective table. Each N_fum value, correspondingly, may be interpreted as representing a manner of structure-relative reference address for each such data value.<br/>
<br/>If this methodology for table-oriented data storage would be extended logically as with regards to  CMUCL <i>widetag</i> and <i>lowtag </i>values, individual tables within the model may be referenced of, each, the respective <i>widetag</i> or <i>lowtag </i>interpretation of each data value's type. With the respective <i>widetag</i> and <i>lowtag</i> values being normatively documented, as for portable applications, the data encoding model, itself, would not be uniquely applicable of the respective Common Lisp implementation in which it would be applied.<br/>
<br/>The CMUCL <i>widetag</i> and <i>lowtag</i> values, as effectively forked in SBCL -- directly, as forked along with the broader CMUCL <i>source tree</i>, from the time of the origin of the fork -- the original CMUCL <i>widetag</i> and <i>lowtag</i> values are defined as a feature of the type system in CMUCL.<br/>
<br/>As an implementation of Common Lisp the Language, 2nd Edition (CLtL2) CMUCL -- as well as SBCL, and the small number of Common Lisp implementations in addition to SBCL and CMUCL --  essentially, every CLtL2 implementations has produced, in each distinct species of CLtL2 implementation, a manner of a semantic approach in implementing the system of data types developed and standardized in in CLtL2. Focusing on the CMUCL implementation, the semantics of the implementation might be observed as around the CTypes system developed in CMUCL, furthermore as with regards to definitions of data types and functionally mechanical forms, such as developed in the CMUCL compiler.<br/>
<br/>The CMUCL compiler's system of type definitions -- insofar as inherited by SBCL, if not furthermore adapted in the forked codebse -- the compiler's system of type definitions described, specifically with regards to SBCL, in an article by Paul Khuong: <a href="http://pvk.ca/Blog/Lisp/hacking_SSE_intrinsics-part_1.html"><i>Hacking SSE Intrinsics (Part 1)</i></a> (2009) with something of a <i>reprise</i>, in the article <a href="http://www.pvk.ca/Blog/2014/08/16/how-to-define-new-intrinsics-in-sbcl/"><i>How to Define New Intrinsics in SBCL</i></a> (2014).  The former of the two articles presents something of functional view of the compiler's types system, extending of an extension of the types system for an implementation of the Intel SSE instruction set, in SBCL. <br/>
<br/>With regards to documenting the implementation in SBCL, certainly, each functional form -- that is to say, each function and macro -- and each data value, as illustrated in either of the two articles, could be more comprehensively described with, of each, a single reference page. Each reference page could be referenced, furthermore, from a  broader documentation as to describe any manners of semantic correlations among the respective forms, in the implementation of the compiler specifically in SBCL. Although that would surely make for an interesting study, it would present a broad diversion from the topical focus of this article at DSP42. <br/>
<br/>In regards to the compiler implementation in CMUCL, and furthermore in SBCL, both implementations each define a set of data types, such that may be applied in a manner essentially internal to the compiler of each of the two implementations. Those data types may be observed for their definition and application, as around the <i>widetag</i> and <i>lowtag</i> values defined in each implementation.  <br/>
<br/>Defining a small subset of the complete set of <i>widetag</i> and <i>lowtag</i> values -- the latter, as would be defined in any single revision of each of CMUCL and SBCL -- essentially, a subset of <i>widetag</i> and <i>lowtag</i> values may be defined, such that the subset would denote the set of <i>widetag</i> and<i> lowtag</i> values defined for "User visible" data types -- i.e. a set of data types, such that might be reasonably expected as to be encountered of data values in portable user programs extending of the respective implementation. This article will denote that subset as it representing a set of <i>types of user object</i>.<br/>
<br/>That subset of <i>widetag</i> and <i>lowtag</i> values may then be applied such that -- for any single such <i>type of user object</i> -- firstly, the <i>widetag</i> value then secondly the <i>lowtag</i> value may each serve as an effective key value onto a single data storage table, such that the format of the respective data storage table may be of a format conducive to encoding and decoding of objects of such type, in a manner of a data serialization model.  Such data serialization model may be implemented as to develop an <i>ad hoc</i> encoding directly onto files, or as to develop a set of table structures and procedural forms in utilizing an existing database management system, essentially as for purposes of data serialization from within any single instance of the respective Common Lisp implementation. <br/>
<br/>In regards to serialization of structure objects, condition types, and standard classes furthermore, each respective type's <i>class OID</i> may serve as a fundamental key reference -- eliding, momentarily, concerns as with regards to  class names -- in a model then allowing for a manner of selection as to which slot values of any single class would be serialized into persistent storage, and which slot values may be initialized simply in interpretation of persistent data.<br/>
<br/>Of course, this does not describe all of the details of an object persistence model. Though it may serve to provide something of a guiding concept with regards to a deign, as such, onto either or both of CMUCL and SBCL -- not a furthermore portable design, immediately -- there may be some additional concerns that may be addressed, as with regards to:<br/>
persistent "linking" of each initialized objects to the object's persisted formfurthermore with regards to making references to objects' serialized forms without preventing garbage collection of objects that would be otherwise unreferencedand thirdly, deallocation of storage blocks on garbage collection of previously <i>persisted </i>objects. In albeit a naive sense, perhaps it might be more efficient to develop a <i>memory mapped file </i>model for the SBCL object system, such that -- in so many memory-mapped file/data areas -- an underlying operating system would immediately store any changes in the respective memory-mapped <i>file/data areas</i>, such that the updated <i>data area</i> might late be reinitialized of its filesystem mirror. This may serve to allow for something of a manner of failover, in a naive sense. With regards to optimization in the underlying file mirror, perhaps it might behoove such a software design, however, to make reference towards methods of filesystem journaling, such as with regards to the copy-on-write methodology  implemented in UFS journaling on FreeBSD.  In such regards, perhaps a broader goal may be defined as to develop a Common Lisp systems model extending immediately of FreeBSD.<br/>
<br/>In regards to the data persistence model denoted in the previous outline, certainly a consideration for the design of such a model is likewise reflected in the previous design discussion as with regards to the <i>table group</i> structures for the {S,P,O} data type.<br/>
<br/>Not as though to try to make such a project idea to seem too specifically grant-friendly, the prospective instance of a <i>Common Lisp on FreeBSD</i> systems model may be applied as for purposes of knowledge representation and knowledge sharing, effectively in any normative context to which an RDF graph may be developed -- ostensibly, even as to present a graph type model of operating system resources, such as mandatory access controls (MAC), on any single host or network, thus as to develop a management layer onto FreeBSD MAC data types -- whether or not, alternately, in as to develop any single, ostensibly peer-reviewed semantic model of the material sciences, or manufacturing, or commerce, for transparent application in communications and infrastructure support systems, at any single scale of support for material activities of a society or smaller community.<br/>
<br/>Not as though to paint with any too broad a brush, simply the very nature of knowledge modeling and knowledge sharing may be, likewise, of the very nature of the sciences. The material sciences being, furthermore, to the very essence of material technology, thence to the nature of material industry, thence to manners of material commerce, it may be possible to support development in all of industry and commerce, in supporting simply a development of science and technology in any single manner of normative social environment. <br/>
<br/>Of course, in this broad view, a concept of intellectual property does not take up any clear or obvious place, neither any concepts of data assurance. <br/>
<br/><b><i>Ed. Note</i></b><b>. </b><i>The following section of the article was begun before the article diverged towards a more comprehensively CMUCL-like encoding for data values.</i><br/>
<br/>As with regards to a question of application, <i>How many </i><i><i>table groups</i></i><i> like fig 6. or fig. 8 may need to be created</i>, in any single application? and a further question, How may of each such <i>table group</i> may be most effectively stored and accessed for reference, in an application?  Considering some of the semantic qualities of RDF Schemas, as with regards to definitions of RDF classes and RDF properties, moreover considering the Web Ontology Language (OWL) as a specialization of RDF extending the essential class/property model, moreover with OWL adding a distinct <i>Individual</i> resource type to the abstract RDF data space, it may be feasible to implement a table group as illustrated in fig. 6, such that a single table group would be defined for every expressly defined OWL Class, likewise for each of OWL:Class and RDF:Class, as to provide an index of instances of the respective class. This naive "Table group per class" methodology may be further refined, if towards any singular application, as with regards to concerns of subsumption relations in RDF schema and other orthogonal considerations.<br/>
<br/>In something of a meta-semantic sense, considering the broad question of how many of a table group — as illustrated in fig. 6 or fig. 8 — may be "Well implemented," in an application, logically the question may be considered as in juxtapositoon to an orthogonal question: To what manner of a context may any such table group "need to be" singularly initialized and referenced, as a representation of any single table of {S,P,O}?<br/>
<br/>Offhand, a number of contexts may be defined — certainly, in no manner of a logically exhaustive list — in presenting at least a naive response to such a question:<br/>
<br/>• <i><b>Application</b></i> as <i>container</i> of <i>graph data sets</i><br/>
• <i><b>Graph data set</b></i><i> </i>as <i>container</i> of <i>tuple</i> or <i>trie</i> references, such as of all references of a format {S, P, O} within any single <i>graph data set</i><br/>
• A <b><i>Class</i></b> A as a <i><b>class</b></i> reference context for tabular indexes of instances of Class A <br/>
• A <i><b>Class</b></i> B as a <i><b>type</b></i> reference context, for tabular indexes of instances of Class B and C, for C being a <i>subclass</i> of B<br/>
<br/>In this naive model, a <i>class</i> or <i>type reference context</i> may be defined for each RDF, RDFS, or OWL class both defined and being applied in any single graph data set, in any single application. <br/>
<br/>A <i>class</i> or <i>type reference context</i> need not be assigned as though exclusively to each single class. The symbolic name of a class — as in reference to cl:class-name, a function portably returning a symbol type value — as a symbol type of object, a class' name may be applied likewise as an associative reference, unique in any single table of <i>graph-local </i>and/or <i>application-local</i> data tables.<br/>
<br/>[RDF Schema] develops a type system for RDF Literal values, essentially in extending of XML Schema Datatypes. <br/>
<br/>In a model for interpretation of RDF data sets in Common Lisp, each XML Schema Datatype may be intepreted as to derive a corresponding data type in Common Lisp, together with a function for each of marshalling and unmarshalling an object of each respective type onto a character stream. Such an implementation, in a functuional regards, may resemble the CMUCL Ctypes model. <br/>
<br/>Depending on the characteristics of a Common Lisp encoding such that may be defined for any single RDF Literal data type, it may be advisable to consider revising the table group illustrated in fig. 6 or fig. 8, such as to allow for a specialized encoding in O onto {S, P, O}. <br/>
<br/>Of course, in a uniquely table stored model such as of an SQL database, then for each tabular reference as in fig. 6 or fig. 8, It may be advisable to encode a value representative of a type identity — such as of a class name, or an implelemtation-specific albeit non-portable value such as a classoid, in CMUCL or SBCL, such that may be applied as a symbolic reference to any type definition data provided of or in relation to any single class definition. A class identity, simply, may be applied for purpose of <i>table selection</i> in row index <i>dereferenfcing,</i> such as in any manner of a revision of the table set model denoted in each of fig. 6 and fig. 8.<br/>
<br/>This article essentially begins to describe a model for an implementation of a data persistence model, broadly, for objects of any arbitrary number of types, inasmuch as may be applied in {S,P,O} references in any arbitrary application. Towards developing an example onto a literary domain, this model may be <i>furthermore</i> developed as for purpose of maintaining a graph formatted registry of bibliographical ínformation structures, such that may be furthermore applied as in an independent bibliográphical management application within an academic content development system, or applied as an integrated feature of a graph-oriented information modeling platform — in the latter, as for purpose of creation and editing of bibliographical annotations onto graph object references, as to provide a framework for peer review of assertions in graph models.</p></div><br/>Anonymoushttp://www.blogger.com/profile/07813030018616878350noreply@blogger.com0