This action item is about how we operate our workgroup going forward, and
how that evolves now that we're an ISO/IEC standard as well as an OGF one.
I believe we will need to create a workgroup document describing these new
practices, particularly when they augment/vary some of the standard OGF
practices.
Please add to this list of issues about how we operate going forward.
- Typography: I assume we have to revise the OGF Spec to match Standard
ISO format (Beyond just A4 page size) so future versions come out in that
conforming style.
- Once we do this I don't want to be maintaining an OGF flavor and an
ISO flavor of the formatting.
- Does a preliminary working document of the DFDL workgroup have to
be specifically marked as such (so that it is clearly preliminary)? What
are these markings?
- If that is done without revisions of content from current OGF
content, would that replace the current ISO-provided document (which is
just a new cover page on our existing OGF GFD.240 document) or does that
wait for a content revision?
- Who are contacts within JTC1 ? Does the OGF Workgroup contact JTC1 by
way of OGF leadership or directly? (or... what is the chain of command
here? Don't want to be jumping across protocol boundaries!)
- Is there a TC within JTC1 that we should work more closely with? Right
away? Eventually? Need contacts there.
- In 6 years a PAS is supposed to become an International Standard. What
does that mean? Does PAS status end? Does OGF participation end, or does
the workgroup merge into a TC? Or is this just a status change assuming
things are going well?
- Day to day working group activity/meetings - is there guidance about
notes/minutes-taking, etc. (templates)?
- Such time as we have revisions to the document, how do we engage with
ISO to get an update to the PAS document? Are these voted?
- What about just typographical corrections?
- Thoughts: Do we just use the OGF process for updates/corrections
and then just submit the changes to JTC1 (some TC?) for consideration?
Mike Beckerle
Apache Daffodil PMC | daffodil.apache.org
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Owl Cyber Defense | www.owlcyberdefense.com
Lisa,
We found some additional issues with the previously sent ISO DFDL PDF.
Besides the problem with the footers being cut off (already reported) we
found:
- Links do not work:
- Table-of-contents entries do not let you navigate to the sections.
- Internal links like "[XML]" to the references section do not work.
- Hyperlink text in the references sections do not work.
- The page margins are inconsistent. Viewed with 2 pages on screen side
by side, the left pages have narrow left margin in comparison to right
pages.
- Tables 46 and 47 in Sections 14.2.1 and 14.2.1 break across page
boundaries. This makes them very hard to interpret, and while some large
tables can split across pages normally, for these specific tables, the page
boundary makes it very hard to understand them. Manual breaks should be
inserted to avoid this.
- Table 48 in Section 14.2.3 does not have a bad-break currently. But
this table is also one that a page-break across it needs to be avoided.
Please forward these to the right parties who are preparing the ISO/IEC
version.
Thank you
Mike Beckerle
OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
Apache Daffodil PMC | daffodil.apache.org
Owl Cyber Defense | www.owlcyberdefense.com
Please note: Contributions to the DFDL Workgroup's email discussions are
subject to the OGF Intellectual Property Policy
<http://www.ogf.org/About/abt_policies.php>
On Fri, Mar 8, 2024 at 9:42 AM Lisa Rajchel <lrajchel(a)ansi.org> wrote:
> Mike,
>
> I have sent your comment to ISO and now it is their hands. No one has
> asked for anything more from you. I will keep you posted.
>
> Best
> Lisa
>
> Sent with BlackBerry Work
> (www.blackberry.com)
>
>
> *From: *Mike Beckerle <mbeckerle.dfdl(a)gmail.com>
> *Date: *Friday, Mar 08, 2024 at 9:23 AM
> *To: *Lisa Rajchel <lrajchel(a)ansi.org>
> *Subject: *[EXTERNAL] Fwd: [DFDL-WG] proof text for ISO/IEC 23415
>
> Lisa,
>
> I am following up on this need for another spin on the DFDL 23415 official
> ISO version.
>
> As far as I know this is out of our hands, meaning the workgroup on DFDL.
> However, we have a workgroup meeting this week, I am wondering if there are
> any actions we need or could take to help get the 23415 through the process
> and fully published.
>
> Please advise
>
> Thank you
>
>
> Mike Beckerle
> OGF DFDL Workgroup Co-Chair | www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
> Apache Daffodil PMC | daffodil.apache.org
> Owl Cyber Defense | www.owlcyberdefense.com
> Please note: Contributions to the DFDL Workgroup's email discussions are
> subject to the OGF Intellectual Property Policy
> <http://www.ogf.org/About/abt_policies.php>
>
>
>
> ---------- Forwarded message ---------
> From: Steve Hanson <smhdfdl(a)gmail.com>
> Date: Sun, Feb 25, 2024 at 5:10 AM
> Subject: Re: [DFDL-WG] proof text for ISO/IEC 23415
> To: Mike Beckerle <mbeckerle.dfdl(a)gmail.com>
> Cc: Lisa Rajchel <lrajchel(a)ansi.org>, DFDL-WG <dfdl-wg(a)ogf.org>
>
>
> It looks like the footer is being cut off in order to accommodate the
> three lines of licence text in every header.
>
> Regards
> Steve
>
> On Sat, Feb 24, 2024 at 10:39 PM Mike Beckerle <mbeckerle.dfdl(a)gmail.com>
> wrote:
>
>> Lisa,
>>
>> The footer is cut off on every page of this PDF, making it impossible to
>> see the page numbers.
>>
>> I have not so far found any problem with the content of the pages, but
>> this problem with the page footers does require a re-spin of the PDF, and
>> if the page sizes change the table-of-contents will need its page numbers
>> updated.
>>
>> -mike
>>
>> Mike Beckerle
>> OGF DFDL Workgroup Co-Chair |
>> www.ogf.org/ogf/doku.php/standards/dfdl/dfdl
>> Apache Daffodil PMC | daffodil.apache.org
>> Owl Cyber Defense | www.owlcyberdefense.com
>> Please note: Contributions to the DFDL Workgroup's email discussions are
>> subject to the OGF Intellectual Property Policy
>> <http://www.ogf.org/About/abt_policies.php>
>>
>>
>>
>> On Tue, Feb 20, 2024 at 4:32 AM Lisa Rajchel <lrajchel(a)ansi.org> wrote:
>>
>>> Good morning,
>>>
>>>
>>>
>>> Attached please find the proof text for ISO/IEC 23415. Please confirm,
>>> by March 18, 2024, that the content is ready for publication.
>>>
>>>
>>>
>>> Best
>>>
>>> Lisa
>>>
>> --
>> dfdl-wg mailing list
>> dfdl-wg(a)lists.ogf.org
>> https://lists.ogf.org/mailman/listinfo/dfdl-wg
>>
>
>
> This e-mail is intended exclusively for the individual or entity to which
> it is addressed or otherwise directed. This e-mail (and its attachments)
> may contain confidential, proprietary or privileged information, and
> unauthorized disclosure or use of such information is prohibited absent
> express authorization of the sender. If you receive this e-mail in error,
> please notify the sender and delete this e-mail from your system.
>
---------- Forwarded message ---------
From: Steve Lawrence <slawrence(a)apache.org>
Date: Wed, Apr 10, 2024, 7:16 AM
Subject: [ANNOUNCE] Apache Daffodil 3.7.0 Released
To: <dev(a)daffodil.apache.org>
The Apache Daffodil community is pleased to announce the
release of version 3.7.0.
This release includes a number of bug fixes and performance
improvements.
Detailed release notes and downloads are available at:
https://daffodil.apache.org/releases/3.7.0/
Apache Daffodil is an open-source implementation of the DFDL
specification that uses DFDL data descriptions to parse fixed format
data into an infoset. This infoset is commonly converted into XML or
JSON to enable the use of well-established XML or JSON technologies
and libraries to consume, inspect, and manipulate fixed format data in
existing solutions. Daffodil is also capable of serializing or
"unparsing" data back to the original data format. The DFDL infoset
can also be converted directly to/from the data structures carried by
data processing frameworks so as to bypass any XML/JSON overheads.
For more information about Daffodil visit:
https://daffodil.apache.org/
Regards,
The Apache Daffodil Team
