xr的软件适配是被放弃了吗

I referred to MbUnit once as "abandonware" only to be corrected (rightly so) by Andy Stopford (here's a listserv about the issue). In this case, it was not clear at a cursory glance if it was being "actively developed."  Here's some metrics that were provided by Jay Flowers that prove that MbUnit is very alive:

我指的是MbUnit 曾经是“放弃软件”，只能由安迪·斯托福德(Andy Stopford)纠正(这是正确的)(有关此问题的列表服务)。 在这种情况下，一目了然并不清楚是否正在“积极开发”它。 以下是Jay Flowers提供的一些指标，这些指标证明MbUnit非常活跃：

Google Groups:
MbUnit.Dev - 62 Members with 60 posts last month
MbUnit.User - 120 Members with 35 posts last month
8 Dev Leaders with rights to Subversion
Here is the Svn FishEye:
http://www.mertner.com/fisheye/browse/MbUnit
4 Devs committing changes in Aug
264 files changes/28 revisions in Aug

Google网上论坛： MbUnit.Dev-上个月有62个成员的60个帖子MbUnit.User-120个成员，上个月有35个帖子8位开发者领袖拥有颠覆权这是Svn FishEye： http://www.mertner.com/fisheye/browse/MbUnit 4个Dev在8月提交更改264个文件更改/ 8月的28个修订

Other folks have done the same thing to DasBlog that I did to MbUnit. Take a cursory glance at the DasBlog SF.NET Projects Page a few weeks back and you'd fine many unanswered questions. In both instances - DasBlog and MbUnit - the project owners needed to take into consideration the external perception by the community of the projects and tighten the screws a bit, all to avoid the label of "Abandonware."

其他人对DasBlog所做的与我对MbUnit所做的相同。 几周前粗略浏览一下DasBlog SF.NET项目页面，您会发现许多未解决的问题。 在这两种情况下(DasBlog和MbUnit)，项目所有者都需要考虑项目社区的外部看法并稍微拧紧螺丝，所有这些都避免使用“ Abandonware”的标签。

Another word invented by Roy Osherove was "frozeablilty" (or chance of being frozen/abandoned. Perhaps frozeabilitishipfulness is a better word?:

Roy Osherove发明的另一个词是“ frozeablilty ”(或被冻结/遗弃的机会。也许frozeabilitifulfulness是一个更好的词？：

MbUnit is also one of the topics that I continually have a dilemma about using. Since its not the de-facto standard out there, I always feel there's a chance of it being frozen in mid development, making all those who depend on it frozen along with it.

MbUnit也是我一直困扰使用的主题之一。 因为它不是实际的标准，所以我总是觉得它有可能在开发中被冻结，从而使所有依赖它的人都被冻结。

[Update: Andrew, one of the leads on mbUnit,  makes some good points on why he thinks this is far from happening - which is reassuring, and I'd like to hold out longer before making a final call on it's "frozeability".]

[更新：mbUnit的负责人之一安德鲁(Andrew)提出了一些很好的观点，说明了为什么他认为这还远远没有发生-这令人放心，我想在最终确定“可冻结性”之前坚持更长的时间。 ]

Now, we're picking on DasBlog and MbUnit here, but both actively developed projects that aren't abandoned. But let's talk about the real issue. Is software that has been abandoned bad? Is it un-usable? Should we only use software that is actively developed?

现在，我们在这里选择DasBlog和MbUnit，但它们都积极开发了未被放弃的项目。 但是，让我们谈谈真正的问题。 被遗弃的软件不好吗？ 它不可用吗？ 我们应该只使用主动开发的软件吗？

Abandonware Example - A .NET Implementation of Schematron

Abandonware示例-Schematron的.NET实现

We recently needed to do some data import work, and we were using XML as the source format and XSD to describe the constraints of the validity of the data. Xml Schema isn't well suited for complex data with conditional interrelationships.

我们最近需要做一些数据导入工作，并且我们使用XML作为源格式，并使用XSD来描述数据有效性的约束。 Xml Schema不适用于具有条件相互关系的复杂数据。

For example, if I have a Payment in Xml Schema, it might have a FromAccountID and an optional DateCompleted (and many other things):

例如，如果我在Xml模式中有一个Payment，它可能有FromAccountID和一个可选的DateCompleted(以及许多其他东西)：

<xs:complexType name="Payment">
  <xs:sequence>
   <xs:element name="FromAccountID">
    <xs:simpleType>
     <xs:restriction base="xs:string">
      <xs:maxLength value="25"/>
      <xs:whiteSpace value="preserve"/>
     </xs:restriction>
    </xs:simpleType>
   </xs:element>
   <xs:element name="DateCompleted" minOccurs="0">
    <xs:simpleType>
     <xs:restriction base="xs:date"/>
    </xs:simpleType>
   </xs:element>
...

<xs：complexType name =“付款”> <xs：sequence> <xs：element name =“ FromAccountID”> <xs：simpleType> <xs：restriction base =“ xs：string”> <xs：maxLength value =“ 25” /> <xs：whiteSpace value =“ preserve” /> </ xs：restriction> </ xs：simpleType> </ xs：element> <xs：element name =“ DateCompleted” minOccurs =“ 0”> <xs：simpleType> <xs：restriction base =“ xs：date” /> </ xs：simpleType> </ xs：element> ...

But, there's a business rule that indicates that if FromAccountID is "PAID" then there must be a DateCompleted. This kind of condition isn't expressable in XSD. I started looking for other solutions like RelaxNG or Schematron.

但是，有一条业务规则表明，如果FromAccountID为“ PAID”，则必须有一个DateCompleted。 这种条件在XSD中无法表达。 我开始寻找其他解决方案，例如RelaxNG或Schematron 。

Schematron is an interesting spec, but the nutshell explanation is that you can augment XSD with additional assertions using XPath. You can also (with some implementations) include Schematron patterns inside of existing Xml Schemas using the xs:annotation element. Schematron the spec is being actively talked about (article at IBM from this July), commented on by Microsoft PMs (quote from July) but there's a reference implementation using XSLT but it hasn't been looked at since 2001. Some bloggers have commented on the uneven state of Schematron.

Schematron是一个有趣的规范，但是简而言之，就是您可以使用XPath通过其他断言来扩展XSD。 您还可以(使用某些实现)使用xs：annotation元素将Schematron模式包含在现有Xml Schema内。 规范讨论者正在积极讨论Schematron(今年7月在IBM上发表的文章)，受到微软PMs的评论(从7月引述)，但是有一个使用XSLT的参考实现，但自2001年以来就没有讨论过。 一些博主评论了Schematron的不平衡状态。

I can extend this XSD with Schematron like this:

我可以使用Schematron扩展此XSD，如下所示：

<xs:complexType name="Payment">  <xs:annotation>
   <xs:appinfo>
    <pattern name="Payment Rules" xmlns="http://www.ascc.net/xml/schematron">
     <rule context="Payment">
      <assert test="(FromAccountID = 'PAID' and DateCompleted) or 
          (FromAccountID != 'PAID')">
             PAID Payments must have a Date Completed
      </assert>
     </rule>
    </pattern>
   </xs:appinfo>
  </xs:annotation>...

<xs：complexType name =“付款”> <xs：annotation> <xs：appinfo> <pattern name =“付款规则” xmlns =“ http://www.ascc.net/xml/schematron ”> <rule context =“ Payment”> <assert test =“(FromAccountID ='PAID'和DateCompleted)或(FromAccountID！='PAID')“> 付费付款必须有完成日期</ assert> </ rule> </ pattern> </ xs：appinfo> </ xs：annotation> ...

And this simple example gives me the semantics I need and I get output like this from a console test application that are exactly what I need:

这个简单的示例为我提供了我需要的语义，并且从控制台测试应用程序中获得了我真正需要的输出：

Results from Schematron validation
    From pattern "Payment Rules"
        Assert fails: PAID Payments must have a Date Completed
        At: /FI[1]/Relationship[1]/Payee[1]/Payment[2]
            <Payment>...</Payment>
            (Line: 73, Column: 5)

Schematron验证的结果从模式“付款规则” 断言失败：PAID付款必须具有完成日期于：/ FI [1] /关系[1] /收款人[1] /付款[2] <付款> ... </付款> (第73行，第5列)

However, doubts about Schematron persist. Uche Ogbuji says:

但是，对Schematron的怀疑仍然存在。 Uche Ogbuji说：

"It has been a sketchy time for Schematron fans. Rick Jelliffe, the father of Schematron has had pressing matters that have prevented him from putting much work into Schematron for a while. Many questions still remain about the technology specification, and alas, there appears to be no place to keep discussions going on these and other matters (the mailing list on SourceForge appears to be defunct, with even the archives giving a 404. Here are some notes on recent Schematron developments I've come across."

“对于Schematron迷来说，这是一个粗略的时刻。Schematron的父亲Rick Jelliffe遇到了紧迫的问题，这使他暂时无法在Schematron中投入大量工作。关于技术规范，仍然存在许多问题，可惜，似乎在任何地方都不能继续进行讨论(SourceForge上的邮件列表似乎已失效，甚至归档中也提供了404。这是我所遇到的Schematron最新开发的一些说明。”

However, it is moving towards being an ISO spec (or may already be?) and there's active talk going on at the SchematronLoveIn mailing list.

但是，它正朝着成为ISO规范(或可能已经成为？)的方向发展，SchematronLoveIn邮件列表中正在进行积极的讨论。

There's also a great (but oldish) article on Introducing the Schematron here. Looks like it might be a fine idea. The XSLT implementation worked group, but I also noticed a native C# .NET implementation at SourceForge. This implementation has the very much added benefit of giving me not only an event when a Schematron assertion fails, but also the line number and additional context. However, it's not been touched since 2002.

关于Schematron的介绍，这里也有一篇很棒的文章(但很古老)。 看起来可能是个好主意。 XSLT实现工作组，但我还注意到SourceForge上的本机C＃.NET实现。 此实现具有非常多的附加好处，不仅为我提供了Schematron断言失败时的事件，还为我提供了行号和其他上下文。 但是，自2002年以来未曾触及过。

Is that a bad thing?

那是一件坏事？

I asked the author of the .NET implementation of Schematron, Daniel Cazzulino, what he thought and he said:

我问了Schematron的.NET实现的作者Daniel Cazzulino的想法，他说：

"Mmm... schematron is mostly abandoned as the new compiled XSLT in .NET 2.0 makes the need for an "xpath native" implementation pretty much useless. If you use the reference meta-stylesheet and provide a nice .NET API over it (alongside better results reporting, such as an object model that can also be serialized into XML and/or XSLT'ed into HTML reports), you should be OK. And you would be in a better position feature-wise, as I never got to complete support for diagnostics elements, etc., which is readily implemented in the meta-stylesheet."

“嗯……schematron几乎被放弃了，因为.NET 2.0中新编译的XSLT使得对“ xpath native”实现的需求几乎没有用。如果您使用引用元样式表并为其提供了一个不错的.NET API(除了更好的结果报告(例如也可以序列化为XML和/或XSLT's到HTML报告的对象模型)之外，您应该还可以。而且，在功能方面，您将处于更好的位置，因为我从没这么做过对诊断元素等的完整支持，可以在meta样式表中轻松实现。”

To translate Daniel's techno-speak into regular-guy-speak he's saying

要将丹尼尔的讲技术的话翻译成常说的话

"Ya, that sucks. You can write a wrapper around this other thing yourself, and that'd be a good idea in the long run, but ya, that sucks."

“是的，这很糟糕。您可以自己为另一件事写一个包装器，从长远来看，这是个好主意，但是，是的，这很糟糕。”

However, this project isn't using .NET 2.0 (client requirements) and the existing .NET Schematron stuff not only works, but it works great. It's many times faster than the XSLT implementation and did I mention, it's open source. That means, I have the source.

但是，该项目未使用.NET 2.0(客户端要求)，并且现有的.NET Schematron内容不仅有效，而且效果很好。 它比XSLT实现快许多倍，而且我提到过，它是开源的。 就是说，我有资料来源。

It's not like the Open Source Fairy is going to delete the software (and source) off my hard drive if a project disappears.

如果项目消失了，开源妖精将不会从硬盘驱动器上删除软件(和源代码)。

To quote Patrick Cauldwell, "Sure, we are assuming the burden of maintenance when we use it, but we're doing that anyway as there's no assurance that someone in the OS community would care about a bug we found."

用帕特里克·考德威尔( Patrick Cauldwell)的话说：“当然，我们在使用它时会承担维护的重担，但无论如何我们都会这样做，因为无法保证OS社区中的某人会在意我们发现的错误。”

This is exemplified by Stuart's recent spitting into the wind with a catastrophic but ignored Subversion case-sensitivity bug.

斯图尔特(Stuart)最近因灾难性的但忽略了Subversion区分大小写的错误而随风而去就是例证。

Moral: What you care about, often ain't what the other guy cares about.

道德：您所关心的，通常不是另一个人所关心的。

Conclusion: The Schematron .NET implementation is total abandonware and I'm going to use it anyway. Since when did 3 year old software become abandoned. I haven't been in my backyard in 3 years, but if I catch you camping there I'll ask you to leave.

结论： Schematron .NET实现是完全的废弃软件，无论如何我都将使用它。 从3岁起就放弃了软件。 我已经三年没有来过我的后院了，但是如果我在那儿露营，我会请你离开。

(If you'd like to receive ComputerZen.com via email, you can subscribe to this blog as a newsletter for free. Subscribe to Scott Hanselman - ComputerZen.com by Email)

(如果您想通过电子邮件接收ComputerZen.com，则可以免费订阅此博客作为时事通讯。通过电子邮件订阅Scott Hanselman-ComputerZen.com )

翻译自: https://www.hanselman.com/blog/what-is-abandonware

xr的软件适配是被放弃了吗