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

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

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


Subject: Re: [energyinterop] URI's


All Oasis documents are always publicly viewable. When you upload 2 Kaci 2 Uris are created - member only and public. The auto email sent on upload contains the publicly accessible uri.

Sent from my iTouch

On Aug 12, 2009, at 4:37 PM, "Toby Considine" <Toby.Considine@gmail.com> wrote:

 

The intent to is to have a public document with a permanent URL that is our starting point. Nothing more. Given the visibility of our claims “Everyone can see everything in OASIS right away…” a long delay is bad. 

 

 

Thanks

 

tc

 


"If something is not worth doing, it`s not worth doing well" - Peter Drucker


Toby Considine
TC9, Inc

Chair, OASIS oBIX Technical Committee
OASIS Technical Advisory Board

  

Email: Toby.Considine@gmail.com
Phone: (919)619-2104

http://www.oasis-open.org

blog: www.NewDaedalus.com

 

 

From: Mary McRae [mailto:mary.mcrae@oasis-open.org]
Sent: Wednesday, August 12, 2009 1:29 PM
To: wtcox@coxsoftwarearchitects.com
Cc: Wilson, David C (St. Paul); Robin Cover; David Holmberg; Toby Considine
Subject: Re: [energyinterop] URI's

 

Was the intent of the TC to start a public review?

 

Mary 

 

 

 

 

 

On Aug 12, 2009, at 1:27 PM, William Cox wrote:



David --

We can give the public links (from the upload message) for readers.

Implementer will have wait until its on docs.

The hurry up is tht itaks done, otherise weald have to add that to the max SLA time. :-)

Hope that's clear.

Thanks!

Bill

Sent via BlackBerry by AT&T

 


From: "Wilson, David C (St. Paul)" 
Date: Wed, 12 Aug 2009 12:18:40 -0500
To: Mary McRae<mary.mcrae@oasis-open.org>
Subject: RE: [energyinterop] URI's

 

Hi Mary,

 

Thanks for your response.

 

I’m trying to reconcile the 30 days in your email with the urgency with which the TC to approved its first Committee Draft to facilitate inter-SDO comments.  Is there a recommended way to circulate the CD01 prior to it’s posting at its home URI?

 

Thanks,

Dave

 

Office: +1.651.407.4168

Mobile: +1.612.741.2759

 


From: Mary McRae [mailto:mary.mcrae@oasis-open.org] 
Sent: Wednesday, August 12, 2009 12:02 PM
To: Wilson, David C (St. Paul)
Cc: Robin Cover; William Cox; David Holmberg; Toby.Considine@gmail.com
Subject: Re: [energyinterop] URI's

 

Hi David,

 

  The turnaround time on documents for uploading (without a public review) is 30 days. The documents must first be QC'ed to ensure they conform to the TC Process, templates, and naming guidelines. The lengthy SLA is because all other time-sensitive requests come first (public reviews, ballots, new TCs, etc.)

 

Regards,

 

Mary

 

Mary P McRae

Director, Standards Development

Technical Committee Administrator

OASIS: Advancing open standards for the information society

twitter: fiberartisan  #oasisopen

phone: 1.603.232.9090

 

Standards are like parachutes: they work best when they're open.

 

 

 

 

 

 

 

 

On Aug 12, 2009, at 12:37 PM, Wilson, David C (St. Paul) wrote:




Mary,

I hope your day is going well and I appreciate your help on this. I see from another email that we're in agreement on URI’s. 

I told the committee to expect these to be posted today or tomorrow, is that reasonable?

 

Here are the specific instructions.  Please call me on cell if you have any questions or comments.

1)      Prose specs

 

Please post the contents of:

http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/33627/energyinterop-1.0-spec-wd-01.zip

to:

 

http://docs.oasis-open.org/energyinterop/ei/v1.0/cd01/

 

2)      XML specs

 

Please post the contents & the zip file itself of:

http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/33767/energyinterop-1.0-xml-cd-01.zip

 

to:

