Matias Klein wrote:
> Hello Everyone,
back from holidays, with a few more answers...
>
> I discovered the following issues in the latest spec. I would
> appreciate your perspectives on them.
>
> 1. DV_PARAGRAPH does seem to make any sense as a data type. This is
> more of a rendering issue.
Matias Klein wrote:
> Hello Everyone,
back from holidays, with a few more answers...
>
> I discovered the following issues in the latest spec. I would
> appreciate your perspectives on them.
>
> 1. DV_PARAGRAPH does seem to make any sense as a data type. This is
> more of a rendering issue.
Hi Matias
Tom is on leave so it is a bit late coming...
> I discovered the following issues in the latest spec. I would
> appreciate your perspectives on them.
>
> 1. DV_PARAGRAPH does seem to make any sense as a data type. This is
> more of a rendering issue. A paragraph can contain multip
Hi Matias
Tom is on leave so it is a bit late coming...
> I discovered the following issues in the latest spec. I would
> appreciate your perspectives on them.
>
> 1. DV_PARAGRAPH does seem to make any sense as a data type. This is
> more of a rendering issue. A paragraph can contain multip
Hi Matias,
I'll reply properly in a few days, but essentially DV_PARAGRAPH is a minimal
construct for grouping blocks of text forming unstructured narrative. Obviously
you want to use structured entry as much as possible for processibility; or
else
post-process narrative into structured (i;e;
Hello Everyone,
I discovered the following issues in the latest spec. I would
appreciate your perspectives on them.
1. DV_PARAGRAPH does seem to make any sense as a data type. This is
more of a rendering issue. A paragraph can contain multiple
observations, but the spec indicates that only
6 matches
Mail list logo
