Sorry I missed the call today. I see from the minutes that this action was mentioned. I would like to work on this further if there is any support for wording like this. I welcome constructive criticism. Frankly, I would like to expand it.
Regards,
Murray Maloney
murray@muzmo.com
On Dec 1, 2011, at 4:26 AM, James Fuller <jim@webcomposite.com> wrote:
> note I have picked this up to integrate/track
>
> thx, J
>
> On Thu, Nov 10, 2011 at 4:40 PM, Murray Maloney <murraymuzmo@gmail.com> wrote:
>> I had an action to write something to motivate each of the profiles.
>>
>> I know that this does not reflect exactly how it is presented in the spec, but it is how "I" factored it for the sake of understanding the differences among the profiles. I took liberties...
>>
>> Each of the profiles presented in the sub-sections following describes a nominal process for the faithful provision of information items and properties from well-formed and namespace-qualified XML documents.
>>
>> [.] We start by processing a well-formed and namespace-qualified XML document from which we derive all of the information items and properties known as Class A and B' and P and X; that is most information items and properties, with the notable exception of those items and properties known as Class B, which are contra-indicated by Class B', and are only available by inspection of the internal and external subsets of an XML document, for which, see the modest profile.
>>
>> [.] The minimum profile includes xml:base processing to resolve relative URIs in links to external resources.
>>
>> [.] The basic profile builds upon the minimum profile by adding xml:id processing to identify IDs in the absence of XML validation, without fetching external resources, and without relying on an internal subset.
>>
>> [.] The modest profile adds external markup declaration processing from which we derive all of the information items and properties known as Class B: notations, unparsed entities, normalized values, attribute types, IDs and IDREFs.
>>
>> [.] The recommended profile adds xi:include processing, to transclude linked infosets in situ as parsed XML or as text, recursively as required.
>>
>> [.] The XML validity profile inserts one or more validation processes, before and/or after the other profiles are applied, depending on how the DTDs are constructed, from which we derive all of the information items and properties known as Class V. [There be dragons here.]
>>
>> [.] The XML Schema validity profile inserts one or more validation processes, before and/or after the other profiles are applied [...] [There be dragons here.]
>>
>> [.] The Schematron validity profile ...
>>
>> [.] The Digital Signatures profile inserts one or more [???] processes, before and/or after the other profiles are applied [...]
>>
>> [.]
>>
>> Regards,
>>
>> Murray
>>
>>
>>
>>
>>
>>
>>
>>
>