http://docs.oasis-open.org/energyinterop/ei/v1.0/cd01/xml/

 

3)      RDDL

 

Please post the html file below:

http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/33768/energyinterop.htm

 

to:

http://docs.oasis-open.org/ns/energyinterop/energyinterop-20090701/

 

4)      RDDL supplemental files

 

I don’t recall if I have an absolutepath for the OASIS logo in the RDDL file or a relative one.  You have my permission (if that’s required) to change the logo path in the file or load the logo and cssinto that folder. Let me know if you’d like me to change it.  Note that the RDDL file & namespaces need a lot of work so please don’t look too closely at them…not my finest work.

 

Thank you so much for your help and I apologize in advance if I committing glaring OASIS newbie breeches of etiquette, etc.  I appreciate your patience and coaching.

 

Regards,

Dave

 

 

Office: +1.651.407.4168

Mobile: +1.612.741.2759

Email: davidcwilson@trane.com

 

-----Original Message-----
From: Wilson, David C (St. Paul)
Sent: Wednesday, August 12, 2009 8:33 AM
To: Toby.Considine@gmail.com; 'Mary McRae'
Cc: 'Robin Cover'; 'William Cox'; 'David Holmberg'
Subject: RE: [energyinterop] URI's

 

Toby,

Here is the URI path you selected:

http://docs.oasis-open.org/energyinterop/ei/v1.0/cd01/energyinterop-1.0-spec-cd-01.html

I propose that we put xml artifacts in a subdirectory:

http://docs.oasis-open.org/energyinterop/ei/v1.0/cd01/xml/

I propose that the xml files be named without meta-data:

EventInfo.xsd

Thus, the home for the file:

http://docs.oasis-open.org/energyinterop/ei/v1.0/cd01/xml/EventInfo.xsd

Please let me know & I'll change the xml and ask Mary to post them.

Regards,

Dave

Office: +1.651.407.4168

Mobile: +1.612.741.2759

Email: davidcwilson@trane.com

 

-----Original Message-----

From: Toby Considine [mailto:tobyconsidine@gmail.com] On Behalf Of Toby Considine

Sent: Tuesday, August 11, 2009 8:49 PM

To: 'Mary McRae'; Wilson, David C (St. Paul)

Cc: 'Robin Cover'; 'William Cox'; 'David Holmberg'

Subject: RE: [energyinterop] URI's

I opted for the shorter EI format

All three formats are in the attached ZIP

Artifacts I have not touched.

 

tc

"If something is not worth doing, it`s not worth doing well" - Peter Drucker

Toby Considine

TC9, Inc

Chair, OASIS oBIX Technical Committee

OASIS Technical Advisory Board

  

Email: Toby.Considine@gmail.com

Phone: (919)619-2104

http://www.oasis-open.org

blog: www.NewDaedalus.com

 

-----Original Message-----

From: Mary McRae [mailto:mary.mcrae@oasis-open.org]

Sent: Tuesday, August 11, 2009 9:31 PM

To: Wilson, David C (St. Paul)

Cc: Robin Cover; Toby.Considine@gmail.com; William Cox; David Holmberg

Subject: Re: [energyinterop] URI's

Here's some suggestions:

 From the URI generator I get:

This version:

http://docs.oasis-open.org/energyinterop/energyinterop/v1.0/cd01/energyinter

op-1.0-spec-cd-01.doc

http://docs.oasis-open.org/energyinterop/energyinterop/v1.0/cd01/energyinter

op-1.0-spec-cd-01.html

http://docs.oasis-open.org/energyinterop/energyinterop/v1.0/cd01/energyinter

op-1.0-spec-cd-01.pdf

Latest version:

http://docs.oasis-open.org/energyinterop/energyinterop/v1.0/energyinterop-1.

0-spec.doc

http://docs.oasis-open.org/energyinterop/energyinterop/v1.0/energyinterop-1.

0-spec.html

http://docs.oasis-open.org/energyinterop/energyinterop/v1.0/energyinterop-1.

