OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [regrep] V3 Proposal: Namespace Manager Function


Title: RE: [regrep] V3 Proposal: Namespace Manager Function

Thanks for your feedback David.  Regarding the piece below:

<Piece>
You can navigate and search via the classification to
either discover or drilldown to the content you desire,
or locate by classification content the specific namespace
value.
</Piece>

What exactly would the "content" be?  Would this be as fine-grained as an element in a schema or XML document?  Or would it have to be a schema, DTD, XML document, etc.?  I had been referencing individual elements/attributes/types.

Thanks,
Joe

> **************************************************************************
>   Joseph M. Chiusano
>   Logistics Management Institute
>   2000 Corporate Ridge
>   McLean, VA 22102
>   Email: jchiusano@lmi.org
>   Tel: 571.633.7722
> **************************************************************************
>


-----Original Message-----
From: David RR Webber - XMLGlobal [mailto:Gnosis_@compuserve.com]
Sent: Monday, January 28, 2002 5:55 PM
To: Farrukh Najmi
Cc: CHIUSANO, Joseph; regrep@lists.oasis-open.org
Subject: Re: [regrep] V3 Proposal: Namespace Manager Function


Joe,

This functionality can also be achieved using the
Classification system in the registry already.

If you create a Classification and then add a note to it
of the namespace, then everything works as
advertised.

This seems much cleaner than tricks to scan content
being loaded, especially as that content may be in
a variety of several different schema flavours.

You can navigate and search via the classification to
either discover or drilldown to the content you desire,
or locate by classification content the specific namespace
value.

This would also give users a much more intuitive interface
than namespace goup - since they could use human
readable names for the namespace value strings.

Then if you also look at the Registry IM - and the registered
object details - you can see that within an implementation
you can setup a user profile to include these kinds of
informations as defaults - a nice short cut ability for
endusers that submit content germane to certain
namespaces - i.e.  DoDEMALLlibrarian user would
default to that namespace and so on.

My take on this is that the registry can already do
items 1 and 2.   Item 3 - a compare function is more a
vendor add-on feature than something for the spec's,
as this has come up before - and can obviously
be implemented external to the spec's by retrieving
the two pieces of content and then running a DIFF function.

Item 4 is already covered off for registered objects - so
if you use classifications to do this - you have all that
supported.

No changes to the spec' need - maybe just an application
note in the Tutorial section to cover this use case - is
my assessment here.

Thanks, DW.
====================================================

Message text written by Joe
>> > XML namespaces.  This includes the ability to:
> >
> >         (1) Associate constructs (elements, attributes, types) with
> a
> > registered namespace
> >
> >         (2) Query on all constructs in a given namespace
> >
> >         (3) Perform a comparison between 2 or more namespaces
> >
> >         (4) Perform life-cycle-type functions on a namespace
> > (registration, deprecation, etc.)
> >
> > Just this morning, I attended a meeting with a government client who
>
> > clearly demonstrated that there was a need for this type of
> > functionality in their environment - hence the proposal.
<



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC