Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Government Your Rights Online

Adobe Pushing For Flash and PDF In Open Government Initiative 172

angryrice tips news that Adobe seems to be campaigning for the inclusion of Flash and PDF in the Obama administration's efforts at increasing government transparency and openness. A post from the Sunlight Labs blog is critical of Adobe's undertaking, in part since PDF is often "non-parsable by software, unfindable by search engines, and unreliable if text is extracted." They also say government's priority should be to publish datasets and the APIs to interact with them, rather than choosing how they're displayed in fancy graphs and charts.
This discussion has been archived. No new comments can be posted.

Adobe Pushing For Flash and PDF In Open Government Initiative

Comments Filter:
  • "non-parsable by software, unfindable by search engines, and unreliable if text is extracted."

    I don't believe this is true - I find PDF documents in search results all the time. The consistency and reliability of PDF for forms creation has no real competition. If you hate Adobe, ok, but don't hate PDF 'cause it's beautiful...

    • by hedwards ( 940851 ) on Saturday October 31, 2009 @08:29AM (#29933975)
      I have no problem with PDFs, there are a number of free and commercial applications out there that can work with them.

      Flash on the other hand is absolutely an abomination that must be wiped from the net. They still haven't released a proper version for *BSD and they commonly don't bother with less popular OSes. If they want it to be used for this sort of purpose then they need to get their act together and make it available for all operating environments on an equal basis. Which I don't think they have the resources to do.
      • by Antique Geekmeister ( 740220 ) on Saturday October 31, 2009 @08:39AM (#29934027)

        PDF remains difficult to manage. Like MS Word documents, an incredible amount of resources is wasted in display information rather than actual text or graphical content. Unlike MS Word, they're parseable: but unfortunately like MS Word, the commercial vendor-sold document creation tool (Adobe Acrobat) generates unstable and unreliable content that interacts very badly with other tools. Oddly, the ghostscript created PDF remains very stable and legible, and tools like "PDFCreator" which uses ghostscript creates long-term viable PDF printouts of other document formats. I use it for complex MS Word documents that cannot be handled by other software, even different versions of MS Word.

        Adobe can actually do better with this, and I hope that they will in the future. But it's not stable enough to be reliably indexed or viewable even 5 years in the future, much less 10 or 20 or 100 such as may be needed for legal or historical documents.

        Flash, you're quite right. Unless they open up the source, it has no business as yet another document format.

        • but unfortunately like MS Word, the commercial vendor-sold document creation tool (Adobe Acrobat) generates unstable and unreliable content that interacts very badly with other tools
          Can you be more specific as to what problems you have had using files from acrobat in other tools?

          • by Antique Geekmeister ( 740220 ) on Saturday October 31, 2009 @09:19AM (#29934331)

            Printing documents created in other language versions of Acrobat. In particular, the Adobe Acrobat for German created documents that were not only unviewable in a normal Acrobat viewer, but when used to "print PDF" for MS Word documents, created documents that actually crashed Windows computers. The Acrobat for Hebrew didn't crash Windows with the printed documents, but was filled with layout errors when rendered even by Acrobat Reader, errors that didn't show up in the Adobe Acrobat tool. Much of this may have been fixed with the latest release, but I'm not spending nor suggesting that my peers overseas spend all the money needed to upgrade.

            Getting our colleagues to stop using Acrobat and use _anything else_ to generate their documents, and use PDFCreator to print them as PDF, stabilized the situation enough for us to generate the documents we needed. It didn't provide PDF forms for people to fill out, which was its only flaw.

          • by xjimhb ( 234034 ) on Saturday October 31, 2009 @10:01AM (#29934647) Homepage

            Just recently I had to look at, and print a few pages from, a PDF document. Knowing where it came from, a corporation that is only very slowly dipping a toe in the water of software other than the big names, I'm sure it was done with Adobe.

            Now I don't even have the Adobe Acrobat reader on my system, when I try to install it, the install crashes. But Fedora comes with several other PDF readers, and the default is set to "Evince" which works fine MOST of the time.

            But I got this PDF, and one page was a picture of a tax form, and when I tried to print it, the tax form came out as a big black blob - man, does that waste ink! Obviously I killed the print job to try something else. (Just VIEWING this tax form was fine, only printing messed up.)

            I remembered using "Xpdf" a while ago, so I tried that, and voila, the tax form printed perfectly. Since I knew there were more tax forms in there, I used Xpdf for the rest of the job.

            So here is a case where two different PDF viewers reacted differently to the same PDF file. I think what we need is is an OPEN DEFINITION for PDF files, probably a subset of Adobe's definition, that any OSS viewer can follow and get the proper results - and ask the user what to do with files that don't follow it.

            And tell Adobe they can either follow the open definition, or stuff it where the sun don't shine!

            • by russotto ( 537200 ) on Saturday October 31, 2009 @10:50AM (#29934951) Journal

              I think what we need is is an OPEN DEFINITION for PDF files, probably a subset of Adobe's definition, that any OSS viewer can follow and get the proper results - and ask the user what to do with files that don't follow it.

              There is such; Adobe publishes it and makes it freely available on its web site. It's possible your file didn't follow it, but it's more likely your reader wasn't 100% compliant; it's a very complicated specification.

        • Re: (Score:2, Informative)

          by Anonymous Coward

          Unlike micros~1 word documents, there are freely available specifications and a reasonable number of quite reasonable third party implementations that can either display or generate PDF, or even both. That is to say, you can very well ``do PDF'' without ever using adobe software. Part of its success is that it's a dumbed-down version of PostScript, also open and arguably the right way to talk to printers. That's a whole sight better than micros~1's ooxml abomination, that once standardized turned out to hav

      • I agree that open government docs should stay away from Flash. I don't agree that Flash is an abomination because Adobe does not bother with less popular OSes. Why should they implement Flash on less popular OSes? That costs Adobe real money and then only a handful of users would benefit. If you were in charge of the engineering budget at Adobe, would you spend $ on a feature for Mac and Windows that 100 million people would use or would you use that same $ to port Flash to a less popular OS with 10,000
        • Adobe ships Flash/PDF readers/plugins to: Windows, OS X, Symbian (in some form), Linux, *BSD and various, uncountable tiny platforms. iPhone/iPod does not count because of obvious reasons.

          Lets see what MS Silverlight ships to: Windows/Intel Mac. Damn thing is so tied to Windows that they couldn't even convert/ship the V2 for PPC Macs or they simply abandoned them. (like we cared!)

          MS XPS format and viewer is the answer to PDF which, some people who didn't use Windows have never, ever heard of. It is that Win

        • Re: (Score:3, Insightful)

          Because Flash is now a crucial part of the internet. Until HTML 5 comes out with video standards and the like, Flash is about the only way you can embed videos in sites without ruining the layout of the site with a third-party media player and without your users searching for codecs.

          If Adobe would simply release the source to the Flash player, they could -save- money, have full platform compatibility and perhaps make more money with the Flash creation products. Think of it this way, if there was a fast
          • Why, as you say, is it good business for Adobe to port it to every single OS, even those with only a handful of users?
            • Because it would allow for a language and framework that works on every single OS. Look at Java, even though it has numerous faults, the fact that it is now open source and ported to just about every single device means that it is used for lots of cross-platform programs. Flash could be the same way if they ported the player to every OS and device. By open sourcing the Flash player they would A) save money in development B) allow the porting of it to various platforms and C) Improve sales for their developm
      • A number of government forms don't work with the free PDF readers.

        This is because Adobe broke its own published spec with its LiveCycle product, and by default it saves files that aren't compatible with anything else. It does a great job of forcing you to buy LiveCycle/Acrobat instead of using free tools. The Adobe people will tell you that it speeds up rendering of downloaded data, which I find hard to believe as the files are between 2x and 3x the size of a regular PDF.

        The current use of Adobe products

        • Re: (Score:3, Informative)

          by jeremyp ( 130771 )

          A PDF file produced by the LiveCycle suite is actually an XML document with a thin PDF wrapper. The XML conforms to the XFA standard which is owned by Adobe but is a published standard (http://partners.adobe.com/public/developer/en/xml/xfa_spec_2_4.pdf).

          • Acrobat Pro can't even edit XFA forms (beyond filling in values), why should 3rd party tools do so? I'm aware that you can save it as a hybrid "compatible" form, but it's not actually editable in Acrobat without stripping out the xfa data with a non-Adobe tool such as pdftk. The spec is subject to change at any time and has quite a few ambiguities, making it much more difficult to work with. How many more extra "open" specs and additions would we see if PDF was the official format of the government?

            XFA/

    • Re: (Score:3, Interesting)

      by Bacon Bits ( 926911 )

      PDFs are only searchable if the document contains text. Half the time PDFs contain text-as-image, which is about as useful to a search engine as a captcha image. Google doesn't run OCR on PDFs, AFAIK. Although, come to think of it, that sounds like something they'd get sued by a random company for doing for "violating copyright proprietary information".

      • Perhaps you know of a document format where the text in images IS searchable?

        • Re: (Score:3, Interesting)

          by Bacon Bits ( 926911 )

          A document format shouldn't store text as an image. That's why it's called text.

          • Re: (Score:3, Insightful)

            by petermgreen ( 876956 )

            That is not really a format issue though, in any format that supports images I can insert an image containing text.

          • I work with PDFs a lot, especially on OS X. I am telling you from an OS which you can have 60 KB 1080p screenshots in PDF in some circumstances: Whoever did that "text as image" trick, he is a complete moron.

            One of the reasons that PDF took off is exactly embedding fonts used in a document so it will appear as pixel perfect on client machines.

            As last resort (and a good practice), you can embed unformatted pure text of the entire PDF in your PDF file. PDF, like Quicktime Mov is one of the formats where peopl

            • Re: (Score:3, Informative)

              Whoever did that "text as image" trick, he is a complete moron.

              Generally text as images in PDFs are the result of people who scan in paper documents but don't have access to or don't use OCR programs to convert the raw image coming in from the scanner into text.

          • A document format shouldn't store text as an image. That's why it's called text.

            A document shouldn't store text as images. A document format can be misused and should not be trying to interpret images and reject them if they contain text. Heck, I can misuse the standard text files by storing the text as ASCII images output by "banner", making the difficult to copy and paste and near impossible to search. That's not the fault of the format, but me for misusing it.

            It's more of a problem with PDF because unlike the example I give with .txt files, because of how the formats are used. Docu

        • Re: (Score:3, Interesting)

          by TheRaven64 ( 641858 )
          You're missing the point. PDFs do not store text. Text is a stream of characters. PDFs store glyphs and their locations. It is more or less possible to convert glyphs into characters, although things like ligatures and the fact that spaces are not really represented make this difficult. In the metadata, some PDFs also store the text of the document, allowing it to be extracted. Given that the PDF is created automatically from the text in most cases, the text is more useful. You can create the PDF fro
    • by TheRaven64 ( 641858 ) on Saturday October 31, 2009 @08:40AM (#29934043) Journal
      The summary does not do a good job of reflecting the original blog post's point. The point was that the government should make data available in a machine-parseable and generic format. PDF is a great format for storing typeset pages, but it is a terrible format for publishing data. It's easy to generate beautiful PDFs from well-structured data but it's much harder to go the other way. Would you rather have budget figures (for example) as a CSV file in a well-defined format or as a PDF of tables and graphs? If the data is available in the former format, it's easy for you or a third party to produce the latter format. If it's only available in the PDF form then it's much harder to create the CSV.
      • The summary does not do a good job of reflecting the original blog post's point. The point was that the government should make data available in a machine-parseable and generic format. PDF is a great format for storing typeset pages, but it is a terrible format for publishing data. It's easy to generate beautiful PDFs from well-structured data but it's much harder to go the other way. Would you rather have budget figures (for example) as a CSV file in a well-defined format or as a PDF of tables and graphs? If the data is available in the former format, it's easy for you or a third party to produce the latter format. If it's only available in the PDF form then it's much harder to create the CSV.

        If the goal is to make the data available, then even CSV would be a better option than PDF. PDF, while pretty, is a terminal format and is the digital equivalent of a mayfly. It's paper that hasn't happened yet and when it does it will exist for a few short hours before finding its way to the circular file.

        Much of the government data consists of tables and tables of data. gzipped csv would be readable by anyone, so would ODF. Adobe appears to be looking for a handout at the expense of creating a usef

      • It's easy to generate beautiful PDFs from well-structured data but it's much harder to go the other way. Would you rather have budget figures (for example) as a CSV file in a well-defined format or as a PDF of tables and graphs?

        More importantly, it's then easy to import that data for visualization and analysis purposes. Data presented as a PDF file is effectively so inaccessible that it will rarely be extracted for further analysis, meaning that some gov't functionary becomes responsible for the presentation and analysis instead of members of the public. Then a panoply of tools become available for finding out things from that data that no one ever knew were there. Something like Tableau Desktop [tableausoftware.com] can slurp in CSV data (or data i

        • > More importantly, it's then easy to import that data for visualization and
          > analysis purposes. Data presented as a PDF file is effectively so
          > inaccessible that it will rarely be extracted for further analysis, meaning
          > that some gov't functionary becomes responsible for the presentation and
          > analysis instead of members of the public.

          Which is exactly why PDF is what you are going to get (or something even more inaccessible).

    • Re: (Score:3, Informative)

      Many implementations of PDF converters merely print a document to images and then embed the images into a PDF. Those are non-searchable and no text can be extracted with the existing tools. I once created a documentation website which relied on these embedded image types of PDF documents. I had to implement an OCR solution in order to extract the text to make my clients documentation searchable. It was ugly and a real pain in the ass.

      Certainly, PDF can be beautiful, but it is often not implemented that

      • Which PDF converters do that ? Because they must be really crap.
        Most PDF converters I have used rely on Ghostscript on a way or another (after all, it's free!), and Ghostscript definitely doesn't do like this.
        Most images-embedded-as-PDF files come from Xerox printers. Which, of course, have trouble knowing whatever was typed in the document in the first place.
    • Can I hate all the multimedia/hyperlink/scripting/vulnerabilities they've added to PDF?

      I'll back this so long as it's PDF light - text and graphics only (OK, maybe I'll allow hyperlinks...).

  • Nobody likes flash (Score:5, Insightful)

    by bcmm ( 768152 ) on Saturday October 31, 2009 @08:31AM (#29933993)
    Nobody likes Flash, and they probably shouldn't use it for anything. But there's not much wrong with PDF, if it's done right. When publishing something, one could offer "source" (some sane, machine-readable format) and PDF (autogenerated from the source, and prettified for easier reading).

    PDF shouldn't be used as a way to encapsulate scanned JPEGs and pretend they're a real electronic document.

    I would also note that many of the complaints about PDF as a format in TFA are really complaints about Adobe's abysmal PDF reading software. For example, the concern about the visually impaired: KDE's Okular does speech synthesis and has a high-contrast mode.
    • Re: (Score:3, Insightful)

      by NotBorg ( 829820 )

      But there's not much wrong with PDF, if it's done right.

      I'm sure they won't fuck this up, after all it is the US government.

    • by robogun ( 466062 )

      Additional reasons are they're closed, and are malware vectors that need to be constantly updated. As if that wasn't enough reason not to use them, there are even phishing scams to update your flash or pdf installs... with the scammers horrible malware.

      Unless you play Flash games or view Youtube all day there is no need to run Flash, all it does is deliver ugly ads or someone's horribly botched schoolboy attempt at an edgy webpage. Flash, far from enabling web usage is often used to RESTRICT usage, go to We

    • by mrmeval ( 662166 )

      Yes PDF is marvelous "No you can't print this document scumbag" "No you can't save a copy cretin" "No you can't extract the pretty pictures asshole". I've run into it and it's a show stopper.

      KDE is not windows and windows is here to stay for the foreseeable future. That is partly microsoft at work but it's also some serious usability and other problems with distributions using either a Linux or BSD kernel.

    • KDE's Okular does speech synthesis and has a high-contrast mode.

      yet can't output PS that my Brother BRScript can handle (Evince does OK).

      All of the open source PDF readers have come a long way in recent years - my only point is that PDF appears to be *hard* to implement. I don't know why somebody would need to, but my imagination is limited. Should a file format essential to government be such a hurdle to potential users?

  • Tremor (Score:3, Funny)

    by sleeponthemic ( 1253494 ) on Saturday October 31, 2009 @08:48AM (#29934087) Homepage

    They also say government's priority should be to publish datasets and the APIs to interact with them, rather than choosing how they're displayed in fancy graphs and charts.

    I felt a great disturbance in the Force, as if millions of IT workers suddenly cried out in terror, and were suddenly silenced.

  • by mattr ( 78516 ) <`moc.ydobelet' `ta' `rttam'> on Saturday October 31, 2009 @08:51AM (#29934101) Homepage Journal

    GP is right. Government should focus on doing what government is needed for success, such as determining standards for formats that everyone can use, with input from academia and industry. For example a human readable parsable format that one could embed in a web page for semantic metadata. Or funding open source software to make it easy (cross platform) to input such data (I am thinking of information about cited papers or books). Typeset information is nice but we already are drowning in information - how many pages of Google results do you usually look at? And we need help before generating 10 times as much.

    Why PDF is bad:
    - It is a potable typeset document package. Not a data sharing package that could be pulled apart easily with tools automatically.
    - PDF is extremely hard to parse, and using current free software does not always give good results.
    - You destroy useful document structure, or in the case of ASCII text parsability and small size, when you convert to PDF. You can't just convert back to the original.
    - It takes significant processing power and commercial software to display well and reliability as far as I can see. Having just gotten the latest Mac I feel like I'm in a dauntless battleship, but I have had many trouble with different unix tools in the past.
    - Scientists publish PDF too but then also use other formats for data. For example on arxiv, one scientists recently published animations inside a zip but it was hard to find the link
    - It is difficult to manage bibliographic information automatically.
    - It is proprietary
    - It requires a huge amount of data, and arcane knowledge, just to build a parser that works most of the time (such as for Asian languages especially).

    • by Anonymous Coward on Saturday October 31, 2009 @09:07AM (#29934227)

      - It is proprietary

      FAIL.

      PDF is an ISO standard. See: ISO 32000-1, Document management – Portable document format – Part 1: PDF 1.7

      This doesn't change the fact that it is a portable typesetting document format though. It's good for read only documents from your word processor but it shouldn't be (ab)used to store tables or graphs or whatever other crap people use it for.

      ---
      As for Flash, lets not even go there. Flash is passable as a streaming video container, if you're making animated cartoons like Homestar Runner or as a platform for small web games but other than those use cases, you're using it wrong.

      • Not only is it a standard, it's also *really* easy to parse. It's specifically structured so that any printer manufacturer can parse it and end up with *exactly* the same document as software displays.

        It still doesn't change the fact that it's not for data transfer, but for pristine document layout though.

    • by bcmm ( 768152 )
      The majority of those issues would be fixed by publishing LaTeX sources next to the PDFs generated from them.
    • by iris-n ( 1276146 )

      - Scientists publish PDF too but then also use other formats for data. For example on arxiv, one scientists recently published animations inside a zip but it was hard to find the link

      Err... also? I've never seen a scientist using pdf to publish data. We use pdf (and ps and div) to publish typeset papers. The actual data is in a lot of formats, dependent on the field and application. I've seen csv, matlab's .mat, xml, jpeg, tiff, proprietary crap, etc.

    • It is a potable typeset document package.

      So you can drink a PDF?!

  • PDF is often "non-parsable by software, unfindable by search engines, and unreliable if text is extracted."

    Have these people not heard of Google? Just because YOU can't write software to parse PDF files doesn't mean that nobody else can and that it doesn't already exist.

    • If you look around, every single Apple computer, device (ipod/iphone) is actively indexing every single PDF thrown at them, instantly and keep database of it.

      It is the famous "Spotlight" technology. They don't even need to look at Google, some of them have same kind of indexing technology (minus relation) running on their laptops.

      One should check the TFA relations with MS. I am sure something will come up.

      • If you look around, every single Apple computer, device (ipod/iphone) is actively indexing every single PDF thrown at them, instantly and keep database of it.

        No it is not. It is indexing every PDF that has text in the metadata. Create a PDF by printing to PostScript and then converting to PDF (the easiest way of creating PDF on Windows or Linux machines) and watch Spotlight completely fail to index it. Spotlight does not index the text that you see when you browse the PDF, because that text is stored as a set of glyph indexes, not as streams of characters.

        And if you want some real fun, open up a PDF containing table in Preview and try to persuade it to cop

  • If you are publishing a document that can be printed then PDF is a good format. If you expect people to extract data from the document then you should look for a different format. It depends on the purpose of posting the document on the web.
    • by lahvak ( 69490 )

      Either you provide data, or you provide a document. Extracting textual data from pdf is not any harder than extracting them from a word file or an odf document.

      If you want to provide data, provide data, in a csv format of something simple like that.

      In fact, with pdf, you can do both, since you can attach the cvs or whatever format data to the document.

  • PDF Yes, Flash No (Score:5, Insightful)

    by markdavis ( 642305 ) on Saturday October 31, 2009 @09:11AM (#29934261)

    I am OK with PDF. I would RATHER see documents in plain HTML, but there are times when formatting is important. In those cases, if it is to be read/print-only, PDF is the way to go. Otherwise, the gov should use ODF.

    But Flash? Are you kidding? The last thing on earth we need is more Flash.

    * Does not work on all devices
    * Slow and/or consumes tons of CPU
    * Consumes tons of RAM
    * Consumes more bandwidth
    * Makes it difficult or impossible to cut and paste
    * Impossible to "search/find"
    * Violates the native UI look and feel
    * Fonts and font sizes are uncontrollable by the end user
    * Can't scroll correctly much of the time
    * Almost completely proprietary
    * Rarely adjusts to screen size
    * Often introduces extremely irritating animation.
    * Doesn't allow text to be "seen" by the browser (or OS), making other plugins (like a screen reader) 100% useless

    At least that SilverDark stuff isn't even on the radar- thank God for little favors.

    • Re: (Score:3, Insightful)

      by gaspyy ( 514539 )

      Most of what you say is implementation-related rather than format-related. It's like saying that C sucks because there are so many crappy programs. I know about feeding the trolls, but for all those who don't know better, here we go:

      Nothing "just works" on all devices and in this area flash fares better than most other technologies; agree is slow; not really agree on RAM usage.

      Flash uses less bandwidth than alternatives, it's quite very well optimized. Sure, someone can stuff some 10 min. mp3s encoded at 25

      • Re: (Score:3, Insightful)

        by Vexorian ( 959249 )

        I know Slashdot crowd loves to hate flash, but at least hate it for the right reasons: its lack of speed and real 3d hardware acceleration.

        Those are very lame reasons. We are talking about open government initiative here, not about "standard for web games" initiative. Flash is:

        Not portable: Many platforms lack proper support. Flash can't be legally redistributed, alternatives are poor. It is no open format in any way.

        Bad for accessibility.

        Not a web standard or anything close to it.

        Nothing "just works" on a

        • Oh, and no half assed "openish" attempts a la MS. The whole entirety of it would have to be open, including the codecs and the tools to generate them. Nothing about proprietary extensions making the standard optionally-open. Also, as a standard for open government initiative, giberish like DRM must be completely out of the question.
        • I have no mod points, but, seriously, that - mod up people.

        • Maybe you haven't seen this: http://www.adobe.com/devnet/swf/ [adobe.com]

          This is 278 pages of very straightforward and in-depth documentation on the SWF file format.

      • >Most of what you say is implementation-related rather than format-related. It's like saying that C sucks because there are so many crappy programs.

        I will agree that there are better and worse ways to IMPLEMENT Flash, but even properly implemented, it doesn't address all (or most) of my issues.

        >Nothing "just works" on all devices and in this area flash fares better than most other technologies; agree is slow; not really agree on RAM usage.

        HTML works fine on all devices. 95% of the time I see Flash us

    • by Lennie ( 16154 )
      Not only that, but so much more is possible these days with a browser that supports proper standards.

      Flash became populair by the web-development community when you had to do a lot of web-programming to get things done and the performance wasn't optimised for those kind of things.

      But that is ages (in internet time) ago.
  • "...unfindable by search engines..."
    That is absolutely not true. Anyone who uses Google knows that the search engine can read PDFs, identify if any of the keywords are located within, and then provide a link both directly to the PDF as well as to an HTML version.

  • This could be a Good Thing, if it means that the formats will be made and remain open. IIRC, PDF is already an open standard, and supported by various programs from multiple sources. I would applaud it if the same were to happen to Flash. And if both formats are open and widely supported, the government could do a lot worse than using them.

  • Just my 2 cents in regards to public records and data.

    I'd like to say that the groups making decisions in this area really should consider a MVC architecture which will avoid the concerns iterated here on /. and by pundits for open data standards everywhere in regards to display aka View technologies.

    With a Model View Controller methodology and pattern in place it really is not a concern what technology is being used to display data at any given time. If public data is *stored* (Model) and *accessed* (Contr

In case of injury notify your superior immediately. He'll kiss it and make it better.

Working...