0-spec.pdf

--

You could shorten the spec abbreviation for the directory to 'ei' and 

get the following result:

This version:

http://docs.oasis-open.org/energyinterop/ei/v1.0/cd01/energyinterop-1.0-spec

-cd-01.pdf

http://docs.oasis-open.org/energyinterop/ei/v1.0/cd01/energyinterop-1.0-spec

-cd-01.html

http://docs.oasis-open.org/energyinterop/ei/v1.0/cd01/energyinterop-1.0-spec

-cd-01.doc

Previous version:

N/A

Latest version:

http://docs.oasis-open.org/energyinterop/ei/v1.0/energyinterop-1.0-spec.pdf

http://docs.oasis-open.org/energyinterop/ei/v1.0/energyinterop-1.0-spec.html

http://docs.oasis-open.org/energyinterop/ei/v1.0/energyinterop-1.0-spec.doc

--

 

For the namespace:

http://docs.oasis-open.org/ns/energyinterop/{unique-name} (some TCs 

use a date, others a single name)

such as (taken from the namespace document you sent):

http://docs.oasis-open.org/ns/energyinterop/20090701

http://docs.oasis-open.org/ns/energyinterop/DRAS

http://docs.oasis-open.org/ns/energyinterop/EventInfo

Regards,

Mary

 

On Aug 11, 2009, at 10:37 AM, Wilson, David C (St. Paul) wrote:

> Hi Mary,

> 

> I hope you had a good weekend.  I'm writing to follow up on the below

> note because we have our TC meeting tomorrow and I would like to have

> the artifacts at their URI's prior to the meeting.

> 

> Is there anything you need from Toby, Bill, David, or me?

> 

> Thanks!!

> Dave

> 

> Office: +1.651.407.4168

> Mobile: +1.612.741.2759

> Email: davidcwilson@trane.com

> 

> -----Original Message-----

> From: Mary McRae [mailto:mary.mcrae@oasis-open.org]

> Sent: Friday, August 07, 2009 4:18 PM

> To: Wilson, David C (St. Paul)

> Cc: Robin Cover; Toby.Considine@gmail.com; William Cox; David Holmberg

> Subject: Re: [energyinterop] URI's

> 

> Hi David,

> 

>   If you send me the documents I can have a look and tell you whether

> or not they comply.

> 

> Regards,

> 

> Mary

> 

> Mary P McRae

> Director, Standards Development

> Technical Committee Administrator

> OASIS: Advancing open standards for the information society

> email: mary.mcrae@oasis-open.org

> web: www.oasis-open.org

> twitter: fiberartisan  #oasisopen

> phone: 1.603.232.9090

> 

> Standards are like parachutes: they work best when they're open.

> 

> 

> 

> 

> 

> 

> 

> 

> On Aug 7, 2009, at 5:09 PM, Wilson, David C (St. Paul) wrote:

> 

>> 

>> Hi Mary,

>> 

>> The Energy Interoperation group approved "CD01" in our last

>> meeting.  We

>> need to settle a URI issue though.  I think the XML location URI's,

>> the

>> specification current location URI's and the ones suggested by the

>> block

>> generator below are all slightly different.

>> 

>> How do you suggest we proceed for finalizing the URI and testing it 

>> in

>> the XML & specification documents?

>> 

>> Thanks!

>> Dave

>> 

>> Office: +1.651.407.4168

>> Mobile: +1.612.741.2759

>> Email: davidcwilson@trane.com

>> 

>> 

>> -----Original Message-----

>> From: Mary McRae [mailto:mary.mcrae@oasis-open.org]

>> Sent: Wednesday, August 05, 2009 7:51 AM

>> To: Robin Cover

>> Cc: Wilson, David C (St. Paul)

>> Subject: Re: [energyinterop] Groups - RDDL for the energyinterop

>> namespace (energyinterop.htm) uploaded (fwd)

>> 

>> Hi David,

>> 

>>  If the OpenADR spec has been contributed to OASIS then any

