Stories
Slash Boxes
Comments

SoylentNews is people

posted by takyon on Thursday September 01 2016, @05:23PM   Printer-friendly
from the making-a-buck-from-free-software dept.

The European Union's interoperability page reports:

Austria published a call for projects on 27 July. The deadline for submitting proposals is 4 October. Information regarding requirements and selection criteria are available at Austria's Research Promotion Agency (FFG).

This is the second call for AT:NET projects. The first round, launched in April, received 50 proposals out of which 31 projects will now be funded with [a] total [of] €3.6 million.

The AT:NET project promotes innovative digital start-ups and small and medium-sized businesses. The project is calling for companies and projects that deal with digitisation of products or services. Topics can include eGovernment, eHealth, eLearning, and eInclusion, as well as commercial products and services.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by TheRaven on Friday September 02 2016, @08:22AM

    by TheRaven (270) on Friday September 02 2016, @08:22AM (#396597) Journal

    A long specification isn't a bad thing, and that argument is part of why ODF adoption was hampered. C is a language with about a dozen keywords and its spec is longer than the ODF spec, and a lot of implementers think that it's inadequate. The sorts of people who were proposing regulations mandating an office document format are used to dealing with specifications and know that ambiguity is the absolute worst thing that you can have in a specification. A longer spec is almost always a sign of a more detailed spec.

    The ODF 1.1 spec is short because it's completely inadequate. I've not read the entire thing, but the things I've looked up in it (mostly in the spreadsheet parts) were clearly drafted by people who have no idea of the purpose of a specification and full of ambiguity. The part of the spec for spreadsheet formulae was a disaster, for example.

    OOXML is not a good spec either, but claiming that it's bad because it's long both misses the reasons why it's bad and discredits your opinion when advocating another format. For reference, the PDF spec is over 6,000 pages and PDF implementers complain that parts of it are insufficiently detailed (for example, the JavaScript integration bit needed for complex forms to work doesn't describe the objects that are exposed by the viewer to the script in adequate detail).

    --
    sudo mod me up
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2