Re: New validating profile.xsd file and profile xml files to help ext:config

Understood.

So, let's go ahead and add this profile.xsd file to ext:config now. 
Given there is no validation going on to date, no harm is expected.

I would also like to spin up a wiki thread regarding "Extensions.next" 
given a handful of folks have,
including myself, have expressed an interest in such work. As such, I've 
added a "Next Steps" section
to the Ext:config wiki:

  http://wiki.java.net/bin/view/Jxta/ExtConfig#Next_Steps

  note: this may not be the perfect placeholder moving forward but it 
is, nonetheless, a start.

Hey John -

  The next steps will include getting a JXTA Contributor Agreement on file:

    http://www.jxta.org/getstart.html

    the JXTA Contributor Agreement is quite standard and a one time process

  We can also register an issue against ext:config to track artifacts, 
review, etc. If you are
  eager to file a Contributor Agreement, then perhaps we should hold on 
this later step so
  as to allow you to create the issue, once the agreement is on file, to 
better familiarize
  yourself w/ the process, etc.

  Will that work?

- james

Mike [bondolo] Duigou wrote:
> I don't believe John is suggesting changing the schema in his patch, 
> rather he is providing more complete definition/validation for the 
> current schema.
>
> As such, short term inclusion is more appropriate than changes to the 
> schema would be.
>
> Mike
>
> James W Todd II wrote:
>>
>> Yeah, and there are likely some subtle profile structural mods we 
>> might want to consider moving forward as well. I know I have a few 
>> ideas, Alex has expressed some as well ... and bringing the validated 
>> schema to the mix may highlight some as well. Functionally the tasks 
>> feel related.
>>
>> Specifically, I've thought about melding the /jxta/service/* elements 
>> as children of the /jxta/network
>> element, bringing into one place both the network resource consumer 
>> data (eg rdv client) and network
>> resource provisioner data (eg rdv, rly).
>>
>> I'm also keen on trying out Alex's idea of incorporating a XSLT 
>> (transform) hook to Profile to further
>> lessen ext:config's [optional] structure to one's application.
>>
>> - james
>>
>> Mike [bondolo] Duigou wrote:
>>> I don't see much downside to incorporating a more 
>>> completed/corrected profile.xsd.
>>>
>>> Agreed that since we are near the release that updating the profiles 
>>> themselves might be too risky at this point. I'm quite curious what 
>>> problems the validation revealed however.
>>>
>>> Mike
>>>
>>> James W Todd II wrote:
>>>>
>>>> Hey John -
>>>>
>>>>  Nice work.
>>>>
>>>>  The next release of JXTA is coming up soon and most major mobs of 
>>>> ext:config
>>>>  have been applied at this time. As such, it is a good time to 
>>>> start thinking
>>>>  about next steps, and having a validating schema is on the short 
>>>> list.
>>>>
>>>>  How about we register an issue with some description and attach your
>>>>  profile.xsd and profile.xml files and go from their? If are doing 
>>>> this for the
>>>>  first time I can walk you through the steps.
>>>>
>>>>  Thx joining the party :)
>>>>
>>>> - james
>>>>
>>>> -- 
>>>>
>>>> John Dickerson wrote:
>>>>> Hi,
>>>>>
>>>>> I have created a new validating profile.xsd and some slightly 
>>>>> modified profile xml files that reference it (e.g. edge.xml, ..... 
>>>>> e.t.c ).  They have not been checked into CVS yet.
>>>>>
>>>>> profile.xsd and its profile xml files live in CVS under:
>>>>>
>>>>>     platform\binding\java\ext\src\net\jxta\ext\config\resources
>>>>>
>>>>>
>>>>> Can anyone advise me what to do with my modified validating 
>>>>> profile.xsd ?
>>>>>
>>>>> Does anyone want me to send them the validating profile.xsd and 
>>>>> referencing profile xml files as a zip file?
>>>>>
>>>>> I don't want to check them in myself unless I get the OK from 
>>>>> someone who is more involved in the JXTA project then myself ( I 
>>>>> am a Newbe ).
>>>>>
>>>>> Thanks for your time and advice,
>>>>>
>>>>> Regards
>>>>>
>>>>> John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>