>> namespaces associated with it must be on OASIS-owned domains as Robin

>> indicated. Certainly fewer are better :)

>> 

>> As far as actual uploading, I do all that. We're in a 'temporary'

>> situation where Members do not have write access to docs.oasis-

>> open.org. When ready, you send the files to me, I review them, let 

>> you

>> know if there's anything that needs to be changed before they can be

>> uploaded, upload them, and make the appropriate announcements.

>> 

>> There's a utility you can use to determine filenames/locations:

>> http://www.oasis-open.org/committees/uri-block-generator.php

>> 

>> Regards,

>> 

>> Mary

>> 

>> Mary P McRae

>> Director, Standards Development

>> Technical Committee Administrator

>> OASIS: Advancing open standards for the information society

>> email: mary.mcrae@oasis-open.org

>> web: www.oasis-open.org

>> twitter: fiberartisan  #oasisopen

>> phone: 1.603.232.9090

>> 

>> Standards are like parachutes: they work best when they're open.

>> 

>> 

>> 

>> 

>> 

>> 

>> 

>> 

>> On Jul 30, 2009, at 1:06 PM, Robin Cover wrote:

>> 

>>> Hello David.

>>> 

>>> I'm forwarding your questions to Mary McRae, OASIS TC Admin,

>>> who has the authority to rule on interpretations of what's 

>>> allowable,

>>> etc.  For example, I'm not aware that OASIS owns the Internet

>>> domain 'openadr.org', so that may become a relevant point in the

>>> discussion.

>>> 

>>> I may have technical opinions of interest, and could discuss these

>>> with you, but generally I do so at Mary's request.

>>> 

>>> The memo about use of a NS URI path with /ns/ for schema files

>>> is a topic we've discussed internally several times, so I felt

>>> the reminder would put nobody at risk, and might save your

>>> design team some backtracking.

>>> 

>>> I'll await further communication from Mary on this.

>>> 

>>> Best wishes,

>>> 

>>> - Robin

>>> 

>>> Robin Cover

>>> OASIS, Director of Information Services

>>> Editor, Cover Pages and XML Daily Newslink

>>> Email: robin@oasis-open.org

>>> Staff bio: http://www.oasis-open.org/who/staff.php#cover

>>> Cover Pages: http://xml.coverpages.org/

>>> Newsletter: http://xml.coverpages.org/newsletterArchive.html

>>> Tel: +1 972-296-1783

>>> 

>>> 

>>> ---------- Forwarded message ----------

>>> Date: Thu, 30 Jul 2009 11:43:12 -0500

>>> From: "Wilson, David C (St. Paul)" <DavidCWilson@trane.com>

>>> To: Robin Cover <robin@oasis-open.org>

>>> Subject: RE: [energyinterop] Groups - RDDL for the energyinterop

>>> namespace

>>>  (energyinterop.htm) uploaded

>>> Message-ID:

>> <8061F76BD8F4224098E5FFD4D8A941A60385F7A4@LSEUSMS1314.am.corp.priv

>>>> 

>>> 

>>> Hi Robin,

>>> 

>>> Hi Robin,

>>> 

>>> Thanks for engaging on the question of namespaces.  I'd like to ask

>>> some

>>> questions off list for a moment.

>>> 

>>> It seems that the root namespace for this TC meets specifications:

>>> http://docs.oasis-open.org/ns/energyinterop/energyinterop-20090701

>>> ...do you agree?

>>> 

>>> The OpenADR standard we inherited defined individual namespaces for

>>> each

>>> type.  For example, the EventInfo XSD type had it's own namespace:

>>> http://www.openadr.org/DRAS/EventInfo

>>> 

>>> Your thoughts?

>>> 

>>> This seems like "excessive" namespace definition.  I have proposed

>>> consolidating the OpenADR namespaces into less OASIS name spaces and

>>> there has been no objection yet.  Bill Cox wants to wait to do this

>>> after the first committee draft and that seems reasonable to me.

>>> 

