I’m not sold on having both Type and
Kind be URI formatted fields. I would assume it would be up to the container context,
in this case Project, to define how these fields were defined. Is this not a
valid assumption.
As stated in the previous email, “It
would be helpful if there were some guidelines, with examples, on how these
fields should be used.”
From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kaczmarek, Pawel
Sent: Monday, July 17, 2006 7:25
AM
To: Corona
development
Subject: RE: [corona-dev] ProjectContainer
Definition
All 3 fields have the URI format.
So they can be used in RDF and we are sure there are no duplicates. URI is
intended to be an identifier of repository itself rather than access
configuration. It MAY be access address but do not have to be.
Marcin & Pawel
From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Monday, July 17, 2006 12:54
PM
To: Corona
development
Subject: RE: [corona-dev]
ProjectContainer Definition
There are now 3 fields that provide some context to a
ProjectContainer's Repository:
1) Type
2) URI
(specifically the URI scheme)
3) Kind
Only the URI has a specific format. Both Type and Kind are free
format, it is up to the container context (e.g. Project) to define the format
and meaning of these fields. It would be helpful if there were some
guidelines, with examples, on how these fields should be used.
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On
Behalf Of Kalka, Edyta
Sent: Monday, July 17, 2006 6:36 AM
To: Corona development
Subject: RE: [corona-dev] ProjectContainer Definition
One more update - kind attribute added to repository definition. Not
needed container-kind removed.
Edyta
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta
Sent: 17 lipca 2006 10:49
To: Corona development
Subject: RE: [corona-dev] ProjectContainer Definition
Container-kind added go Generic Container schema - see attachment.
Edyta
-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: 17 lipca 2006 10:17
To: Corona development
Subject: Re: [corona-dev] ProjectContainer Definition
We defenitely need a "kind" attribute in the repository
definition.
Currently there is a "type" attribute which determins what is
a
persistance method for the respository (eg. XML, JDBC, file, etc.). But
we still need to know what kind of information it provides - if it is
team member, artifact or web page repository.
Marcin
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify
us immediately and then destroy it.
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify
us immediately and then destroy it.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.