Update namespace documents #589
Conversation
|
@himorin For your review. The next step would be to publish the documents at the URIs specified therein. |
|
(and this reminds me about w3c-ns update discussion at himorin/w3c-ns#1 ...) |
Can you clarify what you mean?
|
| <p>The namespace <code>http://www.w3.org/ns/ttml/profile/imsc1.1/image</code> is specified by the <a | ||
| href="https://www.w3.org/TR/ttml-imsc1.2/#image-profile-designator">IMSC 1.2</a> Recommendation.</p> |
There was a problem hiding this comment.
Given the note in IMSC 1.2 that it is unchanged from IMSC 1.1, is this correct, or should it point to IMSC 1.1 instead?
There was a problem hiding this comment.
IMSC 1.2 clarifies ambiguities that were present in IMSC 1.1, so I would still point people to IMSC 1.2 even if the profile itself was not modified.
There was a problem hiding this comment.
Here's a diff between v1.1 and v1.2 for reference. I agree that the specification makes non-substantive improvements, and I don't have strong views here, but I would note that in relation to Image profile specifically, it is very hard to find any changes that clarify ambiguities.
As I say, no strong views, so happy to leave as is. I had thought it possibly just an editing oversight.
|
The Timed Text Working Group just discussed
The full IRC log of that discussion<nigel> Subtopic: Update namespace documents #589<nigel> github: https://github.com//pull/589 <nigel> Atsushi: Sorry I haven't had time to get to this yet <nigel> .. I am not sure what the process is for updating namespace documents <nigel> .. I will consult the team <nigel> .. The document is on github so we can do it with a pull request <nigel> .. but the question is what content is required <nigel> Nigel: Would it be something different from what's in the pull request? <nigel> Atsushi: No idea actually <nigel> Nigel: OK, I suggest put a comment on the pull request when you know <nigel> Atsushi: The process says this is part of CRS publication, but we haven't done it for previous IMSC <nigel> .. publications so I definitely need to do something for this. <nigel> SUMMARY: Reviews to continue |
|
The Timed Text Working Group just discussed
The full IRC log of that discussion<nigel> Subtopic: Update namespace documents #589<nigel> github: https://github.com//pull/589 <nigel> Nigel: I think we're waiting on Atsushi for how to update namespace documents <nigel> Atsushi: I'm still getting up to speed on this. <nigel> .. I think I will open a PR onto the W3C repo directly and see what will happen <nigel> Pierre: Sounds like a good idea <nigel> Atsushi: I'm not sure what kind of DTD or supporting material we should attach to it. <nigel> .. I suppose nobody in industry will expect material or DTDs from the namespace URLs, right? <nigel> .. I had several identity-related libraries getting DTDs from namespace URLs <nigel> .. but for our case in TT we just use them to define a namespace. <nigel> .. I'm not familiar with the tools for implementations. <nigel> Pierre: I think that the requirement is that every time a namespace is created in a document <nigel> .. that it be formally reserved, set aside, and the way to do that is by publishing a namespace document. <nigel> .. Even though the chance of namespace reuse is very low, I understand this is a formal requirement of W3C. <nigel> Atsushi: If implementations will not look at the contents of the URL, we may <nigel> .. not need to pay strict attention to its content. <nigel> Pierre: There's no DTD here, or XSL or anything like that. It's just a web page. <nigel> Atsushi: Then let me go and try and see what happens. <nigel> SUMMARY: @himorin to open a pull request to add the new namespace pages |
Closes #580