RE: ISSUE-107 (Namespace of profile element and attribute): prefix for profile elements [DFXP 1.0 (Editorial)]

It was mostly editorial, to justify the inclusion of the feature and extension namespace URI's.

e.g.
If the URI expressed by the content of the ttp:feature element is a relative URI, then, when combined with the namespace value of the base attribute of the nearest ancestor ttp:features element, it must express an absolute URI. In either case (original absolute URI or resulting absolutized URI), the URI expressed by the ttp:feature element must further adhere to the syntax of a feature designation as defined by E.1 Feature Designations<http://www.w3.org/TR/2009/WD-ttaf1-dfxp-20090511/#feature-designations#feature-designations>.



Sean Hayes
Media Accessibility Strategist
Accessibility Business Unit
Microsoft

Office:  +44 118 909 5867,
Mobile: +44 7875 091385

From: Glenn A. Adams [mailto:gadams@xfsi.com]
Sent: 28 May 2009 2:42 AM
To: Sean Hayes
Cc: Public TTWG List
Subject: RE: ISSUE-107 (Namespace of profile element and attribute): prefix for profile elements [DFXP 1.0 (Editorial)]

One more comment on this thread regarding your proposal to change the terminology on feature and extension element. I don't think any change is needed there, since feature and extension both have similar (but not identical) language, which, for example under 6.1.3 ttp:feature, now reads as follows:

If the URI expressed by the content of the ttp:feature element is a relative URI, then, when combined with the value of the base attribute of the nearest ancestor ttp:features element, it must express an absolute URI. In either case (original absolute URI or resulting absolutized URI), the URI expressed by the ttp:feature element must further adhere to the syntax of a feature designation as defined by E.1 Feature Designations<http://www.w3.org/TR/2009/WD-ttaf1-dfxp-20090511/#feature-designations#feature-designations>.

The language can't be identical to profile case, since xml:base is not operating with profile, but is operating with feature and extension relative URIs.

I'm not sure from your proposal below whether you have a technical issue or an editorial issue with this language.

________________________________
From: Sean Hayes [mailto:Sean.Hayes@microsoft.com]
Sent: Friday, May 22, 2009 9:56 PM
To: Glenn A. Adams; Public TTWG List
Subject: RE: ISSUE-107 (Namespace of profile element and attribute): prefix for profile elements [DFXP 1.0 (Editorial)]

OK, I see the language now, I'm not that happy about a namespace URI for designators, but I guess there is nothing wrong with it. However if that is the usage we intend, can you, when you fix up the language around xml:base, change the terminology of the feature and extension element, to similar wording to that in <profile> so that it mentions the namespace.

A profile designator must adhere to the xsd:anyURI data type defined by [XML Schema Part 2]<http://www.w3.org/TR/ttaf1-dfxp/#xsd-2>, §3.2.17. If the profile designator is expressed as a relative URI, then it must be absolutized by using the TT Profile Namespace value as the base URI.
 Thanks,

Sean

From: public-tt-request@w3.org [mailto:public-tt-request@w3.org] On Behalf Of Glenn A. Adams
Sent: 22 May 2009 1:49 PM
To: Public TTWG List
Subject: Re: ISSUE-107 (Namespace of profile element and attribute): prefix for profile elements [DFXP 1.0 (Editorial)]

You can close this issue. The answer to this question is already addressed the second paragraph of the note under Table 1 of 5.1, quoted below. In the specific case of the TT Profile Namespace, it is use to label standard profiles as well as provide a deferenceable URL to a TT AF Profile Definition Document.

Note:

If a reference to an element type is used in this specification and the name of the element type is not namespace qualified, then the TT Namespace applies.

For certain namespaces defined above, the default prefix is specified as none if no XML vocabulary is defined in the namespace by this specification (nor expected to be defined in a future version of this specification). In such cases, the use of the namespace URI is for purposes other than defining XML vocabulary, e.g., for designating profiles, features, extensions and for dereferencing standard profile definitions.




On 5/22/09 8:14 PM, "Timed Text Working Group Issue Tracker" <sysbot+tracker@w3.org> wrote:

>
> ISSUE-107 (Namespace of profile element and attribute): prefix for profile
> elements [DFXP 1.0 (Editorial)]
>
> http://www.w3.org/AudioVideo/TT/tracker/issues/107
>
> Raised by: Sean Hayes
> On product: DFXP 1.0 (Editorial)
>
> In section 6.2.7 ttp:profile the ttp: prefix is used for the profile attribute
> and element. the ttp: prefix in Table 1 - Namespaces is used for the parameter
> namespace. Was it intended that the profile elements and attributes are in the
> profile namespace or the parameter namespace?
>
> If the latter, what then is the role of the profile namespace?
>
>
>