MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"gapcontinue": "Resume_FAQ",
"continue": "gapcontinue||"
},
"warnings": {
"main": {
"*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
},
"revisions": {
"*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
}
},
"query": {
"pages": {
"2095": {
"pageid": 2095,
"ns": 0,
"title": "Redvant",
"revisions": [
{
"contentformat": "text/x-wiki",
"contentmodel": "wikitext",
"*": "<html><style> .mw-headline {color: black !important;}</style></html>\n<div style=\"font-weight: 600;background-color: #fbfcf8; color: black;\">\n<blockquote><br>\n{{TOCleft}}\n= Purpose =\n\nThe original purpose of the <b>Redvant</b> moniker was to name the separation of some product lines from their domain space aspects. Products developed under its rubric can be compiled for operation strictly on the basis of the FOSS or COTS software upon which they are based without any integration with DS though in some cases this can gut the app if presentation of a DS feature was its purpose. A non-DS application can then supply a new purpose. My <b>tl;dr</b> line and other product lines sold on stores may thus have core function repurposed to such new apps without committing to DS, DCP, etc..\n\nHowever this separation is only in evidence at the time of its application in GC* projects and this separability is not discussed outside of such projects but it will be evident in the supporting implementation.\n\n*<span style=\"font-weight:normal;font-size:8px;\">General Contracting (Rate Chart)<span>\n= Précis =\n<span class=plainlinks>\n'''Redvant''' , or ''''<dcms'''' (dcms-bra), is a collective term for software including react and [https://haskell-servant.readthedocs.io/en/stable/ <font color=lime>servant</font>] within a DCP context and packaged as a reusable resource demonstrated in various applications such as the tl:dr and by the KEE. \n<div style=\"position: relative;left: 50px;\">\n\"red\" could be\n<blockquote>\n react, redis, light in the ~700 nm range, a proper name as in red5, the parfume, lil riding hood, Malcom X, Simply, etc..\n</blockquote> \nand \"vant\" is just from haskell-servant.\n</div>\n<div style=\"font-weight: normal;background-color: #fbfcf8; color: black;\">\n\n= Substance =\n<html>\n<blockquote><span class=plainlinks>\nIn the original remit, use of Apache </html>[https://isis.apache.org <font color=lime>causeway (formerly ISIS)</font>]<html> or other fat DDD pkg was intended later in fulfillment of our overall DDD product line engineering (as 'redvantis'). Some enterprise users may prefer a java basing of ISIS or an ERP core and this is still an option for GC projects.\n<p>However, subsequently, I decided a package I first ran into in the telematics work in '14/15 could be repurposed as a basis for <b><u><a href=https://redvant.ai-integration.biz>product line engineering</a></u></b> and Redvant. <a href=https://clafer.org>Clafer</a> is essentially forked for this purpose here, its repos forked within 6 mo of the Sept. '23 update, which was the first activity on it in some time. It appears to be preserved and maintained but not actively developed which is fine as I intend the baseline here to veer strongly toward actual product line engineering of actually fielded apps and the redvant mission as well as DS DDD generally making it essentially Clafer for DS and my product lines.\n<p>Although I mean to keep local clafer tools close to the original on the common code intersection, there will be some rebranding to Redvant instead of Clafer to make clear the diff between just clafer the domain modeling lang and its use here.\n</blockquote></html>\n\n= Visibility =\n\nThis is the sole exposition at this scope and will remain so. Technical detail will be in an eponymous § in the Books DCMS volume.\n<br><br>\n</blockquote><html><img width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=REDVANT></html>\n</div>"
}
]
},
"1562": {
"pageid": 1562,
"ns": 0,
"title": "References",
"revisions": [
{
"contentformat": "text/x-wiki",
"contentmodel": "wikitext",
"*": "[[Resume|To Flash Landing]]\n\n<b><font size=4>If ...</font></b><br/> \nYou are considering me for work with a nominal hourly wage rate of $100 or €70 or thereabouts¹, please ignore the below and send a message to <b>juan@acm.org</b> and I will put you in contact with current and recent clients.\n<br/>\n<br/>\n<b><font size=4>In general ...</font></b><br/> My typical working relationship lasts about a year or two, some are a matter of days or weeks and I worked as a contractor with IBM over about a 7 or 8 year period. Having prior clients and coworkers constantly contacted by possible new ones would not make sense. In a spirit of reason and reciprocity I ask that if you are not willing to act as a reference for a period of a year after satisfactory completion, receiving calls like the ones you intend to make, and are not offering a market wage for my skill and experience level¹,², then please DIY:\n<br/>\n* There is an older references Word doc in http://ai-integration.biz/pub/references.doc .\n* More recent references can be supplied, <b>at the appropriate time</b>.\n<br/>\n\n<b><font size=4>Otherwise ...</font></b>\n<br/>\n* You are welcome to use the Word doc above or do any other independent checking.\n* I find the whole references thing unenlightened:\n# It's demeaning for the worker and unequal. Do you provide references from former co-workers in your enterprise(s)?\n# Doesn't really prove anything, \"past performance is no guarantee of future success\".\n# There are superior means for reducing your risk such as deferring full delivery of sources and payment until function has been demonstrated thru the web, delivery of binary with expiry, ordinary liability insurance³, etc.<br/> This is an area of interest for me in regards to automated IT labor markets so may be developing further in the context of these domains.\n# It's like the testing thing, if you don't have whatever it takes to make this judgment on your own, structure an appropriate deal logistics, I'd rather you just pass to another worker.\n<hr>\n¹ Offsite rate $40-60 USD/hr. before [http://www.bls.gov/oes/2008/may/oes_nat.htm#b15-0000 2008-11], Sr. SW/Systems Engineer would be the relevant job description except that I'm usually performing other functions as well and the BLS statistics are for employees not contractors, so I don't go below this floor.<br/>\n² A uniform nominal €50 per hour after 2009-11-02.<br/>\n³ At standard current commercial rate per $1 M liability."
}
]
}
}
}
}