>>> Do you have any objection to that timing?

>>> 

>>> XSD FILES

>>> 

>>> I think you are saying that the actual XSD files should not be under

>>> the

>>> namespace URI.  That makes sense to me.  What should be the URI's 

>>> for

>>> the actual XSD files?

>>> 

>>> RDDL file

>>> When should the RDDL draft file be uploaded to it's actual URL?  Who

>>> does this?  If I'm supposed (in my tech editor role) to do it, what

>>> method & credentials do I need to do it?

>>> 

>>> Regards,

>>> Dave

>>> 

>>> p.s. Please feel free to reply on or off list as you think is

>>> appropriate.

>>> 

>>> Office: +1.651.407.4168

>>> Mobile: +1.612.741.2759

>>> Email: davidcwilson@trane.com

>>> 

>>> -----Original Message-----

>>> From: Robin Cover [mailto:robin@oasis-open.org]

>>> Sent: Wednesday, July 29, 2009 9:58 AM

>>> To: Wilson, David C (St. Paul)

>>> Cc: energyinterop@lists.oasis-open.org; Mary McRae

>>> Subject: Re: [energyinterop] Groups - RDDL for the energyinterop

>>> namespace (energyinterop.htm) uploaded

>>> 

>>> On Wed, 29 Jul 2009, davidcwilson@trane.com wrote:

>>> 

>>> 

>> 

> ------------------------------------------------------------------------

>>> --------

>>> http://lists.oasis-open.org/archives/energyinterop/200907/

>>> msg00067.html

>>> 

>>> The document named RDDL for the energyinterop namespace

>>> (energyinterop.htm)

>>> has been submitted by Mr. David Wilson to the OASIS Energy

>>> Interoperation

>>> TC document repository.

>>> 

>>> Document Description:

>>> This is a draft of the RDDL.  It currently only references the

>>> EventInfo.xsd document.

>>> 

>>> View Document Details:

>>> http://www.oasis-open.org/committees/document.php?document_id=33572

>>> 

>>> Download Document:

>>> 

>> 

> http://www.oasis-open.org/committees/download.php/33572/energyinterop.ht

>>> m

>>> 

>>> 

>> 

> ------------------------------------------------------------------------

>>> --------

>>> 

>>> I have not been tracking closely with proposed namespace URI and

>>> "information

>>> resource" URI design in this group, but I think I did spot a couple

>>> instances

>>> where it's proposed that XML schema definition files and other

>>> file-system

>>> resources be located in a URI hierarchy beneath a proposed /ns/ 

>>> path,

>>> 

>>> viz.,

>>> 

>>> XML Schema(s)

>>> EventInfo.xsd

>>> 

>> 

> http://docs.oasis-open.org/ns/energyinterop/energyinterop-20090701/Event

>>> Info.xsd

>>> This version:

>>> 

>> 

> http://docs.oasis-open.org/ns/energyinterop/energyinterop-20090701/Event

>>> Info.xsd

>>> 

>>> seen in this draft RDDL document:

>>> 

>>> 

>> 

> http://www.oasis-open.org/committees/download.php/33572/energyinterop.ht

>>> m

>>> 

>>> Now, personally (unofficially), I see no problem with the proposed

>>> XML

>>> NS URI

>>> as:

>>> 

>>> http://docs.oasis-open.org/ns/energyinterop/energyinterop-20090701

>>> 

>>> However, the OASIS Naming Guidelines, sub the Section with title

>>> "XML Namespace Design, Allocation, and Management" [1]

>>> 

>>> clarifies that URIs should not be created for file system resources

>>> downstream

>>> (in the path hierarchy) from the Namespace URI containing the /ns/

>>> component

>>> 

>>> This is specified as a means of avoiding collisions [2] at the point

>>> of

>>> the

>>> XML namespace URI terminal, which can be a "slash" variant ending

>>> with

>>> "/"

>>> 

>>> Here's an expanded summary from the Naming Guidelines, using

