From Toby.Considine@gmail.com Tue Jan 25 03:42:57 2011 Return-Path: X-Original-To: link-relations@core3.amsl.com Delivered-To: link-relations@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 515503A6A70 for ; Tue, 25 Jan 2011 03:42:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDA97W7YLrOm for ; Tue, 25 Jan 2011 03:42:52 -0800 (PST) Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 3E69D3A63C9 for ; Tue, 25 Jan 2011 03:42:52 -0800 (PST) Received: by gyd12 with SMTP id 12so1953243gyd.31 for ; Tue, 25 Jan 2011 03:45:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:reply-to:from:to:cc:subject:date :organization:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=63ZEsXf1Mj/7WLebfGQTsZ2vUq7uesXbL+5R684fuwU=; b=TTf+p9jbv4zJpQBVrKeKP+hE5BElXlRczyun6AAgAinUkuxHSVvdPKIgnfp0L2eA5D /8I8hti5TnMu+hGhCxiRBcerUaWzY1z093wi+NuIpDwOjHvxPwIptoGy/1C+yeYvyhxH nIFiFM2fqs/krOhwOHdWevuTtdSSulhulytqs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:reply-to:from:to:cc:subject:date:organization:message-id :mime-version:content-type:x-mailer:thread-index:content-language; b=IZuwtset2v4+Bz7tS9cS+7gVQ2S8K6cHDSQcdgRAwbXWlEL3hS/4JnHis4NuDpGJqJ 8SkZh6qBHQoHGlOb0/PHbZFK8njXdOawFmdlCTEn6e58GuuoMSqIadKbvprfTaq0lizu ZEKau7Lltx27KWZCbCR5NWW9R5yCsNMLW8wxU= Received: by 10.150.145.7 with SMTP id s7mr6198049ybd.126.1295955949030; Tue, 25 Jan 2011 03:45:49 -0800 (PST) Received: from Guacamole (user-0c2h58a.cable.mindspring.com [24.40.149.10]) by mx.google.com with ESMTPS id 50sm326473yhl.29.2011.01.25.03.45.46 (version=SSLv3 cipher=RC4-MD5); Tue, 25 Jan 2011 03:45:47 -0800 (PST) Sender: Toby Considine From: "Toby Considine" To: Date: Tue, 25 Jan 2011 06:45:40 -0500 Organization: TC9, Inc Message-ID: <033901cbbc85$6524bd90$2f6e38b0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_033A_01CBBC5B.7C4F9FF0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Acu8hV6kGtE1uUbWS06IxZZ/mxfTsw== Content-Language: en-us X-Mailman-Approved-At: Tue, 25 Jan 2011 04:33:26 -0800 Cc: wtcox@coxsoftwarearchitects.com Subject: [link-relations] NEW APP DATA - request for Advice - WS-Calendar X-BeenThere: link-relations@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Toby.Considine@gmail.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2011 11:45:52 -0000 This is a multipart message in MIME format. ------=_NextPart_000_033A_01CBBC5B.7C4F9FF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings This is *not yet* a request. Within the OASIS WS-Calendar TC, we have looked to several relations that could perhaps be developed using links (RFC5988). We have called these the "temporal relations". As it sits now, there four of the general format: [link] [relation] [duration] WS-Calendar generally uses semantics from RFC5545, and chains intervals (expressed as vtodo objects) together to create sequences. While sequences might be one after another, with no gap, they may not. The relations are [finishtostart] [fs] when this interval finishes, linked interval starts. [starttostart] [ss] when this interval starts, linked interval starts. [finishtofinish] [ff] linked interval may not finish until this interval finishes. [starttofinish] [sf] linked interval must finish before this starts. Each of these relations *may* be accompanied by a gap, expressed as an icalendar duration which modifies the close link described above. If I understand the specification properly, this means that I am requesting the above be the relation types, and that the normal format be: [finishtostart][target IRI][ gap] Each object already contains an identifier, which I think could be defined as the context IRI Does this give you sufficient information? tc _____ "It is difficult to get a man to understand something, when his salary depends upon his not understanding it" -- Upton Sinclair. _____ Toby Considine TC9, Inc OASIS Technical Advisory Board TC Chair: oBIX & WS-Calendar TC Editor: EMIX, EnergyInterop U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee Email: Toby.Considine@gmail.com Phone: (919)619-2104 http://www.tcnine.com/ blog: www.NewDaedalus.com ------=_NextPart_000_033A_01CBBC5B.7C4F9FF0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings

 

This is = *not yet* a request.

 

Within the = OASIS WS-Calendar TC, we have looked to several relations that could = perhaps be developed using links (RFC5988). We have called these the = “temporal relations”. As it sits now, there four of the = general format:

 

[link] = [relation] [duration]

 

WS-Calendar = generally uses semantics from RFC5545, and chains intervals (expressed = as vtodo objects) together to create sequences. While sequences might be = one after another, with no gap, they may not.

 

The = relations are

 

[finishtostart] [fs] when this interval finishes, = linked interval starts.

[starttostart] [ss] when this interval starts, linked = interval starts.

[finishtofinish] = [ff] linked interval  may not finish until this interval = finishes.

[starttofinish] [sf] linked = interval must finish before this starts.

 

Each of = these relations *may* be accompanied by a gap, expressed as an = icalendar duration which modifies the close link described = above.

 

If I understand the specification properly, this means = that I am requesting the above be the relation types, and that the = normal format be:

 

[finishtostart][target IRI][ gap]

 

Each object = already contains an identifier, which I think could be defined as the = context IRI

 

Does this give you sufficient = information?

 

tc

 

“It is difficult to get a man to understand = something, when his salary depends upon his not understanding it” = -- Upton Sinclair.

Toby Considine
TC9, = Inc

OASIS Technical Advisory = Board
TC Chair: oBIX & WS-Calendar

TC Editor: EMIX, EnergyInterop

U.S. = National Inst. of Standards and Tech. Smart Grid Architecture = Committee

  

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

http://www.tcnine.com/
blog: = www.NewDaedalus.com

 

 

------=_NextPart_000_033A_01CBBC5B.7C4F9FF0--