Re: Listing request names

[Michael Mealling <michael@xxxxxxxxxxxxxxxx>]

Chris Weider said this:
> > -----Original Message-----
> > From:	Michael Mealling [SMTP:michael@xxxxxxxxxxxxxxxx]
> > Sent:	Monday, November 24, 1997 10:43 AM
> > To:	Chris Weider
> > Cc:	michaelm@xxxxxxxxxx; M.Wahl@xxxxxxxxxxxxxxxxxx; phoffman@xxxxxxx;
> > ietf-schema-reg@xxxxxxx
> > Subject:	Re: Listing request names
> > 
> > Chris Weider said this:
> > > Michael:
> > >   The OID registration service is implicit in the listing being able to
> > > assign names to the nameless.
> 	[Chris Weider]  
> > Sure. But are those the names that the schema is supposed to use within
> > its own system? I.e. are the OIDs the service assigns going to the the
> > OIDs that LDAP uses everywhere?
> 	[Chris Weider]  Yes
> 
> > By nameless do you mean schema's that have not yet been created or 
> > schema that use names other than OIDs?
>
> 	[Chris Weider]  Yes, and for schema that do not yet have unique ids
> assigned (e.g. Dublin Core).
>

Yes to all of 'em? If whois++ wants to list its schema in the service it
will have to rename its schema to the OID that the service assigns?

-MM

> > > > -----Original Message-----
> > > > From:	Michael Mealling [SMTP:michael@xxxxxxxxxxxxxxxx]
> > > > Sent:	Sunday, November 23, 1997 9:05 PM
> > > > To:	M.Wahl@xxxxxxxxxxxxxxxxxx
> > > > Cc:	phoffman@xxxxxxx; ietf-schema-reg@xxxxxxx
> > > > Subject:	Re: Listing request names
> > > > 
> > > > Mark Wahl said this:
> > > > > 
> > > > > I also am in agreement with Paul Hoffman's suggested approach, with
> > one 
> > > > > modification: I would prefer to have the temporary OID assignment be
> > > > done with
> > > > > a real-time protocol (e.g. HTTP?) than with a store-and-forward
> > protocol
> > > > (SMTP).
> > > > > When the user clicks the 'send to listing service' button on their
> > > > schema 
> > > > > design tool, it would allow the tool to obtain an OID and send the
> > > > message 
> > > > > immediately, rather than waiting for an intermediate response to
> > wander 
> > > > > through the MTAs.
> > > > > 
> > > > > I don't see a problem with missing numbers in the sequence; when in
> > > > future
> > > > > the listing service becomes pruned there will be more missing
> > numbers.  
> > > > > 
> > > > 
> > > > Mark, 
> > > >   What is LDAP going to be doing with the OIDs that the registry
> > assigns?
> > > > I assume that the above scenario is needed so that you can get and use
> > > > the registries assigned OID, right? If so are you planning on using
> > the
> > > > registry's assigned OID as the OID of the actual schema in LDAP? If so
> > > > then I think that is a bad mistake. That means that not only is the
> > > > registry acting as a place to hold schema definitions, it has also
> > become
> > > > an owner of schema definitions and an OID registration service.
> > Neither of
> > > > which we're ready for yet.
> > > > 
> > >
> > 
> > -- 
> > --------------------------------------------------------------------------
> > ----
> > Michael Mealling	| 505 Huntmar Park Drive       | Phone:
> > (703)742-0400
> > Software Engineer	| Herndon, VA 22070	       | Fax:
> > (703)742-9552
> > Network Solutions	| <URL:http://www.netsol.com>  | michaelm@xxxxxxxxxx
> 


-- 
------------------------------------------------------------------------------
Michael Mealling	| 505 Huntmar Park Drive       | Phone:  (703)742-0400
Software Engineer	| Herndon, VA 22070	       | Fax:    (703)742-9552
Network Solutions	| <URL:http://www.netsol.com>  | michaelm@xxxxxxxxxx