[dsdl-discuss] Re: Fw: Re: Response to rest of Martin's comments

Martin Bryan wrote:

>Rick
>
>Your earlier statement in response to my:
>
>
>>>A) The origin of any names for character set blocks used, whether
>>>
>>>
>>user-defined or from a standard, needs to be explicitly stated, and not
>>implied as at present.
>>
>>
>of
>
>
>>See above. There are no user-defined block names.
>>
>>
>worried me greatly. Going back to the Philadelphia notes this morning I note
>recorded there the clear statement under the heading of Comments on Part 7
>reading:
>
>"Part 7 should be restricted to creating named character sets using block
>names, ranges, and properties as defined in Unicode database, and should not
>be concerned with things like sorting, UC/LC mapping, etc.
>
My suggested Part 7 does these.

The schemas, patterns, rules and assertions can have IDs and URLs and FPIs.
Patterns, rules and assertions can be referenced by name in other
shemas, patterns
and rules. So it is possible to have a rule for ISO 8859-1, for
example, and to
invoke this as an assertion in other schemas, by ID, URL or FPI (pubid).

It is even possible to name a character set and use that in an expression,
using a variety of mechanisms. However, these mechanisms (entity, abstract
rules, abstract patterns) are built on-top-of the assertion test
language, not
inside it, currently.

<pattern abstract="true" id="extended8859-1">
    <rule context=" $context ">
       <assert test=" \p{IsASCII}\p{IsLatin1} $extensions ">
          This text should only contain ISO 8859-1 characters + some
extensions
       </assert>
   </rule>
</pattern>

used by
 <pattern is-a="extended8859-1">
    <title>All Data Content is 8859-1+</title>
    <param name="context" value="*" />
    <param name="extensions" value="&#x2014" />
  </pattern>

>For private use
>
>
>characters the text should only refer to the code points, not define any
>properties of the characters."
>
>
My suggested Part 7 does not do these.

>I must ask that some means be found of honouring this demand to allow the
>creation of user-defined named character sets, if only by allowing reference
>to user-defined set defined using Martin Duerst's 2000 W3C note on defining
>character sets by referencing URLs with specific IDs that uniquely reference
>a set.
>
Why isn't the above mechanism adequate? I don't see that the Phillie
note requires that
the same syntax used for expressing Unicode properties must be available
for expressing
home-made collections. (However, I do agree it would be neater to be
able to extend
the expression language.)

Cheers
Rick

--
DSDL members discussion list
To unsubscribe, please send a message with the
command  "unsubscribe" to dsdl-discuss-request@dsdl.org
(mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)