sw00271rtj-status.update

Regarding This Journal - E5                      
 -
                                             R T J (links/contents)


 -
 18MAR07 Status Update


 Although the updating of this Salchert's Weblog is far 
 from complete, my progress has beeen substantial.  I
 will be using (except where it is not practical to do so)
 the font size three AOL's program herein has.  If the
 darker of the two fonts seems a bit large, as to me it
 does, I've chosen it because that font's size two seems
 too small.  Better to display an easily readable font.
 -
 Had forgotten I had begun a series of entries entitled:
 Regarding This Journal.  So, when its presence showed,
 I got to thinking I ought to set up a link entry for it.  That
 only a few presently exist did not ensure there would not
 be many at some time.  This led to changing entry titles
 an "j" codes, and links, et cetera.  I settled on 'jr" for the
 links/content entry, and I changed my code system page
 from "jc" to "jcs".  There is a pure "jc" entry: it lists the
 2006 contents of this journal/weblog.
 -
 Moments ago I finally tracked down a site on which was
 a clear explanation of the difference between URL & URI.
 I also learned there that URL has been deprecated.  URI
 is now the preferred term: it means  Universal Resource
 Identifier as opposed to:  Universal Resource Locater.  
 I, therefore, replaced "URL" with "URI" in several places.  
 It may be somewhat like exchanging a tit (URL) for a  
 tat (URI), but tat's where it's at.
 -
 Anyhow, here is a re-explanation:  I have an "http" URI, 
 whose primary section is "journals.aol.com/" followed by
 a screen name section followed by what I am currently
 using to identify my journal's location.  The next sections
 required by AOL's configuration for more exactly IDing
 the location of as-yet-not-evident information are:
 "entries/2007/03/18/".  The section following these is
 determined by a journal's author.  Until I concluded I
 needed logical brief URI's, some of what I chose to
 insert in that next-to-last section was too unwieldy
 in the extreme, even if they were logically descriptive.
 I saw that anAOL-assigned entry number was always
 present in the final section, but that the number in one 
 entry did not guarantee that the next entry's number
 would always be greater by 1.  This was the catalyst
which initiated my moving away from plain language
 codes to codes which included in-order numbering.
 Fine, but I needed to somehow identify the source
 of these numbers and also the meaning of them.  So,
 after some pondering, I chose to begin each of these
 codes with "sw", repesenting Salchert's Weblog.  I
 then thought it best to insert a hyphen after my "sw"
 so as not to intermix it with the entry-proper coded
 information.  I thought about using "e" next, but I did
 not really want to.  I thought about not using any letter,
 but I did not really want to do that either.  In the end I
 chose "p" because it could mean either post or page.
 In this manner "sw" and "p" became my prefixal letters.
 This, however, was insufficient, since no reader of "sw-
 p00001" would ever be able to figure out what that code 
 referred to.  As I did not want to use real words, I knew
 I would need to provide an entry where explanations for
 my codes could be found.  This I have done, but it will
 never be a finalized page so long as my/ weblog exists,
 and I--or some other--is able to / cares to tinker with it.
 Here is the next-to-last section code for that page:
 sw-p00254jcs.  The "jcs" means "journal code system".
 It is among what I call my suffixal letters.  These letters
 are the ones which point to what an entry holds.  They
 do not reveal much beyond a category, but I feel// they
 are sufficient.
 -
 This will zip you to salcherts weblog codes center.
 -

 19MAR07                    Concluding Note
 -
 I know about RDF and OWL but have no clue about them 
 otherwise, and I feel no urge to find out.  I do know and do
 use simple HTML (in a particular format I learned last year
 from someone's site--a someone I am grateful to but do 
 not recall) in the javascript environment provided by AOL.
 -
 I prefer simple HTML.
 -
 Acronyms are used extensively in our world, and early
 this morning while yet in bed, I began pondering the use
 of letter codes in what might be called the URL part of
 a URI.  That pondering evolved into wondering if it
 would be possible to construct--perhaps one already
 exists--an acronym dictionary that would be practical 
 enough to serve as a basis for online letter codes.  I
 almost immediately encountered a barrier because many
 specific letter strings, such as "BAJS" are--just do a
 search and you will see--acronymsfor dozens of
 organizations and businesses and, and--.  Still, a start
 is a start.
 -
 The idea is to create logical, brief, unique URI's, and in
 my case/ the conjunction of what matters to AOL and
 what has come to matter to me, I believe, achieves that.
 I am at "http://" "journals.aol.com".  The sreen name I  
 am using is unlike any other in the kingdom of AOL.  
 These two location facts alone guarantee uniqueness.  
 Yes, it may be that someone else is using the same letters 
 I am to identify his/her journal/weblog/blog's name; but not  
 with the same screen name in AOL.  The URI weblog name 
 I have is only four characters, and it is inherently logical.  It
 was not so when I began my journal.  Am I boasting?  No.
 After all, I say the logic in the URI weblog name I have is
 inherent because it is an acronym rather than a verifiable
 name.  The point of it is: brevity.



Brian A. J. Salchert