On 3/28/2016 9:40 PM, Janusz S. "Bień"
wrote:
If you seriously wanted to present "all that is known about a
> character" you would need to excerpt all mentions of it in the core
> specification, as well as (potentially) any additional details
> presented in the version of the proposal document that was approved by
> the UTC as part of encoding the character.
Exactly.
The essential information for LATIN SMALL LETTER P WITH FLOURISH is that
in Medieval manuscripts it is used for "pro" or "por". This information
is available only in
http://www.unicode.org/L2/L2006/06027-n3027-medieval.pdf
Is this a static and permanent link?
Yes.
BTW, the Unicode Consortium goes out of its way to make as many
links permanent as feasible. With anything in a nature of an
archive, not only the link but its contents will be stable.
What is the copyright status of the
document?
The terms of use (ostensibly for the entire site) are defined here:
http://www.unicode.org/copyright.html
The document archive has not been designated with anything more
restrictive, more specific or even explicit, but the documents
themselves do not carry copyrights. As far as the Consortium is
concerned, it requires the submitters to follow this policy
http://www.unicode.org/policies/ipr_policy.html
which gives the Consortium the rights to distribute submissions for
any purpose.
For example:
Can it be redistributed and replicated on other sites?
The Consortium places restrictions on the use of material on "pay
sites".
Can it be quoted
literally in a Wikipedia entry?
Do you see anything that would restrict you, other than not having
any written policy that explicitly covers the Wikipedia?
In general, what can be done to make access to such information easier?
Over time, some of the information should move from the proposals to
the text of the core specification and / or into a technical report.
(For the mathematical characters, there exists a UTR that covers
more details than the core specification, but for completeness, the
core specification still contains some higher level stuff).
This process can be user-driven or user\- assisted, by people
identifying gaps and either proposing text for the core
specification or writing a Unicode Technical Note or proposing a UTR
to cover the information.
A UTN or UTR may be appropriate vehicles to collect information
about a particular field of application (e.g. medievalist use).
A./
PS: proposals for text should use the contact form.
http://www.unicode.org/reporting.html
Best regards
Janusz
Received on Tue Mar 29 2016 - 00:16:03 CDT