Hi All,
I just wanted to add to that (thanks to Schawn again), that most of my
earlier mentioned problems with the schema files have been fixed in the
version online. I can now use them in combination with XMLSpy without
changing them and even with the schema files being locally on my drive.
Biggest remaining problem I see with this version is like said the fact
that
using multiple (not if it is this big a number) schema files in
combination
with IMS CP does not seem practical to me.
Pierre
----- Original Message -----
From: "Lorna M. Campbell" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, May 12, 2004 9:58 PM
Subject: Re: Implementing IEEE LOM Metadata
> Hi there,
>
> >Important Note: The 04/13 schema release changed the LOM namespace!!!
> >(yay, everyone update all your instance docs :)
>
> >So, do we know if the new namespace URI is going to be persistent?
>
> I've raised this issue with Schawn Thropp, one of the authors of the XSD
that
> accompanies IEEE P1484.12.3 Draft Standard for Extensible Markup
Language
(XML)
> Schema Definition Language Binding for Learning Object Metadata, and he
has said
> that the namespace was changed in response to a ballot comment and that
the
> current namespace, http://ltsc.ieee.org/xsd/LOM, will remain persistent
pending
> further comments.
>
> Schawn has forwarded the original IEEE comment and resolution which I've
copied
> below
>
> Comment:
> proposed namespace URI is too brittle
>
>
> Resolution:
>
> Replace "http://ltsc.ieee.org/xsd/LOMv1p0" with
> "http://ltsc.ieee.org/xsd/LOM".
>
> -- Less semantic confusion for adopters. References to the LOM
namespace
> will never need to be adjusted in any XML document instances as versions
of
> XML Schema bindings change or as LOM itself changes, whether the binding
> changes or not
> -- Many validating parsers will seek out a schema at the specified
namespace
> URI in the absence of any schemaLocation override. Using a non-version
> specific URI guarantees that these parsers will always access the most
> current schema, if the LTSC adopts the policy of placing the most
current
> schema instance at that URI and placing version-specific instances in
their
> own version-specific folders off of the 'root' path;
> -- Metadata instance creators who desire a specific binding instance for
the
> LOM namespace can always add an xsi:schemaLocation attribute that
specifies
> a particular file to use with the 'generic' namespace. This approach
also
>
>
> Hope this helps.
>
> Bye
> Lorna
>
>
>
> On 10 May 2004, at 07:12, Phil Barker wrote:
>
>
>
> -------- Original Message --------
> Subject: Re: Implementing IEEE LOM Metadata
> Date: Fri, 7 May 2004 20:26:22 +0100
> From: Andy Powell <[log in to unmask]>
>
> On Fri, 7 May 2004, Chris Hubick wrote:
>
> Important Note: The 04/13 schema release changed the LOM namespace!!!
> (yay, everyone update all your instance docs :)
>
> :-(
>
> So, do we know if the new namespace URI is going to be persistent?
>
>
> -- end
>
> Hi Lorna, I was wondering who to ask about this, then remembered where
you
were
> this week ... is there anyone around who could might know?
>
> Phil.
>
>
>
> --
> Phil Barker Learning Technology Adviser
> ICBL, School of Mathematical and Computer Sciences
> Mountbatten Building, Heriot-Watt University,
> Edinburgh, EH14 4AS
> Tel: 0131 451 3278 Fax: 0131 451 3327
> Web: http://www.icbl.hw.ac.uk/~philb/
>
> --
> Lorna M. Campbell
> Assistant Director
> Centre for Educational Technology Interoperability Standards (CETIS)
> Centre for Academic Practice, University of Strathclyde
> +44 (0)141 548 3072
> http://www.cetis.ac.uk/
>
----------------------------------------------------------------
Op deze e-mail zijn de volgende voorwaarden van toepassing:
http://www.fontys.nl/disclaimer
The above disclaimer applies to this e-mail message.
----------------------------------------------------------------
|