OpenDocument TC Members,
** Notes w/ details in  -  below, but you probably do not need to inspect details
On the matter of DNS+HTTP resolution of the two URI references (identifying namespace names) as mentioned earlier , I have fixed the OASIS Web server configuration so that the URIs now resolve. However, my investigation into recommended server configurations for "semantic-web" style NS URIs [often the "hash" type] also prompts an additional question for the TC members:
Do you have a preference as to whether the two URI references resolve to A or B ?
A) directly to the formal OWL ontology files (.owl)
B) indirectly, via the existing XML namespace documents
Documentation available to me on this topic reflects varying professional opinion, as does past/current practice with respect to resolution that best serves the interests of the users, whether human agents or machines .
If you think OpenDocument v1.2 implementations involve semantic web applications that directly make use of the two namespace URIs -- e.g., where a machine defeferences the URI so as to fetch and process the OWL (RFD/XML) source file -- then it may be preferable to implement "A" above
If you think the XML namespace name URIs are typically (or exclusively) used by human agents, e.g., readers who view the prose OpenDocument specifications and click on the two corresponding hyperlinks from the spec cover page, then it may be preferable to implement "B", as is currently done
As far as I know, I can implement "A" or "B" using server directives currently under our control, but I need to know which you prefer.
And yes, I'm aware that some server implementations use content negotiation and related strategies to support the fetching of alternate representations, depending upon particular HTTP requests and resulting client-server interactions. At this time, we are expecting to support a minimal configuration that involves "A" or "B", but not both. OASIS has only one standard that contains OWL/RDF artifacts, so we don't have much experience with recommended data preparation and server configs expected for SemWeb files; we may get some experience soon, to support OSLC specs.
 resolution of URI referenced is borked (404)
Declared XML namespaces:
Open Document Format for Office Applications (OpenDocument) Version 1.2
29 September 2011
OpenDocument v1.2 Metadata Manifest Ontology
ODF Schema Metadata Manifest
OpenDocument v1.2 Package Metadata Manifest Ontology
ODF Package Metadata Manifest
OWL file declarations:
 see sample behaviors, from the human-user POV -- using a browser and no advanced HTTP request headers. With appropriately prepared data and advanced server configurations, one might get (e.g., for "prov#" - "b" below), a representation in HTML (.html), RDF/XML (.rdf), Turtle (.ttl), or W3C XML Schema (.xsd)