>>> slightly improved pseudo-syntax for the variables vs. literals

>>> 

>>> NS URIs must be rooted at the "docs.oasis-open.org" Internet domain

>>> using one of the following two patterns containing the literal

>>> /ns/ path element, unless an alternative URI is approved by the TC

>>> Administration:

>>> 

>>> (1) http://docs.oasis-open.org/ns/<ShortName>/<Versioned-NS-String>

>>> OR

>>> (2) http://docs.oasis-open.org/<ShortName>/ns/<Versioned-NS-String>.

>>> 

>>> Where: <ShortName> is the approved short name for the TC or Member

>>> Section;

>>> <Versioned-NS-String> is a short string identifying a namespace 

>>> using

>>> a versioning subcomponent [and where a versioning subcomponent could

>>> be

>>> a string encoding a date, cardinal-number-identifier, etc]

>>> 

>>> But: TCs should avoid creating collision/confusion and semantic

>>> overloading at the point of a XML Namespace URI which could be

>>> mistaken for a regular directory URI, or vice versa; thus,

>>> for any Type 1 or Type 3 HTTP scheme namespace URI terminating

>>> in

>>> 

>>> a) ...<Versioned-NS-String>      /* OR */

>>> b) ...<Versioned-NS-String>/

>>> 

>>> no URIs should be created for information resources matching "*" in

>>> 

>>> http://docs.oasis-open.org/ns/<ShortName>/<Versioned-NS-String>/*

>>> http://docs.oasis-open.org/ns/<ShortName>/<Versioned-NS-String>/

>>> <OtherPa

