<jar286> http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/URI_Best_Practices/Recommendations/MeaningOfaTerm

[JR] HCLS URI Recommendations - What story to we give about LSID?

[SS] My understanding was that we wouldn't explicitly discuss LSIDs in doc.

[SS] Why does JR feel it's essential to mention LSIDs?

[JR] People are using LSIDs.

[JR] Why is HCLS ignoring work taken place four years ago? We should consider the good work people did on LSIDs.

[JR] Some problems were solved by LSID folks. We can mention those without pushing LSIDs.

[EP] We shouldn't provide multiple possiblities. We should just recommend one.

[SS] Learn from LSIDs but don't explicitly mention them.

[JR] We should form a group or task force to drill into these issues in more detail.

[JR] Maybe a reinvention of LSID solutions within the HTTP space.

<Susie> http://www.w3.org/2007/06/HCLSForm

[SS] How is the URI document coming along?

[JR] I have a revised work plan.

<jar286> http://esw.w3.org/topic/HCLSIG_BioRDF_Subgroup/Tasks/URI_Best_Practices/Work_Plan

[SS] Jonathan is looking for feedback on the document he sent out yesterday.

[SS] Feedback will enable Jonathan to move forward on the work plan (URL above)

[AR] It might be worth spliting out the producer and client sides.

[AR] Client and producer expectations need to match. These are first impressions on document Jonathan sent out.

[SS] Once we've agreed on the technical part we can go to vendors, etc.

[EN] If we go back to the original HCLS document, we are the bridge between technical and social.

[EN] We need to figure out what are the social constraints.

<jar286> TDWG just became LSID committed.... that's a biggy

[EN] Has anyone been monitoring growth and content of LSID sites versus HTTP?

[EN] What is the best way for people to quickly adopt a connectible model?

[EN] Some orgs adopted LSID internally.

[AR] Good idea. And we need to know what they're doing with LSIDs.

[AR] How they're doing it, what their use cases are, etc.

<jar286> lsids are uris

[AR] Uniprot is using URIs.

[SS] The next version of Uniprot will be available in RDF.

<eneumann> I do think Rolf A is using Eric Jain's model

<jar286> you mean http uris. (lsids are uris too.)

<matthiassamwald> beta.uniprot.org makes all datasets available as RDF which uses the PURLs.

Thank you Mathias

<jar286> What exactly is meant by 'a PURL'? something served by PURL software? something hosted by OCLC? ...

[JR] The URI draft is only covering a part of the issue so far.

<matthiassamwald> Sorry, I was unclear: it uses the http://purl.uniprot.org/ namespace.

<matthiassamwald> That's all.

[JR] If we're going to use shared names, then some organization will need to

[JR] post names or provide standard names.

[EP] Recommend that URIs should have the following characteristics.

[EP] Get the requirements out first. Then how we figure out how

[EP] to meet the requirements.

[SS] Next week Jonathan will discuss the Wiki page.

[SS] Alan...updates on Demo?

[AR] Request about querying anatomy

[AR] Updated Demo page with sample query.

[AR] Jonathan put RDF mostly in one place

<jar286> Don's 11:33 remark should be a reference to "Meaning of a Term", not to a "URI draft"

<jar286> "Meaning of a Term" talks only about the client perspective, not minting or publishing

<jar286> or URIs for public database records

[SS] Semantic Web students are creating ontologies.

[SS] Experimental design and clinical trial ontologies.

[AR] Is the intention that one will be able to reproduce the conversion in code?

[MS] Should enable people to do same with their own DB

[AR] Working code is more valuable than discussion.

Neurosciences meeting is November 3 through November 7 in San Diego, CA

www.sfn.org

<ericP> Neurosciences meeting overlaps with W3C Technical Plenary November 5 to 10

Eric N...what is the command to save notes?

This is scribe.perl Revision: 1.128  of Date: 2007/02/23 21:38:13  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: Don
Inferring Scribes: Don

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: Don Don_Doherty Eric_Neumann Jonathan_Rees Kei_Cheung Microsoft P15 Susie aaaa alanr eneumann ericP jar286 matthiassamwald
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 10 Sep 2007
Guessing minutes URL: http://www.w3.org/2007/09/10-BioRDF-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report