>>> th>/*

>>> 

>>> Example: using an imaginary TC with <ShortName> 'ws-xx' and a

>>> <Versioned-NS-String> with value 'WS-XX-20080115', we could create

>>> an XML Namespace URI of these types (also with terminal '#'):

>>> 

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/

>>> http://docs.oasis-open.org/ws-xx/ns/WS-XX-20080115

>>> http://docs.oasis-open.org/ws-xx/ns/WS-XX-20080115/

>>> 

>>> but we will not create a (literal) file-system object

>>> (folder/directory) 'WS-XX-20080115' and we will therrefore

>>> also not install any information resources on the file

>>> system matching '*' based upon some imaginary directory

>>> 'WS-XX-20080115':

>>> 

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/*

>>> http://docs.oasis-open.org/ws-xx/ns/WS-XX-20080115/*

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/<OtherPath>/*

>>> http://docs.oasis-open.org/ws-xx/ns/WS-XX-20080115/<OtherPath>/*

>>> 

>>> The HTTP scheme XML namespace URI is put in a reserved path,

>>> and it may be used as a base URI for related properties, functions,

>>> messages, faults, dialects (etc) which merit identification using

>>> URI references, where these URIs identity non-information resources.

>>> 

>>> For example, a TC might define URIs based upon the NS URI

>>> 

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/

>>> 

>>> to identify/name faults, functions, etc:

>>> 

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/faultFoo

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/faultFaz

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/functionFizzle

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/propertyBar

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/messageBaz

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/messageBaz/

>>> Revoked

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/dialectSnark

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/signalBlort

>>> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/signalBlort/

>>> Blarney

>>> 

>> 

> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/signalBlort/Blarney/0

>>> 1

>>> 

>> 

> http://docs.oasis-open.org/ns/ws-xx/WS-XX-20080115/signalBlort/Blarney/0

>>> 2

>>> 

>>> In the current OASIS server implementation for XML namespace URI

>>> handling,

>>> requests to the server for a resource matching a NS URI or

>>> derived (function, fault) name will be handled as a URI rewrite

>>> (resolving) to the resource serving as the namespace document,

>>> viz., a

>>> textual document [3] which documents the XML Namespace URI (what

>>> groups owns is, what specifications declare or use it, what

>>> policies govern its versioning, etc).

>>> 

>>> Note: in the future, we may modify OASIS practice to use (or allow

>>> for)

>>> redirect of an HTTP scheme NS URI to the namespace document URI 

>>> (HTTP

>>> Status

>>> code 303 or other), as recommended in a W3C TAG Finding on

>>> "Associating Resources with Namespaces":

>>> 

>>> "We recommend that in all such cases server configurations

>>> should be changed, in line with [HTTPRANGE], to respond

>>> with a 303 redirection from the namespace URI to a related

>>> URI for the namespace document...."

>>> 

>>> Details: http://xml.coverpages.org/ni2008-06-26-a.html

>>>        http://www.w3.org/2001/tag/doc/nsDocuments/

>>> 

>>> Please feel free to contact me with any questions.

>>> 

>>> Cheers,

>>> 

>>> Robin Cover

>>> 

>>> =========== References:

>>> 

>>> [1]

>>> 

>> 

> http://docs.oasis-open.org/specGuidelines/namingGuidelines/resourceNamin

>>> gV08.html#NamespaceDesign

>>> 

>>> [2] note on avoiding collisions

>>> 

>>> 

>> 

> http://docs.oasis-open.org/specGuidelines/namingGuidelines/resourceNamin

>>> gCommentaryV08.html#uri-overloading

>>> 

>>> [3] HTTP scheme NS URIs must resolve under DNS+HTTP

>>> 

>>> 

>> 

> http://docs.oasis-open.org/specGuidelines/namingGuidelines/resourceNamin

>>> gV08.html#urisMustResolve

>>> 

>>> "HTTP scheme namespace URIs must resolve to some informative

>>> resource, ideally meeting the requirements for a (RDDL)

>>> namespace document; OASIS will supply a default namespace

>>> document if the TC designates/supplies no resource for resolution"

>>> 

>>> 

>>> 

>> 

> http://docs.oasis-open.org/specGuidelines/namingGuidelines/resourceNamin

>>> gCommentaryV08.html#resolution

>>> http://www.w3.org/TR/webarch/#namespace-document

>>> 

>>> --

>>> 

>>> Robin Cover

>>> OASIS, Director of Information Services

>>> Editor, Cover Pages and XML Daily Newslink

>>> Email: robin@oasis-open.org

>>> Staff bio: http://www.oasis-open.org/who/staff.php#cover

>>> Cover Pages: http://xml.coverpages.org/

>>> Newsletter: http://xml.coverpages.org/newsletterArchive.html

>>> Tel: +1 972-296-1783

>>> 

>>> 

>>> 

>>> 

>>> PLEASE NOTE:  If the above links do not work for you, your email

>>> application

>>> may be breaking the link into two pieces.  You may be able to copy

>>> and

>>> paste

>>> the entire link address into the address field of your web browser.

>>> 

>>> -OASIS Open Administration

>>> 

>>> ---------------------------------------------------------------------

>>> To unsubscribe from this mail list, you must leave the OASIS TC that

>>> generates this mail.  Follow this link to all your TCs in OASIS at:

>>> https://www.oasis-open.org/apps/org/workgroup/portal/

>>> my_workgroups.php

>>> 

>>> 

>>> The information contained in this message is privileged and intended

>>> only for the recipients named. If the reader is not a representative

>>> of the intended recipient, any review, dissemination or copying of

>>> this message or the information it contains is prohibited. If you

>>> have received this message in error, please immediately notify the

>>> sender, and delete the original message and attachment..

>> 

>> 

>> The information contained in this message is privileged and intended

>> only for the recipients named. If the reader is not a representative

>> of the intended recipient, any review, dissemination or copying of

>> this message or the information it contains is prohibited. If you

>> have received this message in error, please immediately notify the

>> sender, and delete the original message and attachment..

> 

> 

> The information contained in this message is privileged and intended 

> only for the recipients named. If the reader is not a representative 

> of the intended recipient, any review, dissemination or copying of 

> this message or the information it contains is prohibited. If you 

> have received this message in error, please immediately notify the 

> sender, and delete the original message and attachment..

 

 

The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachment..

 

 

The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.

 



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